Defining a Model's Purpose

Moving to Model Based System Engineering brings with it a number of challenges and traps for teams who are more accustomed to working with document-centric methods. Probably the commonest trap is to start modeling without having a clear understanding or definition of the purpose of the models.

In comparison with document-centric modeling approaches, it is more difficult to define the purpose of a model than it is to define the purpose of a suite of documents. The model is orders of magnitude more useful and effective than a document and can be used to perform work that is unimaginable with a document-based system. Some of the advantages of the model based approach are:

• Consistency checks can be easily applied
• Alternative views can be readily created and kept consistent
• If documentation is required it can be generated automatically
• Models are interlocking and consistent
• Change impact can be visualized and automated
• Models can be kept compliant with an underpinning metamodel
• Models can be versioned and baselined
• Requirements traceability can be easily managed
• Models can be easily manipulated and changed
• The model can be used to generate code and standards
• Models can be simulated producing rich visualizations
• Models can be transformed from one level of abstraction to another
• Parts of the model can be easily reused creating efficiency

This diagram shows how traceability can be visualized and managed in the tool, allowing you to view the way that parts of the models interlock and how elements form a graph of connections, helping you to describe and comprehend your model.

Enterprise Architect harnesses the power of the SysML, along with a large set of tools built with System Engineering Managers, Systems Engineers and other stakeholders in mind, providing simple but effective ways to take advantage of the Model-Based Systems Engineering approach.

There are other profound benefits that can be achieved by moving to a model-based approach, including ensuring that projects and programs of work are performed with rigor, productivity and efficiency using a tool that encourages excellence and collaboration. For more information see the Why Enterprise Architect? Help topic.