Standard for Software Documentation for Rail Equipment and Systems
|Publication Date:||23 September 2004|
Software is used in many facets of the rail transit industry, including real-time software control of electronics on rail vehicles, wayside control, and centralized operations control centers. Over time, the number, complexity, and interconnectivity of these systems have increased, while expectations for trouble-free operation have increased. Systems in this industry require the interaction of many software-based subsystems often provided by multiple suppliers.
Documentation, developed and contractually required for software-based subsystems, has evolved as well. Variation in the interpretation of the existing IEEE software standards has occurred within the rail transit industry. Although similarities in software documentation exist, both from project-to-project and from supplier-to-supplier
This standard is intended to reduce the variation in the interpretation of the referenced software standards. In addition, this standard minimizes the duplication of information in the resulting set of documents as would result if each IEEE standard was implemented in its entirety.
This documentation standard establishes a uniform set of documents, consistent terminology, and a uniform interpretation of the underlying referenced software standards. Use of this standard will provide acquirers and suppliers with a consistent document set as well as a consistent set of contents.
This standard places requirements on the software development process. However, this standard neither defines a software development practice (particularly as it relates to safety critical software or a software development life cycle) nor does it require a particular design methodology or programming language.
This standard establishes the minimum requirements for application software documentation throughout the software development life cycle for rail equipment and systems including associated test and maintenance equipment.