Name
Abstract | ||
|---|---|---|
Non-functional Requirements (NFRs) play a unique role in the development of any software-intensive system. They often have a significant impact upon the architectural design and drive critical trade-offs. However, such trade-off decisions are often based on assumptions about future workloads, environmental factors, and anticipated system behavior. From a traceability perspective, it is thus necessary to trace individual NFRs into the design and their associated design rationales, and further forward into the running system in order to monitor and assess the design-time assumptions at runtime. When runtime data indicates that a mismatch has occurred that adversely impacts system performance and/or behavior, measures need to be taken, such as applying critical bug fixes, or refactoring performance bottlenecks. In this paper, we explore five different types of NFRs across the design and runtime phases of the development process. Our approach is illustrated by examples from the Dronology System for Fault Tolerance, Security, Usability, Performance, and other critical qualities.
|
Year | DOI | Venue |
|---|---|---|
2019 | 10.1109/SST.2019.00010 | Proceedings of the 10th International Workshop on Software and Systems Traceability |
Keywords | DocType | ISSN |
cyber-physical systems, testing, traceability | Conference | 2157-2186 |
ISBN | Citations | PageRank |
978-1-7281-2256-4 | 0 | 0.34 |
References | Authors | |
26 | 4 | |
Name | Order | Citations | PageRank |
|---|---|---|---|
| Michael Vierhauser | 1 | 280 | 25.55 |
| Jane Cleland-Huang | 2 | 2204 | 139.78 |
| Janet Burge | 3 | 0 | 0.34 |
| Paul Grunbacher | 4 | 306 | 25.59 |