Zachman Framework asEnterprise ArchitectureOntology              Osama Abandeh, TOGAF, SOA                                ...
Agenda and presentation goals  Understand EA concept      Enterprise, Architecture, and EA      IT Organization chart w...
EA concept   Enterprise   Architecture   Enterprise Architecture The word “process” was added to IT in the year 1991 ...
EA concept   Enterprise   Architecture   Enterprise Architecture The word “process” was added to IT in the year 1991 ...
When do you need to Architect? When you are building small wood house or writing an  algorithm, probably you don’t need a...
EA Concept in Cobit
Architecture misconceptions   It is not system design   It is not SOA   It is not Business Analysis   It is not PM   ...
Discussion Area number 1
How Toyota able to provide acustom car in 5 days? Can we do the same and have services per customer?! IT now is Order Dr...
IEEE 1471 Standard Every system has architecture, weather it is documented or  not, the architecture is representing a co...
IEEE 1471 and Viewpoints
EA Frameworks Zachman, TOGAF, DoDaf, MODAF, NATO, Gartner EA, SAP  EA, SOA The value of EA is the value of the Enterpris...
Where we can find viewpoints? We can find viewpoints in Zachman, TOGAF, Gartner EA,  IEEE 1471, and other frameworks How...
Zachman Framework “EA Innovation is function of time not people” John said “The problem is culture in the people not the...
Zachman Framework “EA Innovation is function of time not people” John said “The problem is culture in the people not the...
Discussion Area number 2
TOGAF ADM
TOGAF ADM-   Run a project-   Data Migration-   Implement EA office-   Enhance Communication between teams-   Merging comp...
Avoid ROI for EA If the organization did not reach to a stage of recognizing the importance of EA, don’t try to convenes o...
How EA helps Organization? EA practice helps doing things faster  because of decreased  complexity  because of having c...
Discussion Area number 3End of presentationThe coming 4 slides is from John A. Zachman presentations …Enjoy …
Thanks
Thanks
Zachman Framework As Enterprise Architecture Ontology
Zachman Framework As Enterprise Architecture Ontology
Zachman Framework As Enterprise Architecture Ontology
Upcoming SlideShare
Loading in...5
×

Zachman Framework As Enterprise Architecture Ontology

3,490

Published on

Zachman Framework As Enterprise Architecture Ontology Presentation

0 Comments
7 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,490
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
7
Embeds 0
No embeds

