SysML is a UML profile, comes with its inherent complexity- need to tailor it to match one modeling process. We retained a very naïve one, limited to SysML-only:
• Requirement diagram
• Use cases
• Block diagrams
• State machines
• Parametric diagrams
• This constrains the semantics fuzziness of SysML to a tractable subset and prepare for the transition to AADLv2
Requirement capture-provide a tree-like structures, with hierarchy and clustering of all requirements:
• Modeling assumptions: define perimeter of the model
• Problem Analysis (à-la UML): define use cases
SysML:
• Architectural Design (à-la UML): define the static architecture
• Validation: mostly functional at this level
• Architecture refinement: refine the static architecture into runtime architecture
• Architecture mapping: map blocks to hardware/software
• Validation: refine all computed metrics
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
File | MIME type | Size (KB) | Language | Download | |
---|---|---|---|---|---|
SysML and AADL, patterns for Integrated Use.pdf | application/pdf | 931.98 KB | English | DOWNLOAD! |