1. IEEE Architecture Council Overview
ITSC Meeting
06-Dec-2004

2. What is Enterprise Architecture?
Enterprise Architecture - a strategic information asset base, which defines the mission, the information necessary to
perform the mission and the technologies necessary to perform the mission, and the transitional processes for implementing new technologies in response to the changing mission needs.
An enterprise architecture includes a baseline architecture, target architecture, and a sequencing plan.
(from A Practical Guide to Federal Enterprise Architecture)
8-Jul-19

3. What is Enterprise Architecture
At a high level, enterprise architecture can be defined as “…an enterprise-wide, integrating framework which incorporates:
Enterprise Business Architecture
Enterprise Information Architecture (aka Data Architecture)
Enterprise Technology Architecture (aka Infrastructure Architecture)
Enterprise Solution Architecture (aka Application Architecture)
(ISWorldNet)
8-Jul-19

4. Why an EA?
The primary purpose of an EA is to inform, guide, and constrain the decisions for the enterprise, especially those related to IT investments. The true challenge of enterprise engineering is to maintain the architecture as a primary authoritative resource for enterprise IT planning. This goal is not met via enforced policy, but by the value and utility of the information provided by the EA.
(from A Practical Guide to Federal Enterprise Architecture)
8-Jul-19

5. Why an EA?
An EA offers tangible benefits to the enterprise and those responsible for evolving the enterprise. The EA can:
Capture facts about the mission, functions, and business strategy in an understandable manner to promote better planning and decision making
Improve communication among the business organizations and IT organizations within the enterprise through a standardized vocabulary
Provide architectural views that help communicate the complexity of large systems and facilitate management of extensive, complex environments
Improve consistency, accuracy, timeliness, integrity, quality, availability, access, and sharing of IT-managed information across the enterprise
8-Jul-19

6. Business Architecture
Identifies the Business strategies, functions, processes, organization and information flow for accomplishing mission of the organization
Functionality driven approach rather than Org-chart, location maps etc.
8-Jul-19

7. Business Architecture
Define businesses based on common functional needs
Develop process to define common vision and goals and a plan to achieve operational efficiencies using Information technology strategies
Develop and define roles and responsibilities to facilitate communication and coordination and a common IT strategy
Regular audits of current capabilities and evaluations of business drivers to influence behaviors
8-Jul-19

8. Information Architecture
Data Strategy
Defining Major types of data needed to conduct the business
Analytical and Operational data needs
Common definitions and vocabulary
Authoritative source and data migration needs
8-Jul-19

9. Information Architecture
Develop a common enterprise wide data definition
Define authoritative data sources
Develop business processes & technology to ensure data integrity
Understand and develop data to support operational and analytical business needs
8-Jul-19

10. Technology Architecture
It covers all the supporting IT elements that must be operated on a day-to-day basis, together with the tools and processes to monitor and manage them
Usually the most clearly defined
Technology “Stacks”
Example:. Weblogic running on Solaris with Oracle RDBMS
8-Jul-19

11. Solution Architecture
Defines Application and supporting capabilities of software systems to manage the underlying data to meet business and performance needs
It begins with the identification of which applications are needed to support the business and carries through the design and construction (or acquisition) and integration of applications
8-Jul-19

12. Solution Architecture
The cataloging of these applications is the definition of the “Building Blocks” project within IT
Reuse and assembly of common application architecture components
Eventually this will lead to an Application capability reference model
Structured across horizontal business areas independent of business functions
8-Jul-19

13. Steps to develop EA Define a process to promote EA
Define current architecture: Continue to take an inventory of where we are today. (Reference Architecture)
Understand business and technology drivers
Define the future EA (Target Architecture)
Plan the trip (Migration Strategy)
8-Jul-19

14. Our Charter Define IEEE Enterprise Architecture standards
Build consensus across departments on common application platforms, tools and infrastructure components
Collaborate and build synergies across our technology platforms aligned with our IEEE Goals and Objectives
8-Jul-19

15. Our Team Publications - Doug Gischler Standards - Bob Labelle
Computer Society - Bob Care and Darin Saunders
Corporate Communications - Sonny Barber and Jon Randall
Communications Society - David Alvarez
Regional Activities/Membership - Vera Sharoff
Technical Activities/Conferences - James Taylor, Mary Ann De Wald
IEEE USA – John Yaglenski
Member and Customer Services - Bill Cook
Information Technology - Sally Waselik, James Pankiewicz, Nimish Shah, Stephen Beck
8-Jul-19

16. IEEE EAC Mission
The mission of the IEEE Enterprise Architecture Council is to create and promote the principles, guidelines, standards and processes for the benefit of IEEE members, clients, volunteers, staff, societies and business areas (the “Enterprise”) by:
building Synergies across organizations - in business processes, infrastructure, data definition & migration and applications
leveraging existing technical and support infrastructure
promoting a culture of re-use leading to decreased time-to-market and lower development costs
keeping abreast with upcoming business and technology trends for applicability
facilitating the efficient and effective introduction of new technology and business solutions
mentoring local steering committees in the adoption of the above in their organizations.
8-Jul-19