01-Business Architecture
Purpose
Inputs (OR)
No |
Input |
Coming from/Output Of |
1.
|
Vision |
|
2.
|
Mission |
|
3.
|
Existing
Architecture |
|
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1. |
Define architecture
problem statement/goals/key objectives |
EA Team |
EA Repository |
EA Repository |
EA Repository |
2. |
Determine
Enterprise architecture team |
EA Team |
EA Repository |
EA Repository |
EA Repository |
3. |
Define decision
taking mechanism |
EA Team |
EA Repository |
EA Repository |
EA Repository |
4. |
Determine
enterprise architecture stakeholders |
EA Team |
EA Repository |
EA Repository |
EA Repository |
5. |
Determine
organization mission/vision |
EA Team |
EA Repository |
EA Repository |
EA Repository |
6. |
Determine existing products/Services |
EA Team |
EA Repository |
EA Repository |
EA Repository |
7. |
Determine Competition and create competition analysis |
EA Team |
EA Repository |
EA Repository |
EA Repository |
8. |
Determine existing pricing strategy |
EA Team |
EA Repository |
EA Repository |
EA Repository |
9. |
Determine Existing/Expected business model: -
Partners -
Customers -
Customer Relationship -
Distribution Channels -
Activities: Value chain -
Key resources -
Value proposition -
Cost -
Revenue |
EA Team |
EA Repository |
EA Repository |
EA Repository |
10. |
Create personas for the customers (Values and characteristics) |
EA Team |
EA Repository |
EA Repository |
EA Repository |
11. |
Establish SWOT analysis to achieve the new vision |
EA Team |
EA Repository |
EA Repository |
EA Repository |
12. |
Build Enhanced model around SWOT: -
How to Utilize strengths -
How to mitigate weaknesses -
How to attack opportunities -
How to prevent/mitigate threats |
EA Team |
EA Repository |
EA Repository |
EA Repository |
13. |
Take corrective actions that support the kick-off for the new business
model |
EA Team |
EA Repository |
EA Repository |
EA Repository |
14. |
Determine initial vision strategy in quantitative objectives |
EA Team |
EA Repository |
EA Repository |
EA Repository |
15. |
Determine initial CSF per each area: Critical success factors |
EA Team |
EA Repository |
EA Repository |
EA Repository |
16. |
Determine Architecture model constraints |
EA Team |
EA Repository |
EA Repository |
EA Repository |
17. |
Determine required skills for the new business strategy |
EA Team |
EA Repository |
EA Repository |
EA Repository |
18. |
Determine expected modifications in Org-chart/functions/ roles and job
descriptions |
EA Team |
EA Repository |
EA Repository |
EA Repository |
19. |
Determine Initial Product/services lifecycle |
EA Team |
EA Repository |
EA Repository |
EA Repository |
20. |
Determine business
principles |
EA Team |
EA Repository |
EA Repository |
EA Repository |
21. |
Determine business
Capabilities to be built |
EA Team |
EA Repository |
EA Repository |
EA Repository |
22. |
Record different
viewpoints: -
Financial -
Operational -
Marketing |
EA Team |
EA Repository |
EA Repository |
EA Repository |
23. |
Determine scope
of organization to be impacted: -
Staged -
Vertical -
Depth |
EA Team |
EA Repository |
EA Repository |
EA Repository |
24. |
Finalize initial
roadmap |
EA Team |
EA Repository |
EA Repository |
EA Repository |
Outputs
No |
Output |
Going To/Input Of |
1 |
Vision/Goal/Objective/Service
diagram |
Data
architecture |
2 |
Business Model |
|
|
Market research |
|
|
Stakeholders’
matrix |
|
3 |
Value chain |
|
4 |
Business
capabilities |
|
5 |
Org chart |
|
6 |
Process Flow
diagram |
|
7 |
Principles
Catalog |
|
|
Capabilities
Catalog |
|
8 |
CSF: Critical
success factors |
|
9 |
SWOT analysis |
|
10 |
PESTEL analysis |
|
11 |
As is Model
Vs To be model |
|
12 |
Skills matrix |
|
13 |
Job description |
|
|
Requires recruitments |
|
|
Architecture framework |
|
|
Governance framework |
|
|
Architecture requirements |
|
|
Scope of work |
|
02-Data Architecture
Purpose
Inputs (OR)
No |
Input |
Coming from/Output Of |
4.
|
Initial
Business Architecture |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1. |
Develop high
level solution architecture landscape |
EA Team |
EA Repository |
EA Repository |
EA Repository |
2. |
Determine
required data for the business model |
EA Team |
EA Repository |
EA Repository |
EA Repository |
3. |
Determine data
ownership and gathering techniques -
Download -
Self-generated -
Crawling -
Third parties |
EA Team |
EA Repository |
EA Repository |
EA Repository |
4. |
Determine
required data analysis approaches |
EA Team |
EA Repository |
EA Repository |
EA Repository |
5. |
Determine machine
learning/Deep learning required approaches |
EA Team |
EA Repository |
EA Repository |
EA Repository |
6. |
Determine data
models lifecycle |
EA Team |
EA Repository |
EA Repository |
EA Repository |
7. |
Determine high
level data security model |
EA Team |
EA Repository |
EA Repository |
EA Repository |
8. |
Determine
required database engines: -
SQL -
No-SQL -
Big data |
EA Team |
EA Repository |
EA Repository |
EA Repository |
9. |
Determine required
Data-marts and data warehousing |
EA Team |
EA Repository |
EA Repository |
EA Repository |
10. |
Determine
high-level backup procedure -
Baseline -
Changes increments -
Retention |
EA Team |
EA Repository |
EA Repository |
EA Repository |
11. |
Define high
level geodes/shards |
EA Team |
EA Repository |
EA Repository |
EA Repository |
12. |
Define initial
data models components as component diagram |
EA Team |
EA Repository |
EA Repository |
EA Repository |
13. |
Develop Data principles |
EA Team |
EA Repository |
EA Repository |
EA Repository |
14. |
Determine Data capabilities
to be built |
EA Team |
EA Repository |
EA Repository |
EA Repository |
Outputs
No |
Output |
Going To/Input Of |
1 |
ERD |
Application
architecture |
2 |
Class diagram |
|
3 |
Data
architecture model/deployment |
|
4 |
Data Dissemination diagram |
|
5 |
Data Security diagram |
|
6 |
Data Lifecycle diagram |
|
7 |
Product
Lifecycle Diagram |
|
8 |
Data sources |
|
9 |
Share policy |
|
10 |
Data to sell |
|
11 |
Data tools |
|
12 |
Baselined data |
|
13 |
Backup strategy |
|
14 |
Data marts |
|
15 |
Data analysis |
|
16 |
AI forecasting
models |
|
03-Application Architecture
Purpose
Inputs (OR)
No |
Input |
Coming from/Output Of |
1.
|
Data
architecture |
|
2.
|
Business
architecture |
|
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1. |
Determine required
solutions for the business/data architecture model |
EA Team |
EA Repository |
EA Repository |
EA Repository |
2. |
Determine core
modules per each required solution |
EA Team |
EA Repository |
EA Repository |
EA Repository |
3. |
Determine
suitable platforms for each persona according to values and characteristics: -
Mobile -
Web -
Desktop -
Tablet -
TV |
EA Team |
EA Repository |
EA Repository |
EA Repository |
4. |
Determine
initial deployment model |
EA Team |
EA Repository |
EA Repository |
EA Repository |
5. |
Determine
initial component model |
EA Team |
EA Repository |
EA Repository |
EA Repository |
6. |
Determine
required technologies |
EA Team |
EA Repository |
EA Repository |
EA Repository |
7. |
Determine Third
parties Integration: -
SSO -
OTP -
SMS Gateway -
E-Payment Gateway -
Notification services -
ML services -
Storage services |
EA Team |
EA Repository |
EA Repository |
EA Repository |
8. |
Develop Technology
principles |
EA Team |
EA Repository |
EA Repository |
EA Repository |
9. |
Determine Application
capabilities to be built |
EA Team |
EA Repository |
EA Repository |
EA Repository |
Outputs
No |
Output |
Going To/Input Of |
1 |
Application
architecture |
Technology
architecture |
2 |
Product
Lifecycle Diagram |
|
3 |
Deployment
model |
|
4 |
Component model |
|
5 |
Class diagrams |
|
6 |
Use cases
diagrams |
|
7 |
State-chart
diagram |
|
8 |
Activity
diagrams |
|
9 |
UX |
|
10 |
User journey |
|
11 |
Internal solutions
mapped to business process |
|
12 |
External
solution |
|
04-Technology Architecture
Purpose
Inputs (OR)
No |
Input |
Coming from/Output Of |
1.
|
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1. |
Determine
opportunities for selected clouds/servers for the mentioned model |
EA Team |
EA Repository |
EA Repository |
EA Repository |
2. |
Determine
opportunities for the data warehousing model |
EA Team |
EA Repository |
EA Repository |
EA Repository |
3. |
Initialize the
cloud instances |
EA Team |
EA Repository |
EA Repository |
EA Repository |
4. |
Determine
opportunities for third parties service providers |
EA Team |
EA Repository |
EA Repository |
EA Repository |
5. |
Develop Technology
principles |
EA Team |
EA Repository |
EA Repository |
EA Repository |
6. |
Determine
technology capabilities to be built |
EA Team |
EA Repository |
EA Repository |
EA Repository |
Outputs
No |
Output |
Going To/Input Of |
1 |
05-Opportunitites and Solutions
Purpose
Inputs (OR)
No |
Input |
Coming from/Output Of |
1.
|
EA Model |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1. |
Determine
decisions alternatives -
As example which SMS gateway to be selected -
Which cloud to be selected |
EA Team |
EA Repository |
EA Repository |
EA Repository |
2. |
Determine
selection criteria |
EA Team |
EA Repository |
EA Repository |
EA Repository |
3. |
Record
decisions ranks according to selection criteria |
EA Team |
EA Repository |
EA Repository |
EA Repository |
4. |
Take final
decisions per each |
EA Team |
EA Repository |
EA Repository |
EA Repository |
Outputs
No |
Output |
Going To/Input Of |
1 |
Deployment
diagram |
|
2 |
Network
computing and hardware diagram |
|
06-Migration Plan
Purpose
Inputs (OR)
No |
Input |
Coming from/Output Of |
1.
|
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1. |
Find gaps
between as is model and to be model in all areas: -
Data architecture -
Application architecture -
Technology architecture |
EA Team |
EA Repository |
EA Repository |
EA Repository |
2. |
Create
architecture landscape/iterations according to predefined criteria |
EA Team |
EA Repository |
EA Repository |
EA Repository |
3. |
Develop
transition architecture model: -
Timeline -
Modules -
Depth -
Capability based planning |
EA Team |
EA Repository |
EA Repository |
EA Repository |
4. |
Define involvement
matrix per each area |
EA Team |
EA Repository |
EA Repository |
EA Repository |
5. |
Go for PM
practices. |
EA Team |
EA Repository |
EA Repository |
EA Repository |
Outputs
No |
Output |
Going To/Input Of |
1 |
Project
context |
|
2 |
Benefits
diagram |
|
07-Implementation Governance
Follow QA Practices