Abstract
An enterprise architecture pattern (EAP) is based on the concepts and ideas of Architecture Enterprise frameworks such as TOGAF, NAF, or Zachman. We first give a short description of Enterprise Architecture, followed by the main concepts conveyed by the frameworks, such as views and viewpoints, architectural domains, architecture bricks, etc. This is followed by a list of stakeholders who might use the patterns in this book. We then explain in detail what an EAP is, define the graphical notations of the different views, and describe the structure of an EAP.
«My theory is to enjoy life, but the practice is against it.»
Charles Lamb
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
The same can be said, for example, of the IT infrastructure library (ITIL): Versions 1 and 2 were more oriented toward technology, whereas version 3 now encompasses strategies and business viewpoints.
- 2.
Interesting enough to be mentioned is that the concepts of architectural views and viewpoints in the standard are depicted itself as a class diagram conforming to the UML notation. This narrows the amount of potential readers dramatically…
- 3.
This role is sometimes also called Business Engineer.
- 4.
We choose deliberately not to use the same naming as in TOGAF, as we wanted to be independent of any architecture framework.
References
ArchiMate (2011) The Open Group: ArchiMate® version 2.0. https://www2.opengroup.org/ogsys/catalog/C118. Accessed 21 June 2013
Alexander C, Ishikawa S, Silverstein M (1977) Pattern language: towns, buildings constructions. Oxford University Press, New York
BPMN (2011) Business process model and notation version 2.0 (BPMN 2.0). http://www.bpmn.org/. Accessed 28 July 2011
Buschmann F, Meunier R, Rohnert H, Sommerlad P, Stal M (2000) Pattern-oriented software architecture. Wiley, New York
CGEIT (2012) Certified in the Governance of Enterprise IT (CGEIT). http://www.isaca.org/Certification/CGEIT-Certified-in-the-Governance-of-Enterprise-IT/Prepare-for-the-Exam/Job-Practice-Areas/Pages/default.aspx. Accessed 5 Dec 2012
Dern G (2006) Management von IT-Architekturen. Vieweg
DoDAF (2011) The DoDAF architecture framework version 2.02. http://dodcio.defense.gov/Portals/0/Documents/DODAF/DoDAF_v2-02_web.pdf. Accessed 28 July 2011
FEAF (1999) Federal Enterprise Architecture (FEA). http://www.whitehouse.gov/omb/e-gov/fea/. Accessed 28 July 2011
Gamma E, Helm R, Johnson R, Vlissides J (1995) Design patterns. Elements of reusable object-oriented software. Addison-Wesley, USA
Harrison R (2007) TOGAF 8.1.1 study guide. Van Haren Publishing, Zaltbommel
ISO/IEC 42010 (2007) JTC 1/SC 7: ISO/IEC 42010:2007 systems and software engineering: recommended practice for architectural description of software-intensive systems. International Organization for Standardization, Geneva
Keller W (2007) IT-Unternehmensarchitektur, dpunkt
Lankhorst M (2005) Enterprise architecture at work modelling, communication, and analysis. Springer, New York
NAF (2011) NATO architecture framework. http://www.nhqc3s.nato.int/HomePage.asp?session=295712985. Accessed 28 July 2011
NIH: National Institute of Health Enterprise Architecture (2008) What is enterprise architecture? https://enterprisearchitecture.nih.gov/Pages/what.aspx. Accessed 21 June 2013
Perks C, Beveridge T (2003) Guide to enterprise IT architecture. Springer, Berlin
Pettey C, Stevens H (2009) Gartner identifies ten enterprise architecture pitfalls. http://www.gartner.com/it/page.jsp?id=1159617. Accessed 28 July 2011
TOGAF (2009) The Open Group architecture framework. http://pubs.opengroup.org/architecture/togaf9-doc/arch/. Accessed 28 July 2011
UML (2010) The Object Management Group: unified modelling language version 2.3. http://www.omg.org/spec/UML/2.3/Infrastructure/PDF/. Accessed 28 July 2011
Wikipedia EA (2011) Enterprise architecture. http://en.wikipedia.org/wiki/Enterprise_architecture. Accessed 28 July 2011
Zachman J (1987) A framework for information systems architecture. IBM Syst J. http://old.zachmaninternational.com/images/stories/ibmsj2603e.pdf
Author information
Authors and Affiliations
Corresponding authors
Rights and permissions
Copyright information
© 2013 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Perroud, T., Inversini, R. (2013). Theory. In: Enterprise Architecture Patterns. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-37561-3_2
Download citation
DOI: https://doi.org/10.1007/978-3-642-37561-3_2
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-37560-6
Online ISBN: 978-3-642-37561-3
eBook Packages: Computer ScienceComputer Science (R0)