OMG-OCSMP-MBI300 OMG-Certified Systems Modeling Professional - Model Builder – Intermediate Questions and Answers

parameters that are mapped to flow ports

parameters in which tokens are never buffered

parameters through which a continuous stream of tokens pass

parameters through which an activity can accept or produce tokens throughout its execution

an activity diagram

a parametric diagram

an internal block diagram

a block definition diagram

Create a block to represent the mass conservation equation, use it in Tank_System. and relate its properties to the properties of wFlowin. wFlowOut. and pipe

Create a constraint block to represent the mass conservation equation, use it in Tank_System. and relate its parameters to the properties of wFiowin. wFlowOut. and pipe

Create a constraint block to represent each of wFlowin wFlowOut and the mass conservation equation; use these constraint blocks In Tank_System. and relate their parameters to the properties of pipe.

Create two flow properties for Tank_System (equivalent to wFlowin and wFlowOut); create a constraint block for the mass conservation equation and use it in Tank_System. and then relate the flow properties to the new constraint property.

It is not possible to model this because wFlowin and wFlowOut are item properties and not flow properties

in a SysML model, either use cases or requirements are modeled, but never both

Use cases are a relic from UML and are. strictly speaking, useless in a SysML model

Use cases are good for capturing functional requirements. For nonfunctional requirements, the requirement element is needed

Use cases are the basis for all requirements in a model. Requirements refine the use cases by adding additional information through then properties.

Option A

Option B

Option C

Option D

Option A

Option B

Option C

Option D

(not full, exclusive)

(partial, exclusive)

{Incomplete, xor)

(incomplete disjoint)

{subset, disjoint}

Only Instances X1 and X? are invalid

Only instances X2 and X4 are invalid.

Only instance X4 is invalid.

All instances (X1, X2, X3, and X4) are valid.

Option A

Option B

Option C

Option D

Message a1 overtakes message m1, which is processed after receipt of a1.

Message a1 overtakes messages m1 and m2 and is processed before them.

Message m1 overtakes message a1, which is processed after receipt of m2.

Message m1 overtakes messages a1 and m2 and is processed before them.

The Security viewpoint conforms to the requirements specified by the Security view

The Security view is intended to address the purpose specified by the Security viewpoint

The Security view imports the Security viewpoint to ensure the security requirements are satisfied

The Security viewpoint imports the model elements associated with flowing down the security requirements

provide a detailed definition of the use case using a behavioral diagram

specify all of the triggers preconditions, and post conditions for the use case

specify all extension points for extend use cases and specify all secondary actors

provide a complete textual description of the main flow and alternative/exceptional flows for the use case

{complete, disjoint{

{incomplete, disjoint}

{complete, overlapping}

{incomplete, overlapping{

Option A

Option B

Option C

Option D

Copy

Trace

Refine

Satisfy

Dependency

Association

composition

The pressure of each part is constrained to be 50 psi.

if not redefined individually by each part, the value of pressure must be 50 psi.

The values may be redefined, but they must be the same for both front and rear.

To be other than 50 psi. instance specifications must be developed for front and rear tires.

suspend and resume

enable and disable

suspend, resume, enable and disable

It has no values, but is intended for a modeler to extend with their own control values.

when a block is typed by another block with similar properties

when it is important to ensure uniform generalization of all blocks

when it is important to ensure uniform specialization of all block properties

when a block that types several part properties exists in multiple variants

A derived property requires an additional constraint expression, whereas SysML parametrics does not.

OCL-based constraint expressions can be used with SysML parametrics but not with derived properties

it takes many more steps to specify derived properties in the typical tool compared to specifying constraint blocks.

SysML parametrics supports non causal expressions, whereas a derived property involves an expression with a fixed output direction

Option A

Option B

Option C

Option D

Option E

The block Fluid, which types item property flow 1 ->2. has a value property press : Pressure with a default value of null

The value property /rate : flow rate is a derived property, which accommodates calculating its value based on oilier properties

Parts t1 and t2 each use part instances to redefine the value of property level : Height

The value of /rate for item property flow 1->2 is positive for flow from t1 to t2. and negative for How in the other direction

Both port p1 on pan t1. and port p1 on t2. must have values defined for value properties /rate and press

The verify relationship is restricted to relating a requirement to a testCase only.

The verify relationship extends the refine relationship to specify how the requirement will be verified.

The verify relationship is an extension of the satisfies relationship, relating a block to a verification activity.

The verify relationship relates a requirement to some other model element such as a testCase. activity, or interaction that can prove the requirement has been satisfied.

The verify relationship is used to prove. That the assertion of the satisfy relationship is true Thus, a verify relationship is meaningless

without a corresponding satisfy relationship.

O1.1 and O2 1

O1.1 and O2 2

O1 1 and O2 3

O1.2 and O2.1

O1 7 and O2.2

O1.2 and O2.3

O1 3 and O2 3

Option A

Option B

Option C

Option D