CPlusOOP
SiteMap
OO Analysis
Problem Analysis
Problem Analysis
«Prev
OO-Design
Problem Analysis
Review PLC
Purpose Scope Analysis
Problem Domain Classes
Identify Classes Objects
Class Diagram Notation
Diagram Associations
Basic Object Modeling
Multiplicity OO Modeling
Define Constraints
Modeling Aggregation
Modeling Composition
Modeling Generalization
Advanced Associations
Qualifiers Reduce Multiplicity
Many to ManyAssociations
Problem Analysis Conclusion
Sequence Diagrams
Sequence Diagram Notation
Applying Sequence Diagram
Applying Sequence Diagram-Quiz
Modeling Sequences Scenarios
Mapping Events Objects
Interfaces, events ,operations
Discover Attribute Information
Sequence Diagram - Conclusion
Interaction Diagram - Quiz
Model Reconciliation
Reconcile Sequence Diagrams
Test Interfaces
Model Refinement
Refactoring Patterns
Encapsulation Principles
Cohesion Coupling Defined
Attribute Responsibility Allocation
Class Description Operations
Refining Object Conclusion
Qualifiers Reduce Multiplicity
1) Start with the class diagram of Customer and Order. The association shows one customer places zero or more orders.
2) To look up a customer's orders individually, identify a field that will uniquely identify the order. The attributes reveal the order number to be a unique identifier.
UML Distilled
3) Place the qualifier box next to the class that will use it. The customer objects need to look up unique orders by ordernumber, so place the qualifier box next to the customer class.
4) Next copy the order number attribute name and data type and place them in the qualifier box.
5) Reduce the multiplicity to show that the ordernumber qualifier allows us to reference exactly one order at a time. The multiplicity is reduced to 1 because the qualifier is a unique value. If the qualifier is not unique, then it remains zero or more (*), but the actual number of objects decreases.