A Modern Enterprise Architecture Approach


Book Description

The revised version of this book to provide essential guidance, compelling ideas, and unique ways to Enterprise Architects so that they can successfully perform complex enterprise modernisation initiatives transforming from chaos to coherence. This is not an ordinary theory book describing Enterprise Architecture in detail. There are myriad of books on the market and in libraries discussing details of enterprise architecture. My aim here is to highlight success factors and reflect lessons learnt from the field within enterprise modernisation and transformation context. As a practising Senior Enterprise Architect, myself, I read hundreds of those books and articles to learn different views. They have been valuable to me to establish my foundations in the earlier phase of my profession. However, what is missing now is a concise guidance book showing Enterprise Architects the novel approaches, insights from the real-life experience and experimentations, and pointing out the differentiating technologies for enterprise modernisation. If only there were such a guide when I started engaging in modernisation and transformation programs. The biggest lesson learned is the business outcome of the enterprise modernisation. What genuinely matters for business is the return on investment of the enterprise architecture and its monetising capabilities. The rest is the theory because nowadays sponsoring executives, due to economic climate, have no interest, attention, or tolerance for non-profitable ventures. I am sorry for disappointing some idealistic Enterprise Architects, but with due respect, it is the reality, and we cannot change it. This book deals with reality rather than theoretical perfection. Anyone against this view on this climate must be coming from another planet. In this concise, uncluttered and easy-to-read book, I attempt to show the significant pain points and valuable considerations for enterprise modernisation using a structured approach and a simple narration especially considering my audience from non-English speaking backgrounds. The architectural rigour is still essential. We cannot compromise the rigour aiming to the quality of products and services as a target outcome. However, there must be a delicate balance among architectural rigour, business value, and speed to the market. I applied this pragmatic approach to multiple substantial transformation initiatives and complex modernisations programs. The key point is using an incrementally progressing iterative approach to every aspect of modernisation initiatives, including people, processes, tools, and technologies as a whole. Starting with a high-level view of enterprise architecture to set the context, I provided a dozen of distinct chapters to point out and elaborate on the factors which can make a real difference in dealing with complexity and producing excellent modernisation initiatives. As eminent leaders, Enterprise Architects are the critical talents who can undertake this massive mission using their people and technology skills, in addition to many critical attributes such as calm and composed approach. Let's keep in mind that as Enterprise Architects, we are architects, not firefighters! I have full confidence that this book can provide valuable insights and some 'aha' moments for talented architects like yourself to tackle this enormous mission of turning chaos to coherence.




The Practice of Enterprise Architecture


Book Description

Based on an extensive study of the actual industry best practices, this book provides a systematic conceptual description of an EA practice and offers practically actionable answers to the key questions related to enterprise architecture.




Enterprise Architecture as Strategy


Book Description

Enterprise architecture defines a firm's needs for standardized tasks, job roles, systems, infrastructure, and data in core business processes. This book explains enterprise architecture's vital role in enabling - or constraining - the execution of business strategy. It provides frameworks, case examples, and more.




Complex Enterprise Architecture


Book Description

Implement successful and cost-effective enterprise architecture projects. This book provides a new approach to developing enterprise architecture based on the idea of emergent behaviors—where instead of micromanaging system implementation, the enterprise architecture effort establishes clear goals and leaves the details to the implementation teams. System development efforts are measured based on their contribution to achieving business goals instead of implementing specific (possibly outdated) requirements. Most enterprise architecture initiatives employ one of the existing system architecture frameworks such as Zachman or The Open Group Architecture Framework, but these are not well-suited for enterprise architecture in a modern, agile organization. The new approach presented in this book is based on the author’s experience with large enterprise architecture efforts. The approach leverages research into complex adaptive systems and emergent behaviors, where a few simple rules result in complex and efficient enterprise behaviors. Simplifying the task of establishing and maintaining the enterprise architecture cuts the costs of building and maintaining the architecture and frees up those resources for more productive pursuits. System implementers are given the freedom to rapidly adapt to changing user needs without the blessing of the enterprise modeling priesthood, and the architecture is transformed from a static pile of obscure models and documents into an operational framework that can be actively used to manage an enterprise’s resources to better achieve business goals. The enterprise architect is free to stop focusing on building and maintaining models and start focusing on achieving business goals. What You’ll Learn Refocus enterprise architecture on business needs by eliminating most of the enterprise-level models Delegate tasks to the development teams who do system implementation Document business goals, establish strategies for achieving those goals, and measure progress toward those goals Measure the results and gauge whether the enterprise architecture is achieving its goals Utilize appropriate modeling techniques that can be effectively used in an enterprise architecture Who This Book Is For Architecture practitioners and architecture managers: Practitioners are experienced architects who have used existing frameworks such as Zachman, and have experience with formal architecture modeling and/or model-based system engineering; managers are responsible for managing an enterprise architecture project and either have experience with enterprise architecture projects that were ineffective or are looking for a different approach that will be more cost-effective and allow for more organizational agility. Government program managers looking for a different approach to make enterprise architecture more relevant and easier to implement will also find this book of value.




