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

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

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

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

This type of data exchange mechanism uses a database that is accessible by two or more tools in order to share data. A repository-based exchange is a way of exchanging data between tools that have direct integration or compatibility. It requires the tools to access a common database that stores the data in a standardized format, such as XMI, AP233, etc. A repository-based exchange can be useful for transferring data in real-time or for performing collaborative operations. However, it can also have some drawbacks, such as security, scalability, orperformance issues. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/AP233/About-AP233/

Views and viewpoints are used to show the aspects of a model that relate to different stakeholders. A view is a representation of a subset of a model that addresses a set of stakeholder concerns. A viewpoint is a specification of a perspective on a model that defines how a view should be constructed and used. By using views and viewpoints, different aspects of a model can be presented in a way that is relevant and understandable for different stakeholders. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://docs.nomagic.com/display/SYSMLP184/Views+and+Viewpoints+Diagram

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

A trade study is a method for making a decision between competing alternatives based on a set of criteria, such as cost, performance, reliability, etc. A trade study allows a user to objectively determine the best means of implementing a particular function by evaluating and comparing the pros and cons of each alternative. A trade study can also help identify trade-offs and risks associated with each alternative

 This feature needs to be added to the systems development environment to conduct a performance simulation because it enables users to solve mathematical equations and models that represent system performance. A numerical solver is a software tool that can perform numerical analysis and computation on a given problem or model. A numerical solver can help users to evaluate system performance by solving equations that describe system behavior, properties, constraints, etc. A numerical solver can also help users to optimize system performance by finding optimal solutions or trade-offs for a given problem or model. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://sysml.org/tutorials/sysml-diagram-tutorial/

 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