- Series: The Enterprise Engineering Series (Book 4)
- Hardcover: 197 pages
- Publisher: Springer; 2011 edition (June 7, 2011)
- Language: English
- ISBN-10: 3642202780
- ISBN-13: 978-3642202780
- Product Dimensions: 6.5 x 0.8 x 9.3 inches
- Shipping Weight: 1 pounds (View shipping rates and policies)
- Average Customer Review: 4 customer reviews
- Amazon Best Sellers Rank: #1,988,768 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Architecture Principles: The Cornerstones of Enterprise Architecture (The Enterprise Engineering Series) 2011th Edition
Use the Amazon App to scan ISBNs and compare prices.
"Enlightenment Now: The Case for Reason, Science, Humanism, and Progress"
Is the world really falling apart? Is the ideal of progress obsolete? Cognitive scientist and public intellectual Steven Pinker urges us to step back from the gory headlines and prophecies of doom, and instead, follow the data: In seventy-five jaw-dropping graphs, Pinker shows that life, health, prosperity, safety, peace, knowledge, and happiness are on the rise. Learn more
Frequently bought together
Customers who viewed this item also viewed
Customers who bought this item also bought
From the Back Cover
Enterprises, from small to large, evolve continuously. As a result, their structures are transformed and extended continuously. Without some means of control, such changes are bound to lead to an overly complex, uncoordinated and heterogeneous environment that is hard to manage and hard to adapt to future changes. Enterprise architecture principles provide a means to direct transformations of enterprises. As a consequence, architecture principles should be seen as the cornerstones of any architecture.
In this book, Greefhorst and Proper focus on the role of architecture principles. They provide both a theoretical and a practical perspective on architecture principles. The theoretical perspective involves a brief survey of the general concept of principle as well as an analysis of different flavors of principles. Architecture principles are regarded as a specific class of normative principles that direct the design of an enterprise, from the definition of its business to its supporting IT. The practical perspective on architecture principles is concerned with an approach to the formulation of architecture principles, as well as their actual use in organizations. To illustrate their use in practice, several real-life cases are discussed, an application of architecture principles in TOGAF is included, and a catalogue of example architecture principles is provided.
With this broad coverage, the authors target students and researchers specializing in enterprise architecture or business information systems, as well as practitioners who want to understand the foundations underlying their practical daily work.
About the Author
Danny Greefhorst is a principal consultant and owner of ArchiXL, and works for clients in the financial and public sector. Danny acts as an IT architect and IT consultant, and is TOGAF 9 certified. He has extensive experience with the definition and implementation of enterprise architectures, application architectures and technical architectures. In addition, he coaches organizations in setting up and executing their architecture function, and is active as an instructor for several classes on architecture. Before starting ArchiXL he worked as a principal consultant at Yellowtail, as a senior IT architect at IBM Business Consulting Services and as a researcher at the Software Engineering Research Centre. Danny is active in the architecture community and regularly publishes on IT and architecture related topics. He is the chairman of the governing board of Via Nova Architectura, a portal and electronic magazine on enterprise architecture. He is also a member of the governing board of the architecture department of the Dutch Computer Science Association (Ngi).
Erik (H.A.) Proper is a senior research manager at the Public Research Centre -- Henri Tudor in Luxembourg, where he leads Services-oriented Enterprise Engineering programme. He also holds a chair in Information Systems at the Radboud University Nijmegen in the Netherlands. Erik has a mixed industrial and academic background. In the past, Erik worked for companies such as Asymetrix, InfoModeller, Origin, ID Research, Ordina and Capgemini, while interleaving this with his work at research institutions such as the Radboud University of Nijmegen, Queensland University of Technology, the Distributed Systems Technology Centre, and the University of Queensland. His general research drive is the modeling of systems. He applies this drive mainly in the fields of service science, enterprise modeling, enterprise engineering and enterprise architecting. He was co-initiator of the ArchiMate project, and currently also serves on the board of the ArchiMate forum of The Open Group. Erik is also one of the editors in chief of Springer's series on enterprise engineering.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
Anyone familiar with Software Architecture understands that quality attributes need to be identified, balanced against one another, and then met through tactics. Principles are a key to unlock the door that has quality attributes hidden away in some dark corner of your enterprise.
As an attribute of principles, your teams will have a better understand of the quality attribute they should be targeting when they are pursuing an architectural principle.
Architecture Principles are described in this book as the cornerstones in Enterprise Architecture and it definitely shows you why this is true.
The lack of Architecture Principles contribute to me hearing things like this-
-- We have an SDLC but we usually do not have time to follow it, so we are more agile. In other words, operating in chaos mode.
-- We have coding standards but they are out of date, so we usually just depend on our individual experience to guide us. In other words, we are still using the big ball of mud anti-pattern to design and code our applications.
-- We built the application now we need to figure out how to test it. In other words, we have no way of know if we met our capacity plan's performance requirements (usually this won't exist either), we can't regression test, and we are paying people to repeatedly do their best to bang away at the application and hope they find the bugs.
-- We have built logging in some places but now we have to figure out how to purge and archive the logs, and get logging into the rest of the application. In other words, we find architecture and design to be unnecessary overhead so we are used to missing things like this.
-- and so on and so on and so on...
This book starts out with a couple chapters that introduce and define enterprise architecture. It then continues with chapters that include A Conceptual Framework for Principles, Architecture Principle Specifications, A Practical Approach, Case Studies, Architecture Principles in Context, and Summary, Conclusions and Future Work.
The book ends with two appendices. One is a Principles Catalogue and the other is Architecture Principles in TOGAF. The Principles Catalogue is a really nice catalogue of 59 basic principles that can be used as a great starting point for getting started with defining your principles.
One of the things I like most about this book is that it defines the essential meaning of enterprise architecture as a normative restriction of design freedom towards projects and programs (or in a positive light- it reduces design stress). In 2005 I started using what I called Restrictive Development (no urls allowed on Amazon, just Google Restrictive Development) as a way to propagated my architectural constraints throughout the analysis, design, and the construction phases of my projects. It was nice to see I was not off base with my line of thought.
One of the things I didn't like about the book is that there is no index. There is a very small (1 page) Glossary and a thorough References section, but no index.
Although this book does not say it, I believe the most important thing this book does is to bring to light that architecture principles should be explicitly defined and implemented. Just like an architecture. It exists whether or not you execute a software architecture business cycle and define it or not. You just don't know what it is and have no way of controlling and improving it. Your enterprise has principles that are guiding your enterprise, but if you do not have them explicitly defined and enforced, you are just flying blind and those invisible principles are doing the driving.
This book is a must read for anyone involved with Enterprise Architecture in any way. Architecture Principles are a very very important topic and they deserves your attention.
This book is a keeper and I have referenced on several occasions at work.