Clarifying Non-functional Requirements to Improve User Acceptance --- Experience at Siemens

Authors:
Christoph Marhold;Clotilde Rohleder;Camille Salinesi;Joerg Doerr
Affiliations:
Siemens PL (DE) GmbH, Nuremberg, D-90471;Siemens PL (DE) GmbH, Nuremberg, D-90471 and CRI - Université Paris 1, Paris, F-75013;CRI - Université Paris 1, Paris, F-75013;Fraunhofer Institute Experimental Software Engineering, Kaiserslautern, D-67663
Venue:
REFSQ '09 Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality
Year:
2009

Citing 8
Cited 1

Design components: toward software composition at the design level

Proceedings of the 20th international conference on Software engineering
Towards requirements-driven information systems engineering: the Tropos project

Information Systems - The 13th international conference on advanced information systems engineering (CAiSE*01)
Visual Variability Analysis for Goal Models

RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Non-Functional Requirements in Industry - Three Case Studies Adopting an Experience-based NFR Method

RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Towards understanding system acceptance: the development of an assessment instrument and workpractice

OZCHI '05 Proceedings of the 17th Australia conference on Computer-Human Interaction: Citizens Online: Considerations for Today and the Future
Supporting requirements engineering for medical products: early consideration of user-perceived quality

Proceedings of the 30th international conference on Software engineering
Visualizing the Impact of 4on-Functional Requirements on Variants: A Case Study

REV '08 Proceedings of the 2008 Requirements Engineering Visualization
Fitting business models to system functionality exploring the fitness relationship

CAiSE'03 Proceedings of the 15th international conference on Advanced information systems engineering

An agile requirements elicitation approach based on NFRs and business process models for micro-businesses

Proceedings of the 12th International Conference on Product Focused Software Development and Process Improvement

Quantified Score

Hi-index	0.00

Visualization

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.