





Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
An overview of class diagrams, discussing the importance of having many simple classes versus few complex ones, and outlining steps for finding and defining classes, their attributes, and operations. It also covers guidelines for extracting classes from specifications and assigning responsibilities.
Typology: Slides
1 / 9
This page cannot be seen from the preview
Don't miss anything!






Classes have simple behavior Less encapsulation More reusable Easier to Implement
More encapsulation, more private behavior. Less reusable Takes more time to implement More complex to implement
Class Operations Methods States Attributes Dependencies Associations Generalizations
Model Physical Objects. Model Conceptual Entities. Use a Single term for each concept. Be wary of the use of adjectives.
Recall the purpose of each class, as implied by its name and specified in the statement of purpose. Extract responsibilities from the specification by looking for actions and information. Identify responsibilities implied by the relationships between classes.
Evenly distributed system intelligence. State responsibility as generally as possible. Keep behavior with related information. Keep information about one thing in one place. Share responsibilities among related classes.