OMG-OCSMP-MBA400 OMG-Certified Systems Modeling Professional - Model Builder - Advanced Questions and Answers

 XMI is a standard format for exchanging metadata information via XML, such as UML models. XMI supports a mechanism for producing a special XMI file that contains only the differences between two versions of a model, called a difference model. This file can be imported into another tool to apply the changes to the original model. This approach is more efficient and reliable than exporting and importing the entire model or parts of it

The best way to ensure that a shared model has consistently-represented elements and diagrams is to use modeling conventions and standards. Modeling conventions and standards are rules and guidelines that define how the model elements and diagrams should be named, defined, structured, formatted and documented. Modeling conventions and standards can help improve the clarity, consistency and quality of the model and facilitate the communication and collaboration among the modelers and stakeholders. Implementation of standard libraries is a good way to ensure that a shared model has reusable and interoperable elements and diagrams, but it may not ensure their consistent representation. Packages that map one-for-one to components is a good way to ensure that a shared model has modular and traceableelements and diagrams, but it may not ensure their consistent representation. Domain stereotypes maintained in a configuration control system is a good way to ensure that a shared model has customized and controlled elements and diagrams, but it may not ensure their consistent representation. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.1

OCL is a formal language that can be used to specify constraints on the elements and relationships of a model. OCL can access the properties and operations of the model elements and check their values and states. OCL is not intended to be transformed into code or to express any imaginable constraint. OCL may not be easily understood by engineers who are not familiar with its syntax and semantics. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.3.1

This aspect of a MBSE-based engineering project falls outside of the scope of AP233 because AP233 does not cover diagrams. AP233 (Application Protocol 233) is a standard that defines an information model for systems engineering. It specifies the concepts and relationships for representing systems engineering data, such as requirements, functions, properties, etc. AP233 does not define any notation or presentation for diagrams, such as SysML diagrams. AP233 only defines the serialization and deserialization of systems engineering data using XMI (XML Metadata Interchange) format. Therefore, AP233 does not address how to exchange diagrams between tools or how to visualize diagrams in different tools. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/AP233/About-AP233/

The SysML diagram type that is a modification of the UML Class diagram is the Block Definition Diagram (BDD). A BDD shows the definition of blocks in terms of their features, such as properties, operations, ports, etc. It is similar to a UML Class diagram, but it adds some features specific to SysML, such as value types, units, flow properties, etc. A block is an extension of the UML Class metaclass that can be used to model any system component with structure and behavior. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://sysml.org/tutorials/sysml-diagram-tutorial/

Stereotypes should be grouped in profiles to facilitate re-use in later projects. A profile is a mechanism for extending UML or SysML with additional modeling elements that are not part of the standard language. A profile defines stereotypes, which are extensions of existing metaclasses. A profile can be applied to a model to make the stereotypes available for use. Bygrouping stereotypes in profiles, they can be easily reused in different models or projects. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.ibm.com/docs/SSB2MU_8.2.0/com.ibm.rhp.sysml.doc/topics/rhp_c_dm_sysml_profile_features.html

 A methodology is a set of principles, methods and practices that guide the execution of a project or activity. A systems engineering project always involves some kind of methodology, even if it is not explicitly defined or documented. Working spontaneously or randomly is also a form of methodology, although it may not be very effective or efficient. A systems engineering project cannot be conducted without applying any methodology at all. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.5

SysML is a general-purpose modeling language for systems engineering that can support various systems engineering methodologies. The stereotype and profile mechanisms are features of SysML that enable customizing and extending the language for a specific domain or purpose. By using stereotypes and profiles, SysML can be adapted to fit different methodologies and conventions without changing the core language semantics

According to the Survey of MBSE Methodologies 1, a methodology is defined as a collection of related processes, methods, and tools. A process is a sequence of steps or activities that transform inputs into outputs. A method is a technique or procedure for performing a specific task. A tool is an instrument or device that supports or automates a process or method. A methodology integrates these elements to support a specific domain or purpose.

Working in UPDM compliance level 1 allows users to bring SysML elements into the architecture to enhance the hand-off between Systems of Systems and Systems. Compliance level 1 is based on UML and SysML concepts and provides integration with system modeling using SysML. Users can use SysML elements, such as blocks, ports, connectors, parametrics, etc., to model system components and their interactions in more detail and precision than using UML elements alone. This can facilitate the transition from architecture modeling to system design and analysis. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.ibm.com/docs/bg/rhapsody/8.3.1?topic=function-designing-updm-profiles