Framework and reference for architecture design

14th Americas Conference on Information Systems, AMCIS 2008

Volumn 2, Issue , 2008, Pages 1195-1208

  Rohloff, Michael ^a  

^a UNIVERSITY OF POTSDAM   (Germany)

Author keywords

Architecture description; Architecture management; Blueprints; Enterprise architecture framework; Stakeholders; Views

Indexed keywords

ARCHITECTURE DESCRIPTION; ARCHITECTURE MANAGEMENT; ENTERPRISE ARCHITECTURE; STAKEHOLDERS; VIEWS;

BLUEPRINTS; INFORMATION SYSTEMS;

DESIGN;

EID: 79951880430     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (58)

1. Allen, P. (2006). Service Orientation, winning strategies and best practices. Cambridge, UK 2006
2. Arbab, F./ de Boer, F. / Bonsangue, M./ Lankhorst, M./. Proper, H./ van der Torre; L. (2007). Integrating Architectural Models. Enterprise Modelling and Information Systems Architectures, 2 (2007) 1, p. 40-57
3. Aranow, E. (2002). Enterprise Integration Strategies, Cutter 2002
4. Avison, D./ Jones, J./ Powell, P./ Wilson, D. (2004). Using and validating the strategic alignment model. In: The Journal of Strategic Information Systems 13 (2004) 3, p. 223-246.
5. Bachmann, F. (2000). Software Architecture Documentation in Practice: Documenting Architectural Layers, Special Report CMU/SEI-2000-SR-004, March 2000
6. Baummöl, U. (2006). Methodenkonstruktion für das Business/ IT Alignment, in: Wirtschaftsinformatik 48 (2006) 5, p. 314-322
7. Bernus, P./ Mertins, K./ Schmidt, G. (Eds.): Handbook of Information Systems, Berlin 1998
8. Bieberstein, N/ Bose, S./ Fiammante, M./ Jones, K./ Shah, R. (2006). Service-Oriented Architecture Compass-Business Value, Planning and Enterprise Roadmap, Upper Saddle River (Pearson) 2006
9. Buhl, U.; Heinrich, B. (Ed.) (2004): Meinung/Dialog: Unternehmensarchitekturen in der Praxis-Architekturdesign vs. situationsbedingte Realisierung von Informationssystemen, Wirtschaftsinformatik 46 (2004) 4, p. 311-321
10. Burke, B. (2003). Enterprise Architecture or City Planning?, META Group, Report 2638, 2003
11. Casewise (2006). Corporate Modeler, see http://www.casewise.com/, called 2008-04-15
12. Clements, P.; Bachmann, F.; Bass, L. (2003). Documenting Software Architectures: Views and Beyond, Addison-Wesley, 2003.
13. Dern, G. (2006). Management von IT-Architekturen, Wiesbaden 2006
14. Dietzsch, A. (2005). Architekturmanagement-Rahmen und Realisierung der Unternehmensarchitektur der Mobiliar, in Schelp, J./ Winter, R. (Ed.): Integrationsmanagement: Planung, Bewertung und Steuerung von Applikationslandschaften, Berlin et al. 2005, p. 231-266
15. Dietzsch, A./ Goetz, T. (2005). Nutzen-orientiertes Management einer Servcie-orientierten Unternehmensarchitektur, in Ferstl, O./ Sinz, E./ Eckert, S./ Isselhorst, T. (Hrsg.) Wirtschaftsinformatik 2005, Heidelberg 2005, p. 1517-1538
16. Durst, M./ Daum, M. (2007). Erfolgsfaktoren serviceorientierter Architekturen, in: HMD Praxis der Wirtschaftsinformatik 42 (2007) 253, S. 18-27
17. FEAF: Federal Enterprise Architecture Framework (FEAF), http://www.whitehouse.gov/omb/egov/, called 2008-04-15
18. Gartner: The Gartner Enterprise Architecture Framework, see http://www3.gartner.com/Init, called 2008-04-15
19. Gartner Group (2002). Enterprise Architecture and IT City Planning, July 2002
20. GERAM. Framework for a Generic Reference Enterprise Architecture Methodology, http://www.cit.gu.edu.au/ ~bernus/taskforce/geram/report.v1/report/report.html, called 2008-04-15
21. Gronau, N./ Rohloff, M. (2007). Managing Change: Business/ IT Alignment and Adaptability of Information Systems, in: Österle, H.; D'Atri, A.; Bartmann, D.; Pries-Heje, D.; Golden, W., Whitley, E. (Hrsg.): Proceedings ECIS 2007, 15th European Conference on Information Systems, Relevant rigour-Rigorous relevance, St. Gallen 2007
22. Günzel, H./ Rohloff, M. (2003). Architektur im Großen: Gegenstand und Handlungsfelder, in: Dittrich K.; König, W.; Oberweis, A., Rannenberg, K.; Wahlster, W. (Hrsg.): Informatik 2003, 33. Jahrestagung der Gesellschaft für Informatik e.V. (GI), Bonn 2003, Vol. 2 p. 422-425
23. Heinrich, L./ Lehner, F. (2005). Informationsmanagement, München et al. 2005
24. Henderson, J. C./ Venkatraman, N. (1999). Strategic alignment: Leveraging information technology for transforming organizations, IBM Systems Journal 38 (1999) 2/3, S. 472-485
25. IBM (1982). Business System Planning: Handbuch zur Planung von Informationssystemen (IBM Form GE-12-1400-2), Stuttgart 1982
26. IEEE (2000). IEEE Standard 1471-2000, Recommended Practice for Architectural Description of Software-Intensive Systems. IEEE Computer Society, New York, October 2000
27. IT Scope (2003a). IT Scope: Infrastructure Architecture Framework Guide, internal document, Siemens AG, 2003
28. IT Scope (2003b). IT Scope: Module Architecture: Master Document, internal document, Siemens AG, 2003
29. James, G. (2004). Architecture Frameworks: Tool Support, Gartner Research, November 2004
30. Keller, W. (2006). IT-Unternehmensarchitektur: Von der Geschäftsstrategie zur optimalen IT-Unterstützung, Heidelberg 2006
31. Krcmar, H. (2005). Informationsmanagement, Berlin et al. 2005
32. Lankes, J./ Matthes, F./ Wittenburg, A. (2005). Softwarekartographie: Systematische Darstellung von Anwendungslandschaften, in Ferstl, O./ Sinz, E./ Eckert, S./ Isselhorst, T. (Hrsg.) Wirtschaftsinformatik 2005: eEconomy, eGovernment, eSociety, Heidelberg 2005, S. 1443-1462
33. Lapkin, A. (2004a). Architecture Frameworks: How to Choose, Gartner Research, November 2004
34. Lapkin, A. (2004b). Architecture Frameworks: Some Options, Gartner Research, November 2004
35. Luftman, J. (2005). Key issues for IT executives 2004, in: MIS Quarterly Executive 4 (2005) 2, p. 269-285
36. Luftman, J. (2003). Assessing IT/business alignment, in: Information Strategy 20 (2003) 1, p. 7
37. Marks, E./ Bell, M. (2006).-Service Oriented Architecture: A Planning and Implementation Guide for Business and Technology. Hoboken 2006
38. Masak, D. (2005). Moderne Enterprise Architekturen, Berlin et al. 2005
39. Meta Group (2002). Executive Insights: Enterprise Architecture Desk Reference, 2002
40. Nieman, K. (2006). From Enterprise Architecture to IT-Governance, Wiesbaden 2006
41. Österle, H./ Winter, R (2003). Business Engineering: Auf dem Weg zum Unternehmen des Informationszeitalters, Berlin et al. 2003
42. Österle, H. (1995). Business Engineering: Prozess-und Systementwicklung, Berlin et al. 1995
43. Pulier, E./ Taylor, H. (2005). Understanding Enterprise SOA. Greenwich 2005
44. Ross, M./ Weil, P./ Robertson, D. (2006). Enterprise architecture as strategy: Creating a foundation for business execution, Harvard Business School Press, Boston 2006
45. Scheer, A.-W (1999). Architecture of Integrated Information Systems: Business Process Framework, Berlin et al. 1999
46. Schekkermann, J. (2006). How to survive in the Jungle of Enterprise Architecture Frameworks: Creating or Choosing an Enterprise Architecture Framework, Trafford 2006
47. Schönherr, M. (Ed.) (2004). Enterprise Application Integration: Serviceorientierung und nachhaltige Architekturen, Berlin 2004
48. Schulman, J. (2004). Architecture Frameworks: Provide System Road Maps, Gartner Research, November 2004
49. Siemens (2005). IT-Navigator Tool Description, internal document Siemens AG CIO, München 2005
50. Sinz, E.J. (2002). Architektur von Informationssystemen, in: Rechenberg, P.; Pomberger, G.: Informatik Handbuch, München 2002, p. 1055-1068
51. Sinz, E. (1997). Architektur von Informationssystemen, München 1997
52. Sowa, J.F./ Zachman, J. (1992). Extending and Formalizing the Framework for Information Systems Architecture, in: IBM Systems Journal 31 (1992) 3
53. Spewak, C./ Hill, S (2006). Enterprise Architecture Planning: Developing a Blueprint for Data, Applications, and Technology, New York 2006
54. TOGAF (2006). The Open Group Architecture Framework: Version 8.1.1 Enterprise Edition, ADM: Architecture Development Method), 2006 see http://www.opengroup.org/togaf/, http://www.togaf.org/ called 2008-04-15
55. Umek, A./ Tannhäuser, C. (2004): Wert schaffen durch nutzenorientiertes Architekturmanagement in EAI Projekten, in: Aier, S., Schönherr, M. (Eds.): Enterprise Application Integration: Service Orientierung und nachhaltige Architekturen, Berlin et al. 2004, pp. 49-71
56. Weiss, J. W./ Anderson, D. (2004). Aligning Technology and business strategy: Issues & Frameworks, A field study of 15 Companies, in: Proceeding of the 37th Hawaii International Conference on System Sciences 8 (2004) 8, S. 1-10.
57. Zachman, J. (1987). A Framework for Information Systems Architecture, in: IBM Systems Journal 26 (1987) 3
58. Zachmann Framework, see http://www.zifa.com/, called 2008-04-15