On principles for model‐based systems engineering

This article addresses the problem of consolidating technical descriptions of how a system is built with operational descriptions of the missions the system shall complete (how the system is to be used). It also discusses how a central model constituted from design objects with requirements, test cases, problems and documents as attributes, to these design objects, can support modern principles for “incremental acquisition” and “incremental development.” Modeling principles, based on entity–relationship diagrams and the UML (Unified Modeling Language) component diagram, combined with pseudo code behavioral descriptions, are described as means to build the “central model.” After a “central model” for systems engineering is established, it is shown how the model can be extended into a “Common Project Model,” being common in two ways: common for “real implementations” and simulators required for the system; common for all concerned stakeholders such as acquirers and contractors. Application of the “Common Project Modeling” principle, with computer‐stored models, holds promises for increased system quality and for more efficient systems engineering. © 2000 John Wiley & Sons, Inc. Syst Eng 3: 38–49, 2000