Requirement-Based Test Approach and Traceability for High-Integrity Airborne Embedded Systems

Requirement-Based Test Approach and Traceability for High-Integrity Airborne Embedded Systems

Sudha Srinivasan, D. S. Chauhan
Copyright: © 2020 |Pages: 16
DOI: 10.4018/978-1-5225-9659-2.ch003
OnDemand:
(Individual Chapters)
Available
$37.50
Current Special Offers
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

One of the biggest challenges in the development of airborne embedded systems is to ensure that the aircraft subsystem meets all its user specifications and ascertain that no important functionality is missing which leads to development of an incorrect product. This chapter proposes a methodology for achieving requirement traceability and thereby performing requirement-based testing for efficient test and evaluation of aircraft subsystems. This methodology integrates requirement traceability throughout the software development life cycle along with requirement-based testing for high-integrity software systems. The methodology has been found to be most effective in revealing errors and optimizes testing by preventing repetition of test cases across test platforms. This unique contribution has the potential to revolutionize the research world in software engineering.
Chapter Preview
Top

Background

B. Ramesh, T. Powers, C. Stubbs and M. Edwards 1995, presented a case study that suggested implementing traceability into the organization's systems development methodology as “an important concept in improving the process of systems engineering activity and overall project quality.” The paper details a case study focussed on the use of requirement traceability starting from the system requirements down to the computer software unit (CSU) level. Once the project reaches the testing phase, this traceability is used to prove that the system meets the stated requirements (Ramesh, Powers, Stubbs, & Edwards, 1995).

Jane Cleland-Huang, 2006 addressed the problems and challenges of requirement traceability along with the traditional and automated methods. The open question on what kind of traceability is used to achieve the desired results in a cost effective way is addressed (Cleland-Huang, 2006).

PredragSkoković and MarijaRakić-Skoković, 2010 have described the requirement based test methodology as a 12 step process for verifying the code against test cases. The paper discusses the introduction of requirement based testing before the implementation phase (Predrag, Skokovic, & Rakic-Skokovis, 2010).

Complete Chapter List

Search this Book:
Reset