UML and Object-Oriented Design

7.

Object-Oriented Analysis and Design Process

7.1.

Requirements Analysis

7.1.1.

Stakeholder Identification

7.1.2.

Requirements Gathering Techniques

7.1.2.1.

7.1.2.2.

7.1.2.3.

7.1.2.4.

Document Analysis

7.1.3.

Functional Requirements

7.1.3.1.

Use Case Identification

7.1.3.2.

Actor Identification

7.1.3.3.

System Boundary Definition

7.1.4.

Non-Functional Requirements

7.1.4.1.

Performance Requirements

7.1.4.2.

Security Requirements

7.1.4.3.

Usability Requirements

7.1.4.4.

Reliability Requirements

7.1.5.

Use Case Documentation

7.1.5.1.

Use Case Templates

7.1.5.2.

Main Success Scenarios

7.1.5.3.

Alternative Flows

7.1.5.4.

Exception Handling

7.1.5.5.

Preconditions and Postconditions

7.2.

Domain Modeling

7.2.1.

Conceptual Model Development

7.2.2.

Class Identification Techniques

7.2.2.1.

Noun Extraction

7.2.2.2.

Domain Vocabulary Analysis

7.2.2.3.

Responsibility Assignment

7.2.3.

Initial Class Diagram Creation

7.2.3.1.

Candidate Classes

7.2.3.2.

Class Relationships

7.2.3.3.

Attribute Identification

7.2.4.

Domain Rules and Constraints

7.2.5.

Model Validation

7.2.5.1.

Walkthrough Scenarios

7.2.5.2.

Stakeholder Review

7.3.

System Architecture Design

7.3.1.

Architectural Patterns

7.3.1.1.

Layered Architecture

7.3.1.2.

Model-View-Controller

7.3.1.3.

Client-Server Architecture

7.3.1.4.

Service-Oriented Architecture

7.3.2.

System Decomposition

7.3.2.1.

Subsystem Identification

7.3.2.2.

Interface Definition

7.3.2.3.

Dependency Management

7.3.3.

Package Organization

7.3.3.1.

Package Structure

7.3.3.2.

Package Dependencies

7.3.3.3.

Namespace Design

7.3.4.

Component Architecture

7.3.4.1.

Component Identification

7.3.4.2.

Component Interfaces

7.3.4.3.

Component Dependencies

7.4.

Detailed Design

7.4.1.

Responsibility Assignment

7.4.1.1.

Class Responsibilities

7.4.1.2.

Method Allocation

7.4.1.3.

Collaboration Design

7.4.2.

Interaction Design

7.4.2.1.

Scenario Modeling

7.4.2.2.

Sequence Diagram Development

7.4.2.3.

Communication Patterns

7.4.3.

Class Design Refinement

7.4.3.1.

Method Signatures

7.4.3.2.

Attribute Specifications

7.4.3.3.

Visibility Decisions

7.4.4.

Design Pattern Application

7.4.4.1.

Pattern Selection

7.4.4.2.

Pattern Integration

7.4.4.3.

Pattern Customization

7.4.5.

7.4.5.1.

Stateful Object Identification

7.4.5.2.

State Machine Design

7.4.5.3.

State Transition Logic

7.4.6.

Error Handling Design

7.4.6.1.

Exception Hierarchies

7.4.6.2.

Error Recovery Strategies

7.5.

Design Validation and Verification

7.5.1.

7.5.1.1.

7.5.1.2.

Walkthrough Sessions

7.5.1.3.

Inspection Processes

7.5.2.

7.5.2.1.

Design Simulation

7.5.2.2.

Prototype Development

7.5.2.3.

Model Validation

7.5.3.

Traceability Management

7.5.3.1.

Requirements Traceability

7.5.3.2.

Design Decision Documentation

7.6.

Implementation Considerations

7.6.1.

Code Generation from Models

7.6.1.1.

Model-to-Code Transformation

7.6.1.2.

7.6.1.3.

Automated Generation Tools

7.6.2.

Forward Engineering

7.6.2.1.

Model-Driven Development

7.6.2.2.

Code Synchronization

7.6.3.

Reverse Engineering

7.6.3.1.

Code-to-Model Extraction

7.6.3.2.

Legacy System Analysis

7.6.4.

Round-Trip Engineering

7.6.4.1.

Model-Code Synchronization

7.6.4.2.

Change Management

7.6.4.3.

Version Control Integration

Previous

6. Design Patterns in UML

Go to top

Next

8. UML Tools and Methodologies