Purpose of allocation in SysML (connecting logical → physical, function → structure)
Types of allocation:
Behavioral allocations (activities/functions to blocks)
Requirement allocations (requirements to design elements)
Structural allocations (interfaces to components)
How allocation supports traceability and system consistency
Hands-On Exercise:
Extend the Day 3 mini-project by allocating:
Use cases to blocks
Requirements to structure
Activities to components
Purpose of tables and matrices: model navigation, traceability visualization
Common table/matrix usages:
Requirement-to-Block table
Use Case-to-Requirement matrix
Function-to-Component allocation matrix
How different tools (e.g., Cameo, Rhapsody) display tables/matrices
Hands-On Exercise:
Generate a Requirement vs Block matrix from the mini-project
Create a Use Case vs Function allocation table
Why stereotypes and profiles? (Customization of SysML)
Defining stereotypes (tags, properties, icons)
Applying stereotypes to blocks and requirements
Difference between a profile and a package
Keeping it basic, without plugins
Hands-On Exercise:
Create a custom stereotype for “Safety-Critical Requirement”
Apply it to selected requirements in the mini-project
Create a profile package to group stereotypes
Combine allocations, tables, and stereotypes into the existing mini-project
Review:
Requirements → allocated to Blocks
Functions → allocated to Components
Safety-critical tagged with stereotypes
Verified through table/matrix views
Group Work Exercise:
Each team prepares an allocation matrix + stereotype-tagged model
Teams present how they customized their SysML model