The OCIO Business Architecture
The OCIO business architecture consider the Office of Chief Information Offier as a critical Line of Busines in the information age rather than a supporting organization. E-OCIO ise essencail to enable E-Gov and E-Enterprise.The OCIO Business Architecture analysis is implemented based the Coherent EA approach in Enterprise Map and Business Architecture model. The Enterprise Map is the effort to see the big picture as the traditional map do. The OCIO Business Architecture analyze OCIO from the aspect of Mission (Why), Function (How), Information (What), Oragnization (Who), Location (Where), Performance (When)by analya their elements, structure and relation.
The OCIO Business Architecture also adopt the Coherent EA principle to lean experiences of the others. There is nothing new under the sun, after a decade, there are many long lasting EA efforts such as the A practicle guide to Federal Enterprsie Architecture by US Federal Goverment Chief Information Officers Council.
The OCIO Business Architecture leverage on past EA effort to populate the OCIO mission, function, informaiton, organization, location and performance. The OCIO have to "eat their own dog food" to render their business in architecture stytle. It is a clear advantage to render OCIO business architecture systematically in a architecture approach over the the traditional redition in a documental stytle. Hopefull, this effort will further renders the value of The CIO Council practicle guide to Federal Enterprsie Architecture which was written in 1999, and has been a very useful EA document.
Please navigate the OCIO Business Architecture by clicking on the chapters on the left column.
^ TOP
OCIO Concept of Operation
2.4. Architecture PrinciplesPrinciples establish the basis for a set of rules and behaviors for an organization. There are principles that govern the EA process and principles that govern the implementation of the architecture. Architectural principles for the EA process affect development, maintenance, and use of the EA. Architectural principles for EA implementation establish the first tenets and related decision-making guidance for designing and developing information systems.
The Chief Architect, in conjunction with the CIO and select Agency business managers, defines the architectural principles that map to the organization’s IT vision and strategic plans. As shown in Figure 1, architectural principles should represent fundamental requirements and practices believed to be good for the organization. These principles should be refined to meet Agency business needs. It should be possible to map specific actions, such as EA development, systems acquisitions, and implementation, to the architectural principles. Deliberate and explicit standards-oriented policies and guidelines for the EA development and implementation are generated in compliance with the principles. Each and every phase of the Systems Life Cycle is supported by the actions necessitated by the architecture principles. CPIC actions are governed by the implications within the principles.
2.5. The Enterprise Life Cycle
The enterprise life cycle is the dynamic, iterative process of changing the enterprise over time by incorporating new business processes, new technology, and new capabilities, as well as maintenance and disposition of existing elements of the enterprise.
Although the EA process is the primary topic of this guide, it cannot be discussed without consideration of other closely related processes. These include the enterprise engineering and program management cycle (more commonly known as the system development/acquisition life cycle) that aids in the implementation of an EA, and the CPIC process that selects, controls, and evaluates investments. Overlying these processes are human capital management and information security management. When these processes work together effectively, the enterprise can effectively manage IT as a strategic resource and business process enabler. When these processes are properly synchronized, systems migrate efficiently from legacy technology environments through
Roy Roebuck in One World
^ TOP