Overview
This activity breaks down the work to be performed into manageable units, and establishes size and cost estimates. A schedule for completing the software project is developed.
Roles and Responsibilities
The project software manager determines the scope of the software project.
Controls
The Project Plan documenting the project’s purpose, schedule, budget, life cycle, and milestones.
Any other available project plans (e.g., Pre-Phase A Work Plan, Phase A Study Plan) documenting the project’s purpose, schedule, budget, life cycle, and milestones. The availability, content, and format of these will vary widely between projects.
Inputs
The software development process outlining the software project’s life cycle and activities to be performed (see activity 1.1.1.3 Define Software Development Process).
Any available system requirements and/or design documentation describing the system’s functionality.
Preliminary Mission Needs Statement which establishes the justification for undertaking an agency objective or effectively pursuing an opportunity pertaining to an agency objective (as described in LHB 7122.1).
The software project organization and resources that must be factored into the schedule and cost estimates (see activity 1.1.1.2 Identify Software Project Organization And Resources).
Procedures
The following subactivities, which determine the software project’s scope, are iteratively performed by the project software manager, and their results are documented in the Software Development Plan (SDP) (see Appendix E):
1) 1.1.1.1.1 Identify Software Project Deliverables. In this activity, the items to be delivered are identified, using the Preliminary Mission Needs Statement, and other available system requirements, design documents, or project plans. These products may be generally categorized as software and related documentation.
2) 1.1.1.1.2 Develop Work Breakdown Structure. In this activity , a work breakdown structure (WBS) is prepared. The WBS subdivides the work to be performed into successively smaller units at each lower level of a tree structure.
3) 1.1.1.1.3 Estimate Lines Of Code. This activity uses the Wideband Delphi technique to estimate the size of a software project as source lines of code (SLOC) that must be produced for each computer software configuration item (CSCI).
4) 1.1.1.1.4 Perform Cost Estimating. This activity covers estimating the cost to complete the software project. This includes estimates for both labor and resources (i.e., hardware and software) that must be purchased.
5) 1.1.1.1.5 Develop Software Schedule. In this activity, a schedule for the software project is produced based on the project schedule in the Project Plan (or other project plans) and the selected software development process.
Outputs
The software project scope defining the software products to be delivered, the size of the software to be developed, and the schedule, all of which are documented in the SDP. The cost to complete the software project is estimated and documented in a separate cost database.