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/

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

It is appropriate to use the MARTE profile to model this system with SysML because the control unit must order the submarine’s operations in real time, which the MARTE profile makes it possible to model in SysML. MARTE is a UML profile that provides concepts and annotations for modeling and analyzing real-time and embedded systems. It supports modeling time-related properties and constraints, such as deadlines, periods, durations, clocks, etc., as well as resource-related properties and constraints, such as memory, CPU, power, etc. By using MARTE, one can capture the real-time requirements and behavior of the system and perform schedulability and performance analysis. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.omg.org/spec/MARTE/1.2/About-MARTE/

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/

Working in UPDM compliance level 1 allows users to bring SysML elements into the architecture to enhance the hand-off between Systems of Systems and Systems. Compliance level 1 is based on UML and SysML concepts and provides integration with system modeling using SysML. Users can use SysML elements, such as blocks, ports, connectors, parametrics, etc., to model system components and their interactions in more detail and precision than using UML elements alone. This can facilitate the transition from architecture modeling to system design and analysis. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://www.ibm.com/docs/bg/rhapsody/8.3.1?topic=function-designing-updm-profiles

OCL is a formal language that can be used to specify constraints on the elements and relationships of a model. OCL can access the properties and operations of the model elements and check their values and states. OCL is not intended to be transformed into code or to express any imaginable constraint. OCL may not be easily understood by engineers who are not familiar with its syntax and semantics. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.3.1

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

To force modelers to use particular metamodeling features, the supervisor must «apply» the profile to the model with the {strict} keyword applied. This keyword indicates that only elements with stereotypes defined in the profile can be created as instances of the extended metaclasses. For example, if a profile defines a stereotype < < quality > > as an extension of Class, then only classes with this stereotype can be created as instances of Class when the profile is applied with the {strict} keyword. 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

OCL is the most suitable and compatible language for placing formal pre-conditions and post-conditions on an activity diagram. OCL is part of the UML standard and can be integrated with SysML without any conflicts or inconsistencies. OCL can express complex logical expressions that can check the state of the system before and after an activity is executed. BPMN is a business process modeling language that is not compatible with SysML. English is a natural language that may not be precise or unambiguous enough for formal specifications. OWL is a web ontology language that is not designed for modeling activities or constraints. VSL is a value specification language that can only express simple values and expressions. XMI and XML are markup languages that are used for exchanging models between tools, not for specifying constraints on models. References: OMG-Certified Systems Modeling Professional - Model Builder – Advanced (OCUP2-ADV) Examination Guide Version 1.0, Section 4.3

The most effective way to verify such requirements is to have the Modelica solver also compute these scalar values from its time-based power usage results. Then import the resulting scalar values into SysML, and compare them to the requirements. This way, the verification can be done at the same level of abstraction as the requirements, and avoid unnecessary transformations or calculations in SysML. Modelica solvers can provide various functions and operators to compute scalar values from time-based results, such as max, min, mean, integral, etc. References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htm https://modelica.org/documents/ModelicaSpec34.pdf