Customer and Sales Agent always can trigger the exact same number of use cases
The use cases of Customer and Sales Agent are independent of one another
Sales Agent can trigger all use cases connected to Customer
Customer can trigger all use cases connected to Sales Agent
Specificity
Conformity
Multiplicity
Encapsulation
Substitutability
True
False
True
False
True
False
Stakeholders have great difficulty with extend relationships
Generalization of actors and use cases should be avoided
Generally, all stakeholders can easily understand actors and use cases
Heavy use of include can make use case models easier to understand
How the system should do what the actors need
Extensive detailed use case descriptions
The design solution for system functionality
What the actors need the system to do
True
False
True
False
May be prefixed or postfixed with a small black arrowhead
Should be a verb or verb phrase
Should be in lowerCamelCase
All of the above
Associations
Name
Attributes
Operations
Connections
Dependencies
Objects
Associations
Name
Multiplicity
Scope
Navigability
Role name
True
False
Repeating
Reflexive
Refractive
Recursive
A to B is navigable
B to A is not navigable
A to B is not navigable
B to A is navigable
True
False
Include implementation details
Avoid implementation details
Class name
Operations
Attributes
Visibility
True
False
Maximize
Minimize
Maximize
Minimize
Beware of many very small classes
About three to five attributes per class
Beware of omnipotent classes
Beware of "functoids"
Beware of few, but very large classes
CRC Analysis
UP Workflows
SEP Phases
RUP Stereotypes
Noun/Verb Analysis
Associations
Responsibilities
Stereotypes
Attributes
Classes
Wait!
Here's an interesting quiz for you.