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

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

The forward temporal order of these development stages is based on the typical sequence of activities in a system engineering process. Needs analysis is the first stage, where the problem and the stakeholder needs are defined. System design is the second stage, where the system architecture and requirements are developed. Trade study is the third stage, where alternative solutions are evaluated and compared based on various criteria. System acceptance is the final stage, where the system is verified, validated, and delivered to the customer.

 Coupling is a measure of how much a system element depends on other system elements. High coupling means that a change in one element affects many other elements, which makes the system harder to understand, maintain and reuse. Low coupling means that the system elements are more independent and modular, which improves the model quality. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.1.2.2

One of the most common reasons to utilize a SysML-Modelica integration is to solve and analyze system dynamics models. Modelica is a language for modeling complex physical systems based on equations and components. SysML is a language for modeling complex systems based on diagrams and textual notations. By integrating SysML and Modelica, system dynamics models can be defined in SysML using parametric diagrams and constraint blocks, and then solved and analyzed using Modelica tools and solvers. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://modelica.org/publications/newsletters/2011-1/index_html#sysml-modelica-integration

The OMG specifications that UPDM uses at L1 are UML and SysML. L1 is the level of abstraction that defines the core concepts of UPDM without any implementation details. It is based on a Domain Metamodel that captures the common elements of DoDAF and MODAF. The Domain Metamodel is mapped to UML and SysML concepts using a Platform Independent Model (PIM). UML and SysML provide the basic metaclasses and diagrams that UPDM uses to represent architectures. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/updm/

Views and viewpoints are used to show the aspects of a model that relate to different stakeholders. A view is a representation of a subset of a model that addresses a set of stakeholder concerns. A viewpoint is a specification of a perspective on a model that defines how a view should be constructed and used. By using views and viewpoints, different aspects of a model can be presented in a way that is relevant and understandable for different stakeholders. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://docs.nomagic.com/display/SYSMLP184/Views+and+Viewpoints+Diagram

A common technique for supporting the automated generation of development artifacts from a SysML model is to apply stereotypes to model elements to add the metainformation required for the generation process. Stereotypes can define tagged values that specify additional information about model elements, such as document templates, formatting options, traceability links, etc. These tagged values can be used by model transformation tools or scripts to generate artifacts from the model. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://docs.nomagic.com/display/SYSMLP190/Libraries+and+profiles

The most important aspect of system development methodologies that the engineer is likely to discuss with the director of field support is how the system model can be used to facilitate change proposals, support plans, and training in the operational environment. The system model can provide a consistent and comprehensive view of the system’s structure, behavior and performance throughout its lifecycle, and can help identify and evaluate potential changes, improvements or issues in the field. The system model can also help document and communicate the support requirements, procedures and resources for the system’s operation and maintenance. The system model can also help design and deliver effective training programs for the system’s users and operators. How field support operations can be modeled using MBSE methods, how software design patterns can be used to suggest Pre Planned Product Improvement (P3I) opportunities, and how operational evaluation (OPEVAL) plans can be developed and cross-checked in a system modeling environment are less important aspects of system development methodologies that may not be relevant or applicable to the director of field support’s concerns. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.5

OCL stands for Object Constraint Language, which is a standard language for expressing constraints on UML and SysML models. Constraints are used to specify additional rules or conditions that are not directly captured by the modeling elements or their relationships. OCL can be used to define constraints on stereotypes, their properties, or their relationships in a profile. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/OCL/About-OCL/

To prevent any use of an unstereotyped block, the supervisor must mark the extending stereotype with the {strict} keyword. This keyword indicates that only elements with this stereotype can be created as instances of the extended metaclass. In this case, only blocks with the stereotype <> can be created as instances of Block. 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