Abstract
[Context/motivation] Quality requirements (QRs) are a concern of both requirement engineering (RE) specialists and software architects (SAs). However, the majority of empirical studies on QRs take the RE analysts’/clients’ perspectives, and only recently very few included the SAs’ perspective. As a result, (i) relatively little is known about SAs’ involvement in QRs engineering and their coping strategies, and (ii) whatever is known mostly comes from small and midsized projects. [Question/problem] The question in this exploratory study is how SAs cope with QRs in the context of large and contract-based software system delivery projects. [Principal ideas/results] We executed an exploratory case study with 20 SAs in the context of interest. The key results indicate the role SAs play in QRs engineering, the type of requirements communication processes SAs are involved in, the ways QRs are discovered, documented, quantified, validated and negotiated. Our most important findings are that in contract-based contexts: (1) the QRs are approached with the same due diligence as the functional requirements and the architecture design demand, (2) the SAs act proactively and embrace responsibilities over the QRs, (3) willingness to pay and affordability seem as important QRs prioritization criteria as cost and benefits do, and (4) QRs engineering is perceived as a social activity and not as much as a tool and method centric activity. [Contribution] The main contributions of the paper are (i) the explication of the QRs process from SAs’ perspective, and (ii) the comparison of our findings with previously published results.
Access provided by Autonomous University of Puebla. Download to read the full chapter text
Chapter PDF
Similar content being viewed by others
Keywords
References
Lauesen, S.: Software requirements: Styles and techniques. Addisson-Wesley (2002)
Sommerville, I.: Integrated Requirements Engineering. IEEE Software 22(1), 16–23 (2005)
Avgeriou, P., Grundy, J., Hall, J.G., Lago, P., Mistrík, I. (eds.): Relating Software Requirements and Architectures. Springer (2011)
Capilla, R., Babar, M.A., Pastor, O.: Quality requirements engineering for systems and software architecting: methods, approaches, and tools. Requir. Eng. 17(4), 255–258 (2012)
Bass, L., et al.: Software Architecture in Practice, 2nd edn. Addison-Wesley (2003)
van Heesch, U., Avgeriou, P.: Mature Architecting - A Survey about the Reasoning Process of Professional Architects. In: 9th WICSA, pp. 260–269
Bentsson-Svensson, R., Höst, M., Regnell, B.: Managing Quality Requirements: A Systematic Review. In: EUROMICRO-SEAA 2010, pp. 261–268 (2010)
Ameller, D., Ayala, C., Cabot, J., Franch, X.: How do software architects consider non-functional requirements: An exploratory study. In: RE 2012, pp. 41–50 (2012)
Poort, E.R., Martens, N., van de Weerd, I., van Vliet, H.: How Architects See Non-Functional Requirements: Beware of Modifiability. In: Regnell, B., Damian, D. (eds.) REFSQ 2011. LNCS, vol. 7195, pp. 37–51. Springer, Heidelberg (2012)
Ameller, D., Franch, X.: How Do Software Architects Consider Non-Functional Requirements: A Survey. In: Wieringa, R., Persson, A. (eds.) REFSQ 2010. LNCS, vol. 6182, pp. 276–277. Springer, Heidelberg (2010)
Poort, E.R., Key, A., de With, P.H.N., van Vliet, H.: Issues Dealing with Non-Functional Requirements across the Contractual Divide. In: WICSA/ECSA 2012, pp. 315–319 (2012)
Groene, B., et al.: Educating Architects in Industry - The SAP Architecture Curriculum. In: 17th IEEE Int. Conf. on Eng. of Computer Based Systems (ECBS), pp. 201–205.
Guessi, M., Nakagawa, E.Y., Oquendo, F., Maldonado, J.C.: Architectural description of embedded systems: a systematic review. In: ACM SIGSOFT ISARCS 2012, pp. 31–40 (2012)
Yin, R.K.: Case Study Research: Design and Methods. Sage, Thousand Oaks (2008)
King, N., Horrock, C.: Interviews in Qualitative Research. Sage, Thousand Oaks (2010)
Charmaz, K.: Constructing Grounded Theory. Sage, Thousand Oaks (2007)
Stakeholder Engagement Standard (AA1000SES), http://goo.gl/fRopv
Groene, B.: TAM – The SAP Way of Combining FCM and UML, http://goo.gl/FW1IA (last viewed on November 8, 2012)
Gilb, T.: Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage, Butterworth (2005)
Karlsson, J.: Managing software requirements using quality function deployment. SQJ 6(4), 311–326
Buglione, L.: Improving estimated by a four pieces puzzle, IFPUG Annual Conference (May 2012), http://goo.gl/bFwRB
IFPUG, Software Non-functional Assessment Process (SNAP) – Assessment Practice Manual (APM) Release 2.0 (January 22, 2013)
Boehm, B., Grunbacher, P., Briggs, R.O.: EasyWinWin: A Groupware-Supported Methodology for Requirement Negotiation. In: 9th ACM SIGSOFT FSE, pp. 320–321 (2001)
de Bono, E.: Six Thinking Hats. Little, Brown, & Co., Toronto (1985)
Buglione, L., Abran, A.: Improving Measurement Plans from multiple dimensions: Exercising with Balancing Multiple Dimensions - BMP. In: 1st Workshop on Methods for Learning Metrics, METRICS 2005 (2005)
Brooks, F.P.: The Design of Design: Essays from a Computer Scientist. Addison-Wesley (2010)
Nicholson, B., Sahay, S.: Embedded Knowledge and Offshore Software Development. Information and Organization 14(4), 329–365 (2004)
Herrmann, A., Daneva, M.: Requirements Prioritization Based on Benefit and Cost Prediction: An Agenda for Future Research. In: RE 2008, pp. 125–134 (2008)
Runeson, P., Höst, M.: Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering 14(2), 131–164 (2009)
Seddon, P., Scheepers, P.: Towards the improved treatment of generalization of knowledge claims in IS research: drawing general conclusions from samples. EJIS, 1–16 (2011)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2013 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Daneva, M., Buglione, L., Herrmann, A. (2013). Software Architects’ Experiences of Quality Requirements: What We Know and What We Do Not Know?. In: Doerr, J., Opdahl, A.L. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2013. Lecture Notes in Computer Science, vol 7830. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-37422-7_1
Download citation
DOI: https://doi.org/10.1007/978-3-642-37422-7_1
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-37421-0
Online ISBN: 978-3-642-37422-7
eBook Packages: Computer ScienceComputer Science (R0)