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

This choice defines a set of common tasks that will prepare the model for the stakeholders by using profiles, viewpoints, and packages. Profiles are used to extend SysML with domain-specific or methodology-specific concepts. Viewpoints are used to define different perspectives on the model that address different stakeholder concerns. Packages are used to organize the model elements into logical groups. These tasks will help to customize, structure, and communicate the model effectively. 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 best practice to provide the MARTE information to the engineers who require it is to define a viewpoint and conform views for the engineers. A viewpoint is a specification of a perspective on a model that addresses a set of stakeholder concerns. A view is a representation of a model that conforms to a viewpoint. By defining a viewpoint and conform views for the engineers, the MARTE information can be presented in a way that is relevant and understandable for them. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/MARTE/1.2/About-MARTE/

Two cross-cutting mechanisms within SysML that can be used to establish traceability between the systems model and a UML software model are allocations and stereotypes. Allocations are dependencies that indicate a relationship between elements in different models or domains. Stereotypes are extensions of existing metaclasses that add additional information or semantics to model elements. By using allocations and stereotypes, different aspects of the systems model and the software model can be linked and traced. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/SysML/1.6/PDF

For a system with stringent real-time requirements and power-consumption constraints, the concern that would lead the designer to employ the MARTE profile is ensuring that the structure could be precisely modeled and that analysis was supported. MARTE provides concepts and annotations for modeling the structure of real-time and embedded systems in terms of components, ports, connectors, flows, etc., as well as for modeling their behavior in terms of state machines, activities, etc. MARTE also provides concepts and annotations for performing analysis of system properties, such as schedulability, performance, power consumption, etc., using various methods and tools. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/MARTE/1.2/About-MARTE/

The typical stakeholder views of a design are composed of both behavioral and structural diagrams, depending on the purpose and perspective of the view. Behavioral diagrams show how the system or part behaves or interacts in different scenarios or states, such as activity, state and sequence diagrams. Structural diagrams show how the system or part is composed of parts, ports, connectors and properties, such as block definition and internal block diagrams. Both types of diagrams are important to convey the functionality and architecture of the system or part to different stakeholders. Use case and requirements diagrams are not sufficient to populate the stakeholder views of a design, as they only capture the functional and non-functional aspects of the system or part. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.4

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/