Enterprise architecture is a description of an enterprise from an integrated business and IT perspective intended to bridge the communication gap between business and IT stakeholders and improve business and IT alignment. Enterprise architecture consists of multiple different artifacts providing certain views of an organization and the available enterprise architecture literature offers a number of comprehensive lists of artifacts that can be used as part of an enterprise architecture practice. However, these lists of enterprise architecture artifacts were never validated empirically and the practical usage of different artifacts still remains largely unexplored. Based on a comprehensive empirical analysis of enterprise architecture artifacts used in 27 diverse organizations, this study identifies the list of 24 common artifacts that proved useful in practice and describes in detail their usage and purpose. Although this study does not attempt to theorize on the findings, it makes a significant empirical contribution to the enterprise architecture discipline. In particular, this study (1) provides the first consistent list of enterprise architecture artifacts that actually proved useful in organizations, (2) offers the first available systematic description of their usage, (3) questions the common view of enterprise architecture as a set of business, information, applications and technology architectures and (4) questions the widely accepted conceptualization of enterprise architecture as a set of the current state, future state and transition roadmap. This study provides compelling empirical evidence in favor of reconceptualizing enterprise architecture and calls for further research in this direction.
AbrahamR. (2013). Enterprise architecture artifacts as boundary objects—A framework of properties. In van HillegersbergJ.van HeckE.ConnollyR. (Eds.), Proceedings of the 21st European Conference on Information Systems (pp. 1–12). Atlanta, GA: Association for Information Systems.
2.
AbrahamsonE. (1991). Managerial fads and fashions: The diffusion and rejection of innovations. Academy of Management Review, 16, 586–612.
3.
AbrahamsonE. (1996). Management fashion. Academy of Management Review, 21, 254–285.
4.
AgerfalkP. J. (2014). Insufficient theoretical contribution: A conclusive rationale for rejection?European Journal of Information Systems, 23, 593–599.
5.
AhlemannF.LegnerC.SchafczukD. (2012). Introduction. In AhlemannF.StettinerE.MesserschmidtM.LegnerC. (Eds.), Strategic enterprise architecture management: Challenges, best practices, and future developments (pp. 1–33). Berlin, Germany: Springer.
6.
AhlemannF.StettinerE.MesserschmidtM.LegnerC. (Eds.). (2012). Strategic enterprise architecture management: Challenges, best practices, and future developments. Berlin, Germany: Springer.
7.
AlaeddiniM.SalekfardS. (2013). Investigating the role of an enterprise architecture project in the business-IT alignment in Iran. Information Systems Frontiers, 15, 67–88.
BenbasatI.GoldsteinD. K.MeadM. (1987). The case research strategy in studies of information systems. MIS Quarterly, 11, 369–386.
13.
BernardS. A. (2012). An introduction to enterprise architecture (3rd ed.). Bloomington, IN: AuthorHouse.
14.
BischoffS.AierS.WinterR. (2014). Use it or lose it? The role of pressure for use and utility of enterprise architecture artifacts. In ProperH. A.RalyteJ.Marchand-MailletS.LinK. J., (Eds.), Proceedings of the 16th IEEE Conference on Business Informatics (pp. 133–140). New York, NY: IEEE.
BlomqvistS.HalenM.HeleniusM. (2015). Connecting enterprise architecture with strategic planning processes: Case study of a large Nordic finance organization. In KornyshovaE. (Ed.), Proceedings of the 17th IEEE Conference on Business Informatics (pp. 43–50). New York, NY: IEEE.
17.
BoarB. H. (1999). Constructing blueprints for enterprise IT architectures. New York, NY: Wiley.
18.
BradleyR. V.PrattR. M.ByrdT. A.OutlayC. N.WynnD. E.Jr. (2012). Enterprise architecture, IT effectiveness and the mediating role of IT alignment in US hospitals. Information Systems Journal, 22, 97–127.
19.
BucklS.ErnstA. M.LankesJ.MatthesF.SchwedaC. M. (2009). State of the art in enterprise architecture management. Munich, Germany: Software Engineering for Business Information Systems.
20.
CameronB. H.McMillanE. (2013). Analyzing the current trends in enterprise architecture frameworks. Journal of Enterprise Architecture, 9(1), 60–71.
21.
CarboneJ. A. (2004). IT architecture toolkit. Upper Saddle River, NJ: Prentice Hall.
22.
ChiassonM. W.DavidsonE. (2005). Taking industry seriously in information systems research. MIS Quarterly, 29, 591–605.
23.
ConnorD. A. (1988). Computer systems development: Strategic Resource Information Planning and Execution. Englewood Cliffs, NJ: Prentice Hall.
DahalinZ. M.RazakR. A.IbrahimH.YusopN. I.KasiranM. K. (2010). An enterprise architecture methodology for business-IT alignment: Adopter and developer perspectives. In SolimanK. S. (Ed.), Proceedings of the 14th International Business Information Management Association Conference (pp. 1–14). King of Prussia, PA: International Business Information Management Association.
26.
DarkeP.ShanksG.BroadbentM. (1998). Successfully completing case study research: Combining rigour, relevance and pragmatism. Information Systems Journal, 8, 273–289.
27.
Department of Defense Architecture Framework. (2007). The DoDAF architecture framework (Version 1.5, Vol. II: Product Descriptions). Arlington County, VA: Department of Defense.
28.
de ReuverM.SørensenC.BasoleR. C. (2018). The digital platform: A research agenda. Journal of Information Technology, 33, 124–135.
29.
de VriesM.van RensburgA. C. J. (2009). Evaluating and refining the ‘enterprise architecture as strategy’ approach and artifacts. South African Journal of Industrial Engineering, 20(1), 31–43.
30.
EdelmanB. (2015). How to launch your digital platform. Harvard Business Review, 93(4), 90–97.
31.
EisenhardtK. M. (1989). Building theories from case study research. Academy of Management Review, 14, 532–550.
32.
FallmyrT.BygstadB. (2014). Enterprise architecture practice and organizational agility: An exploratory study. In SpragueR. H. (Ed.), Proceedings of the 47th Hawaii International Conference on System Sciences (pp. 3788–3797). New York, NY: IEEE.
33.
Federal Enterprise Architecture. (2001). A practical guide to federal enterprise architecture (Version 1.0). Springfield, VA: Chief Information Officer Council.
34.
Federal Enterprise Architecture Framework. (1999). Federal enterprise architecture framework (Version 1.1). Springfield, VA: Chief Information Officer Council.
35.
FoorthuisR.van SteenbergenM.BrinkkemperS.BrulsW. A. (2016). A theory building study of enterprise architecture practices and benefits. Information Systems Frontiers, 18, 541–564.
36.
GallN. (2012). Gartner’s 2011 Global Enterprise Architecture Survey: EA frameworks are still homemade and hybrid (#G00226400). Stamford, CT: Gartner.
37.
GibsonJ. W.TesoneD. V. (2001). Management fads: Emergence, evolution, and implications for managers. Academy of Management Executive, 15, 122–133.
38.
GreefhorstD.ProperE. (2011). Architecture principles: The cornerstones of enterprise architecture. Berlin, Germany: Springer.
39.
HalenM.BlomqvistS.HeleniusM. (2014). Enterprise architecture applied or not? In GrozdanicV. (Ed.), Proceedings of the 10th European Conference on Management, Leadership and Governance (pp. 118–127). Sonning Common, UK: Academic Conferences and Publishing International.
40.
HambrickD. C. (2007). The field of management’s devotion to theory: Too much of a good thing?Academy of Management Journal, 50, 1346–1352.
41.
HansenA. M.KraemmergaardP.MathiassenL. (2011). Rapid adaptation in digital transformation: A participatory process for engaging IS and business leaders. MIS Quarterly Executive, 10, 175–185.
42.
HarrellJ. M.SageA. P. (2010). An enterprise architecture methodology to address the enterprise dilemma. Information, Knowledge, Systems Management, 9, 211–237.
43.
HelfatC. E. (2007). Stylized facts, empirical research and theory development in management. Strategic Organization, 5, 185–192.
44.
HolcmanS. B. (2013). Reaching the pinnacle: A methodology of business understanding, technology planning, and change. Pinckney, MI: Pinnacle Business Group.
45.
HolstM. S.SteensenT. W. (2011). The successful enterprise architecture effort. Journal of Enterprise Architecture, 7(4), 16–22.
46.
IBM. (2006). An introduction to IBM’s enterprise architecture consulting method. Armonk, NY: IBM Global Services.
47.
JosephD. (2009). Trends in enterprise architecture: Virtualization, visualization, service-orientation, and personal architectures. Journal of Enterprise Architecture, 5(3), 9–17.
48.
KappelmanL.McLeanE.JohnsonV.GerhartN. (2014). The 2014 SIM IT key issues and trends study. MIS Quarterly Executive, 13, 237–263.
49.
KappelmanL.McLeanE.JohnsonV.TorresR. (2016). The 2015 SIM IT issues and trends study. MIS Quarterly Executive, 15(1), 55–83.
50.
KappelmanL.McLeanE.JohnsonV.TorresR.NguyenQ.MaurerC.SnyderM. (2017). The 2016 SIM IT issues and trends study. MIS Quarterly Executive, 16(1), 47–80.
51.
KarimiJ.WalterZ. (2015). The role of dynamic capabilities in responding to digital disruption: A factor-based study of the newspaper industry. Journal of Management Information Systems, 32(1), 39–81.
52.
KeenP.WilliamsR. (2013). Value architectures for digital business: Beyond the business model. MIS Quarterly, 37, 643–648.
53.
KiatS. E.ChiewL. H.HongP. S.FungC. C. (2008). The organization’s compass–Enterprise architecture. Journal of Enterprise Architecture, 4(1), 11–19.
54.
KieserA. (1997). Rhetoric and myth in management fashion. Organization, 4, 49–74.
55.
KotusevS. (2017a). Different approaches to enterprise architecture. Journal of Enterprise Architecture, 12(4), 9–16.
56.
KotusevS. (2017b). Enterprise architecture: What did we study?International Journal of Cooperative Information Systems, 26(4), 1–84.
57.
KotusevS.SinghM.StoreyI. (2015a). Consolidating enterprise architecture management research. In BuiT. X.SpragueR. H. (Eds.), Proceedings of the 48th Hawaii International Conference on System Sciences (pp. 4069–4078). New York, NY: IEEE.
58.
KotusevS.SinghM.StoreyI. (2015b). Investigating the usage of enterprise architecture artifacts. In BeckerJ.vom BrockeJ.de MarcoM. (Eds.), Proceedings of the 23rd European Conference on Information Systems (pp. 1–12). Atlanta, GA: Association for Information Systems.
59.
LangeM.MendlingJ.ReckerJ. (2016). An empirical analysis of the factors and measures of enterprise architecture management success. European Journal of Information Systems, 25, 411–431.
60.
LangenbergK.WegmannA. (2004). Enterprise architecture: What aspects is current Research targeting? (#IC/2004/77). Lausanne, Switzerland: Ecole Polytechnique Federale de Lausanne.
61.
LankhorstM. (2013). Enterprise architecture at work: Modelling, communication and analysis (3rd ed.). Berlin, Germany: Springer.
62.
LiW.LiuK.BelitskiM.GhobadianA.O’ReganN. (2016). e-Leadership through strategic alignment: An empirical study of small- and medium-sized enterprises in the digital age. Journal of Information Technology, 31, 185–206.
63.
LongepeC. (2003). The enterprise architecture IT project: The urbanisation paradigm. London, England: Kogan Page Science.
64.
MillerD. (2007). Paradigm prison, or in praise of atheoretic research. Strategic Organization, 5, 177–184.
65.
MillerD.HartwickJ. (2002). Spotting management fads. Harvard Business Review, 80(10), 26–27.
66.
MillerD.HartwickJ.Le Breton-MillerI. (2004). How to detect a management fad—And distinguish it from a classic. Business Horizons, 47(4), 7–16.
67.
MykhashchukM.BucklS.DierlT.SchwedaC. M. (2011). Charting the landscape of enterprise architecture management. In BernsteinA.SchwabeG. (Eds.), Proceedings of the 9th International Conference on Wirtschaftsinformatik (pp. 570–577). Atlanta, GA: Association for Information Systems.
68.
NiemannK. D. (2006). From enterprise architecture to IT governance: Elements of effective IT management. Wiesbaden, Germany: Vieweg.
69.
NiemiE.PekkolaS. (2017). Using enterprise architecture artefacts in an organisation. Enterprise Information Systems, 11, 313–338.
70.
NurcanS.SchmidtR. (2009). Service oriented enterprise-architecture for enterprise engineering introduction. In TosicV. (Ed.), Proceedings of the 13th IEEE International Enterprise Distributed Object Computing Conference Workshops (pp. 247–253). New York, NY: IEEE.
The Open Group Architecture Framework. (2011). TOGAF Version 9.1 (#G116). Reading, UK: The Open Group.
74.
Partnership for Research in Information Systems Management. (1986). PRISM: Dispersion and interconnection: Approaches to distributed systems architecture. Cambridge, MA: CSC Index.
75.
PulkkinenM. (2006). Systemic management of architectural decisions in enterprise architecture planning. Four dimensions and three abstraction levels. In SpragueR. H. (Ed.), Proceedings of the 39th Hawaii International Conference on System Sciences (pp. 1–9). New York, NY: IEEE.
76.
RadekeF. (2010). Awaiting explanation in the field of enterprise architecture management. In SantanaM.LuftmanJ. N.VinzeA. S. (Eds.), Proceedings of the 16th Americas Conference on Information Systems (pp. 1–10). Atlanta, GA: Association for Information Systems.
77.
RahimiF.GotzeJ.MollerC. (2017). Enterprise architecture management: Toward a taxonomy of applications. Communications of the Association for Information Systems, 40, 120–166.
78.
RossJ. W. (2011). Gaining competitive advantage from enterprise architecture (Executive Seminar: Enabling IT Value Through Enterprise Architecture). Retrieved from https://www.youtube.com/watch?v=ScHG63YmJ2k&t=572
79.
RossJ. W.SebastianI.BeathC.MockerM.MoloneyK.FonstadN. (2016). Designing and executing digital strategies. In FitzgeraldB.MooneyJ. (Eds.), Proceedings of the 37th International Conference on Information Systems (pp. 1–17). Atlanta, GA: Association for Information Systems.
80.
RossJ. W.WeillP.RobertsonD. C. (2006). Enterprise architecture as strategy: Creating a foundation for business execution. Boston, MA: Harvard Business School Press.
81.
Saint-LouisP.MorencyM. C.LapalmeJ. (2017). Defining enterprise architecture: A systematic literature review. In HalleS.DijkmanR.LapalmeJ. (Eds.), Proceedings of the 21st IEEE International Enterprise Distributed Object Computing Conference Workshops (pp. 41–49). New York, NY: IEEE.
82.
SchekkermanJ. (2004). How to survive in the jungle of enterprise architecture frameworks: Creating or choosing an enterprise architecture framework (2nd ed.). Victoria, British Columbia, Canada: Trafford Publishing.
83.
SchekkermanJ. (2005). Trends in enterprise architecture 2005: How are organizations progressing?Amersfoort, The Netherlands: Institute for Enterprise Architecture Developments.
84.
SchekkermanJ. (2006). Extended enterprise architecture framework essentials guide (Version 1.5). Amersfoort, The Netherlands: Institute for Enterprise Architecture Developments.
85.
SchekkermanJ. (2008). Enterprise architecture good practices guide: How to manage the enterprise architecture practice. Victoria, British Columbia, Canada: Trafford Publishing.
86.
SchmidtC.BuxmannP. (2011). Outcomes and success factors of enterprise IT architecture management: Empirical insight from the international financial services industry. European Journal of Information Systems, 20, 168–185.
87.
SchoenherrM. (2008). Towards a common terminology in the discipline of enterprise architecture. In FeuerlichtG.LamersdorfW. (Eds.), Proceedings of the 3rd Trends in Enterprise Architecture Research Workshop (pp. 400–413). New York, NY: Springer.
88.
ScholtzB.CalitzA.ConnolleyA. (2013). An analysis of the adoption and usage of enterprise architecture. In GerberA.van DeventerP. (Eds.), Proceedings of the 1st Enterprise Systems Conference (pp. 1–9). New York, NY: IEEE.
89.
ShanksG.GloetM.SomehI. A.FramptonK.TammT. (2018). Achieving benefits with enterprise architecture. Journal of Strategic Information Systems, 27, 139–156.
90.
SiaS. K.SohC.WeillP. (2016). How DBS bank pursued a digital business strategy. MIS Quarterly Executive, 15, 105–121.
91.
SimonD.FischbachK.SchoderD. (2013). An exploration of enterprise architecture research. Communications of the Association for Information Systems, 32(1), 1–72.
92.
SimonD.FischbachK.SchoderD. (2014). Enterprise architecture management and its role in corporate strategic management. Information Systems and E-Business Management, 12(1), 5–42.
93.
SowaJ. F.ZachmanJ. A. (1992). Extending and formalizing the framework for information systems architecture. IBM Systems Journal, 31, 590–616.
94.
SpewakS. H.HillS. C. (1992). Enterprise architecture planning: Developing a blueprint for data, applications and technology. New York, NY: Wiley.
95.
TammT.SeddonP. B.ShanksG.ReynoldsP. (2011). How does enterprise architecture add value to organisations?Communications of the Association for Information Systems, 28, 141–168.
96.
Technical Architecture Framework for Information Management. (1996). Department of defense technical architecture framework for information management (Vol. 4, DoD Standards-Based Architecture Planning Guide, Version 3.0). Arlington County, VA: Defense Information Systems Agency.
WagterR.van den BergM.LuijpersJ.van SteenbergenM. (2005). Dynamic enterprise architecture: How to make it work. Hoboken, NJ: Wiley.
101.
WardleC. (1984). The evolution of information systems architecture. In NunamakerJ.KingJ. L.KraemerK. L. (Eds.), Proceedings of the 5th International Conference on Information Systems (pp. 205–217). Atlanta, GA: Association for Information Systems.
102.
WeillP.OlsonM. H. (1989). Managing investment in information technology: Mini case examples and implications. MIS Quarterly, 13(1), 3–17.
103.
WeillP.RossJ. W.QuaadgrasA. (2010). Achieving superior value from digitization: The MIT CISR value framework. Cambridge, MA: Center for Information Systems Research, MIT Sloan School of Management.
104.
WeillP.WoernerS. L. (2013a). Managing total digitization: The next frontier. Cambridge, MA: Center for Information Systems Research, MIT Sloan School of Management.
105.
WeillP.WoernerS. L. (2013b). Optimizing your digital business model. MIT Sloan Management Review, 54(3), 71–78.
106.
WeillP.WoernerS. L. (2018a). Is your company ready for a digital future?MIT Sloan Management Review, 59(2), 21–25.
107.
WeillP.WoernerS. L. (2018b). What’s your digital business model? Six questions to help you build the next-generation enterprise. Boston, MA: Harvard Business School Press.
108.
WestermanG.BonnetD. (2015). Revamping your business through digital transformation. MIT Sloan Management Review, 56(3), 10–13.
109.
WestermanG.BonnetD.McAfeeA. (2014). Leading digital: Turning technology into business transformation. Boston, MA: Harvard Business School Press.
110.
WinterR.FischerR. (2006). Essential layers, artifacts, and dependencies of enterprise architecture. In VallecilloA. (Ed.), Proceedings of the 10th IEEE International Enterprise Distributed Object Computing Conference Workshops (pp. 30–37). New York, NY: IEEE.
111.
YeowA.SohC.HansenR. (2018). Aligning with new digital strategy: A dynamic capabilities approach. Journal of Strategic Information Systems, 27(1), 43–58.
112.
YinR. K. (2003). Case study research: Design and methods (3rd ed.). Thousand Oaks, CA: SAGE.
113.
ZachmanJ. A. (1987). A framework for information systems architecture. IBM Systems Journal, 26, 276–292.
114.
ZachmanJ. A. (1996). Concepts of the framework for enterprise architecture: Background, description and utility. Monument, CO: Zachman International.
