OMG-OCSMP-MBA400 OMG-Certified Systems Modeling Professional - Model Builder - Advanced Question and Answers

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

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

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 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

A V development approach is a systems engineering methodology that follows a V-shaped process model. The left side of the V represents the decomposition of requirements into system and subsystem specifications. The bottom of the V represents the integration and testing of system components. The right side of the V represents the verification and validation of system performance against requirements. A function to structure allocation relationship is pivotal in a V development approach, because it defines how the system functions are realized by the system structure (i.e., components). This relationship enables traceability and consistency between requirements, design, implementation, and testing

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

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

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 link actions of an activity in a SysML model to a software application described in a UML model is to use CallBehaviorActions in the UML model that call the actions in the SysML model. A CallBehaviorAction is an action that invokes a behavior and provides inputs and outputs. By using CallBehaviorActions, the software application can reuse the behavior defined in the SysML model without having to duplicate or copy it. This also ensures consistency and traceability between the models. 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_activity_diagram.html

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