OMG OMG-OCSMP-MBA400 - Questions & Answers

A common rationale for defining and applying a profile to a SysML model is that the profile extends the model with reusable elements, such as units, quantities, value types, etc. These elements can be defined in a model library and imported into other models by applying the profile. This way, the profile enables consistent and standardized modeling of properties and parameters of blocks and constraints.
References:
https://www.omg.org/ocsmp/ocsmp-adv-exam.htm
https://github.com/Systems-Modeling/SysML-v2-Release

The first step in building the model in executing a model-based systems engineering methodology should be to define the initial model organization. The initial model organization defines the structure and scope of the model, such as the packages, views, viewpoints and frameworks that will be used to organize the model elements and diagrams. The initial model organization provides the foundation and context for the subsequent steps in building the model, such as defining the domain model structure, defining the initial set of system requirements or defining the business or enterprise use cases. The initial model organization can also help establish the modeling conventions and standards that will be followed throughout the model development process.
References:
OMG-Certified Systems Modeling Professional - Model Builder ?Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.1

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

The capability of MARTE that will help determine whether the existing processors at the data center can handle the anticipated data increase is support for schedulability analysis. Schedulability analysis is a technique for verifying that a set of tasks can be executed within given time constraints on a given platform. MARTE provides concepts and annotations for modeling tasks, resources, scheduling policies, deadlines, etc., and for performing schedulability analysis 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 main difference between software development methodologies and systems development methodologies is that software development methodologies tend to focus on high quality code, such as functionality, reliability, performance and maintainability, while systems developmentmethodologies tend to focus on holistic issues, such as stakeholder needs, system boundaries, interfaces, trade-offs and lifecycle management. Software development methodologies are usually applied to software-intensive systems or subsystems, while systems development methodologies are usually applied to complex systems that involve multiple disciplines and domains. It is not true that all current systems development methodologies are extensions of previous software development methodologies, as some systems development methodologies have different origins and foundations. It is not true that software development methodologies employ formal architecting techniques, while systems development methodologies tend not to, as both types of methodologies can use different levels of formality and rigor in their architecting approaches. It is not true that for software intensive systems, there is effectively no difference between system development methodologies and software development methodologies, as software intensive systems still require a broader and deeper perspective than software development methodologies can provide. It is not true that there is no difference between any methodology good for software development and any methodology good for systems development, as different types of systems may require different types of methodologies that suit their characteristics and challenges.
References:
OMG-Certified Systems Modeling Professional - Model Builder ?Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.5

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

This configuration management strategy is likely to be most successful because it allows the engineers to work on the system model collaboratively and concurrently, while maintaining configuration control and avoiding conflicts. A configuration management tool is a software tool that helps manage changes to model elements and track their versions and history. A package is a grouping mechanism that can contain any kind of model element, such as diagrams, blocks, activities, etc. By using a configuration management tool, the engineers can check out packages for editing, which locks the elements in that package and prevents other users from modifying them. The engineers can also view packages in read-only mode by any user at any time, which allows them to see the latest version of the model without affecting it. The engineers can also receive alerts when a package they are viewing has been modified and checked-in by another user, and see the changes highlighted. This way, the engineers can stay informed and synchronized with the model updates. By not allowing packages to remain checked out overnight, the engineers can avoid holding up the work of other users who need toaccess or modify those packages.
References:
https://www.omg.org/ocsmp/ocsmp-adv-exam.htm
https://sysml.org/tutorials/sysml-diagram-tutorial/

A fundamental goal of UPDM is to define a common means of expressing DoDAF and MODAF architectures using the same underlying metamodel. UPDM is a UML profile that supports both DoDAF and MODAF, which are two main architectural frameworks used in the defense domain. UPDM provides a common set of elements and relationships that can be used to represent architectures in either framework, using a Domain Metamodel that captures the core concepts of both frameworks. UPDM also provides mappings to UML and SysML concepts to enable implementation and integration with other modeling languages and tools.
References:
https://www.omg.org/ocsmp/ocsmp-adv-exam.htm
https://www.omg.org/updm/

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

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/