Revision as of 03:01, 15 June 2006 edit Mjchonoles (talk \| contribs) 730 edits →A tool to connect mechanical, electrical, and software sub-systems ← Previous edit		Revision as of 16:42, 15 June 2006 edit undo Allan McInnes (talk \| contribs) Extended confirmed users, Pending changes reviewers 4,932 edits →A tool to connect mechanical, electrical, and software sub-systems: certainly an innovation over UML, not obviously an innovation over things like IDEF Next edit →
Line 4: SysML is notable for the wide range of systems concepts it can model. In an automotive application, for example, the language can be used to specify mechanical objectives and constraints such as maximum acceleration, [[curb weight]], [[air conditioning]] performance, and interior cabin [[acoustical engineering\|noise management]]. It can specify electrical parameters ranging from the [[FM radio]] [[tuning sensitivty]] to the [[real-time]] response of the [[antilock brake\|anti-lock braking]] control electronics. It can specify and model the [[embedded software]] used to control the on-board automotive computers. Finally, it can model the factories used to build the car, as well as the interfaces between the organizations that work in the factory. A notable innovation of SysML (over ~~other standardized [[modeling languages]] such as~~the [[Unified Modeling Language\|UML]]) is support for [[requirements modeling]]. During the design process, designers and users of specific sub-systems can communicate the design criteria using several alternative design formats including diagrams, tables, and tree structures. The requirements provide a checkable interface and documentation of the evolution of the system design over time. SysML does not replace the simulation tools used to model specific subsystems, but rather provides the "glue" to model the interaction between subsystems.

Systems modeling language: Difference between revisions