Enterprise Architecture Strategy.pdfl UPD
HALEY SCHANDELMIER
Information architecture is the practice of organizing knowledge. Like building architecture, it involves designing and constructing an effective structure. For companies creating an information architecture strategy allows users to better manage and find information.
In short, everyone! Keeping knowledge organized and accessible helps organizations accomplish more together. Without an information architecture strategy, knowledge can easily become disorganized, hard to use and outdated.
Description
Enterprise Solution Architecture - Strategy Guide takes you through all the essential concepts, strategies, workflows, documentation, and process maps that guide you in designing solutions that meet your existing enterprise architecture. Anyone who thinks about designing a strategy, defining and implementing a project, or transforming the project from poor execution to new techniques are the most opportunistic readers of this book.
It will streamline what needs to be prepared in terms of documentation. You will learn to develop documentation for different stages, various project phases, and how to use them effectively. This book will enable anyone looking to switch into the architecture forum by grabbing all the deep concepts and laying out strategies. They will be aided by all the visual implants in the book. Furthermore, this book highlights all the industry-specific processes which are required to be followed during any solution architecture-based project.
About the Authors
Nitesh Garg: The author has been working in the field of IT Technology for the last 19 years as a Sr. Enterprise Solution Architect. He has been in customer-facing roles right from the start and has worked across industry domains and clients. Technical Proficiency: His technical area of expertise has been Enterprise Solution Architecture/Pre-Sales/Solutions and Designs/Cloud Technologies/ Virtualization Technologies /Datacenter Technologies and DevOps Technologies. LinkedIn Profile:
Blogs: -nitesh-garg Atul Sharma: Atul is currently working as a Senior DevOps & Cloud Solution Architect. He has rich experience of over 17 years in the field of the IT industry. He has been handling customers across the globe right from the start of his career as an enterprise architect. Education/Certifications: He has completed B. Tech (Mechanical) and has been certified in many Cloud/DC/DevOps technologies such as:, Google Cloud Architect, Microsoft Azure Cloud Certified Architect, Amazon Cloud, Kubernetes Containerization Certification, Terraform Coding Certification, LinkedIn Profile:
The most important consideration is that your org-strategy is an Enterprise Architecture level decision and should not be made without a thourough understanding and analysis of your Enterprise Architecture model. In Enterprise Architecture as Strategy (Ross et al.) the authors described an enterprise architecture operating model using the following 22 matrix where the axis are A) Business Process Integration and B) Business Process Standardization.
Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."[1]
The United States Federal Government is an example of an organization that practices EA, in this case with its Capital Planning and Investment Control processes.[2] Companies such as Independence Blue Cross, Intel, Volkswagen AG,[3] and InterContinental Hotels Group also use EA to improve their business architectures as well as to improve business performance and productivity. Additionally, the Federal Enterprise Architecture's reference guide aids federal agencies in the development of their architectures.[4]
As a discipline, EA "proactively and holistically lead[s] enterprise responses to disruptive forces by identifying and analyzing the execution of change" towards organizational goals. EA gives business and IT leaders recommendations for policy adjustments and provides best strategies to support and enable business development and change within the information systems the business depends on. EA provides a guide for decision making towards these objectives.[5] The National Computing Centre's EA best practice guidance states that an EA typically "takes the form of a comprehensive set of cohesive models that describe the structure and functions of an enterprise. The individual models in an EA are arranged in a logical manner that provides an ever-increasing level of detail about the enterprise."[6]
Important players within EA include enterprise architects and solutions architects. Enterprise architects are at the top level of the architect hierarchy, meaning they have more responsibilities than solutions architects. While solutions architects focus on their own relevant solutions, enterprise architects focus on solutions for and the impact on the whole organization. Enterprise architects oversee many solution architects and business functions. As practitioners of EA, enterprise architects support an organization's strategic vision by acting to align people, process, and technology decisions with actionable goals and objectives that result in quantifiable improvements toward achieving that vision. The practice of EA "analyzes areas of common activity within or between organizations, where information and other resources are exchanged to guide future states from an integrated viewpoint of strategy, business, and technology."[7]
The term enterprise can be defined as an organizational unit, organization, or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.[8] In that sense, the term enterprise covers various types of organizations, regardless of their size, ownership model, operational model, or geographical distribution. It includes those organizations' complete sociotechnical system,[9] including people, information, processes, and technologies. Enterprise as a sociotechnical system defines the scope of EA.
The term architecture refers to fundamental concepts or properties of a system in its environment; and embodied in its elements, relationships, and in the principles of its design and evolution.[10] A methodology for developing and using architecture to guide the transformation of a business from a baseline state to a target state, sometimes through several transition states, is usually known as an enterprise architecture framework. A framework provides a structured collection of processes, techniques, artifact descriptions, reference models, and guidance for the production and use of an enterprise-specific architecture description.[citation needed]
Paramount to changing the EA is the identification of a sponsor. Their mission, vision, strategy, and the governance framework define all roles, responsibilities, and relationships involved in the anticipated transformation. Changes considered by enterprise architects typically include innovations in the structure or processes of an organization; innovations in the use of information systems or technologies; the integration and/or standardization of business processes; and improvement of the quality and timeliness of business information.[citation needed]
According to the standard ISO/IEC/IEEE 42010,[10] the product used to describe the architecture of a system is called an architectural description. In practice, an architectural description contains a variety of lists, tables, and diagrams. These are models known as views. In the case of EA, these models describe the logical business functions or capabilities, business processes, human roles and actors, the physical organization structure, data flows and data stores, business applications and platform applications, hardware, and communications infrastructure.[11]
The first use of the term "enterprise architecture" is often incorrectly attributed to John Zachman's 1987 A framework for information systems architecture.[12] The first publication to use it was instead a National Institute of Standards (NIST) Special Publication[13] on the challenges of information system integration.[citation needed] The NIST article describes EA as consisting of several levels. Business unit architecture is the top level and might be a total corporate entity or a sub-unit. It establishes for the whole organization necessary frameworks for "satisfying both internal information needs" as well as the needs of external entities, which include cooperating organizations, customers, and federal agencies. The lower levels of the EA that provide information to higher levels are more attentive to detail on behalf of their superiors. In addition to this structure, business unit architecture establishes standards, policies, and procedures that either enhance or stymie the organization's mission.[13]
The main difference between these two definitions is that Zachman's concept was the creation of individual information systems optimized for business, while NIST's described the management of all information systems within a business unit. The definitions in both publications, however, agreed that due to the "increasing size and complexity of the [i]mplementations of [i]nformation systems... logical construct[s] (or architecture) for defining and controlling the interfaces and... [i]ntegration of all the components of a system" is necessary. Zachman in particular urged for a "strategic planning methodology."[12]
dd2b598166