Question | Answer |
Class definition approaches | 1) Application domain approach
2) Syntactic approach (analyze use case texts)
3) Design patterns approach
4) Component-based approach |
Object Types | 1) Bounday Obejcts
2) Control Obejcts
3) Entity Objects |
Mapping parts of speech to model components (Abbot’s Technique) | 1) proper noun -> object
2) common noun -> class
3) doing verb -> operation
4) having verb -> aggregation
5) modal verb -> contraint
6) Adjective -> attribute
7) Transitive verb -> operation
8) Intransitive verb -> constrain, class, association |
UML is extendable with | 1) tags
2) Constrains
3) Stereotypes |
UML stereotypes | For example, when modeling a network you might need to have symbols for representing routers and hubs. By using stereotyped nodes you can make these things appear as primitive building blocks. |
Dynamic Models | 1) Interaction Diagrams
2) State chart diagrams |
Interaction diagrams | 1) Sequence Diagram
2) Collaboration Diagram |
State Chart Diagram | 1) A state machine that describes the response of an object of a given class to the receipt of outside stimuli (Events).
2) Activity Diagram |
Layout of Sequence Diagrams | Layout:
1st column: Should be the actor of the use case
2nd column: Should be a boundary object
3rd column: Should be the control object that manages the rest of the use case |
Fork Diagram (Sequence) | The dynamic behavior is placed in a single object, usually a control object |
Stair Diagram (Sequence) | The dynamic behavior is distributed. Eacho bject delegates responsibility to other objects |
State | An abstraction of the attributes of a class ◦ State is the aggregation of several attributes a
class |
Verification | Verification is an equivalence check between the transformation of two models |
Validation | Validation is the comparison of the model with reality |