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

It is appropriate to use the MARTE profile to model this system with SysML because the control unit must order the submarine’s operations in real time, which the MARTE profile makes it possible to model in SysML. MARTE is a UML profile that provides concepts and annotations for modeling and analyzing real-time and embedded systems. It supports modeling time-related properties and constraints, such as deadlines, periods, durations, clocks, etc., as well as resource-related properties and constraints, such as memory, CPU, power, etc. By using MARTE, one can capture the real-time requirements and behavior of the system and perform schedulability and performance analysis. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/MARTE/1.2/About-MARTE/

The most significant deficiency impeding widespread use of SysML (without MARTE) in the real-time and embedded domain is a quantifiable notion of time and resources. SysML does not provide a standard way to model time-related properties or constraints, such as deadlines, periods, durations, clocks, etc., nor does it provide a standard way to model resource-related properties or constraints, such as memory, CPU, power, etc. These aspects are essential for real-time and embedded systems design and analysis. MARTE addresses this deficiency by providing concepts and annotations for modeling time and resources in a precise and quantitative way. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/MARTE/1.2/About-MARTE/

 A systems engineering methodology is a collection of related processes, methods, and tools that support the discipline of systems engineering in a specific context. A systems engineering methodology should be aligned with the company’s business processes and goals, and should be updated and improved as needed to reflect changes in the environment, technology, customer needs, etc. By noting if the systems engineering methodology still works with the company’s business processes, and making modifications where needed, the director canresolve the conflict between the requirements analysts and the system engineering design team by ensuring that they follow a consistent and effective approach to systems engineering

 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

OCL is the most suitable and compatible language for placing formal pre-conditions and post-conditions on an activity diagram. OCL is part of the UML standard and can be integrated withSysML without any conflicts or inconsistencies. OCL can express complex logical expressions that can check the state of the system before and after an activity is executed. BPMN is a business process modeling language that is not compatible with SysML. English is a natural language that may not be precise or unambiguous enough for formal specifications. OWL is a web ontology language that is not designed for modeling activities or constraints. VSL is a value specification language that can only express simple values and expressions. XMI and XML are markup languages that are used for exchanging models between tools, not for specifying constraints on models. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.3

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

The most important factor that the engineer should consider in selecting a system development methodology for an unprecedented system with unclear or incomplete user and system requirements is the ability to rapidly explore required system functionality. The ability to rapidly explore required system functionality means that the system development methodology can support the elicitation, analysis, validation and verification of the user and system requirements through various techniques, such as use cases, scenarios, prototypes, simulations and tests. The ability to rapidly explore required system functionality can help reduce the uncertainty and ambiguity of the requirements and increase the confidence and satisfaction of the stakeholders. The ability to rapidly prototype the user interface is a less important factor that may not be relevant or applicable to all systems or projects. Access to a large model library and legacy code base is a less important factor that may not be available or suitable for an unprecedented system. A robust ontology for characterizing complex systems is a less important factor that may not be necessary or sufficient for defining the requirements. Direct support for quickly characterizing and prototyping services is a less important factor that may not be relevant or applicable to all systems or projects. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.5

A model library is a package that contains reusable model elements that can be imported into other models. A model library can add common concepts to a SysML model, such as units, quantities, value types, etc. These concepts can be used to define properties and parameters of blocks and constraints in a consistent and standardized way. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/SysML/1.6/PDF

A measure of model quality is a metric that evaluates how well a model satisfies some desired characteristics, such as correctness, completeness, consistency, clarity, etc. The number of actions and activities with no incoming object or control flows is a measure of model quality that indicates how well the model captures the dependencies and sequences of events in the system. A high number of such actions and activities may imply that the model is incomplete or inconsistent, and may lead to errors or ambiguities in the system behavior.

The element that would be used to depict a model library on a diagram is a package with the stereotype <> applied to it. This stereotype indicates that the package contains reusable model elements that can be imported into other models. Option C shows a package with this stereotype. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/SysML/1.6/PDF