What is BS EN 50657 - Software for railway applications about?
In the railway industry, the costs of software failure can be huge, resulting in recalls and even loss of life. There is need to comply with quality standards to improve safety-critical software.
BS EN 50657 specifies the process and technical requirements for the development of software for programmable electronic systems for use in railway rolling stock applications. BS EN 50657 is related to and should be read in conjunction with the EN 50126 series.
BS EN 50657 is applicable to software and the interaction between software and the system of which it is part. BS EN 50657 also applies to safety-related as well as non-safety-related software, including for example, application programming, operating systems, support tools, and firmware.
Note: BS EN 50657 does not specify the requirements for the development, implementation, maintenance and/or operation of security policies or security services needed to meet security requirements that may be needed by the safety-related system.
Who is BS EN 50657 - Software for railway applications for?
BS EN 50657 on software for railway applications is useful for:
- The railway industry
- Software engineers/developers
- The IT industry
- Regulatory authorities
- Government railway authorities
Why should you use BS EN 50657 - Software for railway applications?
BS EN 50657 focuses on the methods which need to be used in order to provide software that meets the demands for software integrity which are placed upon it by these wider considerations.
BS EN 50657 provides you with a set of requirements for the development, deployment and maintenance of any software intended for railway rolling stock applications. It defines requirements concerning organizational structure, the relationship between organizations and the division of responsibility involved in the development, deployment and maintenance activities. Criteria for the qualification and expertise of personnel are also provided in this European Standard.
BS EN 50657 addresses techniques and measures for the five levels of software integrity where basic integrity is the lowest and 4 the highest one. The higher the risk resulting from software failure, the higher the software integrity level will be. has identified techniques and measures for the five levels of software integrity.
