Getting Started With Enterprise Architecture

This novel textbook introduces Enterprise Internet of Things from technology, management and business perspectives, carefully examining enterprise environments through the lens of modernization with the Internet of Things (IoT). It also includes detailed case studies to offer meaningful insights for readers from various disciplines and areas. The book analyzes the ways in which the technology could contribute to the enterprise world in terms of revenue and new business models, and addresses the strategies and principles involved in developing IoT solutions with software engineering practices such as DevOps and Micro services architecture principles. By doing so, it offers readers a clear overview of the power of Internet of Things in building next generation enterprise use cases. The book enables readers to understand the latest opportunities to create new business models in enterprises using the unprecedented level of device connectivity, and the wealth of data generated and information exchange among these devices. As such, it appeals to various user groups, such as engineers trying to solve problems in their own domains using Enterprise IoT, academics interested in gaining a better understanding of applications of IoT in large-scale enterprises, and researchers wanting to contribute to the ever-growing and complex area of IoT.

Implement a basic enterprise architecture from start to finish using a four stage wheel-based approach. Aided by real-world examples, this book shows what elements are needed for the initial implementation of a fundamental enterprise architecture The book's pragmatic approach keeps existing architecture frameworks and methodologies in mind while providing instructions that are readable and applicable to all. The Enterprise Architecture Implementation Wheel builds on the methodology of existing architecture frameworks and allows you to apply the theory more pragmatically and closer to the reality that an architect encounters in daily practice. While the main focus of the book is the actual steps taken to design an enterprise architecture, other important topics include architecture origin, definition, domains, visualization, and roles. Getting Started with Enterprise Architecture is the ideal handbook for the architect who is asked to implement an Enterprise Architecture in an existing organization. What You'll Learn Implement measurable goals and objectives for a baseline architecture Create meaningful catalogues, diagrams, and maps to communicate the architecture to an organization Measure the progress of implementing the architecture Identify a company’s needs and develop an appropriate strategy to satisfy those needs Who This Book Is For Enterprise architects, project managers and executives.

Learn how to institute and implement enterprise architecture in your organization. You can make a quick start and establish a baseline for your enterprise architecture within ten weeks, then grow and stabilize the architecture over time using the proven Ready, Set, Go Approach. Reading this book will: 1. Give you directions on how to institute and implement enterprise architecture in your organization. You will be able to build close relationships with stakeholders and delivery teams, but you will not need to micromanage the architecture’s operations. 2. Increase your awareness that enterprise architecture is about business, not information technology. 3. Enable you to initiate and facilitate dramatic business development. The architecture of an enterprise must be tolerant of currently unknown business initiatives. 4. Show you how to get a holistic view of the process of implementing enterprise architecture. 5. Make you aware that information is a key business asset and that information architecture is a key part of the enterprise architecture. 6. Allow you to learn from our experiences. This book is based on our 30 years of work in the enterprise architecture field, colleagues in Europe, customer cases, and students. We do not pretend to cover all you need to know about enterprise architecture within these pages. Rather, we give you the information that is most important for effective and successful guidance. Sometimes, less is more. If your company is about to make a major change and you are looking for a way to reduce the changes into manageable pieces—and still retain control of how they fit together—this is your handbook. Maybe you are already acting as an enterprise architect and using a formal method, but you need practical hints. Or maybe you are about to set up an enterprise architect network or group of specialists and need input on how to organize your work. The Ready-Set-Go method for introducing enterprise architecture provides you, the enterprise architect, with an immediate understanding of the basic steps for starting, organizing, and operating the entirety of your organization’s architecture. Chapter 1: Ready shows how to model and analyze your business operations, assess their current status, construct a future scenario, compare it to the current structure, analyze what you see, and show the result in a city plan. Chapter 2: Set deals with preparing for the implementation of the architecture with governance, enterprise architecture organization, staffing, etc. This is the organizing step before beginning the actual work. Chapter 3: Go establishes how to implement a city plan in practice. It deals with the practicalities of working as an enterprise architect and is called the “running” step. The common thread through all aspects of the enterprise architect’s work is the architect’s mastery of a number of tools, such as business models, process models, information models, and matrices. We address how to initiate the architecture process within the organization in such a way that the overarching enterprise architecture and architecture-driven approach can be applied methodically and gradually improved.

Presents current developments, issues, and trends in enterprise architecture (EA). Provides insights into the impact of effective EA on IT governance, IT portfolio management, and IT outsourcing.

Enterprise architecture is leading IT's way to the executive boardroom, as CIOs are now taking their place at the management table. Organizations investing their time, money, and talent in enterprise architecture (EA) have realized significant process improvement and competitive advantage. However, as these organizations discovered, it is one thing

To provide structure and transparency to the complex world of IT, Enterprise Architecture was created. However, we created complexities within Enterprise Architecture with Frameworks that are not easily understandable and purposefully implementable. In this book, Nagesh and Gerry help to turnaround Enterprise Architecture organizations. They introduce a simple IDEA Framework that is based on common practices and investments within IT organizations. The Ten deliverables presented in this book bring structure and clarity to IT organizations that are 10-people IT shops and 1000+ IT staff enterprises alike. This book is not an ivory tower work, it is actionable, applied Enterprise Architecture. It is also a healthy dose of EA tough love. If you want to know why EA fails, read the second chapter. It is introspective, it does not blame external forces: the not-my-fault syndrome. It also does not blame, in fact it hardly mentions, technology. To be fair, the Nagesh and Gerry do recognize external influences; however they are viewed as risks that must be managed. Most corporations focus on this years budget, investments, and rewards. The same focus rolls downhill to the Information Technology department. If the IT department has not successfully communicated the budget and managed to spend it within the limits (10% variance), everything else may seem irrelevant. Eventually, Nagesh and Gerry started looking through current IT systems and IT assets to understand: (a) where the current funds were being invested, (b) how these investments jelled or were mandated because of the previous investments that had been made by IT, and (c) how the companys business priorities aligned with future technology needs, including the need to meet compliance requirements. Considering and discovering the answers to these three questions led Nagesh and Gerry to develop a definition of Enterprise Architecture that was based on technology investments Investment Driven Enterprise Architecture (IDEA) Framework. The purpose of the IDEA Framework is to provide guidance on how the corporations future technology will be drafted and communicated. Its method is to utilize actual systems, hardware, people, and business functions in order to establish boundaries within which the IDEA Framework will work. The structure of the IDEA Framework differs from that of many others because it consists of key deliverables that fit into day-to-day activities and it accommodates an enterprise-wide strategic plan. It also provides for the much-needed interaction between these key deliverables and facilitates contributions from key stakeholders across Business Units and the various IT departments. In essence, the IDEA Framework takes the key deliverables, stakeholders, and organizations and demonstrates how they dynamically function together.