Successful IT application architecture design: An empirical study

Information Systems and e-Business Management

Volumn 4, Issue 2, 2006, Pages 107-135

  Martin, Andrew ^a  

^a UNIVERSITY OF WARWICK   (United Kingdom)

Author keywords

Application; Architecture; Design; Information; Performance; Project; Software engineering; Technology

Indexed keywords

EID: 33645233143     PISSN: 16179846     EISSN: 16179854     Source Type: Journal    
DOI: 10.1007/s10257-005-0029-y     Document Type: Article

References (49)

1. Aerts ATM, Goossenaerts JBM, Hammer DK, Wortmann JC (2004) Architectures in context: On the evolution of business, application software, and ICT platform architectures. Inf Manage 41:781-794
2. Ballantine J, Bonner M, Levy M, Martin A, Munro I, Powell P (1996) The 3-D model of information systems success: The search for the dependent variable continues. Inf Resour Manage J 9(4):5-14
3. Bass L, Clements P, Kazman R (1998) Software architecture in practice. Addison-Wesley, Reading, MA
4. Behrsin M, Mason G, Sharpe T (1994) Reshaping IT for business flexibility: The IT architecture as a common language for dealing with change. McGraw-Hill, NY
5. Broadbent M, Weill P (1997) Management by maxim: How business and IT managers can create IT infrastructure. Sloan Manage Rev Spring 1997:77-91
6. Broadbent M, Weill P (1999) The implications of information technology infrastructure for business process redesign. MIS Q 23(2):159-172
7. Broadbent M, Weill P, Neo BS (1999) Strategic context and patterns of IT infrastructure capability. J Strateg Inf Sys 8(2):157-187
8. Ewusi-Mensah K, Przasnyski Z (1991) On information systems project abandonment: An exploratory study of organizational practices. MIS Q 15(1):67-86
9. Finkelstein A, Kramer J (2000) Software engineering: A roadmap. In: Finkelstein A (ed) The future of software engineering, ACM Press, NY, pp 5-22; also at http://www.cs.ucl.ac.uk/staff/A.Finkelstein/fose/ finalfinkelstein.pdf last accessed August 2005
10. Fitzgerald G (1990) Achieving flexible information systems: The case of improved analysis. J Inf Technol 5:5-11
11. Fitzgerald B (1996) Formalized systems development methodologies: A critical perspective. Inf Sys J 6:3-23
12. Fitzgerald B (1997) The use of systems development methodologies in practice: A field study. Inf Sys J 7:201-212
13. Fitzgerald G, Philippedes A, Probert S (1999) Information systems development, maintenance and enhancement: Findings from a UK study. Int J Inf Manage 19:319-328
14. Gonzales R (2005) Developing the requirements discipline: Software vs. systems. IEEE Softw 22(2):59-61
15. Harris T, Rothwell JW, Lloyd PTL (1999) Experiences in reusing technical reference architectures. IBM Sys J 38(1):98-117
16. Huber N (2003) Hitting targets? The state of UK IT project management. Comput Wkly 11/4/2003:22-23
17. Jeffery M, Leliveld I (2004) Best practices in IT portfolio management. MIT Sloan Manage Rev Spring 45(3):41-49
18. Jiang JJ, Klein G, Hwang H-G, Huang J, Hung S-Y (2004) An exploration of the relationship between software development process maturity and project performance. Inf Manage 41:279-288
19. Kazman R, Bass L (2002) Making architecture reviews work in the real world. IEEE Softw 19(1):67-73
20. Keider S (1984) Why systems development projects fail. J Inf Syst Manage 1(3):33-38
21. Langdon CS (2003) Information systems architecture styles and business interaction patterns: Toward theoretic correspondence. Inf Sys e-Bus Manage 1:283-304
22. Lloyd PTL, Galambos GM (1999) Technical reference architectures. IBM Syst J 38(1):51-75
23. Lyytinen K, Hirschheim R (1987) Information systems failures: A survey and classification of the empirical literature. Oxf Surv Inf Technol 4:257-309
24. Lyytinen K, Mathiassen L, Ropponen J (1996) A framework for software risk management. J Inf Technol 11(4):275-285
25. Lyytinen K, Mathiassen L, Ropponen J (1998) Attention shaping and software risk- a categorical analysis of four classical approaches. Inf Sys Res 9(3):233-255
26. Maier MW, Rechtin E (2002) The art of systems architecting, 2nd edn. CRC Press, Boca Raton
27. Maranzano JF, Rozsypal SA, Zimmerman GH, Warnken GW, Wirth PE, Weiss DM (2005) Architecture reviews: Practice and experience. IEEE Softw 22(2):34-43
28. Martin A (2003) What drives the configuration of information technology projects?: Exploratory research in ten organizations. J Inf Technol 18(1):1-15
29. Martin A, Chan M (1996) Information systems project redefinition in New Zealand: Will we ever learn. Aust Comput J 28(1):27-40
30. Nidumolu S (1995) The effect of coordination and uncertainty on software project performance: Residual performance risk as an intervening variable. Inf Sys Res 6(3):191-219
31. Norusis MJ (1985) SPSS-X advanced statistics guide. SPSS/McGraw-Hill
32. Paulk MC, Curtis B, Chrissis MB, Weber CV (1993) Capability maturity model, Version 1.1. IEEE Softw 10(4):18-27
33. Pinto JK, Slevin DP (1987) Critical factors in successful project implementation. IEEE Trans Eng Manage EM-34(1):22-27
34. Remenyi D, Money A, Twite A (1991) A guide to measuring and managing IT benefits. NCC Blackwell, Oxford
35. Ropponen J, Lyytinen K (2000) Components of software development risk: how to address them? A project manager survey. IEEE Trans Softw Eng 26(2):98-112
36. Ross JW (2003) Creating a strategic IT architecture competency: Learning in stages. MIS Q Exec 1(2):31-43
37. Sauer C, Willcocks LP (2002) The evolution of the organizational architect. MIT Sloan Manage Rev Camb 43(3):41-49
38. Sewell MT, Sewell LM (2002) The software architect's profession: An introduction. Prentice Hall PTR, Upper Saddle River NJ
39. Shaw M, Garlan D (1996) Software architecture: Perspectives on an emerging discipline. Prentice Hall, NJ
40. Software Engineering Institute (2002a) CMMISM for systems engineering/ software engineering, Version 1.1, continuous representation (CMMI-SE/ SW, V1.1, Continuous), technical report CMU/SEI-2002-TR-001, and http://www.sei.cmu.edu/publications/documents/02.reports/02tr001.html last accessed 31/8/2005
41. Software Engineering Institute (2002b) CMMISM for systems engineering/ software engineering, Version 1.1, staged representation (CMMI-SE/SW, V1.1, Staged), technical report CMU/SEI-2002-TR-002, and http://www.sei.cmu.edu/publications/documents/02.reports/02tr002.html last accessed 31/8/2005
42. Software Engineering Institute (2005) Capability maturity model integration (CMMI) overview. http://www.sei.cmu.edu/cmmi/adoption/pdf/ cmmi-overview05.pdf Last accessed 31/8/2005
43. Sommerville I (2004) Software engineering, 7th edn. Pearson Addison-Wesley, Boston
44. Thorogood A, Yetton P (2004) Reducing the technical complexity and business risk of major systems projects. In: 37th Hawaii International Conference on System Sciences
45. Truex D, Baskerville R, Travis J (2000) Amethodical systems development: the deferred meaning of systems development methods. Acc Manage Inf Technol 10:53-79
46. Wallace L, Keil M, Rai A (2004) How software project risk affects project performance: An investigation of the dimensions of risk and an exploratory model. Decis Sci 35(2):289-321
47. Weill P, Broadbent M (2000) Managing IT infrastructure: A strategic choice. In: Zmud RW (ed) Framing the domains of IT management: projecting the future... through the past, Pinnaflex, pp 329-353
48. Weill P, Subramani M, Broadbent M (2002) Building IT infrastructure for strategic agility. MIT Sloan Manage Rev 44(1):57-65
49. Yetton P, Martin A, Sharma R, Johnston K (2000) A model of information systems development project performance. Inf Sys J 10(4):263-289