Data Management at Scale


Book Description

As data management and integration continue to evolve rapidly, storing all your data in one place, such as a data warehouse, is no longer scalable. In the very near future, data will need to be distributed and available for several technological solutions. With this practical book, you’ll learnhow to migrate your enterprise from a complex and tightly coupled data landscape to a more flexible architecture ready for the modern world of data consumption. Executives, data architects, analytics teams, and compliance and governance staff will learn how to build a modern scalable data landscape using the Scaled Architecture, which you can introduce incrementally without a large upfront investment. Author Piethein Strengholt provides blueprints, principles, observations, best practices, and patterns to get you up to speed. Examine data management trends, including technological developments, regulatory requirements, and privacy concerns Go deep into the Scaled Architecture and learn how the pieces fit together Explore data governance and data security, master data management, self-service data marketplaces, and the importance of metadata




Principle Based Enterprise Architecture


Book Description

The Principle Based Enterprise Architecture (PBEA) Method is a proven approach for implementing an enterprise-wide architecture practice in large- and medium-sized technology organizations. The method begins with a set of architecture objectives linked to concepts that matter to the business. It then lays out how to build technology platforms from components we call assets and how to manage those assets over time, through the calculation and management of technical debt. The PBEA method is a pragmatic approach to enterprise technology architecture which is based on the fundamental tenet that technology is never perfect, compromises must be made, and one of the most valuable functions an enterprise architecture group can provide for a company is a method for managing those compromises. We call the cost of these compromises "technical debt". It is essentially the difference between what we should have spent on technology and what we did spend. The PBEA method grew from the experience of watching how large technology organizations function (or do not function as the case may be). You will learn about such essential topics as: Best practices for building, managing, and ultimately evolving an enterprise architecture. Defining principles and golden rules to guide the high-quality creation of the building blocks of products and platforms (assets). Calculating technical debt and assessing the business risk associated with carrying that debt. Identifying and managing the actions required to pay off technical debt and mitigate any associated business risk. If you have witnessed products and platforms 'collapsing under the burden of technical debt', then this book is for you. If you have seen technology organizations fail to learn from their mistakes, then this book is also for you. If you have been involved in the development of products where Version 2 required almost a rewrite of Version 1 or worked in technology organizations that spend an excessive portion of their budget on maintenance, then the PBEA method may provide both insight and benefit. Or if you are an enterprise architect and have witnessed one or more Enterprise Architecture functions get eliminated because they were seen as 'too ivory tower' and too distant from the customer, then this book will provide you with a concrete, fact-based approach for building an enterprise architecture function that is fully aligned with business objectives and that delivers real measurable benefit to the corporation.




Business Architecture


Book Description

Organizations today exist in an environment of unprecedented change. They do so against a backdrop of a global, competitive marketplace, the fast-paced enablement of technology, amplified regulation and accelerating organizational complexity. Many organizations are addressing change in a sub-optimal way and they are operating without a clear view of where their operational risks lie. It is these dynamics that are leading organizations to recognise and embrace Business Architecture. Despite this environment, Business Architecture can be a difficult ’sell’ - it is often perceived to be abstract and lacking in tangible delivery. To succeed, Business Architecture must be pragmatic and, to be sustainable, it must focus on achieving long-term value and, at the same time, recognise the shorter-term tactical needs of the organisation. With these challenges in mind, this book provides a practical guide on how to employ Business Architecture and how to build a balanced proposition that delivers value to a broad range of stakeholders. As the book states, Business Architecture should not be practised in isolation, nor should it be thought of as a one-off process; it needs to be woven into the fabric of the organization. And so the authors illustrate the opportunities for weaving the Business Architecture Practice into this fabric through the various stakeholders and life cycles that exist, both formally and informally, within an organization. Whilst recognizing best practice, this book explores a new, inspirational level of Business Architecture whilst acknowledging that the best way to realize the vision is one step at a time.




