Abstract
[Context and motivation] Quality requirements are a main driver for architectural decisions of software systems. Although the need for iterative handling of requirements and architecture has been identified, current architecture design processes do not provide systematic, quantitative feedback for the prioritization and cost/benefit considerations for quality requirements. [Question/problem] Thus, in practice stakeholders still often state and prioritize quality requirements before knowing the software architecture, i.e. without knowledge about the quality dependencies, conflicts, incurred costs, and technical feasibility. However, as quality properties usually are cross-cutting architecture concerns, estimating the effects of design decisions is difficult. Thus, stakeholders cannot reliably know the appropriate required level of quality. [Principal ideas/results] In this research proposal, we suggest an approach to generate feedback from quantitative architecture evaluation to requirements engineering, in particular to requirements prioritization. We propose to use automated design space exploration techniques to generate information about available trade-offs. Final quality requirement prioritization is deferred until first feedback from architecture evaluation is available. [Contribution] In this paper, we present the process model of our approach enabling feedback to requirement prioritization and describe application scenarios and an example.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Berander, P., Andrews, A.: Requirements prioritization. In: Aurum, A., Wohlin, C. (eds.) Engineering and Managing Software Requirements, pp. 69–94. Springer, Heidelberg (2005)
Berntsson Svensson, R., Gorschek, T., Regnell, B., Torkar, R., Shahrokni, A., Feldt, R.: Quality requirements in industrial practice – an extended interview study at eleven companies. IEEE Trans. on Software Engineering (preprint:1, 2011)
Berntsson Svensson, R., Gorschek, T., Regnell, B., Torkar, R., Shahrokni, A., Feldt, R., Aurum, A.: Prioritization of quality requirements state of practice in eleven companies. In: RE 2011, pp. 69–78. IEEE (2011)
Berntsson Svensson, R., Sprockel, Y., Regnell, B., Brinkkemper, S.: Setting quality targets for coming releases with QUPER: an industrial case study. In: Requirements Engineering, pp. 1–16
Boehm, B.W.: A spiral model of software development and enhancement. Computer 21(5), 61–72 (1988)
Chung, L., do Prado Leite, J.C.S.: On Non-Functional Requirements in Software Engineering. In: Borgida, A.T., Chaudhri, V.K., Giorgini, P., Yu, E.S. (eds.) Mylopoulos Festschrift. LNCS, vol. 5600, pp. 363–379. Springer, Heidelberg (2009)
de Gooijer, T., Jansen, A., Koziolek, H., Koziolek, A.: An industrial case study of performance and cost design space exploration. In: ICPE 2012 , Boston, USA (to appear, 2012)
Herrmann, A., Daneva, M.: Requirements prioritization based on benefit and cost prediction: An agenda for future research. In: RE 2008, pp. 125–134. IEEE (2008)
Immonen, A., Niemelä, E.: Survey of reliability and availability prediction methods from the viewpoint of software architecture. Software and System Modeling 7(1), 49–65 (2008)
Koziolek, H.: Performance evaluation of component-based software systems: A survey. Performance Evaluation 67(8), 634–658 (2010)
Martens, A., Koziolek, H., Becker, S., Reussner, R.H.: Automatically improve software models for performance, reliability and cost using genetic algorithms. In: WOSP/SIPEW 2010, pp. 105–116. ACM, New York (2010)
Meedeniya, I., Buhnova, B., Aleti, A., Grunske, L.: Reliability-driven deployment optimization for embedded systems. Journal of Systems and Software 84(5), 835–846 (2011)
Nuseibeh, B.: Weaving together requirements and architectures. IEEE Computer 34(3), 115–117 (2001)
Woods, E., Rozanski, N.: How software architecture can frame, constrain and inspire system requirements. In: Avgeriou, P., Grundy, J., Hall, J.G., Lago, P., Mistrk, I. (eds.) Relating Software Requirements and Architectures, pp. 333–352. Springer, Heidelberg (2011), doi:10.1007/978-3-642-21001-3_19
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2012 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Koziolek, A. (2012). Research Preview: Prioritizing Quality Requirements Based on Software Architecture Evaluation Feedback. In: Regnell, B., Damian, D. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2012. Lecture Notes in Computer Science, vol 7195. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-28714-5_5
Download citation
DOI: https://doi.org/10.1007/978-3-642-28714-5_5
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-28713-8
Online ISBN: 978-3-642-28714-5
eBook Packages: Computer ScienceComputer Science (R0)