01. A model shows a «satisfy» relationship drawn from the requirement Alarm Response Time to the use case Clear Alarms.
What is wrong with it?
a) It should be «deriveReqt», the relationship for a requirement's source.
b) The direction is reversed, because satisfy runs from the model element that fulfills the requirement to the requirement itself.
c) Only a block may satisfy a requirement, never a use case.
d) Nothing is wrong: satisfy may be read in either direction between a requirement and its element.
02. A modeler must present a subsystem to a safety board concerned only with which parts can propagate a hazardous flow.
Which diagram serves that audience better, and why?
a) A block definition diagram of the subsystem tree, since decomposition is the most abstract view available.
b) Whichever diagram fits on one page, since a review audience will not read a dense one.
c) An internal block diagram of the connectors that carry the hazardous flow, because the concern sets what the view shows.
d) The full internal block diagram with every connector, because leaving anything out of a review diagram misrepresents the design that was built.
03. A modeler must show that Print Receipt happens during Withdraw Cash only when the customer asks for one.
Which model expresses that?
a) A generalization from Print Receipt to Withdraw Cash.
b) «extend» from Print Receipt to Withdraw Cash, conditioned at an extension point of Withdraw Cash.
c) «extend» from Withdraw Cash to Print Receipt, conditioned at an extension point.
d) «include» from Withdraw Cash to Print Receipt, with the customer's request written as a guard on that relationship.
04. A profile defines the stereotype «purchasedItem» with a property partNumber, and the stereotype is applied to three blocks. What does the model then hold?
a) A single partNumber value, held by the stereotype in the profile and shared by all three blocks.
c) A partNumber parameter on the profile's extension.
d) A partNumber value property on each block, listed in that block's values compartment.
b) A partNumber tagged value on each block, set separately for each one.
05. A team must judge whether a large SysML model is complete before a design gate.
Which check answers that question, and why?
a) Trace the relationships each element holds, because that is what completeness is made of.
b) Count the diagrams against the plan, because a model with every planned diagram drawn has been specified in full.
c) Check that no diagram still carries an unresolved note, because those notes are what mark the work outstanding.
d) Have each author confirm that their own packages are finished.
06. A use case model draws «extend» from Offer Loyalty Points to Pay For Fuel, and «include» from Pay For Fuel to Validate Payment Card.
Which of the two may be dropped while Pay For Fuel still describes a complete interaction?
a) Offer Loyalty Points, because a base use case is meaningful without whatever extends it.
b) Neither, because a use case that any relationship reaches cannot be removed without leaving the remaining model ill formed.
c) Either, because both relationships attach a separate use case.
d) Validate Payment Card, because an included use case only factors out steps the base already describes on its own.
07. In a block's owned activity, a partition names a part that the block's composition does not contain.
What does that tell you about the model?
a) The activity belongs to the part it names and must be moved there.
b) A partition is the more precise of the two views, so the composition should be widened to include every part any partition names.
c) Nothing is wrong, because a partition is a graphical grouping that needs no element behind it.
d) Behavior is allocated to a part the structure does not provide, so either the partition or the composition is wrong.
08. Supervisor is a specialization of Operator. Operator is associated with View Alarms and Supervisor with Clear Alarms.
Which use cases may a Supervisor take part in?
a) Both, because the specialized actor inherits the general actor's associations.
b) Only View Alarms, since inheritance runs the other way.
c) Only those redrawn on Supervisor itself.
d) Only Clear Alarms, because a specialized actor replaces the general actor's associations with its own.
09. Three use cases — Pay by Card, Pay by Cash and Pay by Voucher — share the same opening and closing steps and differ only in how the payment is taken. A modeler proposes a general Take Payment use case that the three specialize.
How should that proposal be judged?
a) Unsound; generalization between use cases shares the actors associated with the general use case and never its behavior.
b) Unsound; use cases carry no inheritance, so shared steps must be factored into an included use case instead.
c) Sound; a specialized use case inherits the general one's behavior and may override it.
d) Sound, provided each specialization also includes Take Payment, since generalization on its own leaves the shared steps unperformed.
10. Withdraw Cash includes Authenticate Customer, and each of the two use cases is specified by an activity.
How should the inclusion appear in the activity that specifies Withdraw Cash?
a) As a partition named for the included use case.
b) As a separate diagram only, since one activity cannot invoke another.
c) As a decision node whose guard decides whether the authentication activity is entered on this run.
d) As a call behavior action invoking the authentication activity.