Search results
Results from the WOW.Com Content Network
The Enterprise Architecture Planning (EAP) methodology is beneficial to understanding the further definition of the Federal Enterprise Architecture Framework at level IV. EAP is a how to approach for creating the top two rows of the Zachman Framework, Planner and Owner. The design of systems begins in the third row, outside the scope of EAP.
The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy.
The Architecture Development Method (ADM) is applied to develop an enterprise architecture which will meet the business and information technology needs of an organization. It may be tailored to the organization's needs and is then employed to manage the execution of architecture planning activities. [18] The process is iterative and cyclic.
Levels of Enterprise Architecture Planning. [5]In his 1992 book Enterprise Architecture Planning (EAP), Spewak defined Enterprise Architecture Planning as "the process of defining architectures for the use of information in support of the business and the plan for implementing those architectures".
Enterprise architecture regards the enterprise as a large and complex system or system of systems. [3] To manage the scale and complexity of this system, an architectural framework provides tools and approaches that help architects abstract from the level of detail at which builders work, to bring enterprise design tasks into focus and produce valuable architecture description documentation.
Enterprise architecture management (EAM) is a "management practice that establishes, maintains and uses a coherent set of guidelines, architecture principles and governance regimes that provide direction and practical help in the design and development of an enterprise's architecture to achieve its vision and strategy."
The Department of Veterans Affairs at the beginning of the 21st century [when?] planned to implement an enterprise architecture fully based on the Zachman Framework. The Zachman Framework was used as a reference model to initiate enterprise architecture planning in 2001. Somewhere in between the VA Zachman Framework Portal was constructed.
John Zachman is one of the founding developers of IBM's Business Systems Planning (BSP), [6] and worked on their Executive team planning techniques (Intensive Planning). In 1987 he originated the Zachman Framework a standard for classifying the descriptive representations (models) that comprise enterprise architecture.