IEEE 1228-1994
IEEE Standard for Software Safety Plans
Available Formats:
- Availability: Immediate Download
- Language: English
- License Type: Single User
- Updates: Not Included
- Availability: Request Quote
- Language: English
- License Type: Enterprise / Multi User
- Updates: Included
About This Item
IEEE 1228-1994 is the IEEE standard for software safety plans, written for computing and processing environments where safety-related software needs structured planning and oversight. It helps define how a software safety plan should be organized, documented, and maintained so safety concerns are addressed from early development through operation. For projects that must manage software hazards with discipline and traceability, this standard provides a practical framework for control and review.
What is IEEE 1228-1994?
This standard sets expectations for a software safety plan, including the kinds of activities, responsibilities, and documentation typically needed to support safe software development. IEEE 1228-1994 focuses on the planning side of software safety rather than the software product itself, making it useful as a reference for defining process controls, safety objectives, and review points. In computing and processing applications, it can help teams align engineering work with safety requirements in a consistent way.
Where is IEEE 1228-1994 used?
IEEE 1228-1994 is commonly relevant in software-intensive systems where incorrect behavior could affect people, equipment, or critical operations. It may be used in control software, embedded applications, monitoring systems, and other computing environments that require formal safety planning. The standard is especially useful during requirements analysis, design, verification, and change control, when teams need a clear plan for identifying hazards and managing safety-related software tasks.
Why is IEEE 1228-1994 important?
IEEE 1228-1994 matters because safety planning helps reduce software-related risk and supports more consistent engineering decisions. A defined safety plan can improve communication between developers, reviewers, and procurement teams by clarifying responsibilities and expected controls. It also supports documentation quality, testing focus, and traceability across the software lifecycle. For organizations working with safety-sensitive systems, the standard offers a practical basis for disciplined planning and review.
- Software safety planning structure
- Hazard identification and control
- Roles, reviews, and responsibilities
- Verification and traceability support
- Safety-focused lifecycle documentation
- Publication Date: 1993
- Standard Status: Inactive
- Publisher: IEEE
- Subject: Computing and Processing
- Official IEEE: Doi link
- This Version: 1228 (1993)
Please request information about the document. Contact Page
Need This Standard?
Request a personalized quote today to receive the latest edition in PDF or other available formats.
Need This Standard?
Request a personalized quote today to receive the latest edition in PDF or other available formats.
Summarize with AI
Get quick summaries using your favorite AI engine.
Online Standart Disclaimer
OnlineStandart.com is an authorized reseller of international standards through partnerships with authorized distributors. We do not own the copyrights or trademarks of the standards we sell, including but not limited to those of API, ASHRAE, BSI, SAE, ASTM, IEEE, IEC, ASME, ISO, and others.
All product names, logos, and brands are property of their respective owners. All company, product, and service names used on this website are for identification purposes only. Use of these names, trademarks, and brands does not imply endorsement.
The content provided on this website is for informational purposes only and is intended to promote our reselling services. OnlineStandart.com is not affiliated with or endorsed by any of the standard organizations unless explicitly stated.