Abstract
[Context and motivation] The starting point for software development is usually the system requirements. The requirements, especially nonfunctional requirements specified in a document are often incomplete and inconsistent with the initial user needs and expectations. [Question/problem] Experience at Siemens showed us that programmers working on software development often have trouble interpreting under-specified non-functional requirements, resulting in code that does not meet the users’ quality expectations and contains “quality faults” that can only be detected later through expensive user acceptance testing activities. [Principal ideas/results] In this problem statement paper, we investigate the need for clarifying non-functional requirements in software specifications to improve user acceptance. In particular we focus on establishing the role of non-functional requirements on user acceptance. [Contribution] Our contribution is that we emphasize the need for a systematic empirical study in this area. We propose a possible set-up where a number of hypotheses have been developed that a systematic experiment will help to validate. Our work is based on industrial experiments at Siemens, in the particular context of the installation of a Product Lifecycle Management (PLM) system.
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.
References
Castro, J., Kolp, M., Mylopoulos, J.: Towards Requirements-Driven Software Development Methodology: The Tropos Project, Information Systems (2002)
CIMdata (2003), http://www.cimdata.com
Chung, L., Nixon, B.A., Yu, E., Mylopoulos, J.: Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers, Boston (2000)
Chung, L., Nixon, B.A., Yu, E.: Dealing with Change: An approach Using Non-Functional Requirements. In: Proceedings of the Second Internation Symposium on Requirements Engineering, York, England. Requirements Engineering Journal, pp. 238–260. Springer, London (1996)
Checkland, P.: Systems Thinking, Systems Practice – Includes a 30 year retrospective. John Wiley and Sons, Chichester (1999)
Doerr, J., Kerkow, D., Landmann, D.: Supporting Requirements Engineering for Medical Products - Early Consideration of User-Perceived Quality. In: Association for Computing Machinery (ACM): 30th International Conference on Software Engineering. ICSE 2008, pp. 639–647. IEEE Computer Society, Los Alamitos (2008)
Doerr, J., Hartkopf, S., Kerkow, D., Landmann, D., Amthor, P.: Built-in User Satisfaction - Feature Appraisal and Prioritization with AMUSE. In: Sutcliffe, A., Jalote, P. (eds.) Proceedings of 15th IEEE International Requirements Engineering Conference, pp. 101–110. IEEE Computer Society, Los Alamitos (2007)
Doerr, J., Kerkow, D., Koenig, T., Olsson, T., Suzuki, T.: Non-Functional Requirements in Industry - Three Case Studies Adopting an Experience-based NFR Method. In: 13th IEEE International Requirements Engineering Conference (2005)
Eigner (2005), http://vpe.mv.uni-kl.de/cms/index.php?id=274
González-Baixauli, B., Sampaio do Prado Leite, J.C., Mylopoulos, J.: Visual Variability Analysis for Goal Models. In: Requirements Engineering Conference, pp. 198–207 (2004)
González-Baixauli, B., Laguna, M.A., Sampaio do Prado Leite, J.C.: A Meta-model to Support Visual Variability Analysis. In: First International Workshop on Variability Modelling of Software-intensive Systems, Limerick, Ireland (2007)
Glinz, M.: On Non-Functional Requirements. In: International Conference on RE (2007)
ISO/IEC 9126-1: Software Engineering - Product Quality - Part 1: Quality Model (2001)
Keller, R.K., Schauer, R.: Design Components: Towards Software Composition at the Design Level. In: Proceedings of International Conference on Software Engineering, Kyoto, Japan, pp. 302–311 (1990)
Lapouchnian, A., Yu, Y., Mylopoulos J., Liaskos S., Sampaio do Prado Leite J.C.: From stakeholder goals to high-variability software design, Tech. rep., University of Toronto (2005), ftp.cs.toronto.edu/csrg-technical-reports/509
Lehane, P., Huf, S.: Towards understanding system acceptance: the development of an assessment instrument and work practice. In: Proc. of OZCHI, Canberra, Australia (2005)
Melnik, G., Read, K., Maurer, F.: Suitability of fit user acceptance tests for specifying functional requirements: Developer perspective. In: Extreme programming and agile methods - XP/Agile Universe 2004, pp. 60–72 (2004)
Mwanza, D.: Towards an Activity-Oriented Design Method for HCI research and practice, Knowledge Media Institute, The Open University, Walton Hall, United Kingdom (2002)
Rohleder, C.: Visualizing the Impact of Non-Functional Requirements on Variants– A Case Study. In: International Conference on Requirements Engineering, REV 2008, Barcelona (2008)
Salinesi, C., Rolland, C.: Fitting Business Models to Systems Functionality Exploring the Fitness Relationship. In: Eder, J., Missikoff, M. (eds.) CAiSE 2003. LNCS, vol. 2681. Springer, Heidelberg (2003)
Potts, C.: Fitness for Use: The System Quality that Matters Most. In: International Workshop on Requirements Engineering: Foundation of Software Quality, Barcelona (1997)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2009 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Marhold, C., Rohleder, C., Salinesi, C., Doerr, J. (2009). Clarifying Non-functional Requirements to Improve User Acceptance – Experience at Siemens. In: Glinz, M., Heymans, P. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2009. Lecture Notes in Computer Science, vol 5512. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-02050-6_12
Download citation
DOI: https://doi.org/10.1007/978-3-642-02050-6_12
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-02049-0
Online ISBN: 978-3-642-02050-6
eBook Packages: Computer ScienceComputer Science (R0)