Chapter

Enterprise Architecture Implementation Collection – Page 5

e-Book: A Practical Guide to Enterprise Architecture Practice

This practical guide to enterprise architecture focuses on the practice of the discipline as opposed to its frameworks, processes and governance. What does an enterprise architect do every day? How does that add value to the business? How to build skills and competency in the enterprise architecture discipline? It is good to understand the theory of enterprise architecture – frameworks, processes, organization, tools, governance – but this e-Book helps you put that theory into practice by detailing the day to day activities of an enterprise architect. (250 pages)

Case Study: Enterprise Architecture For Business Transformation

This case study highlights the use of enterprise architecture in facilitating business transformation. The author describes the challenges his organization faced and how they devised a strategy to overcome them with enterprise architecture playing a critical role. 

Enterprise Architecture in Practice

What does an enterprise architect do for a living? What activities do/should they perform? When? How? Why – how does enterprise architecture create business value? This ebook focuses on answering these seemingly simple but often overlooked foundational questions related to enterprise architecture. Excellent Read! (150 pages)

Implementing the Federal Enterprise Architecture (FEA)

This document provides a standard approach to federal enterprise architecture (FEA) implementation – principles and standards for how business, information, and technology architectures should be developed across the enterprise so they can be used consistently at various levels of scope within and between domains/departments/divisions, as well as with external stakeholders.

Service Enablement Case Study

This case study discusses the steps taken for service enablement in a business area through market research, developing architecture design patterns, and strategy and roadmap.

Requirement and Constraint Analysis

This paper discusses the impact of non-functional requirements on software systems. "One of the most important roles for an architect is in the requirements engineering phase; this is how architects help define the solution that best satisfies all stakeholders."

CIO Portal