No notes for slide
  • Place of hookup:Toyota custom car in 5 days  link this hook with building blocks In Bowing, how does they makes changes?  link this hook The meeting of Process was introduced last in 64  we are in new information age that have EA
  • Enterprise is having elements like (people, processes, applications, technologies, vision, mission, principles, business drivers, customers, data, policies and regulations) = it is a system
  • Enterprise is having elements like (people, processes, applications, technologies, vision, mission, principles, business drivers, customers, data, policies and regulations) = it is a system
  • The need of EA is increased in big organizations. You might not need an EA in small organization.
  • 20 years of development of this model
  • 20 years of development of this model
  • Transcript of "Zachman Framework As Enterprise Architecture Ontology"

    1. 1. Zachman Framework asEnterprise ArchitectureOntology Osama Abandeh, TOGAF, SOA 2012
    2. 2. Agenda and presentation goals  Understand EA concept  Enterprise, Architecture, and EA  IT Organization chart with EA office  Samples of EA Jobs  Architecture misconceptions  Discussion Area number 1  Introduction to EA Frameworks  Zachman  Discussion Area number 2  TOGAF  Discussion Area number 3
    3. 3. EA concept  Enterprise  Architecture  Enterprise Architecture The word “process” was added to IT in the year 1991 EA is the issue of this century
    4. 4. EA concept  Enterprise  Architecture  Enterprise Architecture The word “process” was added to IT in the year 1991 EA is the issue of this century
    5. 5. When do you need to Architect? When you are building small wood house or writing an algorithm, probably you don’t need an architecture, because you can see the hole picture in your head However, when you want to describe corporation or to implement a change for international system, then you need an architecture
    6. 6. EA Concept in Cobit
    7. 7. Architecture misconceptions It is not system design It is not SOA It is not Business Analysis It is not PM Application Expert is not EA System design is one view of the system SOA is Technology Architecture covers XML, DTD, XSLT, SOAP, WSDL, WS-* defined by W3 School, OAISIS, and WS-I Business Analysis, works to define the initial part of the architecture Project manager seeking signoff, EA seeking the truth behind signoff Application Expert is named as Domain Architect (Application Architect, Network Architect, Data Architect …) “EA is a collection of integrated viewpoints of the enterprise systems, that covers stakeholders concerns and updated according to predefined processes” Osama Abandeh
    8. 8. Discussion Area number 1
    9. 9. How Toyota able to provide acustom car in 5 days? Can we do the same and have services per customer?! IT now is Order Driven Business; Job Shop; IT responds to CRs Like most of organizations ; This is the Traditional Level Enhanced Model: Products, Stock shop like IBM before 20 years They are able to customize the car by having Forecasting / Reusability of Building Blocks
    10. 10. IEEE 1471 Standard Every system has architecture, weather it is documented or not, the architecture is representing a collection of integrated viewpoints, each viewpoint covers stakeholder concerns
    11. 11. IEEE 1471 and Viewpoints
    12. 12. EA Frameworks Zachman, TOGAF, DoDaf, MODAF, NATO, Gartner EA, SAP EA, SOA The value of EA is the value of the Enterprise When it came to acquisitions, do you know that the value of the enterprise is much higher if it has an EA office?
    13. 13. Where we can find viewpoints? We can find viewpoints in Zachman, TOGAF, Gartner EA, IEEE 1471, and other frameworks However we have hundreds of VP in the market, ideally you should define the VPs according to your organization stakeholders concerns
    14. 14. Zachman Framework “EA Innovation is function of time not people” John said “The problem is culture in the people not the technologies ” John said “I see the pattern, I did not invent it ” John said Zachman is defined as ontology that positions multiple viewpoints to describe one system The Row is the stakeholder type, Column is concerns
    15. 15. Zachman Framework “EA Innovation is function of time not people” John said “The problem is culture in the people not the technologies ” John said “I see the pattern, I did not invent it ” John said Zachman is defined as ontology that positions multiple viewpoints to describe one system The Row is the stakeholder type, Column is concerns
    16. 16. Discussion Area number 2
    17. 17. TOGAF ADM
    18. 18. TOGAF ADM- Run a project- Data Migration- Implement EA office- Enhance Communication between teams- Merging companies- Acquisitions- In short, give solutions for pain points
    19. 19. Avoid ROI for EA If the organization did not reach to a stage of recognizing the importance of EA, don’t try to convenes others by ROI, it is a strategic practice of the EA with long terms values, EA value is shown by comparing to other organizations, and by ROV. The below table is written by: “2004 Anthony Brown”
    20. 20. How EA helps Organization? EA practice helps doing things faster  because of decreased complexity  because of having clear views, building blocks and impact analysis Help to avoid duplicate team works and reuse the existing capabilities Helps management to know the existing capabilities of IT systems (The databases we have, the out of the box features we already have, the paid and unused licenses we have …) Having unified clear place for documentations for complex systems, to help us replacing the old black blocks easily and to have better handover between employees Strongly take care about non functional requirements (Secure production data we well as production systems, specially when it came to vendor – client relationship Clear view and engagement of stakeholders (DS Exchange Rates) Use the systems to the max Infrastructure and servers RAM, CPU can be rapidly reduced Ensure that approved CR is implemented in production as it should be, and to have a link between approved CR and Admin work in deployment!
    21. 21. Discussion Area number 3End of presentationThe coming 4 slides is from John A. Zachman presentations …Enjoy …
    22. 22. Thanks
    23. 23. Thanks

    ×