Abstract
The Systems Engineering discipline needs a common Systems Engineering Modeling Language (SEML). On way to create an SEML is to start with the Unified Modeling Language (UML), created by Rational Software Inc. and originally intended for software. Some requirements of an SEML are analyzed together with the UML. The result is that a subset of the UML, primarily the Component diagram, can be combined with a pseudo code subset of the programming language Ada 95 to satisfy the requirements stated. Specially requirements concerning management of system-level missions and abilities combined with requirements on formality and understandability causes concern with the unmodified UML, which is why the UML needs to be both reduced and extended. The Component diagram supports architectural descriptions with system components ordered, according to dependency, with the system's missions as top components. The result is an SEML, compatible with the UML, readily understandable for analyzers and end users, and sufficiently formal for automated consistency checks. © 2000 John Wiley & Sons, Inc. Syst Eng 3: 212–224, 2000
Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
