Use Case Realization: the Design Discipline Within Up Iterations
Chapter 8: Use Case Realization: The Design Discipline Within UP Iterations
Blueprints
* Initial drawings and builds a set of detailed plans * Design models
Object – Oriented Design * Process by which a set of detailed object – oriented design model is built, which the programmers will later use to write code and test the new system
System Design * A bridge between a user’s requirements and programming for the new system
Object – Oriented Programs * Consists of a set of objects that cooperate to accomplish a result * Event – driven
Instantiation
* Creation of an object based on the template provided by the class definition
Multilayer Design * Dividing the objects into different groups
Design Class Diagrams * End result of the design process * Summary of the final design that was developed using the detailed sequence diagrams * Document and describe the programming classes
Statechart Diagram * Captures information about the valid states and transitions of an object * Used in the design discipline to define the behavioral constraints of the system classes related during design and describe the method logic within class methods
Package Diagram * Denote which classes work together as a subsystem
Realization of Use Cases * Specification of all detailed system processing for each use case * Determine what objects collaborate by sending messages to each other
Object – Oriented Design Process: 1. Create first – cut model of the design class diagrams 2. Develop interaction diagrams for each use case or scenario 3. Update the design class diagrams (names, attributes, and navigation visibility) 4. Partition the design class diagrams into related functions using package diagrams
Interaction Diagrams * Used to refine a design class diagram as development progresses * At the heart of object – oriented design
Stereotype
* A way of categorizing a model element by its
Blueprints
* Initial drawings and builds a set of detailed plans * Design models
Object – Oriented Design * Process by which a set of detailed object – oriented design model is built, which the programmers will later use to write code and test the new system
System Design * A bridge between a user’s requirements and programming for the new system
Object – Oriented Programs * Consists of a set of objects that cooperate to accomplish a result * Event – driven
Instantiation
* Creation of an object based on the template provided by the class definition
Multilayer Design * Dividing the objects into different groups
Design Class Diagrams * End result of the design process * Summary of the final design that was developed using the detailed sequence diagrams * Document and describe the programming classes
Statechart Diagram * Captures information about the valid states and transitions of an object * Used in the design discipline to define the behavioral constraints of the system classes related during design and describe the method logic within class methods
Package Diagram * Denote which classes work together as a subsystem
Realization of Use Cases * Specification of all detailed system processing for each use case * Determine what objects collaborate by sending messages to each other
Object – Oriented Design Process: 1. Create first – cut model of the design class diagrams 2. Develop interaction diagrams for each use case or scenario 3. Update the design class diagrams (names, attributes, and navigation visibility) 4. Partition the design class diagrams into related functions using package diagrams
Interaction Diagrams * Used to refine a design class diagram as development progresses * At the heart of object – oriented design
Stereotype
* A way of categorizing a model element by its