The release four years ago of the Systems Modeling Language (SysML) and this year’s Unified Profile (UP) for the Department of Defense Architecture Framework (DoDAF) and the British Ministry of Defense Architectural Framework (MoDAF) — referred to altogether as UPDM — as open specifications managed by the Object Management Group (OMG), provides new opportunities for expressing systems and enterprise models using formal grammar. The presentation started by discussing modeling in the context of these specifications and then looked at SysML semantics. This was followed by a review of enterprise architectures and their roles. With this background, the discussion turned to UPDM and its application of SysML to provide consistent methods for realizing enterprise architectures. Four models were examined highlighting various issues encountered in the application of these specifications. SysML and UPDM can best be described as emerging technologies and so the presentation concluded with thoughts regarding possible impediments future practitioners may want to consider before proceeding.
BACKGROUND: Four projects provided the case studies used in the presentation including 1) a UPDM model of a flight readiness system supporting mission development from requirements through liftoff. Such a system involves large amounts of technical information and a wide variety of stakeholders with diverse interests and a necessity for collaboration at many decision points. It is hoped that such a model will provide stakeholders with a common understanding of all the issues and a more efficient way of agreeing to the creation of an effective system. 2) A mission operations flight product process reengineering model that includes data on over 500 processes, 700 products, and 3,060 exchanges. The objective is to understand, simulate, and optimize the use of resources during a mission. 3) A UPDM model that incorporates the attributes and relationships of some 300 Ares documents comprising the project’s development artifacts. The model in its current form provides the basis for exploring Ares behaviors and modeling the contents of the documents. Such fidelity might in the future lead to more efficient and cost-effective ways of organizing the project. 4) The Fire Satellite (FireSat) challenge team, sponsored by the International Council on Systems Engineering (INCOSE), is producing a SysML model of a satellite. The purpose is to both better understand the problems with SysML modeling and to potentially produce a reusable model, making it easier for others to create missions.
NASA PROGRAM FUNDING: Constellation Information Systems Office
Contact: Ted Kahn, Ian Sturken