Object-Oriented Design II
Preparation
Have ArgoUML downloaded and installed on your computer. See http://argouml.tigris.org/.
Please be aware the ArgoUML supports version 1.4 of the Unified Modeling Language (UML) specification. Some of the diagram elements may differ from those presented in class.
Reading
None
Objectives
- Know HP’s Design Quality Attributes
- Know some common symbology used for object-oriented design classes
- Know the design class quality characteristics of complete and sufficient, primitiveness, high cohesion, and low coupling
- Apply the five common design activities to a specific development.
- Make use of ArgoUML to create UML diagrams and generate corresponding Java code.
Notes
-
HP’s Design Quality Attributes (circa 1987)
- Functionality
- Feature set and capabilities, includes Security
- Usability
- Ease-of-use, aesthetics, consistency, and documentation
- Reliability
- Low frequency and severity of faults, accuracy of output, long MTTF, fast recovery
- Performance
- Processing speed, response time, resource consumption, throughput, efficiency
- Supportability
- Easy to extensibility, adaptability, serviceability
-
Know common symbology used for Object-Oriented Design Classes
- User Interface (boundary) classes
- Business Domain (entity) classes
- Process (controller) classes
- Persistent (data store) classes
- System classes
-
Know the design class quality characteristics
- Complete and Sufficient
- All necessary attributes and methods
- Primitiveness
- Each method focused on accomplishing one service
- High Cohesion
- Single-minded focus
- Low Coupling
- Collaboration with other classes kept to a minimum
-
Recall the five common design activities:
- Define the context and modes of use of the system
- Design the system architecture
- Identify the principal system objects
- Develop design models
- Specify object interfaces