An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.
- Sponsor Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
Learn More About C/S2ESC - Software & Systems Engineering Standards Committee - Status
- Superseded Standard
- Board Approval
- 1986-12-11
- History
-
- ANSI Approved:
- 2003-04-18
- Published:
- 1986-11-30
- Reaffirmed:
- 2009-12-09
Working Group Details
- Society
- IEEE Computer Society
Learn More About IEEE Computer Society - Sponsor Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
Learn More About C/S2ESC - Software & Systems Engineering Standards Committee - Working Group
-
WG_LCP - Working Group for Life Cycle Processes
- IEEE Program Manager
- Patricia Roder
Contact Patricia Roder - Working Group Chair
- Teresa Doran
Other Activities From This Working Group
Current projects that have been authorized by the IEEE SA Standards Board to develop a standard.
P12207
Systems and software engineering -- Software life cycle processes
This document establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software system, product or service and during the supply, development, operation, maintenance and disposal of software products. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. Software includes the software portion of firmware. This document includes those aspects of system definition needed to provide the context for software systems and services. This document also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project.
P24748-4
Systems and Software Engineering -- Life Cycle Management -- Part 4: Systems Engineering Management Planning
ISO/IEC/IEEE 15288, Systems and software engineering -- System life cycle processes, provides a common process framework covering the life cycle of human-made systems, from the conception of ideas through to the retirement of a system. It provides the processes for acquiring and supplying systems. In addition, this framework provides for the assessment and improvement of the life cycle processes. This common framework improves communication and cooperation among the parties that create, utilize, and manage modern systems in order that they can work in an integrated, coherent fashion. The acquisition or supply of a system is usually done within a project. A project prepares and implements the technical planning, resources and schedules necessary to guide the project toward accomplishment of its objectives and proper conclusion. The project's authorization and objectives are documented in an information item identified as a Systems Engineering Management Plan (SEMP). This document defines a SEMP as the key vehicle for representing a project's application of systems life cycle processes. In this document, the terms technical planning and systems engineering planning are used interchangeably to emphasize or differentiate technical contributions in the processes under discussion.
Standards approved by the IEEE SA Standards Board that are within the 10-year lifecycle.
No Active Standards
These standards have been replaced with a revised version of the standard, or by a compilation of the original active standard and all its existing amendments, corrigenda, and errata.
No Superseded Standards
These standards have been removed from active status through a ballot where the standard is made inactive as a consensus decision of a balloting group.
No Inactive-Withdrawn Standards
These standards are removed from active status through an administrative process for standards that have not undergone a revision process within 10 years.
No Inactive-Reserved Standards