underflows, etc). This model validation shall be documented Any model used in validation must have a scope, profile, and scale that is equal to or greater than the models that are to be used in the safety related system. Any restrictions to the model state space that are introduced to limit the execution time of the model shall be justified. 26 Detailed To ensure the software 7.4.5.2, For all safety integrity levels ensure that design and safety requirements 7.4.5.3, is evidence that the design is: development specification, the 7.4.5.4 description of the software The necessary information (specification architecture design and of requirements, architecture design and the software safety validation plan for software aspects of validation plan are system safety) was available prior to the available prior to the start start of software design of the detailed design, and that there is modularity, The design of each module is specified structure, testability, the Capable of verification which is expressed capacity of safe in the software module test specification modification, software module design and testing is specified and that Complete with respect to the requirements specification (objective structured methods are completeness criteria applied R2) employed –
underflows, etc). This model validation shall be documented Any model used in validation must have a scope, profile, and scale that is equal to or greater than the models that are to be used in the safety related system. Any restrictions to the model state space that are introduced to limit the execution time of the model shall be justified. 26 Detailed design and development To ensure the software safety requirements specification, the description of the software architecture design and the software safety validation plan are available prior to the start of the detailed design, and that there is modularity, structure, testability, the capacity of safe modification, software module design and testing is specified and that structured methods are employed 7.4.5.2, 7.4.5.3, 7.4.5.4 For all safety integrity levels ensure that is evidence that the design is: The necessary information (specification of requirements, architecture design and validation plan for software aspects of system safety) was available prior to the start of software design The design of each module is specified Capable of verification which is expressed in the software module test specification Complete with respect to the requirements specification (objective completeness criteria applied – R2)
CASS_TOES_for_software_assessment_IEC_61508-3_2010_-_ABRIDGED_v1.docx