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

 The SysML diagram type that is a modification of the UML Composite Structure diagram is the Internal Block Diagram (IBD). An IBD shows the internal structure of a block in terms of its parts, ports, connectors, and flows. It is similar to a UML Composite Structure diagram, but it adds some features specific to SysML, such as flow ports, flow specifications, item flows, nested connectors, etc. 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

 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

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

This configuration management strategy is likely to be most successful because it allows the engineers to work on the system model collaboratively and concurrently, while maintaining configuration control and avoiding conflicts. A configuration management tool is a software tool that helps manage changes to model elements and track their versions and history. A package is a grouping mechanism that can contain any kind of model element, such as diagrams, blocks, activities, etc. By using a configuration management tool, the engineers can check out packages for editing, which locks the elements in that package and prevents other users from modifying them. The engineers can also view packages in read-only mode by any user at any time, which allows them to see the latest version of the model without affecting it. The engineers can also receive alerts when a package they are viewing has been modified and checked-in by another user, and see the changes highlighted. This way, the engineers can stay informed and synchronized with the model updates. By not allowing packages to remain checked out overnight, the engineers can avoid holding up the work of other users who need toaccess or modify those packages. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://sysml.org/tutorials/sysml-diagram-tutorial/

The most significant deficiency impeding widespread use of SysML (without MARTE) in the real-time and embedded domain is a quantifiable notion of time and resources. SysML does not provide a standard way to model time-related properties or constraints, such as deadlines, periods, durations, clocks, etc., nor does it provide a standard way to model resource-related properties or constraints, such as memory, CPU, power, etc. These aspects are essential for real-time and embedded systems design and analysis. MARTE addresses this deficiency by providing concepts and annotations for modeling time and resources in a precise and quantitative way. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/MARTE/1.2/About-MARTE/

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

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/

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

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