Boundary Objects for Value-based Requirements Engineering

Value-based requirements engineering focuses on the alignment of requirements engineering decisions and business value decisions. There is much evidence on the importance of this alignment and there are several approaches for tackling specific alignment decisions such as e.g. release planning. However, for the general picture of what this alignment is about, a common language between requirements engineering and business decision makers is needed. The goal of this paper is to make explicit the boundary objects between requirements engineering and business value decisions. These boundary objects have been derived from literature and are evaluated in three typical scenarios of how software can provide value to business: (1) the product management scenario, where software is (part of) a product sold by the company, (2) the IT procurement scenario where the software and related services are procured by the company, and (3) the IT development scenario, where software is developed in-house to be used in the IT infrastructure of the company. An empirical study of the relevance of the identified boundary objects is the most important future work.

[1]  Patrick C. K. Hung,et al.  Factors affecting the buy vs build decision in large Australian organisations , 2008, J. Inf. Technol..

[2]  Blaize Horner Reich,et al.  IT alignment: what have we learned? , 2007, J. Inf. Technol..

[3]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.

[4]  Susan Leigh Star,et al.  Institutional Ecology, `Translations' and Boundary Objects: Amateurs and Professionals in Berkeley's Museum of Vertebrate Zoology, 1907-39 , 1989 .

[5]  Nicholas G. Carr,et al.  Does IT Matter? Information Technology and the Corrosion of Competitive Advantage , 2004 .

[6]  Claes Wohlin,et al.  A Value-Based Approach in Requirements Engineering: Explaining Some of the Fundamental Concepts , 2007, REFSQ.

[7]  R. Kaplan,et al.  The balanced scorecard--measures that drive performance. , 2015, Harvard business review.

[8]  F. Sastron,et al.  Introduction to the information system , 1992 .

[9]  Hans Nilsson,et al.  Aligning IT Strategy with Business Strategy through the Balanced Scorecard in a Multinational Pharmaceutical Company , 2007, 2007 40th Annual Hawaii International Conference on System Sciences (HICSS'07).

[10]  Ram Chillarege,et al.  The Marriage of Business Dynamics and Software Engineering , 2002, IEEE Softw..

[11]  Sherif Ali Mohtady Mohamed,et al.  Strategic implementation of IT/IS projects in construction , 2002 .

[12]  Claes Wohlin,et al.  Aligning Requirements with Business Objectives : A Framework for Requirements Engineering Decisions , 2005 .

[13]  Linda Gorchels.  The Product Manager's Handbook: The Complete Product Management Resource , 2000 .

[14]  D. Probert,et al.  Developing a framework for make‐or‐buy decisions , 2000 .

[15]  Karl Cox,et al.  Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams , 2006, J. Syst. Softw..

[16]  Albert Boonstra,et al.  Managing Information Systems: An Organisational Perspective , 2002 .

[17]  R. Westbrook,et al.  SWOT Analysis: It's Time for a Product Recall , 1997 .

[18]  Barry W. Boehm,et al.  Value-based software engineering: reinventing , 2003, SOEN.

[19]  Leslie P. Willcocks,et al.  Project Management For Information Systems , 1991, J. Inf. Technol..

[20]  Christof Ebert,et al.  The impacts of software product management , 2007, J. Syst. Softw..

[21]  Suzanne D. Pawlowski,et al.  Supporting shared information systems: boundary objects, communities, and brokering , 2000, ICIS.