Abstract
This paper discusses some essential reasons why socio-technical systems do not get the acceptance by end-users that is typically needed for a successful usage of the systems. One major prerequisite to achieve sufficient acceptance is to ensure a specific treatment of end-users, and stakeholders in general during the requirements engineering phase. The paper illustrates examples how requirements engineering activities for current as well as for future applications can help to increase the acceptance of socio-technical systems.
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
References
IEEE international symposium on requirements engineering (RE’93) (1993) San Diego, CA, USA
Mayhew DJ (1999) The usability engineering lifecycle: a practitioner’s handbook for user interface design. Morgan Kaufmann, San Francisco. ISBN 1558605614
Pruitt J, Grudin J (2003) Personas: practice and theory. In: DUX ‘03 Proceedings of the 2003 conference on designing for user experiences, ACM, New York, pp 1–15
Adam S, Doerr J, Eisenbarth M, Gross A (2009) Using task-oriented requirements engineering in different domains – experiences with application in research and industry. In: Requirements engineering conference, 2009. RE ‘09. 17th IEEE international requirements engineering conference, Atlanta, pp 267–272
Lauesen S (2002) Software requirements: styles and techniques. Addison-Wesley Longman, Amsterdam
Doerr J, Hartkopf S, Kerkow D, Landmann D, Amthor P (2007) Built-in user satisfaction – Feature appraisal and prioritization with AMUSE, 15th IEEE international requirements engineering conference. RE 2007 – Proceedings, IEEE Computer Society, Los Alamitos, pp~101–110
Seyff N, Graf F, Maiden N (2010) Using mobile RE tools to give end-users their own voice. In: 18th IEEE international requirements engineering conference (RE 2010), Sydney, pp 37–46
Paech B, Kohler K (2004) Task-driven requirements in object-oriented development. In: Perspectives on software engineering. Kluwer Academic Publishers, Boston
Roberston S, Robertson J (2006) Mastering the requirements process. Addison-Wesley Professional, Reading
Cooper A, Reimann R, Cronin D (2007) About Face 3.0: The essentials of interaction design, Wiley, Indianapolis
Dardenne A, van Lamsweerde A, Fickas S (1993) Goal directed requirements acquisition. Sci Comput Program 20:3–50
Yu ESK (1997) Towards modeling and reasoning support for early-phase requirements engineering. In: Proceedings of the third IEEE international symposium on requirements engineering, IEEE, Annapolis
Business Process Modeling Notation Version 2.0, Feb 2013, http://www.omg.org/spec/BPMN/2.0/
Keller G, Nüttgens M, Scheer A-W (1992) Semantische Prozeßmodellierung auf der Grundlage Ereignisgesteuerter Prozeßketten (EPK). Universität des Saarlandes, Saarbrücken
Rumbaugh J et al (1998) The unified modeling language reference manual. Addison-Wesley, Reading
Cockburn A (2000) Writing effective use cases. Addison-Wesley, Boston
Beyer H, Holtzblatt K (1998) Contextual design: defining customer centered systems. Morgan Kaufmann Publishers, San Francisco
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2014 Springer International Publishing Switzerland
About this paper
Cite this paper
Doerr, J. (2014). Towards Acceptance of Socio-technical Systems – An Emphasis on the Requirements Phase. In: Zweig, K., Neuser, W., Pipek, V., Rohde, M., Scholtes, I. (eds) Socioinformatics - The Social Impact of Interactions between Humans and IT. Springer Proceedings in Complexity. Springer, Cham. https://doi.org/10.1007/978-3-319-09378-9_10
Download citation
DOI: https://doi.org/10.1007/978-3-319-09378-9_10
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-09377-2
Online ISBN: 978-3-319-09378-9
eBook Packages: Computer ScienceComputer Science (R0)