Process Component: Design

Description

The Design process component is concerned with the process of designing software. Design focusses on transforming requirements into an logical abstraction of the system structure and behaviour (the Design Model). Design is constrained by the key decisions defined by the software’s architecture, and provides guidance for the implementation.

Design is an important concern in any software system and is a key practice area for which RUP provides process guidance. The inclusion of this process component in this process configuration reflects the intent to use modern software design practices in your software project.

Dependencies

Software Architecture is closely coupled with Design. A process that include the Design component should also include the Architecture component. It is also recommended that the top level Requirements, Management, and Assessment components also be included as a minimum, to provide context.

Content

• Description: GUI Design
  • Description: User-Interface Designer
    • Concepts
      • Concept: User-Centered Design
      • Concept: Usability Testing
    • Description: Design the User Interface
      • Guidelines
        • Guideline: Representing Graphical User-Interfaces
        • Guideline: User Interface (General)
    • Description: Prototype the User-Interface
      • Concepts
        • Concept: Prototypes
  • Description: User-Interface Prototype
  • Description: Navigation Map
    • Examples
      • Example: CSPS Navigation Map - Inception Phase
• Description: Real-Time Design
  • Description: Capsule Designer
    • Description: Capsule Design
      • Guidelines
        • Guideline: Concurrency
        • Guideline: Statechart Diagram
• Description: Database Design
  • Description: Database Designer
    • Concepts
      • Concept: Conceptual Data Modeling
      • Concept: Relational Databases and Object Orientation
      • Concept: Normalization
    • Description: Database Design
  • Description: Data Model
    • Guidelines
      • Guideline: Data Model
      • Guideline: Reverse-engineering Relational Databases
      • Guideline: Forward-Engineering Relational Databases
    • Checklist: Data Model
• Description: Design with Use Cases
  • rup_analysis_model_uc
    • Anonymous: Analysis Use-Case Realization
      • Templates
        • Template: Use-Case-Realization Specification
      • Report: Use-Case Realization
• Description: Designer
  • Concepts
  • Whitepapers
    • Whitepaper: RUP/XP Guidelines: Test-first Design and Refactoring
    • Whitepaper: Developing Large-Scale Systems with the Rational Unified Process
  • Description: Class Design
    • Guidelines
      • Guideline: Statechart Diagram
      • Guideline: Class Diagram
      • Guideline: Aggregation
      • Guideline: Association
      • Guideline: Subscribe-Association
      • Guideline: Generalization
  • Description: Subsystem Design
    • Guidelines
      • Guideline: Statechart Diagram
  • Description: Use-Case Analysis
    • Guidelines
      • Guideline: Use-Case-Analysis Workshop
      • Guideline: Use-Case Realization
      • Guideline: Sequence Diagram
      • Guideline: Communication Diagram
      • Guideline: Analysis Class
  • Description: Use-Case Design
    • Guidelines
      • Guideline: Use-Case Realization
      • Guideline: Sequence Diagram
      • Guideline: Statechart Diagram
  • Description: Design Testability Elements
• Description: Analysis Model
  • Concepts
    • Concept: Analysis Mechanisms
  • Description: Analysis Class
    • Checklist: Analysis Class
    • Guideline: Analysis Class
  • Examples
    • Example: Analysis Model