Systems modeling language: Difference between revisions

Revision as of 23:32, 7 July 2006

Revision as of 23:35, 7 July 2006

Line 7:

* SysML model management constructs support models, views, and viewpoints. These constructs extend UML's capabilities and are architecturally aligned with IEEE-Std-1471-2000 (IEEE Recommended Practice for Architectural Description of Software Intensive Systems).

SysML reuses seven of UML 2.0's thirteen diagrams, and adds two diagrams (Requirements and Parametric diagrams) and Allocation Tables, which arecan be dynamically derived from itsSysML diagrams. A table which compares SysML and UML 2.0 diagrams is available in the [http://www.sysmlforum.com/faq.htm SysML FAQ].

The advantages of SysML over UML for systems engineering become more obvious if you consider a concrete example, such as modeling an automotive system. With SysML you can use Requirement diagrams to efficiently capture functional, performance and interface requirements, whereas with UML you are subject to the limitations of Use Case diagrams to define high-level functional requirements. Likewise, with SysML you can use Parametric diagrams to precisely define performance and mechanical constraints such as maximum acceleration, [[curb weight]], [[air conditioning]] capacity, and interior cabin [[acoustical engineering|noise management]]. UML provides no straightforward mechanism to capture this essential performance and mechanical information.

As for the rest of the automotive system, SysML enhanced Activity and State Machine diagrams can be used to specify the [[embedded software]] control logic for the on-board automotive computers. Other SysML structural and behavioral diagrams can be used to model factories that build the automobiles, as well as the interfaces between the organizations that work in the factories.