The purpose of Integrated Software Management is to integrate the software engineering and management activities into a coherent, defined software process that is tailored from SSC San Diego's standard software process and related process assets, which are described in Organization Process Definition.
Integrated Software Management involves developing each project's defined software process and managing each software project using this defined software process. Each project's defined software process is tailored from SSC San Diego's standard software process to address the specific characteristics of the project.
The software development plan is based on the project's defined software process and describes how the activities of the project's defined software process will be implemented and managed. The management of the software project's size, effort, cost, schedule, staffing, and other resources is tied to the tasks of the project's defined software process.
SSC San Diego shall:
1. Define each project's software process as a tailored version of SSC San Diego's standard software process.
2. Plan and manage each project according to the project's defined software process.
3. Provide adequate resources and funding for managing each software project using the project's defined software process.
4. Require training for the individuals responsible for developing each
project's defined software process in how to tailor SSC San Diego's standard
software process and use the related process assets.
5. Require training for the software managers in managing the technical,
administrative, and personnel aspects of the software project based on the
project's defined software process.
6. Develop each project's software process by tailoring SSC San Diego's standard software process according to a documented procedure.
7. Revise each project's defined software process according to a documented procedure.
8. Develop and revise each project's software development plan, which describes the use of the project's defined software process, according to a documented procedure.
9. Manage each software project in accordance with the project's defined software process.
10. Use software process database for software planning and estimating.
11. Manage the size of the software work products (or size of changes to the software work products) according to a documented procedure.
12. Manage each project's software effort and costs according to a documented procedure.
13. Manage each project's critical computer resources according to a documented procedure.
14. Manage the critical dependencies and critical paths of each project's software schedule according to a documented procedure.
15. Identify, assess, document, and manage each project's software risks according to a documented procedure.
16. Periodically perform reviews of each software project, to determine the actions needed to bring the software project's performance and results in line with the current and projected needs of the business, customer, and end users, as appropriate.
17. Make and use measurements to determine the effectiveness of the integrated software management activities.
18. Review the activities for managing each software project with senior management on a periodic basis.
19. Review the activities for managing each software project with its project
manager on both a periodic and event-driven basis.
20. Have the software quality assurance group conduct reviews or audits of the
activities and work products for managing each software project and report the
results.
The SSC San Diego Commanding Officer is responsible for implementing this policy.
The Software Engineering Process Office (SEPO) is responsible for maintaining this policy.