Speaking Notes:Ask the audience to throw out words and phrases of what they think (and others think) of when they hear the term “Enterprise Architecture”. The association can be definitional (what it is) and/or positive and negative connotations about the business value EA offers (what problem is it trying to solve). Repeat and accept all answers and encourage the audience to have fun with this.
Transcript of "ea2009 Enterprise Architecture keynote Final"
Recommended set of products and configurations (EA processes, architecture content, implementation roadmap, governance)</li></ul>How do you pragmatically apply these?<br />Zachman Framework<br /><ul><li> John Zachman (IBM, 1980’s)
Start of it all</li></ul>The Open Group Arch Framework<br />(TOGAF)<br /><ul><li> Since 1995
Widely Adopted in the Commercial Sector</li></ul>Federal Enterprise Architecture (FEA)<br /><ul><li> Since 1999
Federal agencies map investment requests to their FEA reference models</li></li></ul><li>Pragmatic Enterprise ArchitectureJust in Time - Enterprise Architecture<br />“Just-enough models should be created just in time to address specific [business-driven requirements].”<br />Gartner EA Process: Evolution 2005<br />
Create roadmaps on a “just in time” basis as you launch specific EA initiatives and architect enterprise solutions. Define “just enough” of the current and future states to implement your transformations and solutions.</li></ul>Exhaustively define Roadmap to “Future State” Architecture<br />
Applying Enterprise Architecture <br />A Solution Blueprint<br />spans all the <br />layers of the OEAF <br />(e.g. Modernisation)<br />A Customer EA is a configuration of the OEAF for a given Customer<br />An Industry Blueprint is a configuration of the OEAF for a given industry (e.g. Retail)<br />