Patterns of Enterprise Application Architecture


Book Description

The practice of enterprise application development has benefited from the emergence of many new enabling technologies. Multi-tiered object-oriented platforms, such as Java and .NET, have become commonplace. These new tools and technologies are capable of building powerful applications, but they are not easily implemented. Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned. Patterns of Enterprise Application Architecture is written in direct response to the stiff challenges that face enterprise application developers. The author, noted object-oriented designer Martin Fowler, noticed that despite changes in technology--from Smalltalk to CORBA to Java to .NET--the same basic design ideas can be adapted and applied to solve common problems. With the help of an expert group of contributors, Martin distills over forty recurring solutions into patterns. The result is an indispensable handbook of solutions that are applicable to any enterprise application platform. This book is actually two books in one. The first section is a short tutorial on developing enterprise applications, which you can read from start to finish to understand the scope of the book's lessons. The next section, the bulk of the book, is a detailed reference to the patterns themselves. Each pattern provides usage and implementation information, as well as detailed code examples in Java or C#. The entire book is also richly illustrated with UML diagrams to further explain the concepts. Armed with this book, you will have the knowledge necessary to make important architectural decisions about building an enterprise application and the proven patterns for use when building them. The topics covered include · Dividing an enterprise application into layers · The major approaches to organizing business logic · An in-depth treatment of mapping between objects and relational databases · Using Model-View-Controller to organize a Web presentation · Handling concurrency for data that spans multiple transactions · Designing distributed object interfaces




An Introduction to Enterprise Architecture


Book Description

An Introduction to Enterprise Architecture is the culmination of several decades of experience that I have gained through work initially as an information technology manager and then as a consultant to executives in the public and private sectors. I wrote this book for three major reasons: (1) to help move business and technology planning from a systems and process-level view to a more strategy-driven enterprise-level view, (2) to promote and explain the emerging profession of EA, and (3) to provide the first textbook on the subject of EA, which is suitable for graduate and undergraduate levels of study. To date, other books on EA have been practitioner books not specifically oriented toward a student who may be learning the subject with little to no previous exposure. Therefore, this book contains references to related academic research and industry best practices, as well as my own observations about potential future practices and the direction of this emerging profession.




Reaching the Pinnacle


Book Description

"Reaching the Pinnacle: A Methodology of Business Understanding, Technology Planning, and Change (Implementing and Managing Enterprise Architecture)" by Samuel B. Holcman explains the detailed process of building an enterprise architecture. Samuel B. Holcman brings his strategic business plans to business and technology professionals with "Reaching the Pinnacle: A Methodology of Business Understanding, Technology Planning, and Change (Implementing and Managing Enterprise Architecture)." In order to bring a method to the madness that can often be today's business structure, Holcman uses "Reaching the Pinnacle" to introduce the process of building an enterprise architecture. Holcman uses his 40 years of experience as a leading trainer and consultant in enterprise architecture in writing "Reaching the Pinnacle." He explains enterprise architecture as the rethinking of how business planning and information technology work together in order to achieve strategic goals. "Reaching the Pinnacle" explains how an organization and its important departments can achieve their goals through a series of project initiatives. Holcman offers a simple, easy-to-understand way to implement an enterprise architecture project into one's organization. "While the approach is not quick - it may take up to a few years to transform an organization - my methodology provides an effective means for moving the organization from its as-is state to its desired state in an iterative manner," says Holcman. Holcman's methods and approach have been used by numerous Fortune 500 companies and have led him to be the top consultant on the topic. He believes the 'for practitioners, by practitioners' approach of "Reaching the Pinnacle" will make the book a crucial resource among business and technology personnel everywhere. "Reaching the Pinnacle: A Methodology of Business Understanding, Technology Planning, and Change (Implementing and Managing Enterprise Architecture)" is available for sale online at Amazon.com, directly from the author at www.PinnacleBusGrp.com, and other channels. REVIEW COPIES AND INTERVIEWS AVAILABLE