Role:  Designer

The designer role defines the responsibilities, operations, attributes, and relationships of one or several classes, and determines how they will be adjusted to the implementation environment. In addition, the designer role may have responsibility for one or more design packages, or design subsystems, including any classes owned by the packages or subsystems.

Staffing

The designer must have a solid working knowledge of:

• use-case modeling techniques
• system requirements
• software design techniques, including object-oriented analysis and design techniques, and the Unified Modeling Language
• technologies with which the system will be implemented

In addition, the designer must:

• understand the architecture of the system, as represented in the Artifact: Software Architecture Document
• understand the role of system testing 
• have a working knowledge of configuration management principles in general and the Artifact: CM Plan specifically

Copyright  © 1987 - 2001 Rational Software Corporation

Rational Unified Process