<Project Name>

Development Case

 

Version <1.0>

 

 

[Note: The following template is provided for use with the Rational Unified Process (RUP). Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]

Important: There are hyperlinks to pages in the RUP in this template. These hyperlinks must be modified when you create your own development case. For example, assume that the RUP is installed in a folder named 'RationalUnifiedProcessX.X'. Also assume that you put the development case at the same level as the RUP. In that case you should: 
   Search: "../../../"
   Replace: "RationalUnifiedProcessX.X"]

Revision History

Date

Version

Description

Author

<dd/mmm/yy>

<x.x>

<details>

<name>

 

 

 

 

 

 

 

 

 

 

 

 

 

Table of Contents

 

 

1. Introduction (to top)

1.1 Purpose (to top)

[A brief description of the purpose of the Development Case, for example:
"The purpose of the document is to describe the development process for the <<project name>>."
Also give a brief description of what the Development Case applies to; what is affected or influenced by this document.]

1.2 Scope (to top)

[A brief description of the scope of this Development Case; what Projects it is associated with, and anything else that is affected or influenced by this document.]

1.3 Definitions, Acronyms, and Abbreviations (to top)

[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the Development Case. This information may be provided by reference to the project's Glossary.]

1.4 References (to top)

[This subsection provides a complete list of all documents referenced elsewhere in the Development Case. Identify each document by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]

1.5 Overview (to top)

[This subsection briefly describes what the rest of the Development Case contains and explains how the document is organized.]

2. Overview of the Development Case (to top)

2.1 Lifecycle Model (to top)

[Briefly describe the lifecycle model employed by the project; containing descriptions of the milestones and their purpose. The purpose is to serve as an introduction to the rest of the development case, not to be a project plan.]

2.2  Disciplines (to top)

[Describe which disciplines the Development Case covers.]

2.3  Discipline Configuration  (to top)

[Explain how the discipline configuration works. Explain the sections in the Discipline sections, using the following text as a starting point:]

The purpose of this section is to explain how the discipline configuration works. This includes an explanation of the purpose for the various tables and for each of the sections that describe the various disciplines listed in the section titled Disciplines.

2.3.1 Workflow
[This section needs to detail any changes made to the structure of the workflow itself. Typical changes include adding activities to describe company-specific ways of working, or removing activities.]
2.3.2 Artifacts
[Using a tabular format, this section describes how the artifact will be used. Additional 'local' artifacts can be added to the table as needed.] 
 
Artifacts How to use Review Details Tools used Templates/
Examples
Incep Elab Const Trans
               
 

Explanation of the table

Column Name Purpose Contents and Comments
'Artifacts'

[The name of the artifact.] 

[A reference to the artifact in the RUP or to a local artifact definition held as part of the development case.] 

'How to use'

[Qualify how the artifact is used across the lifecycle.]

[Decide for each phase: 

  • Must have

  • Should have

  • Could have

  • Won't have

These are defined in Guidelines: Classifying Artifacts.] 

'Review Details'

[Define the review level and review the procedures to be applied to the artifact.] 

[Decide on the review level: 

  • Formal-External

  • Formal-Internal

  • Informal

  • None

For details, see Guidelines: Review Levels.

Also add a reference to the definition and detail of the relevant review procedures. The reference could point to either the RUP or to the general Review Procedure section in the Development Case. More specific review procedures are defined under the subsection titled Additional Review Procedures.]

'Tools used'

[Definition of the tool or tools used to produce the artifact.]

[Reference the details of the tools used to develop and maintain this artifact.]

'Templates/Examples'

[The templates to be used and examples of artifacts using the templates.]

[Reference the templates and examples. This could be references to either the templates and examples in the RUP or to local templates and examples. This column may also contain references to actual artifacts to provide additional help to the project members.]

2.3.3 Notes on Artifacts
[This section has three main purposes: 
 
Artifacts How to Use Reason
 
 
 
2.3.4 Reports
[This section lists the reports to be used. Additional 'local' reports can be added to the table as needed.]
 
Reports How to use Templates/Examples Tools Used
   
 
 
2.3.5 Notes on the Reports
[This section has two purposes. First, it will list all reports that the project has decided it 'Won't' use and the motives behind why it decided not to use them. Secondly, if the Development Case is an organization-level use case, this is where you add notes on what each project needs to consider when they decide what to do with the report.]
2.3.6 Additional Review Procedures
[This section captures any additional review procedures that are required for the artifacts used in the discipline. These supplement the general "Review Procedures" described in "Overview of the Development Case" section.]
2.3.7 Other Issues
[This section captures any outstanding issues with the discipline's configuration and can be used as an issues list when the Development Case is being built.]
2.3.8 Configuring the Discipline
[This section is used if the development case is an organization-level development case. This section contains references to helpful information for use when configuring the discipline. This section can be removed by a project.] 

2.4 Artifact Classification (to top)

[Introduce the artifacts and the classification scheme, using the following text as a starting point:]

An artifact is a deliverable of the process. It is often developed within one discipline, though there are exceptions. The artifacts are organized in the discipline where it's created. To describe how an artifact needs to be used, use the following classification scheme (see Guidelines: Classifying Artifacts for details): 

2.5 Review Procedures (to top)

[Introduce the review levels and any additional review procedures, using the following text as a starting point:]

This project uses the following review levels:  For details see Guidelines: Review Levels.

2.6 Sample Iteration Plans  (to top)

2.6.1 Inception Phase
[List the sample iteration plans used during Inception.]
2.6.2 Elaboration Phase
[List the sample iteration plans used during Elaboration.]
2.6.3 Construction Phase
[List the sample iteration plans used during Construction.]
2.6.4 Transition Phase
[List the sample iteration plans used during Transition.]

3. Disciplines (to top)

3.1 Business Modeling (to top)

[See the section titled Discipline Configuration that describes what each of the following sections needs to contain.]
3.1.1 Workflow
3.1.2 Artifacts
 
Artifacts How to use Review Details Tools used Templates/
Examples
Incep Elab Const Trans
Business Analysis Model
 
 
 
 
 
 
 

Business Entity

 
 
 
 
 
 
 

Business Event

 
 
 
 
 
 
 

Business System

 
 
 
 
 
 
 

Business Use-Case Realization

 
 
 
 
 
 
 

Business Worker

 
 
 
 
 
 
 
Business Architecture Document
 
 
 
 
 
 
 
Business Glossary
 
 
 
 
 
 
 
Business Goal
 
 
 
 
 
 
 
Business Rule
 
 
 
 
 
 
 
Business Use-Case Model
 
 
 
 
 
 
 

Business Actor

 
 
 
 
 
 
 

Business Use Case

 
 
 
 
 
 
 
Business Vision
 
 
 
 
 
 
 
Supplementary Business Specification
 
 
 
 
 
 
 
Target-Organization Assessment
 
 
 
 
 
 
 
3.1.3 Notes on the Artifacts
 
Artifacts How to Use Reason
 
 
 
3.1.4 Reports
 
Reports How to use Templates/Examples Tools Used
Business Actor  
 
 
Business Analysis Model Survey  
 
 
Business Entity  
 
 
Business Rules Survey  
 
 
Business Use-Case  
 
 
Business Use-Case Realization  
 
 
Business Use-Case Model Survey  
 
 
Business Worker  
 
 
3.1.5 Notes on the Reports
3.1.6 Additional Review Procedures
3.1.7 Other Issues
3.1.8 Configuring the Discipline

3.2 Requirements (to top)

[See the section titled Discipline Configuration that describes what each of the following sections needs to contain.]
3.2.1 Workflow
3.2.2 Artifacts
 
Artifacts How to use Review Details Tools used Templates/
Examples
Incep Elab Const Trans
Glossary              
Requirements Attributes              
Requirements Management Plan              
Stakeholder Requests              
Software Requirement              
Software Requirements Specification              
Storyboard              
Supplementary Specifications              
Use-Case Model              

Actor

 
 
 
 
 
 
 

Use Case

             

Use-Case Package

             
Vision              
3.2.3 Notes on the Artifacts
 
Artifacts How to Use Reason
 
 
 
3.2.4 Reports
 
Reports How to Use Templates/Examples Tools Used
Actor      
Use-Case  
 
 
Use-Case Model Survey  
 
 
3.2.5 Notes on the Reports
3.2.6 Additional Review Procedures
3.2.7 Other Issues
3.2.8 Configuring the Discipline

3.3 Analysis & Design (to top)

[See the section titled Discipline Configuration that describes what each of the following sections needs to contain.]
3.3.1 Workflow
3.3.2 Artifacts
 
Artifacts How to use Review Details Tools used Templates/
Examples
Incep Elab Const Trans
Analysis Model
 
 
 
 
 
 
 

Analysis Class

 
 
 
 
 
 
 
Architectural Proof-Of-Concept              
Data Model              
Deployment Model              
Design Model              

Capsule

             

Design Class

             

Design Package

             

Design Subsystem

             

Event

             

Interface

             

Protocol

             

Signal

             

Test Design

             

Testability Class

             

Use-Case Realization

             
Navigation Map              
Reference Architecture              
Software Architecture Document              
User-Interface Prototype              
3.3.3 Notes on the Artifacts
 
Artifact How to Use Reason
 
 
 
3.3.4 Reports
 
Reports How to Use Templates/Examples Tools Used
Class      
Design-Model Survey      
Design Package/Subsystem      
Use-Case Realization      
3.3.5 Notes on the Reports
3.3.6 Additional Review Procedures
3.3.7 Other Issues
3.3.8 Configuring the Discipline

3.4 Implementation (to top)

[See the section titled Discipline Configuration that describes what each of the following sections needs to contain.]
3.4.1 Workflow
3.4.2 Artifacts
 
Artifacts How to use Review Details Tools used Templates/
Examples
Incep Elab Const Trans
Build              
Implementation Model
 
 
 
 
 
 
 

Implementation Element

             

Implementation Subsystem

 
 
 
 
 
 
 

Testability Element

             

Test Stub

             
Integration Build Plan              
3.4.3 Notes on the Artifacts
 
Artifacts How to Use Reason
 
 
 
3.4.4 Reports
 
Reports How to Use Templates/Examples Tools Used
   
 
 
3.4.5 Notes on the Reports
3.4.6 Additional Review Procedures
3.4.7 Other Issues
3.4.8 Configuring the Discipline

3.5 Testing (to top)

[See the section titled Discipline Configuration that describes what each of the following sections needs to contain.]
3.5.1 Workflow
3.5.2 Artifacts
 
Artifacts How to use Review Details Tools used Templates/
Examples
Incep Elab Const Trans
Test Automation Architecture
 
 
 
 
 
 
 
Test Case
 
 
 
 
 
 
 
Test Data
 
 
 
 
 
 
 
Test Environment Configuration              
Test Evaluation Summary              
Test Ideas List              
Test Interface Specification              
Test Log              
Test Strategy              
Test Suite              
Test Plan              
Test Results              
Test Script              
Workload Analysis Model              
3.5.3 Notes on the Artifacts
 
Artifacts How to Use Reason
 
 
 
3.5.4 Reports
 
Reports How to Use Templates/Examples Tools Used
Test Survey  
 
 
3.5.5 Notes on the Reports
3.5.6 Additional Review Procedures
3.5.7 Other Issues
3.5.8 Configuring the Discipline

3.6 Deployment (to top)

[See the section titled Discipline Configuration that describes what each of the following sections needs to contain.]
3.6.1 Workflow
3.6.2 Artifacts
 
Artifacts How to use Review Details Tools used Templates/
Examples
Incep Elab Const Trans
Deployment Plan
        
 
 
 
 
 
 
End-User Support Material
 
 
 
 
 
 
 

Release Notes

             

Training Materials

             
Product              

Bill of Materials

        
 
 
 
 
 
 

Deployment Unit

        
 
 
 
 
 
 

Installation Artifacts

             

Product Artwork

             
3.6.3 Notes on the Artifacts
 
Artifacts How to Use Reason
 
 
 
3.6.4 Reports
 
Reports How to Use Templates/Examples Tools Used
   
 
 
3.6.5 Notes on the Reports
3.6.6 Additional Review Procedures
3.6.7 Other Issues
3.6.8 Configuring the Discipline

3.7 Configuration & Change Management (to top)

[See the section titled Discipline Configuration that describes what each of the following sections needs to contain.]
3.7.1 Workflow
3.7.2 Artifacts
 
Artifacts How to use Review Details Tools used Templates/
Examples
Incep Elab Const Trans
Change Request
 
 
 
 
 
 
 
Configuration Audit Findings
 
 
 
 
 
 
 
Configuration Management Plan              
Project Repository              
Workspace              
3.7.3 Notes on the Artifacts
 
Artifacts How to Use Reason
 
 
 
3.7.4 Reports
 
Reports How to Use Templates/Examples Tools Used
   
 
 
3.7.5 Notes on the Reports
3.7.6 Additional Review Procedures
3.7.7 Other Issues
3.7.8 Configuring the Discipline

3.8 Project Management (to top)

[See the section titled Discipline Configuration that describes what each of the following sections needs to contain.]
3.8.1 Workflow
3.8.2 Artifacts
 
Artifacts How to use Review Details Tools used Templates/
Examples
Incep Elab Const Trans
Business Case
 
 
 
 
 
 
 
Issues List
 
 
 
 
 
 
 
Iteration Assessment
 
 
 
 
 
 
 
Iteration Plan              
Project Measurements              
Review Record              
Risk List              
Software Development Plan              

Measurement Plan

             

Problem Resolution Plan

             

Product Acceptance Plan

             

Quality Assurance Plan

             

Risk Management Plan

             
Status Assessment              
Work Order              
3.8.3 Notes on the Artifacts
 
Artifacts How to Use Reason
 
 
 
3.8.4 Reports
 
Reports How to Use Templates/Examples Tools Used
   
 
 
3.8.5 Notes on the Reports
3.8.6 Additional Review Procedures
3.8.7 Other Issues
3.8.8 Configuring the Discipline

3.9 Environment (to top)

[See the section titled Discipline Configuration that describes what each of the following sections needs to contain.]
3.9.1 Workflow
3.9.2 Artifacts
 
Artifacts How to use Review Details Tools used Templates/
Examples
Incep Elab Const Trans
Development Infrastructure              
Development-Organization Assessment              
Development Process
 
 
 
 
 
 
 

Development Case

             

Project-Specific Guidelines

             

Business Modeling Guidelines

 
 
 
 
 
 
 

Design Guidelines

 
 
 
 
 
 
 

Programming Guidelines

             

Test Guidelines

             

Use-Case Modeling Guidelines

             

Project-Specific Templates

             
Manual Styleguide              
Tools              
3.9.3 Notes on the Artifacts
 
Artifacts How to Use Reason
 
 
 
3.9.4 Reports
 
Reports How to Use Templates/Examples Tools Used
   
 
 
3.9.5 Notes on the Reports
3.9.6 Additional Review Procedures
3.9.7 Other Issues
3.9.8 Configuring the Discipline

4.  Roles (to top)

[This section is used for the following purposes: