Abstract

Requirements Engineering is the set of activities involved in creation, managing, documenting, and maintaining a requirements’ set for a product. Engineering involves the use of systematic repeatability techniques to ensure that the Software Requirements are complete, consistent, valid, and verifiable. Software Requirements Specification is an organized process oriented toward defining, documenting and maintaining requirements throughout the development life cycle. Many authors suggest that requirements should always focus their claims on what the software product needs to address, without specifying how to implement them. However, the detail of Software Requirements is influenced by several factors such as: organizational thinking; existing specification standards; and regulatory needs. This work fits exactly with regulatory needs, where the characteristics of Software Requirements Specification in Regulated Environments such as aeronautics, railways and medical are presented and explored. This paper presents and analysis of software requirements specification characteristics in regulated environments. The four characteristics identified are: consistency (internal and external), unambiguity, verifiability, and traceability. The paper also describes the three standards used in these regulated environments (RTCA DO-178C, IEC 62279 and IEC 62304) and examines their similarities and differences from a Requirements Specification standpoint. The similarities and differences will be used to address a future requirements framework universal process that can be configured to address each standard by the usage of Software Process Lines.

Highlights

  • Safety-Critical Software is developed in environments regulated by standards and Regulatory agencies in safety-critical industries typically require system providers to meet stringent certification requirements [1]

  • The aim of this paper is to provide an analysis of software requirements specification characteristics in regulated environments

  • Radio Technical Commission for Aeronautics (RTCA) DO178C requires the definition of a Software Requirements Standards (SRSt) which shall define the methods, notations, rules and tools to be used to develop the Software HighLevel Requirements (SW-HLR), which shall be adherent to SRSt

Read more

Summary

INTRODUCTION

Safety-Critical Software is developed in environments regulated by standards and Regulatory agencies in safety-critical industries typically require system providers to meet stringent certification requirements [1]. A common characteristic in the rules and standards of these domains is the Requirements Specification. SRE does not involve a completely heterogeneous area, but consists of many different development cultures, which have common characteristics that allow them to be correlated, such as: a) Software product type; b). International technical entities, or regulatory agencies influence the development of SRE by means of guidelines for software processes and products [6], given the risk. The aim of this paper is to provide an analysis of software requirements specification characteristics in regulated environments. The specific objectives of this paper are: a) Present the selected software standards (RTCA DO-178C [7], IEC 62279 [8] and IEC 62304 [9]); and b) Identify their similarities and differences in Requirements Specification.

REGULATORY SOFTWARE STANDARDS
Selection of Software Standards
RTCA DO-178C
IEC 62279
IEC 62304
Internal and External Consistency
Unambiguity
Verifiability
Traceability
CONCLUSION
Full Text
Published version (Free)

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 call