OBJECTIVE

System Concept Development begins when the Concept Proposal has been formally approved and requires study and analysis that may lead to system development activities.

The review and approval of the Concept Proposal begins the formal studies and analysis of the need in the System Concept Development Phase and begins the life cycle of an identifiable project.

TASKS AND ACTIVITIES

The following activities are performed as part of the System Concept Development Phase. The results of these activities are captured in the four phase documents and their underlying institutional processes and procedures

1.  Study and Analyze the Business Need

The project team, supplemented by enterprise architecture or other technical experts, if needed, should analyze all feasible technical, business process, and commercial alternatives to meeting the business need. These alternatives should then be analyzed from a life cycle cost perspective. The results of these studies should show a range of feasible alternatives based on life cycle cost, technical capability, and scheduled availability. Typically, these studies should narrow the system technical approaches to only a few potential, desirable solutions that should proceed into the subsequent life cycle phases.

2.  Plan the Project

The project team should develop high-level (baseline) schedule, cost, and performance measures which are summarized in the System Boundary Document. These high-level estimates are further refined in subsequent phases.

3.  Study and Analyze the Risks

Identify any programmatic or technical risks. The risks associated with further development should also be studied. The results of these assessments should be summarized in the SBD and documented in the Risk Management Plan.

4.  Manage Capital Asset and Resources

Estimate, justify, submit requests for, and obtain resources to execute the project in the format of the Capital Asset Plan and Justification.