The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.02 - March-April (2013 vol.17)
pp: 91-94
Christophe Vetterli , University of St.Gallen
Walter Brenner , University of St.Gallen
Falk Uebernickel , University of St.Gallen
Charles Petrie , University of St.Gallen
ABSTRACT
Requirements engineering methods are geared for developing information systems and aren't what's needed for today's world of rapidly changing, app-enabled products. Today's apps are more and more an integrated and central part of service delivery of new products. Requirements engineering for this new world can greatly benefit from design thinking. Merging design thinking with requirements engineering will integrate the strongly diverging human-oriented perspective as well as the more technically driven perspective. Overall, this results in a holistic perspective to develop a more customer-oriented solution, incorporating functional and nonfunctional requirements.
INDEX TERMS
paradigm shift, design thinking, requirements engineering, apps
CITATION
Christophe Vetterli, Walter Brenner, Falk Uebernickel, Charles Petrie, "From Palaces to Yurts: Why Requirements Engineering Needs Design Thinking", IEEE Internet Computing, vol.17, no. 2, pp. 91-94, March-April 2013, doi:10.1109/MIC.2013.32
REFERENCES
1. B. Nuseibeh and S. Easterbrook, “Requirements Engineering: A Roadmap,” Proc. Conf. Future of Software Eng. (ICSE 00), ACM, 2000, pp. 35–46.
2. P. Zave, “Feature Interactions and Formal Specifications in Telecommunications,” Computer, vol. 26, no. 8, 1993, pp. 20–29.
3. B.H.C. Chen and J.C. Atlee, “Research Directions in Requirements Engineering,” Proc. Future Software Eng. (FOSE 07), IEEE CS, 2007, pp. 285–303.
4. F. Paetsch, A. Eberlein, and F. Maurer, “Requirements Engineering and Agile Software Development,” Proc. 12th IEEE Int'l Workshop Enabling Technologies: Infrastructure for Collaborative Enterprises (WETICE 03), IEEE, 2003, pp. 308–313.
23 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool