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

Enterprise Information Systems

Volumn 6, Issue 2, 2012, Pages 189-213

  Quartel, Dick ^a   Steen, Maarten W A ^a   Lankhorst, Marc M ^a  

^a Novay   (Netherlands)

Author keywords

ArchiMate; business requirements management; enterprise architecture; portfolio management; portfolio valuation

Indexed keywords

FINANCIAL DATA PROCESSING; INVESTMENTS;

ARCHIMATE; ARCHITECTURE-BASED; BUSINESS REQUIREMENT; ENTERPRISE ARCHITECTURE; LANGUAGE EXTENSIONS; PORTFOLIO MANAGEMENTS; PROJECT PORTFOLIO; SOFTWARE APPLICATIONS;

APPLICATION PROGRAMS;

EID: 84857164910     PISSN: 17517575     EISSN: 17517583     Source Type: Journal    
DOI: 10.1080/17517575.2011.625571     Document Type: Article

References (36)

1. Archer, N.P. and Ghasemzadeh, F. 1999. "An integrated framework for project portfolio selection". In Project portfolio management project portfolio management, Edited by: Dye, L.D. and Pennypacker, J.S. 117-133. West Chester: Center for Business Practices.
2. Benson, R., Bugnitz, T. and Walton, B. 2004. From business strategy to IT action: right decisions for a better bottom line, Hoboken, NJ: John Wiley Publishers.
3. CMMI Product Team. 2006. CMMI® for Development, Version 1.2, CMU/SEI-2006-TR-008 [online], Software Engineering Institute, Carnegie Mellon University. Available from: http://www.sei.cmu.edu/reports/06tr008.pdf [Accessed 28 September 2011]
4. Dardenne, A., van Lamsweerde, A. and Fickas, S. 1993. Goal-directed requirements acquisition. Science of Computer Programming, 20: 3-50.
5. Devraj, S. and Kohli, R. 2002. The IT Payoff - measuring the business value of information technology investments, Upper Saddle River, NJ: Prentice Hall Publishers.
6. Engelsman, W. 2010. Extending enterprise architecture modelling with business goals and requirements. Enterprise Information Systems, 5(1): 9-36.
7. Gammelgård, M., Ekstedt, M. and Närman, P. 2010. A method for assessing the business value of information system scenarios with an estimated credibility of the result. International Journal of Services Technology and Management, 13(1/2): 105-133.
8. Iacob, M.-E. and Jonkers, H. 2007. Quantitative analysis of service-oriented architectures. International Journal of Enterprise Information Systems, 3(1): 42-60.
9. ISACA. 2007. "CobiT 4.1 [online]. Rolling Meadows, Illinois, IT Governance Institute". Available from: http://www.isaca.org/cobit.htm [Accessed 28 September 2011]
10. ISO/IEC. 1991. Information technology - software product evaluation - quality characteristics and guidelines for their use, Geneva: International Standard ISO/IEC 9126, International Organization for Standardization, International Electrotechnical Commission.
11. ITGI. 2008. "Enterprise value: governance of IT investments". In The Val IT Framework 2.0 [online]. Rolling Meadows, Illinois, IT Governance Institute. Available from: http://www.itgi.org/valit/ [Accessed 28 September 2011]
12. Jacobson, I. 1995. "The use-case construct in object-oriented software engineering". In Scenario-based design: envisioning work and technology in system development, Edited by: Carroll, J.M. 309-338. New York: John Wiley & Sons.
13. Janssen, W., van Buuren, R. and Gordijn, J. Business case modelling for E-Services. Proceedings of the 18th BLED conference (e-Integration in Action).
14. Jeffery, M. and Leliveld, I. 2004. Best practices in IT portfolio management, MIT Sloan Management Review, 45 (3), 41-49.
15. Johnson, P. 2007. Enterprise architecture analysis with extended influence diagrams. Information System Frontiers, 9(2-3): 163-180.
16. Jonkers, H. 2004. Concepts for modelling enterprise architectures. International Journal of Cooperative Information Systems (IJCIS) [special issue on Architecture in IT], 13(3): 257-288.
17. Jonkers, H. 2010. ArchiMate extension for modeling TOGAF's implementation and migration phases, Reading, Berkshire: Whitepaper, The Open Group.
18. Kazman, R. Experience with performing architecture tradeoff analysis. Proceedings of the 21st international conference on software engineering. pp.54-63.
19. Kazman, R., Asundi, J. and Klein, M. 2002. "Making architecture design decisions: an economic approach". Pittsburgh, PA: Carnegie Mellon University. Report Number (CMU/SEI-2002-TR-035)
20. Lagerström, R. 2009. A method for creating enterprise architecture metamodels - applied to systems modifiability analysis. International Journal of Computer Science & Applications, 6(5): 89-120.
21. Lankhorst, M.M. 2009. Enterprise architecture at work - modelling, communication and analysis, 2nd ed., Berlin, Heidelberg: Springer.
22. Nord, R.L. 2003. Integrating the architecture tradeoff analysis method (ATAM) with the cost benefit analysis method (CBAM), Pittsburgh, PA: Carnegie Mellon University. Report Number (CMU/SEI-2003-TN-038)
23. Orr, K. 2002. Framework and processes for developing enterprise architectures. Cutter Executive Update, 6(2)
24. van der Pols, R. and Backer, Y. 2006. Application services library - a management guide, Zaltbommel: ASL Foundation/Van Haren Publishing.
25. Quartel, D., Engelsman, W. and Jonkers, H. 2010. Archimate extension for modeling and managing motivation, principles and requirements in TOGAF, Reading, Berkshire: Whitepaper, The Open Group.
26. Ranti, B. A review of information technology investment evaluation methodologies: the need for appropriate evaluation methods. Prosiding Konferensi Nasional Teknologi Informasi & Komunikasi untuk. Mei3-42006, Indonesia. Aula Barat & Timur Institut Teknologi Bandung.
27. Remenyi, D., Money, A. and Bannister, F. 2007. The effective measurement and management of ICT costs and benefits, USA: CIMA Publishers.
28. Schoman, K. and Ross, D.T. 1977. Structured analysis for requirements definition. IEEE Transactions on Software Engineering, 3(1): 363-386.
29. Schuurman, P., Berghout, E.W. and Powell, P. Calculating the importance of information systems: the method of Bedell revisited. CITER WP/010/PSEBPP. Sprouts working papers on information systems. University of Groningen. Available from: http://sprouts.aisnet.org/8-37. [Accessed 28 September 2011]
30. The Open Group. 2009a. ArchiMate_1.0 Specification, Zaltbommel: Van Haren Publishing.
31. The Open Group. 2009b. TOGAF™ Version 9, Zaltbommel: Van Haren Publishing.
32. Venkatraman, N. 1997. Beyond outsourcing: managing it resources as a value center. MIT Sloan Management Review, 38(3): 51-64.
33. Wierenga, H. 2009. Architectural information economics [online] Via Nova Architectura Available from: http://www.via-nova-architectura.org/artikelen/tijdschrift/architectural-information-economics.html. [Accessed 28 September 2011]
34. Wieringa, R. 2004. Requirements engineering: problem analysis and solution specification [extended abstract]. Lecture Notes in Computer Science, 3140: 13-16.
35. Willcocks, L.P. and Lester, S. 1996. Beyond the IT productivity paradox. European Management Journal, 14(3): 279-290.
36. Yu, E. Towards modelling and reasoning support for early-phase requirements engineering. Proceedings of the 3rd IEEE international symposium on requirements engineering (RE'97). January6-8. pp.226-235. Washington, DC: IEEE Computer Society.