Do you want BuboFlash to help you learning these things? Or do you want to add or correct something? Click here to log in or create user.


  • Presentation
  • Question
  • Answer

Question
How to model relationships ?
Answer

1. Model Relationships Horizontally

2. Collaboration Indicates Need for a Relationship

3. Model a Dependency When The Relationship is Transitory

4. Depict Similar Relationships Involving A Common Class As A Tree. In Figure 6 you see that both Delivery and Order have a dependency on OIDGenerator . Note how the two dependencies are drawn in combination in "tree configuration", instead of as two separate lines, to reduce clutter in the diagram.

5. Always Indicate the Multiplicity

6. Avoid a Multiplicity of "*"

7. Replace Relationships By Indicating Attribute Types. In Figure 7 you see that Customer has a shippingAddress attribute of type Address - part of the scaffolding code to maintain the association between customer objects and address objects.

8. Do Not Model Implied Relationships

9. Do Not Model Every Single Dependency

10. Center Names on Associations

11. Write Concise Association Names In Active Voice

12. Indicate Directionality To Clarify An Association Name

13. Name Unidirectional Associations In The Same Direction

14. Word Association Names Left-To-Right

15. Indicate Role Names When Multiple Associations Between Two Classes Exist

16. Indicate Role Names on Recursive Associations

17. Make Associations Bi-Directional Only When Collaboration Occurs In Both Directions. The lives at association of Figure 9 is uni-directional.

18. Redraw Inherited Associations Only When Something Changes

19. Question Multiplicities Involving Minimums And Maximums


Question
How to model relationships ?
Answer
?

Question
How to model relationships ?
Answer

1. Model Relationships Horizontally

2. Collaboration Indicates Need for a Relationship

3. Model a Dependency When The Relationship is Transitory

4. Depict Similar Relationships Involving A Common Class As A Tree. In Figure 6 you see that both Delivery and Order have a dependency on OIDGenerator . Note how the two dependencies are drawn in combination in "tree configuration", instead of as two separate lines, to reduce clutter in the diagram.

5. Always Indicate the Multiplicity

6. Avoid a Multiplicity of "*"

7. Replace Relationships By Indicating Attribute Types. In Figure 7 you see that Customer has a shippingAddress attribute of type Address - part of the scaffolding code to maintain the association between customer objects and address objects.

8. Do Not Model Implied Relationships

9. Do Not Model Every Single Dependency

10. Center Names on Associations

11. Write Concise Association Names In Active Voice

12. Indicate Directionality To Clarify An Association Name

13. Name Unidirectional Associations In The Same Direction

14. Word Association Names Left-To-Right

15. Indicate Role Names When Multiple Associations Between Two Classes Exist

16. Indicate Role Names on Recursive Associations

17. Make Associations Bi-Directional Only When Collaboration Occurs In Both Directions. The lives at association of Figure 9 is uni-directional.

18. Redraw Inherited Associations Only When Something Changes

19. Question Multiplicities Involving Minimums And Maximums

If you want to change selection, open document below and click on "Move attachment"

UML 2 Class Diagram Guidelines
on a UML class diagram we'll consider it a relationship. Figure 6. Shipping an order. Figure 7. Modeling an order. Figure 8. Professors and seminars. Figure 9. Modeling people at a university. <span>Model Relationships Horizontally Collaboration Indicates Need for a Relationship Model a Dependency When The Relationship is Transitory Depict Similar Relationships Involving A Common Class As A Tree. In Figure 6 you see that both Delivery and Order have a dependency on OIDGenerator. Note how the two dependencies are drawn in combination in "tree configuration", instead of as two separate lines, to reduce clutter in the diagram. Always Indicate the Multiplicity Avoid a Multiplicity of "*" Replace Relationships By Indicating Attribute Types. In Figure 7 you see that Customer has a shippingAddress attribute of type Address - part of the scaffolding code to maintain the association between customer objects and address objects. Do Not Model Implied Relationships Do Not Model Every Single Dependency Center Names on Associations Write Concise Association Names In Active Voice Indicate Directionality To Clarify An Association Name Name Unidirectional Associations In The Same Direction Word Association Names Left-To-Right Indicate Role Names When Multiple Associations Between Two Classes Exist Indicate Role Names on Recursive Associations Make Associations Bi-Directional Only When Collaboration Occurs In Both Directions. The lives at association of Figure 9 is uni-directional. Redraw Inherited Associations Only When Something Changes Question Multiplicities Involving Minimums And Maximums 6. Inheritance Guidelines Inheritance models "is a" and "is like" relationships, enabling you to easily reuse existing data and code. When "A" inherits from "B" we say that "A" is the s

Summary

statusnot learnedmeasured difficulty37% [default]last interval [days]               
repetition number in this series0memorised on               scheduled repetition               
scheduled repetition interval               last repetition or drill

Details

No repetitions

Discussion

Do you want to join discussion? Click here to log in or create user.