Software Development Process: Phases and Deliverables

Software Development Process: Activities

Implementation Process

  • Analysis of System Requirements
  • Design System Architecture
  • Analysis of Software Requirements
  • Design Software Architecture
  • Detailed Design of Software
  • Coding and Testing Software
  • Software Integration
  • Software Qualification Testing
  • System Integration
  • System Qualification Testing
  • Installing Software
  • Support for Software Acceptance

Rational Unified Process (RUP) Phases

  • Inception: The goal in this phase is to determine the project’s vision.
  • Elaboration: At this stage, the objective is to determine the optimal architecture.
  • Construction: At this stage, the objective is to achieve initial operational capability.
  • Transition: The objective is to obtain the release of the project.

Key Deliverables in the Inception Phase

  • Stakeholder Applications: This document contains all requests made on the project, and the approach or response to them.
  • Vision Software Project: This document collects, analyzes, and defines the needs and characteristics of the project at a high level, focusing on stakeholder requirements.
  • Software Development Plan: Describes the key elements of the work plan, including:
    • Stages of development and their completion dates
    • Resources involved in the project development
    • Products of the system with their respective deadlines
    • Team structure
    • Work plan with respective timelines
  • List of Risks: Identifies and assesses risks based on the initial project vision. It involves identifying, analyzing, and prioritizing project risks to determine appropriate risk management strategies.
  • Iteration Plan: This document allows the project manager to plan the activities and tasks for each iteration, identify necessary resources, and track progress. Team members use it to understand their tasks, their purpose, and dependencies.

Comprehensive List of Deliverables

  1. Scope Statement: The present document.
  2. Business Object Model: Describes the performance of each business use case, including internal actors, information handling, and workflow. Uses collaboration diagrams, class diagrams, and activity diagrams.
  3. Use Case Model Business: Represents the system’s functions and the actors who use them, using Use Case Diagrams.
  4. Use Case Specification: Provides a detailed description for complex use cases, using a document template and potentially an Activity Diagram.
  5. User Interface Prototype: Includes drawings on paper, graphical tool drawings, or executable interactive prototypes, depending on project progress.
  6. Analysis and Design Model: Translates use cases into classes, moving from analysis to design, considering the deployment environment.
  7. Iteration Plan: Lists activities and tasks with allocated resources and dependencies, created for each iteration and phase.
  8. Risk Matrix: Lists identified project risks in descending order of importance, with contingency or mitigation plans.
  9. Product: Packaged product files on a CD with installation mechanisms.
  10. Progress Reports: Documents progress and budget versus actual.
  11. Closing Report: Includes release and acceptance letters, and a final results report.