on include, but are not limited to, the following: Where there are changes in the requirements or specification; Timing/concurrency issues; Interface issues; Use of mathematical algorithms; Control mechanisms (the use of control theory should be independently validated); Complex logic (e.g. logic based on finite state machine formalism). 5 Software To enable the software 7.2.2.5 For all safety integrity levels: ensure that safety developer to review the there is evidence that the software safety requirements software safety requirements have been reviewed by the presentation requirements specification software developer. and review by to ensure the software requirements are If the software developer is the author of the software safety requirements, ensure developer adequately specified that appropriate peers have reviewed the software safety requirements. Ensure that there is evidence that the review evidence identifies the version of the software safety requirements specification
on include, but are not limited to, the following: Where there are changes in the requirements or specification; Timing/concurrency issues; Interface issues; Use of mathematical algorithms; Control mechanisms (the use of control theory should be independently validated); Complex logic (e.g. logic based on finite state machine formalism). 5 Software safety requirements presentation and review by software developer To enable the software developer to review the software safety requirements specification to ensure the requirements are adequately specified 7.2.2.5 For all safety integrity levels: ensure that there is evidence that the software safety requirements have been reviewed by the software developer. If the software developer is the author of the software safety requirements, ensure that appropriate peers have reviewed the software safety requirements. Ensure that there is evidence that the review evidence identifies the version of the software safety requirements specification