Abstract
As we have described in Chap. 1, achieving alignment between business and IT is one of the most important drivers for architecture. Architecture alignment is the problem of designing architectures at the infrastructure, application, and business levels such that each fits optimally with the other architectures. By studying project documentation obtained in case studies in several large Dutch organisations, we have tried to find alignment patterns that are actually used in practice. These results provide the context in which architectures are designed. Insight into this context helps the reader in better applying the techniques presented in this book.
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
References
Blanchard BS, Fabrycky WJ (1990), Systems Engineering and Analysis. Prentice Hall, Englewood Cliffs, New Jersey.
Buschmann F, Meunier R, Rohnert H, Sommerlad P, Stal M (1996), A System of Patterns: Pattern-Oriented Software Architecture. Wiley, New York.
Conway ME (1968), How do committees invent? Datamation, 14(4):28–31.
Dijkstra EW (1968), Structure of the ‘THE’-Multiprogramming System, Communications of the ACM, 11(5):341–346.
Eertink H, Janssen W, Oude Luttighuis P, Teeuw W, Vissers C (1999), A Business Process Design Language, Proc. 1st World Congress on Formal Methods, Toulouse, France.
Hall AD (1962), A Methodology for Systems Engineering. Van Nostrand, Princeton, New Jersey.
Hall AD (1969), Three-Dimensional Morphology of Systems Engineering. IEEE Transactions on System Science and Cybernetics, SSC-5(2):156–160.
Hardjono TW, Bakker RJM (2001), Management van processen: Identificeren, besturen, beheersen en vernieuwen. Kluwer, Dordrecht (in Dutch).
Harel D, Pnueli A (1985), On the development of reactive systems. In Apt K, (Ed.), Logics and Models of Concurrent Systems, pp. 477–498. NATO ASI Series. Springer, Berlin.
Henderson JC, Venkatraman N (1993), Strategic alignment: leveraging information technology for transforming operations, IBM Systems Journal, 32(1):4–16.
Kruchten P (1995), Architectural Blueprints – The ‘4+1’ View Model of Software Architecture, IEEE Software, 12(6):42–50.
Martin, J (1982), Strategic Data-Planning Methodologies. Prentice Hall, Englewood Cliffs, New Jersey.
Martin, J (1989), Information Engineering (3 vols.). Prentice Hall, Englewood Cliffs, New Jersey.
Olle TW, Hagelstein J, Macdonald IG, Rolland C, Sol HG, van Assche FJM Verrijn-Stuart AA (1988), Information Systems Methodologies: A Framework for Understanding. Addison-Wesley, Reading, Massachusetts.
Pahl G, Beitz W (1986), Konstruktionslehre. Handbuch für Studium und Praxis. Springer, Berlin.
Roozenburg NFM, Eekels J (1995), Product Design: Fundamentals and Methods. Wiley, New York.
Smith JM, Smith DCP (1977), Database Abstractions: Aggregation and Generalization, ACM Transactions on Database Systems, 2:105–133.
Sowa JF, Zachman JA (1992), Extending and Formalizing the Framework for Information Systems Architecture, IBM Systems Journal, 31(3):590–616.
Treacy M, Wiersema, F (1997), The discipline of market leaders. Perseus Publishing, Reading, Massachusetts.
Van der Sanden WAM, Sturm BJAM (1997), Informatiearchitectuur, de infrastructurele benadering. Panfox, Rosmalen (in Dutch).
Van Eck PAT, Blanken H, Wieringa RJ (2004), Project GRAAL: Towards operational architecture guidelines. International Journal of Cooperative Information Systems, 13(3):235–255.
Van Velzen RCG, Van Oosten JNA, Snijders T, Hardjono TW (2002), Procesmanagement en de SqEME-benadering. Kluwer, Dordrecht.
Weill P, Vitale M (2002), What IT Infrastructure Capabilities Are Needed to Implement E-Business Models? MIS Quarterly Executive, 1(1):17–34.
Wieringa RJ (1996), Requirements Engineering: Frameworks for Understanding. Wiley, New York.
Wieringa RJ (1998a), Postmodern Software Design with NYAM: Not Yet Another Method. In Broy M, Rumpe B (eds.), Requirements Targeting Software and Systems Engineering, LNCS 1526, pp. 69–94. Springer, Berlin.
Wieringa RJ (1998b), A Survey of Structured and Object-Oriented Software Specification Methods and Techniques, ACM Computing Surveys, 30(4):459–527.
Wieringa RJ (2003), Design Methods for Reactive Systems: Yourdon, Statemate and the UML. Morgan Kaufmann, San Francisco.
Wieringa RJ, Blanken HM, Fokkinga MM, Grefen PWPJ (2003), Aligning application architecture to the business context. Proc. Conference on Advanced Information System Engineering (CaiSE’03), LNCS 2681, pp. 209–225. Springer, Berlin.
Zachman JA (1987), A Framework for Information Systems Architecture, IBM Systems Journal, 26(3):276–292.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2013 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Lankhorst, M. (2013). Architecture Alignment. In: Enterprise Architecture at Work. The Enterprise Engineering Series. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-29651-2_9
Download citation
DOI: https://doi.org/10.1007/978-3-642-29651-2_9
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-29650-5
Online ISBN: 978-3-642-29651-2
eBook Packages: Business and EconomicsBusiness and Management (R0)