Abstract
The relation of Enterprise Architecture to the traditional architectural roles of software engineering (platform architect, component architect as defined below) is similar to the relation between “city planning” and “building blueprints” in the building domain. There is a difference in scale, scope, necessary competences and methodologies. It is the intent of this article to stimulate this understanding summarized in the following two theses:
-
1.
Enterprise Architecture is a necessary and distinct architectural role. Successful large-scale system as well as virtual enterprise development requires appreciation and inclusion of this role in the IT-engineering process.
-
2.
Enterprise Architecture means cross-system coordination with similar stakeholders outside the own business ownership. This distinguishes Enterprise Architecture from traditional architectural roles and implies distinct tasks, methodologies, and required skills.
The updated original online version for this book can be found at DOI: 10.1007/978-0-387-35585-6_68
Chapter PDF
Similar content being viewed by others
References
Abowd, G. ei al.; Recommended Best Industrial Practice for Software Architecture Evaluation. Pittsburgh, Pa.: Software Engineering Institute, CMU, 1996.
Barbacci, M.; et al.; Steps in an Architecture Tradeoff Analysis Method: Quality Attribute Models and Analysis. Pittsburgh, Pa.: Software Engineering Institute, CMU, 1997.
Barroca L, Hall J., Hall P.; Software Architecture; Springer Verlag, 1999
Bredemeyer D., Malan R.; The Role of the Architect in Software Development; http://www.bredemeyer.com/role.pdf 1999.
Brown W.J., Malveau R.C., McCormick H.W.; Anti Pattems; 1998; Wiley.
Buschmann, F., et al.; Pattern-Oriented Software Architecture; Wiley, 1996.
Gamma, E., el. al.; Design Patterns, Elements of Reusable Object-Oriented Software, Addison-Wesley, 1995.
IHE - Integrating the Healthcare Enterprise; http://www.rsna.org/ihe 2001
R. Kaiman, G. et.al.; Scenario-Based Analysis of Software Architecture; IEEE Software November 1996, 47–55.
Kr chten, P. B.; The 4+1 View Model of Architecture; IEEE Software November 1995, p. 42–50.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2002 IFIP International Federation for Information Processing
About this paper
Cite this paper
Birkhölzer, T., Vaupel, J. (2002). Handling the Complexity of IT-Environments with Enterprise Architecture. In: Camarinha-Matos, L.M. (eds) Collaborative Business Ecosystems and Virtual Enterprises. PRO-VE 2002. IFIP — The International Federation for Information Processing, vol 85. Springer, Boston, MA. https://doi.org/10.1007/978-0-387-35585-6_4
Download citation
DOI: https://doi.org/10.1007/978-0-387-35585-6_4
Publisher Name: Springer, Boston, MA
Print ISBN: 978-1-4757-4789-8
Online ISBN: 978-0-387-35585-6
eBook Packages: Springer Book Archive