Purpose is to develop and maintain a usable set of software process assets that improve process performance and provide a basis for cumulative, long-term benefits.
Developing and maintaining the organization’s standard software process such as descriptions of software life cycle, process tailoring guidelines and criteria, process database and related process documentation.
Defining standards for documenting standard software processes and tailored software processes and revised tailored processes.
The project is planned and managed according to the project’s defined SOFTWRE process
The organization's software process database is used for software planning and estimating.
The size of the software work products (or size of changes to the software work products) is managed
The project's software effort and costs are managed
The project's critical computer resources are managed
The critical dependencies and critical paths of the project's software schedule are managed
The project's software risks are identified, assessed, documented, and managed
Reviews of the software project are periodically performed 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
Purpose is to consistently perform a well designed engineering process that integrate all the software engineering activities to produce correct, consistent software products effectively and efficiently.
Performing the engineering tasks to build and maintain the software using appropriate tools and methods.
Documentation required is developed and reviewed to ensure they are appropriate for subsequent tasks.
Revising the appropriate documents when changes are approved.
The software engineering tasks are defined, integrated, and consistently performed to produce the software
Appropriate software engineering methods and tools are integrated into the project's defined software process
The software requirements are developed, maintained, documented, and verified by systematically analyzing the allocated requirements according to the project's defined software process
The software design is developed, maintained, documented, and verified, according to the project's defined software process, to accommodate the software requirements and to form the framework for coding
The software code is developed, maintained, documented, and verified, according to the project's defined software process, to implement the software requirements and software design
Software testing is performed according to the project's defined software process
Software work products are kept consistent with each other
Consistency is maintained across software work products, including the software plans, process descriptions, allocated requirements, software requirements, software design, code, test plans, and test procedures.
Purpose is to establish a means for the software engineering group to participate actively with other engineering groups so that the project is able to satisfy the customer’s needs effectively and efficiently.
Disciplined interaction and coordination of the project engineering groups with each other to address system-level requirements, objectives, and plans.
Defining working interfaces and interactions between various engineering groups and support groups.
Purpose is to remove defects from the software work products early and efficiently. An important effect is to develop a better understanding of the software work products and of defects that might be prevented
Methodical examination of work products by the producer’s peers to identify defects and areas where changes are needed.
Identifying products that will undergo a peer review in the project’s defined software process and schedule as part of the project planning activities.
Identifying and training the review team for performing effective reviews.
Recording the review defects and removing them from work products.