IEEE 1558-2004 pdf download IEEE Standard for Software Documentation for Rail Equipment and Systems
1.Overview
1.1 Scope
This standard establishes the minimum requirements for application software documentation throughout thesoftware development life cycle for rail equipment and systems including associated test and maintenanccequipment.
1.2 Purpose
Many differing requirements for application software documentation are presently being specified forsoftware used in rail cquipent and systems and for related applications, which has led to a lack ofstandardization in the information provided on equpment and systems incorporating software, Thisstandard, when used by the authority having jurisdiction, car builders, and system/subsystem suppliers, isintended to specify documents that improve the understanding of software functionality, facilitate softwarecorrections and upgrades, improve on-time delivery, and lower software acquisition and maintenance costs.
1.3 Existing applications
Existing projects in progress before the effective date of this standard need not comply with the new orrevised requirements of this edition, except where specifically required by the authority having jurisdiction.
2 References
This standard shall be used in conjunction with the following publications
EIA/IEEE J-STD-016-1995, Trial-Use Standard for Information Technology Software Life Cycle ProcessSoftware Development Acquirer-Supplier Agreement (withdrawn).
IEEE Std 610.12 TM -1990, IEEE Standard Glossary of Software Engineering Terminology. 2, 3
IEEE Std 730 TM -2002, IEEE Standard for Software Quality Assurance Plans.
IEEE Std 828 TM -1998, IEEE Standard for Software Configuration Management Plans.
IEEE Std 829 TM -1998, IEEE Standard for Software Test Documentation.
IEEE Std 830 TM -2002, IEEE Recommended Practice for Software Requirements Specifications.
IEEE Std 1012 TM -1998, IEEE Standard for Software Verification and Validation.
IEEE Std 1016 TM -1998, IEEE Recommended Practice for Software Design Descriptions.
IEEE Std 1058 TM -1998, IEEE Standard for Software Project Management Plans.
3. Definitions, acronyms, and abbreviations
3.1 Definitions
For the purposes of this standard, the following terms and definitions apply. The Authoritative Dictionary ofIEEE Standards Terms (B1] and IEEE Std 610.12-1990 should be referenced for terms not defined in thisclause.4,5
3.1.1 software integrity level: A denotation of a range of values of a property of an item necessary to maintain system risks within acceptable limits. For items that perform mitigating functions, the property is thereliability with which the item must perform the mitigating function. For items whose failure can lead to athreat, the property is the limit on the frequency of that failure.
3.2 Acronyms and abbreviations
DBDD database design description
DBMS database management system
EIA Electronic Industries Association
ICD interface control document
IEEE Institute of Electrical and Electronics Engineers, Inc.
SCI(s) software configuration item(s)
SCM software configuration management
SCMP software configuration management plan
SDD software design description
SPMP software project management plan
SQA software quality assurance
SQAP software quality assurance plan
SRS software requirements specification
SRTM software requirements traceability matrix
STP software test plan
STPr software test procedure
STR software test report
SUM software users manual
SVD software version description
SVVP software verification and validation plan
SVVR software verification and validation report
V&V verification and validation
IEEE 1558-2004 pdf download
PS:Thank you for your support!
