OMG-OCSMP-MBI300 Questions and Answers

Option A

Option B

Option C

Option D

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.

It is a constraint that prevents adding a nested ignore fragment for any one of ml. m2 or m3.

It ignores all messages other than ml m2 and m3 in the scenario being described by the interaction

The meaning is undefined because the diagram is ill-formed in the absence of n>3. which must be considered.

It allows the invocation of the operations corresponding to messages m 1. m? and m3 only when they appear in that order

whether component s0 subclasses component u3

which parts of each component participate in the connection

which parts of each component participate in a reference association

whether any part that belongs to component s0 subclasses a pan that belongs to component u3

Option A

Option B

Option C

Option D

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

An objective function is usually a function of only one MOE.

An objective function is usually a function of several different MOEs

An MOE is usually composed of only one objective function.

An MOF is usually composed of several different objective functions

11

14

13

There is no value - the instance model is invalid

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.

Option A

Option B

Option C

Option D

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.

an Interaction use referencing an interaction defined on a separate sequence diagram

an interaction template construct that is instantiated from the referring sequence diagram

the call interaction operator with an operand referring to the reusable Interaction defined elsewhere

an activation on the referring sequence diagram allocated to another activation on the referenced diagram

Only items compatible with Card Connection may pass over connector c1. There are no other implications

If SD Card and Card Reader blocks ever have ports, they must be compatible with the Card Connection association

Card Connection represents the pan that d uses to connect SD Card to Card Reader, eg the arrangement of contact points

An association must exist between the SD Card block and Card Reader block, and not just between parts in the Digital Picture Frame block.

SysML defines the package structure

The modeling tool creates the package structure

The modeling methodology defines the package structure.

Each modeler can create packages for that engineer's specific purpose

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.

action 1. stop activity X (if running), action 7, action 8, action 5, start activity Y

stop activity X (if running), action 8, action 5, start activity Y, action 7

stop activity X (if running) action 8, action 5, start activity Y, action 7, action 7

stop activity X (if running), action 2, action 8, action 5, start activity Y, action 7, action 7

stop activity X (if ninning). action 2, action 8, action 5, start activity Y, action 7, action 7, action 6

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

It remains in State 1.

it arbitrarily enters either State 2 or State 3.

It terminates

Its behavior is not defined.

Option A

Option B

Option C

Option D

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.

a lower bound on the number of changes to an object's value per time Interval

a lower bound on the number of objects that will traverse the edge per time interval

the expected number of changes to an object's value per time interval.

the expected number of objects that traverse the edge per time interval

an upper bound on the number of changes to an object's value per time interval

an upper bound on the number of objects that will traverse the edge per time interval

Option A

Option B

Option C

Option D