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 conform to styleguide for class diagram ?
Answer

1. Use Common Terminology for Names

2. Prefer Complete Singular Nouns for Class Names

3. Name Operations with a Strong Verb

4. Name Attributes With a Domain-Based Noun

5. Do Not Model Scaffolding Code. Scaffolding code refers to the attributes and operations required to implement basic functionality within your classes, such as the code required to implement relationships with other classes. Figure 3 depicts the difference between the OrderItem class without scaffolding code and with it.

6. Never Show Classes With Just Two Compartments

7. Label Uncommon Class Compartments

8. Include an Ellipsis ( . . . ) At The End of Incomplete Lists

9. List Static Operations/Attributes Before Instance Operations/Attributes

10. List Operations/Attributes in Decreasing Visibility

11. For Parameters That Are Objects, Only List Their Type

12. Develop Consistent Method Signatures

13. Avoid Stereotypes Implied By Language Naming Conventions

14. Indicate Exceptions In An Operation's Property String. Exceptions can be indicated with a UML property string, an example of which is shown in Figure 4.


Question
How to conform to styleguide for class diagram ?
Answer
?

Question
How to conform to styleguide for class diagram ?
Answer

1. Use Common Terminology for Names

2. Prefer Complete Singular Nouns for Class Names

3. Name Operations with a Strong Verb

4. Name Attributes With a Domain-Based Noun

5. Do Not Model Scaffolding Code. Scaffolding code refers to the attributes and operations required to implement basic functionality within your classes, such as the code required to implement relationships with other classes. Figure 3 depicts the difference between the OrderItem class without scaffolding code and with it.

6. Never Show Classes With Just Two Compartments

7. Label Uncommon Class Compartments

8. Include an Ellipsis ( . . . ) At The End of Incomplete Lists

9. List Static Operations/Attributes Before Instance Operations/Attributes

10. List Operations/Attributes in Decreasing Visibility

11. For Parameters That Are Objects, Only List Their Type

12. Develop Consistent Method Signatures

13. Avoid Stereotypes Implied By Language Naming Conventions

14. Indicate Exceptions In An Operation's Property String. Exceptions can be indicated with a UML property string, an example of which is shown in Figure 4.

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

UML 2 Class Diagram Guidelines
ure 3. The OrderItem class with and without scaffolding code. Figure 4. Indicating the exceptions thrown by an operation. + findAllInstances(): Vector {exceptions=NetworkFailure, DatabaseError} <span>Use Common Terminology for Names Prefer Complete Singular Nouns for Class Names Name Operations with a Strong Verb Name Attributes With a Domain-Based Noun Do Not Model Scaffolding Code. Scaffolding code refers to the attributes and operations required to implement basic functionality within your classes, such as the code required to implement relationships with other classes. Figure 3 depicts the difference between the OrderItem class without scaffolding code and with it. Never Show Classes With Just Two Compartments Label Uncommon Class Compartments Include an Ellipsis ( . . . ) At The End of Incomplete Lists List Static Operations/Attributes Before Instance Operations/Attributes List Operations/Attributes in Decreasing Visibility For Parameters That Are Objects, Only List Their Type Develop Consistent Method Signatures Avoid Stereotypes Implied By Language Naming Conventions Indicate Exceptions In An Operation's Property String. Exceptions can be indicated with a UML property string, an example of which is shown in Figure 4. 3. Interfaces An interface is a collection of operation signature and/or attribute definitions that ideally defines a cohesive set of behaviors. Interfaces are implemented, "realized" i

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.