• Use-Case Analysis

• Analysis Class
• Analysis Class
• Use-Case Realization

• Analysis Model
• Use-Case Realization

The designer must have a solid working knowledge of:

• system requirements
• the architecture of the system
• software design techniques, including object-oriented analysis and design techniques, and the Unified Modeling Language
• technologies with which the system will be implemented
• project guidelines on how the design relates to the implementation, including the level of detail expected in the design before implementation should proceed.

A designer may be assigned responsibility for implementing a structural part of the system (such as a class or implementation subsystem), or a functional part of the system, such as a use-case realization or feature that crosses classes/subsystems.

It is common for a person to act as both implementer and designer, taking on the responsibilities of both roles.

It is possible for design responsibilities to be divided, such that a high level sketch of the design is the responsibility of one designer, while detailed design (such as details of operation signatures, or the identification and design of helper classes) is deferred to another designer who also acts as the implementer.

• Analysis Class
• Design Class
• Design Package
• Design Subsystem
• Use-Case Realization

• Aggregation
• Association
• Class Diagram
• Design Class
• Design Package
• Design Subsystem
• Generalization
• Interface
• Subscribe-Association
• Use-Case-Analysis Workshop
• Use-Case Realization

• RUP/XP Guidelines: Test-first Design and Refactoring
• Developing Large-Scale Systems with the Rational Unified Process