Artifact:  Development Case

Development Case	The development-case description describes the development process that you have chosen to follow in your project.
Role:	Process Engineer
Enclosed in:	Software Development Plan
Template:	Word Template HTML Template
More Information:	Guidelines:Development Case Guidelines:Process Discriminants Guidelines:Classifying Artifacts Guidelines:Important Decisions in Requirements Guidelines:Important Decisions in Environment Guidelines:Important Decisions in Project Management Guidelines:Important Decisions in Configuration & Change Management Guidelines:Important Decisions in Implementation Guidelines:Important Decisions in Deployment Guidelines:Review Levels Guidelines:Important Decisions in Analysis & Design Guidelines:Important Decisions in Business Modeling Guidelines:Important Decisions in Test Guidelines:Tailoring the Process
Examples:	Development Case Development Case - from the Course Registration System Development Case - from the Collegiate Sports Paging System (e-Business)
Purpose Brief Outline Timing Responsibility Tailoring Annotated Outline (hyperlinks into HTML template in a new window) Additional Information

Input to Activities: Develop Design Guidelines Develop Programming Guidelines Develop Manual Styleguide Select and Acquire Tools Set Up Tools Develop Tool Guidelines Verify Tool Configuration and Installation Develop Business-Modeling Guidelines Develop Use-Case Modeling Guidelines Develop User-Interface Guidelines Develop Test Guidelines Develop Project-Specific Templates Launch Development Case Develop Iteration Plan Compile Software Development Plan Assess Iteration Acquire Staff Develop Development Case

Output from Activities: Develop Development Case

Purpose

The purpose of the Development Case is to capture the tailored process for the individual project.

Brief Outline

(hyperlinks into HTML template in a new window)

• Introduction

  • Purpose

  • Scope

  • Definitions, Acronyms and Abbreviations

  • References

  • Overview

• Overview of the Development Case

  • Lifecycle Model

  • Disciplines

  • Discipline Configuration

  • Artifact Classification

  • Review Procedures

  • Sample Iteration Plans

• Disciplines

  • Business Modeling

  • Requirements

  • Analysis & Design

  • Implementation

  • Testing

  • Deployment

  • Configuration & Change Management

  • Project Management

  • Environment

• Roles 

Timing

The Development Case is created in the early Inception Phase, and is updated throughout the project as needed.

A first version of the development case is created at the onset of the project. It is recommended to develop the development case in increments, covering more and more of the disciplines in each iteration. The first version of the development case will normally only cover a subset of the disciplines. In each of the subsequent iterations, more will be covered by the development case. As you evaluate the results of each iteration the development case is likely to change based on the lessons learned.

Responsibility

The Role: Process Engineer is responsible for creating and maintaining the Development Case.

Tailoring

Normally, a project does not start using all disciplines in the Rational Unified Process™ (RUP). In that case, the corresponding sections can be removed.

If needed, add more information about how to use the artifacts for each discipline. For example, add references to templates used to describe the artifacts.

If needed, add references to guidelines and information that the project wants to use in addition to the RUP®.

Additional Information

Use the development case in parallel with the Iteration Plan for each iteration. The development case tells specifically what parts of each model you have chosen to use in your project.

Copyright  © 1987 - 2001 Rational Software Corporation

Rational Unified Process