OMG-Certified Systems Modeling Professional - Model Builder - Advanced

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.

A methodology is a set of principles, methods and practices that guide the execution of a project or activity.
A systems engineering project always involves some kind of methodology, even if it is not explicitly defined or documented. Working spontaneously or randomly is also a form of methodology, although it may not be very effective or efficient. A systems engineering project cannot be conducted without applying any methodology at all.
References:
OMG-Certified Systems Modeling Professional - Model Builder ?Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.5

A profile is a mechanism for customizing SysML for a specific domain or purpose. A stereotype is a way of extending or modifying the semantics of a SysML element. A tag is an attribute of a stereotype that can store additional information. By defining a profile that contains a stereotype with a tag that can store the name of the module in X, the engineers can easily map the blocks in the design model to the corresponding modules in X, and use scripts to automate the creation of analysis models. This approach is more flexible than using notes, dependencies, or predefined tags, because it allows for more control and consistency over the mapping proces

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 main diagram type in Modelica corresponds most closely to the ibd (internal block diagram) in SysML.
An ibd shows the internal structure of a block in terms of its parts, ports, connectors, and flows. It is similar to a Modelica diagram, which shows the components of a model in terms of their connectors and equations. Both diagram types can be used to represent physical systems composed of interconnected elements with defined behaviors and properties.

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.

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.

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

The most important aspect of system development methodologies that the engineer is likely to discuss with the director of field support is how the system model can be used to facilitate change proposals, support plans, and training in the operational environment. The system model can provide a consistent and comprehensive view of the system's structure, behavior and performance throughout its lifecycle, and can help identify and evaluate potential changes, improvements or issues in the field. The system model can also help document and communicate the support requirements, procedures and resources for the system's operation and maintenance. The system model can also help design and deliver effective training programs for the system's users and operators. How field support operations can be modeled using MBSE methods, how software design patterns can be used to suggest Pre Planned Product Improvement (P3I) opportunities, and how operational evaluation (OPEVAL) plans can be developed and cross-checked in a system modeling environment are less important aspects of system development methodologies that may not be relevant or applicable to the director of field support's concerns.
References:
OMG-Certified Systems Modeling Professional - Model Builder ?Advanced (OCUP2-ADV) Examination Guide Version
1.0, Section 4.5

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