Module 13 - Requirements Flashcards
purpose of a requirements diagram ?
it displays requirement elements and other elements ( packages , use cases , test cases) that the requirements are related to within the model
stakeholder requirements are also known as _________ requirements
mission
Cameo tip - you can create _______ generalization relationships . like “ProjectX Requirement”
custom
commonly used relationships with requirements
- containment
- trace
- derive requirement
- refine
- satisfy
- copy
2-7 are special kinds of dependency relationships ,, supplier client , if one element changes another element may change. that is true for trace, derive requirement , refine satisfy .. and copy
verify
«trace» relationship
- it conveys only client if the supplier change the client may change.
why would the the modler use the trace relationship if its the same as depend relationship ?
sometimes the customer likes to see the word trace between requirements. its a preference at that point.
key idea for derive requirement
both the client and supplier must be ________ elements. nothing else is legal.
cant be a block and a requirements or any element like that.
how its read .. derive requirement is derived from the supplier requirement
requirement
key idea for refine relationship
- it conveys only client if the supplier change the client may change.
what makes it special
1. not limited to only requirements
2 used between two elements
(arrowhead) more abstract
(tailhead) more refined
** the arrow is always drawn from the more concrete representation to the more abstract representation
its a matter of modeler judgment to use the refine relationship
whats the difference between modeler exam 1 and 2
difference is the style of questions . its how the question asks the user to interpret the diagram.
on model exam 2 the stem of the question is text and you are asked to select the diagram that represents that text.
key idea satisfy relationship
- instances of the client element ( tail end) will satisfy the requirement at the supplier end ( arrow head ) .
- supplier must be a __________ element ( nothing else is legal )
- client element can be anything ( block , act , stm , use case ,value type)
requirement
what design decision is conveyed when there are more than one model element with satisfy relationships to a requirement ?
it can either be one model element that satisfies OR another .. not both
a verify relationship conveys that the client element at the tail end is the verification of the supplier on the ____ end will be satisfied by the system being designed
supplier end (the one verifying) has to be a requirement
arrow
test case and ____ are the two most common ways a requirement is verified
block
key idea of a copy relationship
- that the requirement at the client end is a copy of the __________ client at the supplied end
- not a common relationship but its covered in the test
requirement
5 notations for a dependency based relationship
direct notation
compartment notation
callout notation
matrices
________
tables
direct notation advantage its clear to identify the client and supplier relationship
disadvantage
1. can be used when both the client and supplier are on the same diagram.
2. not space efficient .
compartment notation is a more compact way to display a supplier client relationship
disadvantage
1. not every element supports compartment notation
- ports , actors cant have compartment notation
Callout notation - comment like that is anchored
most versatile notation
disadvantage
- takes up alot of space
- not as clear to read like direct notation
Matrix show arrows in cells that show the relationships
disadvantage - it cant display properties or text of a requirement.
table benefits
- all stakeholders know how to read a table
- multiple relationships can be shown on a table
- compared to matrix notation it can display properties
table disadvantages
- takes up alot of space
