Book Image

Realize Enterprise Architecture with AWS and SAFe

By : Rajnish Harjika
Book Image

Realize Enterprise Architecture with AWS and SAFe

By: Rajnish Harjika

Overview of this book

Agile implementation of enterprise architecture (EA) in the cloud is a powerful organizational tool, but it is challenging, particularly for architects who are used to on-premises environments. This in-depth guide will tell you all you need to know to reap the benefits of applying EA in your organization to achieve operational efficiency. Starting with an overview of the foundations of enterprise architecture, you'll see how it can be applied to AWS as well as explore the frameworks AWS provides for EA, such as the AWS Well-Architected Framework. That's not all – the book shows you how these frameworks align with The Open Group Architecture Framework (TOGAF) architecture development method (ADM) and the Zachman Framework so that you can choose the right fit for your organization. As you advance, you'll learn how to apply SAFe to make your organization agile as well as efficient. Once you've gotten to grips with the theory, you can explore use cases and take a quiz at the end of the book to test yourself and see how EA is applied in practice. By the end of this enterprise architecture book, you'll have the skills and knowledge required to apply EA in the cloud with AWS and drive your organization to become super-efficient and agile.
Table of Contents (17 chapters)
1
Part 1 – Enterprise Architecture Foundation and Implementation
5
Part 2 – Enterprise Architecture Frameworks
9
Part 3 – SAFe in EA and the Cloud
12
Part 4 – Setting Up an EA

Setting up the Architecture Board

The CIO (or another senior executive) is often the executive sponsor of the initial architecture effort in most companies. Sponsoring bodies have more influence, however, when it comes to garnering corporate support. An Architecture Board is the sponsoring body here, but the title isn’t important. The strategic architecture and all of its sub-architectures are reviewed and maintained by this executive-level group.

Triggers

Typically, an Architecture Board is established in response to one or more of the following:

  • The new CIO
  • Acquisitions or mergers
  • Considering switching to a more advanced form of computing
  • Recognizing the lack of alignment of IT with the business
  • Technology as a means of achieving a competitive advantage
  • Implementation of the EA program
  • Rapid growth or significant business changes
  • Cross-functional requirements for complex solutions

Within the enterprise, the Architecture Board...