Term
| usually what should be the name for a use case? |
|
Definition
| action of what is to be accomplished |
|
|
Term
| usually what's the length of a textual use case description? |
|
Definition
|
|
Term
| why is it important to start flow of events like "the actor" or "the system" |
|
Definition
| easy to indicate which one is responsible for what |
|
|
Term
| what is the main goal for object modeling? |
|
Definition
|
|
Term
| what are 4 approaches to find classes? |
|
Definition
1. application domain approach
2. systematic approach
3. design patterns approach
4. component-based approach |
|
|
Term
| after objects are found, how to classify object's type? |
|
Definition
entity: data, core
boundary: interaction between users
control: controls |
|
|
Term
| what are 2 reasons that class identification is hard? |
|
Definition
1. boundary of the system
2. analysis is needed |
|
|
Term
| draw UML representation for each class of objects |
|
Definition
|
|
Term
| what's abbott's technique? |
|
Definition
pick a flow of event from use case
1. nouns are candidates for objects and verbs are candidates for operations
2. real world entities? real world procedures? interface artifacts? |
|
|
Term
| why there are 3 types of objects? |
|
Definition
|
|
Term
| what are two types of people that uses class diagrams? |
|
Definition
1. application domain expert
2. developer |
|
|
Term
| what are two heuristics for identifying classes from dynamic models? |
|
Definition
1. actions in state machine diagrams are candidates for public operations in class
2. activity lines in sequence diagrams are candidate for objects |
|
|
Term
| before getting started to draw diagrams for dynamic models, what are 3 things you need to identify? |
|
Definition
1. identify events
2. identify operations
3. identify participating objects |
|
|
Term
| what's heuristics for sequence diagrams in terms of layout, creation of objects, and access of objects? |
|
Definition
layout: 1st column should be actor, 2nd column should be boundary object, 3rd column should be control object
creation of objects: boundary objects create control objects at beginning of event flow
access of objects: entity objects can be access by control objects and boundary objects, but entity objects should not access boundary or control objects |
|
|
Term
| from looking at sequence diagram, how can you tell if the system is centralized or decentralized? |
|
Definition
|
|
Term
| in state machine diagram, how to show if something is event? |
|
Definition
|
|
Term
| in state machine diagram, how to show condition? |
|
Definition
|
|
Term
| in state machine diagram, how to show actions? |
|
Definition
|
|
Term
| how can state machine diagrams help UI design? |
|
Definition
states: name of screens
actions: bullets under the screen name
transitions: result of interface exit actions |
|
|
