Abstract
The aim of this paper is to propose a consensual model of software safety requirements for decomposition and allocation of system safety integrity levels of quality. For this purpose, a procedural method is used for describing and evaluating the proposed model of software safety requirements; using a strategy that is based neither on our own views nor on individual researchers view of such type of requirements, but that is based on a consensus perspectives documented in international standards of software safety as quality requirements. This work contributes to the research knowledge by proposing a model that guides in practice both system and software engineers for early identification and specification of the software safety non functional requirements and their detailed allocation as specific safety functions.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Review on Computers and Software (IRECOS)
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
