Abstract
[Context and motivation] With increasing use of software, quality attributes grow in relative importance. Robustness is a software quality attribute that has not received enough attention in requirements engineering even though it is essential, in particular for embedded and real-time systems. [Question/Problem] A lack of structured methods on how to specify robustness requirements generally has resulted in incomplete specification and verification of this attribute and thus potentially a lower quality. Currently, the quality of robustness specification is mainly dependent on stakeholder experience and varies wildly between companies and projects. [Principal idea/results] Methods targeting other non-functional properties such as safety and performance suggest that certain patterns occur in specification of requirements, regardless of project and company context. Our initial analysis with industrial partners suggests robustness requirements from different projects and contexts, if specified at all, follow the same rule. [Contribution] By identifying and gathering these commonalities into patterns we present a framework, ROAST, for specification of robustness requirements. ROAST gives clear guidelines on how to elicit and benchmark robustness requirements for software on different levels of abstraction.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
IEEE Computer Society, IEEE standard glossary of software engineering terminology. IEEE, Tech. Rep. Std. 610.12-1990 (1990)
Shahrokni, A., Feldt, R., Petterson, F., Back, A.: Robustness verification challenges in automotive telematics software. In: SEKE, pp. 460–465 (2009)
Jaffe, M., Leveson, N.: Completeness, robustness, and safety in real-time software requirements specification. In: Proceedings of the 11th International Conference on Software Engineering, pp. 302–311. ACM, New York (1989)
Lutz, R.R.: Targeting safety-related errors during software requirements analysis. Journal of Systems and Software 34(3), 223–230 (1996)
Newmann, P.: The computer-related risk of the year: weak links and correlated events. In: Proceedings of the Sixth Annual Conference on Computer Assurance, COMPASS 1991, Systems Integrity, Software Safety and Process Security, pp. 5–8 (1991)
Ho, C.-W., Johnson, M., Maximilien, L.W.E.: On agile performance requirements specification and testing. In: Agile Conference 2006, pp. 46–52. IEEE, Los Alamitos (2006)
Ho, C.-W.: Performance requirements improvement with an evolutionary model. PhD in Software Engineering, North Carolina State University (2008)
Konrad, S., Cheng, B.H.C.: Requirements patterns for embedded systems. In: Proceedings of the IEEE Joint International Conference on Requirements Engineering (RE 2002), Essen, Germany (September 2002)
Gamma, E., Helm, R., Johnson, R., Vlissides, J.: Design Patterns. Addison-Wesley, Boston (January 1995)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2010 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Shahrokni, A., Feldt, R. (2010). Towards a Framework for Specifying Software Robustness Requirements Based on Patterns. In: Wieringa, R., Persson, A. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2010. Lecture Notes in Computer Science, vol 6182. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-14192-8_9
Download citation
DOI: https://doi.org/10.1007/978-3-642-14192-8_9
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-14191-1
Online ISBN: 978-3-642-14192-8
eBook Packages: Computer ScienceComputer Science (R0)