Application and project portfolio valuation using enterprise architecture and business requirements modelling

This article describes an architecture-based approach to IT valuation. This approach offers organisations an instrument to valuate their application and project portfolios and to make well-balanced decisions about IT investments. The value of a software application is assessed in terms of its contribution to a selection of business goals. Based on such assessments, the value of different applications can be compared, and requirements for innovation, development, maintenance and phasing out can be identified. IT projects are proposed to realise the requirements. The value of each project is assessed in terms of the value it adds to one or more applications. This value can be obtained by relating the ‘as-is’ application portfolio to the ‘to-be’ portfolio that is being proposed by the project portfolio. In this way, projects can be ranked according to their added value, given a certain selection of business goals. The approach uses ArchiMate to model the relationship between software applications, business processes, services and products. In addition, two language extensions are used to model the relationship of these elements to business goals and requirements and to projects and project portfolios. The approach is illustrated using the portfolio method of Bedell and has been implemented in BiZZdesign Architect.

[1]  M. Jeffery,et al.  Best Practices in IT Portfolio Management , 2004 .

[2]  Ivar Jacobson,et al.  The use-case construct in object-oriented software engineering , 1995 .

[3]  Frank Bannister,et al.  The effective measurement and management of ICT costs and benefits. 3rd edition. , 2007 .

[4]  Mark Klein,et al.  Experience with performing architecture tradeoff analysis , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[5]  Van Haren,et al.  TOGAF Version 9.1 , 2011 .

[6]  Jaap Gordijn,et al.  Business Case Modelling for E-Services , 2005, Bled eConference.

[7]  Robert Lagerström,et al.  A method for creating entreprise architecture metamodels applied to systems modifiability , 2009, Int. J. Comput. Sci. Appl..

[8]  Fereidoun Ghasemzadeh,et al.  An integrated framework for project portfolio selection , 1999 .

[9]  Maria-Eugenia Iacob,et al.  ArchiMate ® Extension for Modeling the TOGAF ™ Implementation and Migration Phases , 2010 .

[10]  Roel Wieringa,et al.  Requirements Engineering: Problem Analysis and Solution Specification (Extended Abstract) , 2004, ICWE.

[11]  Wilco Engelsman,et al.  ArchiMate Extension for Modeling and Managing Motivation , Principles and Requirements in TOGAF TM , 2010 .

[12]  Hoppenbrouwers,et al.  Concepts for Modelling Enterprise Architectures , 2003 .

[13]  Robert Lagerström,et al.  Enterprise architecture analysis with extended influence diagrams , 2007, Inf. Syst. Frontiers.

[14]  Bill Walton,et al.  From Business Strategy to IT Action: Right Decisions for a Better Bottom Line , 2004 .

[15]  Henk Jonkers,et al.  Concepts For Modeling Enterprise Architectures , 2004, Int. J. Cooperative Inf. Syst..

[16]  Rick Kazman,et al.  Making Architecture Design Decisions: An Economic Approach , 2002 .

[17]  Henk Jonkers,et al.  ArchiMate Extension for Modeling TOGAFs Implementation and Migration Phases , 2010 .

[18]  Magnus Gammelgård,et al.  A method for assessing the business value of information system scenarios with an estimated credibility of the result , 2010, Int. J. Serv. Technol. Manag..

[19]  Shan Rajegopal,et al.  Project Portfolio Management: Leading the Corporate Vision , 2007 .

[20]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[21]  James E. Tomayko,et al.  Integrating the Architecture Tradeoff Analysis Method (ATAM) with the Cost Benefit Analysis Method (CBAM) , 2003 .

[22]  Douglas T. Ross,et al.  Structured Analysis for Requirements Definition , 1977, IEEE Transactions on Software Engineering.

[23]  Rajiv Kohli,et al.  The IT Payoff: Measuring the Business Value of Information Technology Investments , 2002 .

[24]  T.M. Duffy,et al.  Scenario-Based Design: Envisioning Work and Technology in System Development [Book Review] , 1996, IEEE Transactions on Professional Communication.

[25]  R. Gisser.  Extended abstract , 2011 .

[26]  N. Venkatraman.  Beyond Outsourcing: Managing IT Resources as a Value Center , 1997 .

[27]  Egon Berghout,et al.  Calculating the Importance of Information Systems: The Method of Bedell Revisited , 2008 .

[28]  Marten van Sinderen,et al.  Extending enterprise architecture modelling with business goals and requirements , 2011, Enterp. Inf. Syst..

[29]  Henk Jonkers,et al.  Quantitative Analysis of Service-Oriented Architectures , 2007, Int. J. Enterp. Inf. Syst..

[30]  Lorin M. Hitt,et al.  Beyond the productivity paradox , 1998, CACM.

[31]  Marc M. Lankhorst.  Enterprise Architecture at Work - Modelling, Communication and Analysis, 3rd Edition , 2005, The Enterprise Engineering Series.

[32]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[33]  John M. Carroll,et al.  Scenario-based design: envisioning work and technology in system development: john wiley & sons , 1995 .