Tool support for generation and validation of traces between requirements and architecture
Proceedings of the 6th ECMFA Traceability Workshop
A framework for classifying and comparing software architecture tools for quality evaluation
ICCSA'11 Proceedings of the 2011 international conference on Computational science and Its applications - Volume Part V
Making software verification tools really work
ATVA'11 Proceedings of the 9th international conference on Automated technology for verification and analysis
A taxonomy for requirements engineering and software test alignment
ACM Transactions on Software Engineering and Methodology (TOSEM)
Journal of Systems and Software
| Hi-index | 0.00 |
Synchronization between component requirements andimplementation centric tests remains a challenge that isusually addressed by requirements reviews with testers andtraceability policies. The claim of this work is that linking requirements, their scenario-based formalizations, andsoftware verification provides a promising extension to thisapproach. Formalized scenarios, for example in the form oflow-level assume/assert statements in C, are easier to traceto requirements than traditional test sets. For a verification engineer, they offer an opportunity to better participatein requirements changes. Changes in requirements can bemore easily propagated because adapting formalized scenarios is often easier than deriving and updating a largeset of test cases. The proposed idea is evaluated in a casestudy encompassing over 50 functional requirements of anautomotive software developed at Robert Bosch GmbH. Results indicate that requirement formalization together withformal verification leads to the discovery of implementationproblems missed in a traditional testing process.