Free Practice Questions for OMG OMG-OCSMP-MBA400 Exam

Tagged values can be defined only as attributes of stereotypes. A tagged value is an extension of a model element with additional information that is not part of its standard properties. A tagged value is defined by an attribute of a stereotype that is applied to the model element. The attribute specifies the name and type of the tagged value. 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

 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

 In a scenario-based development approach, use case diagram could best be used to describe the scenarios. A use case diagram shows how actors interact with use cases in different scenarios or situations. A use case diagram can capture the functional requirements and goals of a system or part from different stakeholder perspectives. A use case diagram can also show how use cases are related to each other by generalization, inclusion or extension relationships. A state diagram shows how an object changes its state in response to events or stimuli. A statediagram is not suitable for describing scenarios that involve multiple actors or use cases. An activity diagram shows how actions are performed in a sequence or in parallel by objects or flows. An activity diagram is not suitable for describing scenarios that involve different situations or alternatives. A requirements diagram shows how requirements are specified, derived, satisfied or verified by model elements. A requirements diagram is not suitable for describing scenarios that involve interactions or behaviors. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.2

MOF stands for Meta-Object Facility, which is a standard for defining metamodels. Metamodels are models of modeling constructs, such as classes, attributes, associations, etc. SysML stands for Systems Modeling Language, which is a standard for modeling complex systems using diagrams and textual notations. SysML models represent real world entities and processes, such as components, behaviors, requirements, etc. The key distinction between SysML modeling and MOF modeling is that SysML models are instances of a metamodel defined by MOF. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/mof/ https://www.omg.org/sysml/

OCL is important to the understanding of both the UML and SysML specifications because it is used to define the semantics and constraints of the modeling elements and relationships in both languages. OCL is part of the UML standard and is adopted by SysML as a complementary language. OCL can also be used to specify queries, expressions and operations on models. OCL is not directly related to a typical high-level domain model, tool-generated XMI for a SysML model, or software developers’ modifications to a SysML model. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.3

The refine relationship is likely to be most heavily used during requirements analysis because it is used to indicate that a model element provides more details or information about a requirement. The refine relationship can be used to link requirements to other requirements, use cases, activities, blocks or any other model elements that can help clarify or elaborate the requirements. The refine relationship can also be used to decompose a requirement into sub-requirements or to show how a requirement is derived from another requirement. The copy relationship is used to indicate that a requirement is identical to another requirement. The satisfy relationship is used to indicate that a design element fulfills a requirement. The verify relationship is used to indicate that a test case or procedure confirms that a design element satisfies a requirement. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.2

The diagram fragment that correctly expresses the requirement that the model must only be built using the constructs defined in the Quality profile is Option C. This option shows an «apply» relationship between the model and the profile with the {strict} keyword applied. This means that only elements with stereotypes from the Quality profile can be created as instances of the extended metaclasses. 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