![]() In recent years, the V-Model has established itself as a procedural model for software development. Software-intensive systems are tested on different levels to enable a stepwise testing process and to increase the confidence in the system’s functionality. ISO26262 (ISO 2011) for automotive systems, EN 50128 (DIN 2012) for railway systems, or DO-178C (RTCA 2012) for avionic systems). In several domains, development standards prescribe the alignment of requirements and test procedures to assure that software-intensive systems are tested effectively (cf. The complexity leads to an increasing number of requirements, which are often expressed in natural language (Mich et al. In many areas, software systems are becoming increasingly complex through the use of open systems, highly automated, or networked devices. By this means, practitioners can easily evaluate how well a systems performs with regards to its specification and, additionally, can reason about the expressiveness of the applied test stage. With our approach, the results of several test levels are linked to the requirements and enable the evaluation of complex test executions. Further, we highlight the general applicability of our approach through this extensive experimental evaluation. Based on the annotations, we are able to analyze how similar the test stages are and how well test stages and test cases are aligned with the requirements. The annotations are then linked to 1300 test executions from a simulation environment and 53 test executions from test drives with human drivers. We annotate 443 natural language requirements of a driver assistance system with the means of our lightweight markup language. In this paper, we use the markup language to compare different test stages with one another. As a result, meaningful insights from a set of test executions can be directly related to artifacts in the requirements specification. ![]() ![]() The annotations are mapped to events and signals in test executions. Previously, we have proposed a lightweight markup language for requirements which provides a set of annotations that can be applied to natural language requirements. With our approach, we close the gap between requirements specifications and test executions. In addition, engineers are reluctant to state their requirements in terms of structured languages or models that would facilitate the relation of requirements to test executions. However, this information is necessary to assure a certain test coverage, to minimize redundant testing procedures, and to avoid inconsistencies between test stages. Monitoring and controlling which requirements are verified in which detail and in which test stage is a challenge for engineers. In this paper, the focus is on the domain of embedded systems, where, among others, typical test stages are Software- and Hardware-in-the-loop. Therefore, specific test suites are defined for each test stage. Each test stages exhibits specific demands and constraints with respect to their degree of detail and what can be tested. These test cases are commonly derived from requirements. The testing of software-intensive systems is performed in different test stages each having a large number of test cases.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |