OMG-OCSMP-MBA400 Sample Questions Answers

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/

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

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/

 A methodology is a set of principles, methods and practices that guide the execution of a project or activity. A systems engineering project always involves some kind of methodology, even if it is not explicitly defined or documented. Working spontaneously or randomly is also a form of methodology, although it may not be very effective or efficient. A systems engineering project cannot be conducted without applying any methodology at all. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.5

The purpose of the Domain Metamodel in UPDM is to define the metamodel concepts and relationships without any implementation. The Domain Metamodel captures the core concepts of DoDAF and MODAF in terms of entities, attributes, associations, and constraints. It does not specify how these concepts are implemented in UML, SysML, or any other language or tool. The Domain Metamodel serves as a requirements model for UPDM and provides traceability links between the domain concepts and the profile elements. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/updm/

SysML is a general-purpose modeling language for systems engineering that can support various systems engineering methodologies. The stereotype and profile mechanisms are features of SysML that enable customizing and extending the language for a specific domain or purpose. By using stereotypes and profiles, SysML can be adapted to fit different methodologies and conventions without changing the core language semantics

The best practice to model a software application in a SysML model for a system is to use a block stereotyped with «software» to represent the software application and its interfaces. A block is a modular unit that encapsulates its structure and behavior and can be connected to other blocks via ports and connectors. A stereotype is an extension of an existing metaclass that adds additional information or semantics to a model element. By using a block stereotypedwith «software», the software application can be modeled as a system component with its own properties, operations, ports, flows, etc., and can be allocated to hardware blocks or other software blocks. 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 profile is a mechanism for extending the UML or SysML metamodel with domain-specific concepts. A profile defines stereotypes, which are extensions of existing metaclasses. A metaclass is a modeling construct that defines the properties and behavior of a set of model elements. For example, the metaclass Class defines the properties and behavior of all classes in a model. When a profile is applied to a model, the stereotypes defined in the profile may beapplied to elements sharing compatible metaclasses. For example, if a profile defines a stereotype <> as an extension of the metaclass Class, then the stereotype <> may be applied to any class in the model. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/UML/About-UML/ https://www.omg.org/spec/SysML/About-SysML/

This modeling approach should be used by the system engineer because it allows him to capture the behavior of his system-of-interest using SysML activities and actions. An activity is a behavior that specifies the coordination of actions. An action is a behavior that specifies a transformation or processing of data. By using activities and actions, the engineer can model the algorithm and its functions in terms of inputs, outputs, control flows, object flows, parameters, etc. He can also use allocations to relate the activities and actions to other model elements, such as blocks or requirements. This way, he can generate MATLAB code from his SysML model for execution and testing. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://sysml.org/tutorials/sysml-diagram-tutorial/

The SysML diagram type that is a modification of the UML Class diagram is the Block Definition Diagram (BDD). A BDD shows the definition of blocks in terms of their features, such as properties, operations, ports, etc. It is similar to a UML Class diagram, but it adds some features specific to SysML, such as value types, units, flow properties, etc. A block is an extension of the UML Class metaclass that can be used to model any system component with structure and behavior. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://sysml.org/tutorials/sysml-diagram-tutorial/

To get this model ready for solving according to the SysML-Modelica Transformation specification, one must provide specific values for the parameters and properties of the blocks, such as resistance, capacitance, voltage, etc. Also, one must define a parametric diagram that includes equations for Kirchhoff’s Laws consistent with the above ibd. A parametric diagram is a SysML diagram that shows constraints and parameters on blocks and their properties. Kirchhoff’s Laws are physical laws that describe how electric currents and voltages behave in a circuit. By defining a parametric diagram with these equations, one can specify how the blocks and connectors in the ibd are related mathematically. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/SyM/1.0/About-SyM/

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

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

The best way to share the profile is to define it as a model library and import it into the other model. A model library is a package with the stereotype <> applied to it. It contains reusable model elements that can be imported into other models by using an «import» relationship. Option B shows this approach. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/SysML/1.6/PDF

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/

According to the Survey of MBSE Methodologies 1, a methodology is defined as a collection of related processes, methods, and tools. A process is a sequence of steps or activities that transform inputs into outputs. A method is a technique or procedure for performing a specific task. A tool is an instrument or device that supports or automates a process or method. A methodology integrates these elements to support a specific domain or purpose.

 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

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

OCL is a formal language that can be used to specify constraints on the elements and relationships of a model. OCL can access the properties and operations of the model elements and check their values and states. OCL is not intended to be transformed into code or to express any imaginable constraint. OCL may not be easily understood by engineers who are not familiar with its syntax and semantics. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.3.1

The kind of models that can be exchanged using XMI are instances of MOF models. MOF (Meta-Object Facility) is a standard that defines a metamodeling architecture and a set of metamodels for creating and manipulating models. A metamodel is a model that defines the abstract syntax and semantics of another model. A model is an instance of a metamodel that conforms to its rules and constraints. XMI (XML Metadata Interchange) is a format specification that enables the interchange of objects and models through an XML formatted file. It is based on a metamodel that defines the mapping of MOF concepts to XML concepts. By using XMI, any model that is an instance of a MOF metamodel can be serialized and deserialized in terms of XML elements and attributes. This includes UML, SysML, and other modeling languages that are defined as MOF metamodels. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/XMI/2.5.1/About-XMI/

This approach would be most effective from a MBSE perspective because it allows the system engineer to create a unified view of the design of the system and its components using SysML blocks and relationships. A block is an extension of the UML Class metaclass that can be used to model any system component with structure and behavior. A relationship is a connection between model elements that specifies some kind of dependency or association. By creating a SysML block structure representing the system and its components, the system engineer can capture the hierarchy, composition, classification, generalization, etc., of the system elements. By creating relationships between the blocks and the design models, such as MCAD, ECAD, or Spreadsheets, the system engineer can link the SysML model with the external models and provide traceability and consistency. The system engineer can also use the SysML model to generate a bill-of-materials for the system and its components, as well as to propagate changes made in one design model to another using allocation or synchronization mechanisms. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://sysml.org/tutorials/sysml-diagram-tutorial/

A complete SysML model is one that has all the necessary information relevant at the level of abstraction that the model represents. A complete model does not necessarily have to trace back to all requirements, use all diagram types, or include all constructs and associations. A complete model should capture the essential features and properties of the system or part being modeled, without being too detailed or too abstract. A complete model should also be consistent, coherent and correct. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.1

The quality of models relates to the quality of the modeling language used to express them in that model quality benefits from the degree of syntactical and semantic formalism supported by the modeling language. Syntactical and semantic formalism refers to the rules and meanings that define how the modeling language elements and relationships can be used and interpreted. A high degree of syntactical and semantic formalism can help improve the clarity, consistency and correctness of the models and avoid ambiguity, inconsistency and error. A high degree of syntactical and semantic formalism can also enable automated analysis, verification and validation of the models. The modeling language does not have to be applicable to a wide range of domains of practice in order to produce high-quality models, as some modeling languages may be more suitable or specialized for certain domains than others. The level of comprehensibility of the modeling language’s abstract syntax does not directly correspond to the quality of the models, as abstract syntax is only one aspect of the modeling language that defines its structure and notation. The quality of the modeling language does influence the quality of the models because the quality of the models depends not only on the skill and knowledge of the modeler but also on the expressiveness and precision of the modeling language. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.1

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/