 |
 |
       |
 |
Home | Site Map | Blog | Contact |
 |
|
|
Research Content / Research Articles / Sample EA Artifacts
Sample EA Artifacts, Templates and How-To's
This area contains material to assist our clients with the design, formatting, creation and content of their proprietary EA artifacts. Material related to this category: EA ‘Jump Start’ Deliverables We frequently receive requests from our clients for examples of EA artifacts that meet the above and, in particular, artifacts that show the mapping of one EA domain to another. To meet these requests we have prepared a ‘Jump Start’ presentation that describes a hypothetical manufacturing business, ABC Company, and provides examples of EA-related artifacts that achieve the above. It is specifically intended for new EA efforts although mature EA teams should also benefit.
The reaction from our Clients to this material has been extraordinary. Excel was used to develop the sample artifacts contained herein. Templates are provided for:
· Enterprise Business Architecture (EBA)
· Enterprise Solutions Architecture (ESA)
· Enterprise Information Architecture (EIA)
· Enterprise Technical Architecture (ETA)
Follow this link to download ‘Jump Start’ sample deliverables Follow this link to see more details on the EA ‘Jump Start’ approach Example EA Principles Principles are an integral element of an effective EA practice. They represent the rationale, at different levels of abstraction, applied to the decisions and recommendations of the EA team. They are based on a variety of factors, including the objectives of the EA, implications of current technology and business trends, best practices, and the strengths and limitations of the enterprise. This document includes guidance on crafting EA principles and gives several examples, both derived and directly taken from client examples. Follow this link to read the whole article Creating the Enterprise Value Network (EVN) Diagram Follow this link to read the whole article Key Questions for Strategy and Capabilities The goal of extracting business strategy statements from the business for the purpose of enterprise architecture is to figure out what kind of changes would be necessary as a result. So anything that is told to you that you have no idea of the impact of the statement (how the company will operate differently, how processes will have to change, how information will be used, applications that would be needed, or technology that could support the strategy) is not an adequate statement. This document contains questions to ask and techniques to use, which will help in the development of business drivers. Follow this link to read the whole article
|
 |
|
 |