Mr. Zachman focused on architecture since 1970. His 1st article and the original framework was published in 1987 (“A Framework for Information Systems Architecture,” IBM Systems Journal, vol. 26(3), 1987. http://www.research.ibm.com/journal/sj/263/ibmsj2603E.pdf ).
In 1992 John Zachman and John Sowa wrote another article (“Extending and Formalizing the Framework for Information Systems Architecture." J.F. Sowa and J. A. Zachman. IBM Systems Journal, vol. 31, no. 3, 1992. http://www.research.ibm.com/journal/sj/313/sowa.pdf ) expanded the framework to its current 36 cell framework (“Enterprise Architecture – A Framework”).
Zachman’s A Framework for Enterprise Architecture ® John A. Zachman, Zachman International http://www.zachmaninternational.coml Business Technical
Zachman – for School Classroom Source: O’Rourke, C. (2003); Enterprise Architecture Using the Zachman Framework ; Course Technology Prepared students Timetables Students & teachers Classroom Montessori or individualization Books Functioning Enterprise Strategy & tactics based on plan, time, location & students Attendance Dismissals Security needs Location of classroom materials Lesson plan Arrange classroom things Sub-contractor Teacher rules and guidelines Teacher assignments Class assignments to remove conflicts Realistic location for activities Course plan based on enrollment & facility Practical material composition Builder Grading rules and guidelines Student and teacher interaction Teacher and student ratios Preferred location of teaching activities Optimal delivery of course plan Optimal material composition Designer Scholastic achievement targets Teaching schedule Teacher workflow Location of facilities Delivery according to student needs Material of classroom content Owner Government mandates School calendar Professors Instructors Staff Delivery technique Approved teaching delivery Approved Curriculum Planner Why Motivation When Time Who People Where Locations How Processes What Things
EA’s value is tied directly to its ability help organizations deal with complexity and change. The greater the complexity and the greater the envisioned change , the greater will be the EA value to facilitate that change.
Readily available descriptive representations of the enterprise
Ability to unify and integrate business processes across the enterprise
Ability to unify and integrate data across the enterprise
Increased flexibility of the enterprise to link with external partners
Increased agility by lowering the "complexity barrier“.
Reduced solution delivery time and development costs by maximizing reuse of enterprise models
Ability to create a common vision of the future shared by the business and IT communities = continuous business/IT alignment
Source: Brown, A. (2004), “ Enterprise Architecture Value Proposition”
Do you have an EA? Does it integrate cross agencies?
Does it show (business) results?
Future of EA in Federal Government E-Gov initiatives LOB Centers of Excellence Smart Buy Implementation/use of Government-wide Lower level Architectures include Department and Agency solutions Agencies include Gov-wide Initiatives in their EA Department/Agency Specific A gencies Contribute to Gov-wide Initiatives Source: Dick Burk Briefing at IAC meeting 1/27/2006 Program Solution Program Solution Program Solution Program Solution Agency/Bureau Solutions Department/Agency Solutions Federal Government-wide Solutions
Capital Investment Planning Strategic Plan Enterprise Architecture Migration Plan FY FY FY FY $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ Maps Investment to Returns Today’s Architecture Future Architecture (today +)
Now that we understand what an EA is and its value to an organization Let’s talk about how to establish a successful EA program office