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

The modeling tool provides the stereotypes

The stereotypes are part of the SysML standard

Each modeler who writes requirements can define stereotypes

A profile that maps modeling methodology concepts to the model defines the stereotypes

Option A

Option B

Option C

Option D

a range property

an interval property

a probability property

a distributed property

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

Option A

Option B

Option C

Option D

Option A

Option B

Option C

Option D

Option A

Option B

Option C

Option D

Option E

action 9, action 1

action 2, action 9, action 1

action 2, action 9, action 1, start activity X, evC

stop activity X (if needed), action 2, action 9, action 1, start activity X

stop activity X (If needed), action 2, action 9, action 1, action 4 start activity X

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.

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.

Option A

Option B

Option C

Option D

Model an activity that refines the functional requirement.

Model a state machine that refines the functional requirement.

The project methodology will indicate which way is compatible with its process.

The requirement text must be a clear and concise specification of the functionality.

a derived property

an analysis property

a calculated property

an estimation property

a replacement property

Option A

Option B

Option C

Option D

Option A

Option B

Option C

Option D

A metamodel is used to define the stereotypes and the properties of a profile.

A metamodel Is the result of applying a profile to a user model to define new domain concepts.

A profile is a mechanism for extending existing concepts defined In a metamodel.

A profile is a mechanism for defining stereotypes, which is not related to metamodels in any way.

as a part contained by the block B1

as a part contained by the block B3

as a part contained by the block B4

as a part contained by the diagram Nested Parts

The arrow '"Start Software" has to be solid and with a closed head.

The first activation on the lifeline SoftwareSession has to be removed

The arrow "Start Software" has to cud at the tail and not at the head of the lifeline SoftwareSession.

No change is required.

a formal gate

a usage point

a message port

an interaction parameter

The modeler set a1 as an input value in case1.

Block A cannot be used by both easel and case2.

Both easel and case2 should not be underlined.

The slash (/) in property a1 of BlockA is an error that paramethes will assume to be a division sign.

suggestions for improving the efficiency of the design

constraints specifying that the direction of the association is ordered and that an instance of A uniquely consists of instances of B

constraints specifying that the set representing the Instances of P is ordered In the context of the association, and all instances are unique

constraints specifying that all instances of B must be ordered in a unique sequence when they are associated with any instance of block A

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

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.