A sample process

The next several sections provide an outline of a sample object-oriented software development process. Specifically, this process is based on the text ``Use Case Driven Object Modeling with UML, A Practical Approach'' by Rosenberg and Scott[4]. This is a real process, based on the theory outlined in the Rational Unified Process.

• Domain modeling
  • What is a class?
    • Attributes
    • Behaviors
  • Discover classes
    • Where else do classes come from?
  • Build generalization relationships
  • Build associations between classes
  • Mine legacy documentation for domain classes
  • Wrapping up domain modeling
    • Continue to iterate and refine
    • Three key principles
• Use case modeling
  • Actors
    • Use Cases
    • Questions to help identify use cases[11]
    • Use case diagrams
    • Use case diagrams - include and extend
    • Wrapping Up Use Case Modeling
    • .
• Robustness analysis
  • Definitions
  • Key roles of robustness analysis
  • Closer look at object types
    • Boundary objects
    • Entity objects
    • Control objects
  • Performing robustness analysis
    • .
• Interaction modeling
  • Introduction
  • Goals of Interaction Modeling
  • Sequence Diagrams
    • Four Sequence Diagram Elements
  • Getting Started
  • Putting Methods on Classes
    • Which Methods Belong With Objects
  • Completing Interaction Modeling
• Collaboration and State Modeling
  • Introduction
  • Collaboration diagrams
  • State diagrams
    • How many state diagrams are needed?
  • Activity diagrams
• Addressing Requirements
  • Introduction
  • Objectives
  • What is a Requirement?
    • Types of Requirements
  • Use Cases and Requirements
  • Requirements Traceability
• Survey of Design Patterns
  • Factory pattern example
    • .