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, b, x

c, a, x

c, a, x, x

a, b. c, x

a, b, c, a, x, x

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

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

Option A

Option B

Option C

Option D

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.

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

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

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.

11

14

13

There is no value - the instance model is invalid

M1, M2. M3, M4

M3. M1. M2, M4

M3, M4. M1, M2

None of these orderings is 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

At most two Initiator actor instances can perform the use case

Two Initiator actor instances are required to trigger the use case

Two Initiator actor instances are required to participate in the use case.

Multiplicities carry no meaning on use case diagrams

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

on any diagram

only on parametric diagrams

only on block definition diagrams

only on block definition diagrams or package diagrams

only on block definition diagrams or parametric diagrams

only on block definition diagrams or internal block diagrams

It remains in State 1.

it arbitrarily enters either State 2 or State 3.

It terminates

Its behavior is not defined.

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.

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.

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

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

action 2

action 2 action 3

action 2 action 4

action 3

action 4

action 5 action 2 action 3

action 5 action 2 action 4

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