OMG-OCSMP-MBI300 Sample Questions Answers

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

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

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

«replace»

«overwrite»

«notbuffer»

No stereotype is needed in this case since it describes the default condition

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.

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.

a range property

an interval property

a probability property

a distributed property

Option A

Option B

Option C

Option D

Option A

Option B

Option C

Option D

a, b, x

c, a, x

c, a, x, x

a, b. c, x

a, b, c, a, x, x

It remains in State 1.

it arbitrarily enters either State 2 or State 3.

It terminates

Its behavior is not defined.

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

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

It states that the corresponding property is provided for reading purposes only

It specifies that the corresponding property cannot be redefined

It specifies that the value of the corresponding property cannot change during the lifetime of its owner.

It specifies that the value of the corresponding property can be changed by its owner, but can only be read by other blocks

initialize the multiplicities of wheel as part of the system Initializer

draw new relationships between Taxi and Wheel and Bus and Wheel using the same role name but different multiplicities

draw new relationships between Taxi and Wheel and Bus and Wheel with the specific multiplicities and mark the wheel end as redefining the wheel end of the relation between PublicTransportCar and Wheel

draw new relationships between Taxi and Wheel and 8us and Wheel with the specific multiplicities and mark the wheel ends as subsets of the wheel end of the relation between PublicTransporlCar and Wheel

Composition allows requirements to inherit properties and requirements relationships

Composition allows role names to be assigned to sub-requirements thus providing a contextual reference

Composition allows a particularly useful requirement to be reused by multiple higher level requirements or specifications

Composition allows a requirement to be decomposed into sub-requirements as long as they don't add to or change the meaning of the original requirement.

Requirements cannot use composition. They are not classifiers

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.

on a lifeline in a sd

on a transition in a stm

on an object node In an act

in the s rates compartment of a block on a bdd

Option A

Option B

Option C

Option D

Option E

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

Every project should create its own domain specific profile to describe modeling standards and conventions

Organizations should create specific modeling standards and conventions to ensure modeling consistency across projects

The SysML specification alone is sufficient to describe modeling standards and conventions when the modeling tool has a proper implementation of SysML

The SysML specification and the modeling tool documentation are sufficient to describe modeling standards and conventions

The testCase model element can be used in SystvIL but it only applies to software

Validation of a requirement can be indicated using a satisfiedBy relationship to a testCase

Only the verdict model element (which can be a property of a testCase) can have a verifies relationship to a requirement.

A requirement can have a vehfiedBy relationship to a testCase even if the test has not yet been conducted or even fully specified

testCase is part of the UML Testing Profile and cannot be used with SysML.

Option A

Option B

Option C

Option D