Roles and Activities > Manager Role Set > Process Engineer > Develop Development Case
A development case is developed to be used in a software-development project.
The project's phase plan and organization has a major impact on the process, and vice versa. Therefore, the development of the development case must be coordinated with development of the project plan. See the Artifact: Software Development Plan, section "Project Plan", for more details. For example, if the project decides to use a different set of phases than in the Rational Unified Process (RUP), this is something that needs to be captured in the development case.
The project's choice of configuration items also has a major impact on the process, and vice versa. Therefore, the development of the development case must be coordinated with development of the configuration management plan. The configuration items are defined in the configuration management plan. See Artifact: Configuration Management Plan and Concepts: Product Directory Structure.
The Artifact: Development-Organization Assessment contains information about the project and the organization. Analyze the factors to decide how they should affect the development case. See the Guideline: Process Discriminants for guidelines on how the main factors influence the choice of process.
Define which disciplines to cover in the development case, by looking at the following aspects of the Development-Organization Assessment:
We recommend that you implement the RUP iteratively, as described in the Concepts: Implementing a Process in a Project. The Development Case does not have to capture the entire process. Be prepared not to cover all disciplines; skip disciplines and delegate process responsibility; see "Delegating Process Responsibility" in Guidelines: Development Case.
Document the result in the section "Scope" in the Development Case.
Decide How to Perform Each Discipline
Once you have decided which disciplines you need to introduce, decide the following for each:
To help you decide, there are is a section "Decide How to Perform the Workflow", in each of the following guidelines:
When you consider introducing a particular discipline, or part of one, take the following into account:
Tailor the artifacts for each of the disciplines. See Guidelines: Tailoring the Process.
Don't do all of the disciplines at once–focus on the next one to be applied in the project. Perform the following steps:
In addition to these steps you should also:
There are more things to decide for each discipline. See the guidelines for each discipline for more details:
Study the modified set of artifacts and the activities that use, create and update these artifacts. Decide whether you should modify or simplify these activities. Note that for each activity input and output artifacts are indicated. Be sure to delete any unnecessary step or activity. Consider the following:
Describe the changes in the Development Case.
Choose the kind of lifecycle model the project should employ. Refine the RUP model and adjust milestones and the milestone evaluation criteria if necessary. You may even decide to omit one or several of the phases, or add or remove milestones. See Phases and Concepts: Iteration for more information and ideas. Document the project's lifecycle model in the section "Overview of the Development Case".
Describe at least one sample iteration plan (more likely you will describe several) for each phase. These iteration plans describe how the project will work in different iterations and phases of the project. The purpose of sample iteration plans in the development case is to describe which activities your project will perform, and in which order. As such it can serve as a more detailed iteration plan. The sample iteration plan is important as a way for team members, to understand how the process will be applied.
The description of the sample iteration plan should be brief. Do not include details that belong in the activities, artifacts and guidelines. You can choose to describe the sample iteration plan in terms of activities or workflow details.
These iteration workflows can be captured textually (or graphically), as in the sample iteration plans that are part of the RUP (see Phases).
In most cases you should describe at least one sample iteration plan per phase. Describe the sample iteration plans as they are needed; there is no reason to describe how to work during the Transition phase at the beginning of a project. Start by defining how the project will work in the Inception phase.
The role Stakeholder represents all possible stakeholders to a project. You need to identify and describe the different types of stakeholders, their needs and responsibilities. Examples of different stakeholders are customer representative, user representative, investor, production manager, and buyer.
Describe the different stakeholders and their needs in the development case, in the section "Roles".
In some development organizations there are job positions defined. If these job positions are commonly used and have a wide acceptance within the organization, it may be worth doing a mapping between the roles in the RUP, and the job positions in the organization. Mapping job positions to roles can make it easier to make people in the organization understand how to employ the RUP. The mapping can also help people understand that roles are not job positions, which is a common misconception. Document this mapping in the development case, section "Roles".
Describe the development case. We recommend that you describe the development case on one or several web pages, with hyperlinks to the RUP online, and to other guidelines. This is explained in the section "Representing a Development Case Online" in Guideline: Development Case. Use the Example: Development Case as a starting point. See also, Toolkit: Creating a Development Case Using the Rational Unified Process, and Toolkit: Authoring Web Pages.
Many of the decisions should be made before the project starts. After each iteration in the software-development project you should evaluate the process, and reconsider the decisions you have made. If a new version of the RUP is released you need to update the development case. This is explained in the Toolkit: Upgrading the Rational Unified Process.
Rational Unified Process