Page 98 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Principles of Software Engineering

Notes Output: Data or material produced by or resulting from a process activity. It must include the
input data in some form. The output title differs from the input title in order to indicate that
an activity has been performed.
Exit Criteria: Elements and/or conditions necessary to be in place to complete a process activity.

Process Metrics: Data collected which can be analyzed and used to improve the process.
Process Overview
Planning Initiation

The SSC San Diego Software Project Planning (SPP) process begins with the planning initiation
step. In this step a software project manager is selected and resources and budget are allocated
to the planning and re-planning activities. The Requirements Management (RM) Guidebook is
an interfacing process to the SPP process. Requirements are the major driving force in SPP and
therefore are a major interface to this process. Without requirements, you would not know what
to plan or what to estimate. Initial software estimates and software activities are also developed
in this step. The SSC San Diego Software Size, Cost, and Schedule Estimation process is an
interfacing process.
Develop SDP
The next step in the process is to develop the Software Development Plan (SDP). The MIL-STD-498
Data Item Description (DID) for the SDP, DI-IPSC-81427, should be used as a format for the SDP.
The SSC San Diego SDP template, which is based on the MIL-STD-498 DID, can be used as a
guide for developing the project specific SDP. The SDP should include items such as software
estimates, schedules, milestones, Work Breakdown Structure (WBS), software development
environment, software development methodology, software test methodology, and software
risks. The SDP is used to establish commitments on the project. Software estimates are refined
using the SSC San Diego Software Size, Cost, and Schedule Estimation process.

Review and Approve SDP
After the SDP has been developed it should undergo formal review and approval. The SSC San
Diego Formal Inspection process is one type of review methodology that can be used. Review of
the SDP should include all groups internal and external to the organization which will be affected
by the work in the SDP. Affected groups, both internal and external to the organization, should
also approve the SDP by signing the signature page of the SDP indicating their commitment
and acceptance of the SDP.
After the SDP has been approved it should be placed under configuration management. The
SSC San Diego Software Configuration Management (SCM) process can be used as a guide to
develop the project’s SCM process.

Implement SDP Processes and Apply SPTO Process
The project is now ready to implement the activities as described in the SDP. In implementing
the SDP, follow the project’s tailored version of the SSC San Diego Software Project Tracking
and Oversight (SPTO) process to provide information about the software project which can
precipitate changes to the SDP. These changes should be implemented in accordance with the
project’s SCM process. The project should also implement the project’s tailored SQA process
in order to monitor the project’s software development activities. In addition, the SQA group
should be monitoring the activities of the SPP process.

Process Measurement and Improvement
Metrics are collected on each process step and are then used to develop process improvements
in the SPP process. These measurements are analyzed against both planned and historical data,
if available.

92 LOVELY PROFESSIONAL UNIVERSITY