OMG-OCSMP-MBA400 Sample Questions Answers

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/

 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

 If a systems modeling tool conforms to the XMI specification and includes the XMI representation of the UML Profile for SysML and the XMI representations of Model Libraries defined by SysML, the tool provides the import and export of both SysML diagrams and model data from one tool to another. 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 abstract syntax and semantics of the model elements. By conforming to the XMI specification, a tool can serialize and deserialize SysML models in terms of XML elements and attributes. The tool can also include the XMI representation of the UML Profile for SysML, which defines the mapping of SysML concepts to UML concepts, and the XMI representations of Model Libraries defined by SysML, which provide predefined types and units for SysML models. This way, the tool can import and export both SysML diagrams and model data from one tool to another, ensuring consistency and interoperability. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/XMI/2.5.1/About-XMI/

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

 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/

The best way to ensure that a shared model has consistently-represented elements and diagrams is to use modeling conventions and standards. Modeling conventions and standards are rules and guidelines that define how the model elements and diagrams should be named, defined, structured, formatted and documented. Modeling conventions and standards can help improve the clarity, consistency and quality of the model and facilitate the communication and collaboration among the modelers and stakeholders. Implementation of standard libraries is a good way to ensure that a shared model has reusable and interoperable elements and diagrams, but it may not ensure their consistent representation. Packages that map one-for-one to components is a good way to ensure that a shared model has modular and traceableelements and diagrams, but it may not ensure their consistent representation. Domain stereotypes maintained in a configuration control system is a good way to ensure that a shared model has customized and controlled elements and diagrams, but it may not ensure their consistent representation. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.1

A method is a technique or procedure for performing a specific task. A method is not generic and cannot be used out-of-the-box, because it depends on the context and purpose of the task. A method is not unnecessary to build an effective SysML model, because it provides guidance and structure for the modeling process. A method does not depend on the specific features of the modeling language, because it can be applied to different languages with appropriate adjustments. Therefore, a method must be adapted to company or project specific needs, because it should reflect the goals, requirements, constraints, and preferences of the stakeholders involved in the project

The main diagram type in Modelica corresponds most closely to the ibd (internal block diagram) in SysML. An ibd shows the internal structure of a block in terms of its parts, ports, connectors, and flows. It is similar to a Modelica diagram, which shows the components of a model in terms of their connectors and equations. Both diagram types can be used to represent physical systems composed of interconnected elements with defined behaviors and properties. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://modelica.org/documents/ModelicaSpec34.pdf

To reuse the type definitions of the properties of a stereotype, the profile needs to import the package where these types are defined. An import relationship indicates that the elements in one package can be referenced by another package without a qualified name. By importing the package with the types, the profile can use them as attributes of the stereotype without having to redefine them. 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 most effective way to verify such requirements is to have the Modelica solver also compute these scalar values from its time-based power usage results. Then import the resulting scalar values into SysML, and compare them to the requirements. This way, the verification can be done at the same level of abstraction as the requirements, and avoid unnecessary transformations or calculations in SysML. Modelica solvers can provide various functions and operators to compute scalar values from time-based results, such as max, min, mean, integral, etc. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://modelica.org/documents/ModelicaSpec34.pdf