Pass the OMG OMG Certification OMG-OCSMP-MBA400 Questions and answers with CertsForce

Option C gives the most general answer without including any irrelevant rules. Option A is incorrect because it does not account for the possibility of an input object being consumed without producing any other object. Option B is incorrect because it introduces the concept of undocumented user need, which is not part of the requirements analysis. Option D is incorrect because it adds an unnecessary rule about cycles of control flows, which are not prohibited in activity diagrams. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.2.1.3

This model organization approach would be most efficient because it allows the bank manager and his core team to modularize and structure their system processes using SysML packages. A package is a grouping mechanism that can contain any kind of model element, such as diagrams, blocks, activities, etc. By creating a package for each of the core processes, the team members can work on their own processes independently and concurrently. By creating a package for each of the relationships between processes, the team can identify and manage the dependencies and interactions among the processes. By creating a package for the overall consolidated process, the team can have a holistic view of the system and perform visualization and analytics using SysML diagrams and parametrics. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://sysml.org/tutorials/sysml-diagram-tutorial/

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

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

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

To force modelers to use particular metamodeling features, the supervisor must «apply» the profile to the model with the {strict} keyword applied. This keyword indicates that only elements with stereotypes defined in the profile can be created as instances of the extended metaclasses. For example, if a profile defines a stereotype <> as an extension of Class, then only classes with this stereotype can be created as instances of Class when the profile is applied with the {strict} keyword. 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 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 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 systems engineering methodology is a collection of related processes, methods, and tools that support the discipline of systems engineering in a specific context. The activities in a typical systems engineering methodology are applied iteratively, meaning that they are repeated and refined until a satisfactory solution is achieved. The activities are not applied sequentially, meaning that they are not performed in a fixed order without revisiting previous steps. The activities cannot be performed in any order, because they have logical dependencies and prerequisites. The activities do not work just as well for specialty engineering activities, because they may require different processes, methods, and tools

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