IEEE 1228-2002 pdf download IEEE Standard for Software Safety Plans
1. Overview
1.1 Purpose
This standard establishes the minimum acceptable requirements for the content of a Software Safety Planalso referred to as the Plan) to address the processes and activities intended to improve the safety of safetycritical software.
1.2 Scope
This standard applies to the Plan used for the development, procurement, maintenance, and retirement otsafety-critical software: for example, software products whose failure could cause loss of life. serious harmor have widespread negative social impact. This standard requires that the Plan be prepared within the context of the system safety program. The scope of this standard includes only the safety aspects of the software. This standard does not contain special provisions required for software used in distributed systems orin parallel processors.
1.3 Application
The Plan is prepared under the direction of project or system safety program management to address theidentified potential software safety risks.
Compliance with this standard requires the creation of a written plan that addresses each topic, subtopic, andstipulation described in clause 4. The level of detail in, and the resources required by an software safety planwill be determined by factors including the type and level of risks associated with the software product, thecomplexity of the application, and external forces such as contractual requirements.
Software is a portion of a system. Other portions of that system include computer hardware, other devices(possibly including mechanical, electrical, chemical, or nuclear devices), and people. Software alone is not asafety issuc; it is only an issue in the context of this larger system. Hence, software safety must begin withthe larger svstem. Software safety must be considered in the context of its associated hardware. environment, and operators, The Plan needs to address interfaces with these elements.
The existence of this standard should not be construed to discourage or prohibit the imposition of additionalor more stringent requirements where the need exists. An assessment should be made for the specific software project to ensure adequacy of coverage and safety assurance, Where this standard is invoked for a project engaged in producing several software products, the applicability of the standard should be specifiedfor cach of the software products encompassed by the project. This standard contains a minimum set ofrequirements for the content of software safety plans. The addition of more stringent requirements shall bethe only acceptable tailoring process for this standard.
1.4 Disclaimer
Preparation of software safety plans according to this standard does not automatically ensure softwaresafety. Compliance with this standard does not absolve the software designer producer, or vendor from anystatutory obligations.
IEEE 1228-2002 pdf download
PS:Thank you for your support!
