ENTERPRISE ARCHITECTURE

Plan your lessons and the goals of your lessons as well as including important content

Get Started. It's Free
or sign up with your email address
Rocket clouds
ENTERPRISE ARCHITECTURE by Mind Map: ENTERPRISE ARCHITECTURE

1. Contoh Framework

1.1. EAP

1.1.1. Initiation Planning

1.1.2. Preliminary business model

1.1.3. ; Enterprise survey

1.1.4. Current systems and technology architecture

1.1.5. Data architecture

1.1.6. Application architecture

1.1.7. Technology architecture

1.1.8. Implementation plan

1.1.9. Planning conclusion

1.1.10. Transition to implementation

1.2. TOGAF

1.2.1. Preliminary

1.2.2. Architecture vision

1.2.3. Business Architecture

1.2.4. IS Architecture

1.2.5. Technology Architecture

1.2.6. Opportunities and Solutions

1.2.7. Migration Planning

1.2.8. Implementation Governance

1.2.9. Architecture Change Management

1.3. DODAF

1.3.1. Capability

1.3.2. Data and Information

1.3.3. Operational

1.3.4. Project

1.3.5. Services

1.3.6. Standards

1.3.7. Systems

1.4. Gartner

1.4.1. Business Owners

1.4.2. Information Specialists

1.4.3. The Technology Implementers.

1.5. FEA

1.5.1. Architectural Analysis

1.5.2. Architectural Definition

1.5.3. Investment and Funding Strategy

1.5.4. Program-Management Plan and Execute Projects

2. Konsep SOA pada Enterprise Architecture (EA) Framework

2.1. SOA

2.1.1. Suatu cara untuk mengembangkan sistem dengan menyusun software agar layanan / function dapat saling terintegrasi

2.2. Service-Oriented Enterprise Architecture (SOEA)

2.2.1. Sinergi antara SOA dan EA yang memungkinkan keduanya untuk menyelesaikan satu sama lain agar lebih baik untuk mendukung kebutuhan bisnis

2.3. perspective SOA

2.3.1. The business perspective

2.3.2. The architecture perspective

2.3.3. The implementation perspective

2.4. Komponen SOA

2.4.1. The service directory

2.4.2. The service provider

2.4.3. The service requester that uses the service directory to find an appropriate service

2.5. Standart SOA

2.5.1. SOAP (Simple Object Access Protocol)

2.5.2. WSDL (Web Services Description Language)

2.5.3. UDDI (Universal Description, Discovery, and Integration)

3. Framework SOEA

3.1. Architectural layers

3.1.1. - Business Architecture

3.1.2. - Application architecture

3.1.3. - Infrastructure architecture

3.2. Proposed Project Phases

3.2.1. - Project Planning

3.2.2. - As-Is Architecture

3.2.2.1. Business As-Is Architecture

3.2.2.2. IT As-Is Architecture

3.2.3. - Analysis of As-Is Architecture

3.2.4. - To-Be Architecture

3.2.4.1. Business To-Be Architecture

3.2.4.2. IT To-Be Architecture

3.2.5. - Migration Plan

3.3. Project management recommendations

3.3.1. - Project Management Plan (PMP)

3.3.2. - Readiness Assessment

3.3.3. - Change Management and learning

3.3.4. - Portfolio of experts

4. Migrasi data dengan TOGAF

4.1. Metode pengembangan dari TOGAF dapat menyediakan kerangka kerja untuk mengatasi masalah migrasi data yang paling umum.

4.2. 4 Dimensi

4.2.1. Organizational dimension

4.2.2. Procedural standards

4.2.3. Business dimension

4.2.4. Technical dimension

4.3. 12 Phase

4.3.1. Project, quality and risk management

4.3.2. Migration strategy

4.3.3. Data analysis

4.3.4. Migration concept

4.3.5. Transformation definition

4.3.6. Program adaption

4.3.7. System preparation

4.3.8. Load and test

4.3.9. Approval

4.3.10. Productive migration

4.3.11. Data cleansing

5. Struktur untuk penyelarasan bisnis dan TI dalam perusahaan

6. Tujuan utama dari EA adalah untuk menyediakan sistem informasi yang tepat berdasarkan tuntutan bisnis perusahaan.

7. Jenis Pola Manajemen EA

7.1. Methodology Patterns (M-Pattern)

7.2. Viewpoint Patterns (V-Pattern)

7.3. Information Model Patterns (I-Pattern)

7.3.1. Business application

7.3.2. Business process

7.3.3. Business Support Migration

7.3.4. Business support provider

7.3.5. Introduction

7.3.6. Organizational unit

7.3.7. Project

7.3.8. Project task

7.3.9. Retirement

7.3.10. Support relationship

7.4. Anti-Pattern