OMG-OCSMP-MBA400 Practice Exam Questions with Answers OMG-Certified Systems Modeling Professional - Model Builder – Advanced Certification

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

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

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/

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

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/

The information that is required to define a viewpoint in SysML in addition to stakeholders is concerns, languages, methods, and purpose. Concerns are aspects of interest about a system that are addressed by a viewpoint. Languages are notations or modeling techniques used by a viewpoint to represent a view. Methods are processes or guidelines for constructing or interpreting views that conform to a viewpoint. Purpose is an explanation of why and how a viewpoint addresses stakeholder concerns. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/SysML/1.6/PDF

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/

This is the most important consideration for selecting a tool to support the project because it gives the project the most flexibility. A built-in support for the method means that the tool has features and functions that are aligned with the SysML-based development method chosen by the project. This can include documentation, context-specific help, templates, wizards, etc. A built-in support for the method can help the project to follow the method more easily and consistently. A mechanism for user-defined extensions to the tool means that the tool allows users to customize or modify the tool according to their needs and preferences. This can include adding new features, changing existing features, creating new views or reports, etc. A mechanism for user-defined extensions to the tool can help the project to tailor the method over the life of the project and adapt to changing requirements or situations. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://sysml.org/tutorials/sysml-diagram-tutorial/

The most important factors that the engineer should consider when advising the team on how MBSE methodology impacts the PLM solution are the spectrum of models the company uses across the system lifecycle, how model elements can be related to each other, and how theserelationships are supported by PLM tools. The spectrum of models refers to the different types, levels and views of models that are used to represent different aspects and phases of the system development, such as requirements, design, analysis, verification and validation. The relationships between model elements refer to the traceability, consistency and dependency links that connect different elements within and across models. The support by PLM tools refers to the ability of the tools to store, manage, access and integrate the models and their relationships throughout the system lifecycle. These factors are important because they affect how well the MBSE methodology can be implemented and executed using the PLM solution. How manufacturing, test and integration methods can be driven by system models is a less important factor that may not be relevant to all systems or projects. The high cost of maintaining modeling tools and modeling proficiency training is a less important factor that may not be specific to MBSE methodology or PLM solution. How well any proposed MBSE methodology interfaces with the company’s Model Driven Software Development methodology is a less important factor that may not apply to all systems or projects. How outputs of system models, software models, and hardware models are archived in Product Data Management (PDM) tools is a less important factor that may not reflect the full potential of MBSE methodology or PLM solution. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.5

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/

 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

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

Parametric and activity diagrams are suitable for performance analysis because they can capture the quantitative aspects of a system, such as parameters, constraints, equations, values, units, flows and rates. Sequence and state diagrams are more focused on the temporal and behavioral aspects of a system, such as interactions, events and states. Use case and requirements diagrams are more focused on the functional and non-functional aspects of a system, such as actors, scenarios and goals. Block definition and package diagrams are more focused on the structural and organizational aspects of a system, such as blocks, parts, ports, connectors and packages. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.4.1

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

A best practice to provide the MARTE information to the engineers who require it is to define a viewpoint and conform views for the engineers. A viewpoint is a specification of a perspective on a model that addresses a set of stakeholder concerns. A view is a representation of a model that conforms to a viewpoint. By defining a viewpoint and conform views for the engineers, the MARTE information can be presented in a way that is relevant and understandable for them. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/MARTE/1.2/About-MARTE/

The information in option E is necessary and sufficient for the engineering team to begin selecting and procuring COTS components for the embedded real-time control system. This information defines the timing and cost requirements and constraints for the system and its components, which are essential for evaluating and comparing the available COTS components. The other options are either incomplete or irrelevant for this purpose. For example, option A does not include the minimum period of time between critical inputs, the maximum number of critical inputs, or the cost information. Option B does not include the minimum period of time between critical inputs or the maximum number of critical inputs. Option C does not include the maximum number of critical inputs or the allocation of cost to system components. Option D does not include the maximum number of critical inputs.

Stereotypes should be grouped in profiles to facilitate re-use in later projects. A profile is a mechanism for extending UML or SysML with additional modeling elements that are not part of the standard language. A profile defines stereotypes, which are extensions of existing metaclasses. A profile can be applied to a model to make the stereotypes available for use. Bygrouping stereotypes in profiles, they can be easily reused in different models or projects. 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 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

This recommendation would be most effective from a MBSE perspective because it allows the system engineer and the analysts to leverage the SysML model as a source of design information and analysis input. A SysML model is a graphical and textual representation of a system and its structure, behavior, requirements, etc. By creating a SysML model for capturing the design of different types of smart-home systems, the system engineer can specify the relevant design details necessary for evaluation, such as parameters, constraints, properties, etc. The analysts can then set up executable templates/scripts to generate analysis models from the SysML model using various methods and tools. This way, the analysts can ensure that their analysis models incorporate the latest design information and are easily adaptable for different types of smart-home systems. The system engineer and the analysts can also use allocation or synchronization mechanisms to link the SysML model and the analysis models and propagate changes between them. 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 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/