60 Second Guide To Enterprise Architecture

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

1 comments

Comments 1 - 1 of 1 previous next Post a comment

  • + craigrmartin Craig Martin 11 months ago
    Its always good to see the correct message for EA getting out there. A good high level view into value of this exciting discipline
Post a comment
Embed Video
Edit your comment Cancel

19 Favorites

60 Second Guide To Enterprise Architecture - Presentation Transcript

  1. The second guide to 60 Colin A. White | Chief Technology Officer | Enterprise Architect www.colinwhite.net | colinwhite@gmail.com | Dec 08 Enterprise Architecture 00:00
  2. 00:00 Q: What IS Enterprise Architecture?
  3. 00:02 A: Strategic Planning … that’s all Q: What IS Enterprise Architecture?
  4. 00:04 but definitions DO vary by Industry A: Strategic Planning … that’s all Q: What IS Enterprise Architecture?
  5. 00:06 Q: WHAT’S the EA value proposition?
  6. 00:08 A: A focus on maximizing investment returns … Q: WHAT’S the EA value proposition?
  7. 00:10 No alchemy or black magic involved A: A focus on maximizing investment returns … Q: WHAT’S the EA value proposition?
  8. 00:12 The most common misconception ?
  9. 00:14 … that it’s a function of IT The most common misconception ?
  10. 00:16 EA is NOT … Systems, Information, Service or Solution Architecture
  11. 00:18 … EAs are stakeholders in their outputs . EA is NOT … Systems, Information, Service or Solution Architecture
  12. 00:20 EA IS about… $ £ ¥ returns, Objectives & Performance
  13. 00:22 EAs typically work FOR the Office of the CIO…
  14. 00:24 EAs typically work FOR the Office of the CIO… THROUGH the Project Management Office (PMO) & Investment Review Board (IRB)
  15. 00:26 IT, Systems Engineering, Business Process Analysis EAs typically COME FROM …
  16. 00:28 EAs are quantitative , model-oriented, left-brain people.
  17. 00:30 EA outputs … Strategic Plans, Road Maps, Blue Prints, Reference Models, Design Patterns, Change Requests
  18. 00:32 EAs LOVE … Standards, Taxonomies, Ontologys
  19. 00:34 EA Lifecycle maps to the Project Management and Systems Engineering lifecycles.
  20. 00:36 Like Zachman, TOGAF, DoDAF, MoDAF, FEA etc. EAs use FRAMEWORKS …
  21. 00:38 EAs use FRAMEWORKS … FRAMEWORKS have their own Methods, Techniques & Tools Like Zachman, TOGAF, DoDAF, MoDAF, FEA etc.
  22. 00:40 Federal Enterprise Architecture (FEA) uses “ Method for Business Transformation (MBT) ”
  23. 00:42 The Open Group Architecture Framework (TOGAF) uses the “Architecture Development Methodology (ADM) ” Federal Enterprise Architecture (FEA) uses “ Method for Business Transformation (MBT) ”
  24. 00:44 The Dept. of Defense Architecture Framework (DoDAF) Uses “ FIPS183 compliant diagramming techniques” Federal Enterprise Architecture (FEA) uses “ Method for Business Transformation (MBT) ” The Open Group Architecture Framework (TOGAF) uses the “Architecture Development Methodology (ADM) ”
  25. 00:46 The US Federal Government (Office of Management & Budget) mandates the use of EA across agencies.
  26. 00:48 The US Federal Government (Office of Management & Budget) mandates the use of EA across agencies. It does NOT prescribe frameworks, methods or techniques.
  27. 00:50 The US Federal Government (Office of Management & Budget) mandates the use of EA across agencies. It does NOT prescribe frameworks, methods or techniques. Civilian Agencies tend to prescribe specific frameworks, techniques and templates
  28. 00:52 The US Federal Government (Office of Management & Budget) mandates the use of EA across agencies. It does NOT prescribe frameworks, methods or techniques. Civilian Agencies tend to prescribe specific frameworks, techniques and templates Defense, Research and Law Enforcement tend to be less prescriptive.
  29. 00:54 Industry tends to favor ZACHMAN and TOGAF
  30. 00:56 EA is viewed as a means to achieve a Service Oriented Architecture (SOA)
  31. 00:58 through enterprise Service & Technical Reference Models (SRM & TRM) EA is viewed as a means to achieve a Service Oriented Architecture (SOA)
  32. 00:60 These can be decomposed, automated and optimized through enterprise Service & Technical Reference Models (SRM & TRM) EA is viewed as a means to achieve a Service Oriented Architecture (SOA) and realized through the PMO & IRB
  33. Colin A. White | Chief Technology Officer | Enterprise Architect www.colinwhite.net | colinwhite@gmail.com | Dec 08 Enterprise Architect For further discussion, contact me.

+ Colin WhiteColin White, 11 months ago

custom

3734 views, 19 favs, 7 embeds more stats

A 60 second introduction to Enterprise Architecture more

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 3734
    • 3540 on SlideShare
    • 194 from embeds
  • Comments 1
  • Favorites 19
  • Downloads 568
Most viewed embeds
  • 136 views on http://bpmfundamentals.wordpress.com
  • 16 views on http://blog.exxeta.com
  • 14 views on http://evolveea.blogspot.com
  • 13 views on http://www.architectureandgovernance.com
  • 13 views on http://enterprise-3.blogspot.com

more

All embeds
  • 136 views on http://bpmfundamentals.wordpress.com
  • 16 views on http://blog.exxeta.com
  • 14 views on http://evolveea.blogspot.com
  • 13 views on http://www.architectureandgovernance.com
  • 13 views on http://enterprise-3.blogspot.com
  • 1 views on http://architectureandgovernance.com
  • 1 views on http://www.netvibes.com

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories