Enterprise Architecture: Use togaf for product development

Document directory

• Combination of product architecture and Enterprise Architecture
• Baseline-based iterative development process
• Iteration stage and main deliverables
• R1. Market Requirement documents
• R3. Gap Analysis
• 01. enterprise scope
• 02. Architecture Team
• 03. Architecture Principles
• A1. stakeholder analysis
• A2. heat map
• A3. concept DIAGRAM OF THE SOLUTION
• B1. organization breakdown chart
• B2. process Breakdown Diagram
• B3. function Breakdown Diagram
• CA1. Information Structure
• Cb1. application structure
• Cb2. application collaboration Diagram
• D1. infrastructure Diagram
• D2. implementation and deployment Diagram

In the first half of this year, I introduced a series of articles on the Enterprise Architecture TOGAF in my blog and published two e-books.Enterprise Architecture framework-togaf v0.2.pdfAndEnterprise development language archimate.pdfAfter receiving emails from many friends, most of them are IT consultants and architects, and some corporate information supervisors. I found that many people are paying attention to this topic. One IT person told me that he learned TOGAF because enterprises explicitly proposed that they should use the TOGAF method to create an information system for their enterprises, so we can see that, TOGAF has been widely promoted in China, and everyone thinks that TOGAF is a good thing. However, many of my friends feel that TOGAF is just an enterprise architecture framework. Although TOGAF9 has added a lot of guidance, it is not easy to apply it in actual work. In this article, I will share with you how I use TOGAF for product development based on my actual work.

 

• Who built the product?
• What is the architecture process?
• What are the important deliverables of the architecture?

 

Combination of product architecture and Enterprise Architecture

Baseline-based iterative development process

Iteration stage and main deliverables

R1. Market Requirement documents
R2. prototype

R3. Gap Analysis

01. enterprise scope

02. Architecture Team

03. Architecture Principles

A1. stakeholder analysis

A2. heat map

A3. concept DIAGRAM OF THE SOLUTION

 

B1. organization breakdown chart

B2. process Breakdown Diagram

B3. function Breakdown Diagram

Ca1. Information Structure

Cb1. application structure

 

Cb2. application collaboration Diagram

D1. infrastructure Diagram

 

D2. implementation and deployment Diagram

PDF document see: http://www.docin.com/p-60953340.html

 

You are welcome to reprint it. Please note: Reprinted fromZhou jingen [http://zhoujg.cnblogs.com/]

Combination of product architecture and Enterprise Architecture