The EA rush / Natty Gur
Embed Size (px)
Transcript of The EA rush / Natty Gur
- 1. The Enterprise Architecture RushNatty Gur The EA group IASA director of technology The Third National Conference INCOSE_IL 2005
- What is Enterprise Architecture?
- How EA is being implemented?
- Whos running EA in the world and what are the outcomes
3. Why? (we need EA)
- Technical architecture debates
- Financial constrains
- Changes in business mission and/or vision
- Law and constitution:
- Clinger-Cohen act
- Sarbanes-Oxley (SOX)
- Systems integration to maximize data usage across the enterprise
4. What exists today
- Infrastructure architecture:16%
- System architecture : 46%
- Enterprise architecture: 15%
- Based on :Enterprise Architecture Trend Report 2004, "How are organizations Progressing?", November 2004, IFEAD .
5. What? (is EA)
- Its not technical!
- Aligning IT to business.
- Answering all of the enterprise needs
- Transverse view.
- knowing and managing the current situation, paving the road towards the desired situation.
- Implementation of information management
- Enforcehomogeneous solutions and enable One system to the users.
6. What? Infrastructures Information Systems Business processesBusiness plans and goals Technologies -- -- -- -- -- -- -- 7. How? (EA is being done) Business Information Application Infrastructure Governance Migration planning 8. Who? (is doing EA)
- Chief enterprise architect
- Business, Information, System, Infrastructure architects.
- EA teams /committees
9. Where? (EA being done)
- All around the world.
- lead by America(33%) and west Europe(27%)
- Unknown in Israel (middle east 6%)
- Medium organization (from 100 workers)
10. When? (EA should be done)
- The sooner, the better
11. EA frameworks
- Reference model
- How to do certain tasks.
- Not an outcome!
- Zachman, FEAF, TOGAF, other sector oriented.
- Theyre all adjustable to your needs.
12. Zachman 13. Zachman
- Classified by basic 6 wh questions
- When, where, why, who, what how
- No predefined order
- Work on 5 layers
- Scope, Enterprise model, system model, technology, components.
- Any cell should be defined.
- The more the relationships between cross cells and layers are defined, the better.
- Must obey the framework rules!
- The columns have no order
- Each column has a simple, basic model
- The basic model for each column must be unique
- Each row represent distinct, unique perspective
- Each cell is unique
- Integration of all row cells constitutes complete row picture.
- The logic is recursive
15. The TOGAF way
- Never ending organization process which builds upon several stages:
- Business architecture.
- Information architecture
- Applications architecture
- Infrastructure architecture
- Gap analysis
- And again
16. Enterprise architecture - TOGAF 17. Who implement it
- Governmental agencies in the states
- Firms & enterprises
- Telco (1.5 B euro).
- Improvement of IT products and savings
- In Israel
18. Cisco example 19. Practical steps
- Read about EA
- Enterprise Architecture Planning, Steven H. Spewak.
- The Practical Guide to Enterprise Architecture by JamesMcGovern ,Scott W. Ambler,Michael E.
- Handbook on Enterprise Architecture (International Handbooks on Information Systems) by Peter Bernus, Laszlo Nemes (Editor), Gunter Schmidt (Editor).
- A Practical Guide for Developing an Enterprise Architecture :http:// www.gao.gov/bestpractices/bpeaguide.pdf
- Organization meetings
20. Practical steps
- Choose a framework
- Learn it
- Consider hiring a consultant that knows it.
- Adjust the framework to your enterprise needs
- Determine the scope and objectives.
- Create a vision.
- Get a CxO level approval.
- Set KPIs (key performance indicator) for measurement.
21. Q&A 22. Thank you
- Natty Gur
- Site:http:// www.theeagroup.net
- The enterprise architects
- 513b Plaza Rd.
- Vestal, NY 13850
- +1 (607) 330-1744
- +972 52 8888377