Governance and Conceptual, Logical and Installed Architecture Alignment Using Work Products and Workflow
暂无分享,去创建一个
Governance and related alignment methods for the management of complex systems are introduced here to facilitate and better decision making. The goal here is to increase re-use and agility. We also show how EA governance can leverage technologies like middleware and workflow to enable service evolution. The methods and work products of the previous Chapter 2 along with the following EA layers guide continual service improvement. What is the ACE EA governance? • How is the organization established? • What are the goals and benefits of EA governance? • What are the different roles and responsibilities of the EA team? How does the Conceptual ACE structure guide the EA team to make enhancements to the Logical and Installed architecture layers? Ramanathan & Ramnath Copyright © 2009, IGI Global, distributing in print or electronic forms without written permission of IGI Global is prohibited. • What is the service life-cycle and how does this use the architecture layers for service improvement? • How does the conceptual architecture relate to the logical and the installed physical layers? • What types of work products are needed to enable the entire service lifecycle? • How is the conceptual layer used to determine governance Roles and responsibilities? • How does EA governance facilitate continual improvement? • What types of business and operational information is needed for engineers and architects to analyze and improve the Interaction performance? • What is missing? Interactions What security, privacy and audit requirements are met by the Roles? Who can see/ update the information?
[1] Klaus Pohl,et al. Adapting traceability environments to project-specific needs , 1998, CACM.
[2] John A. Zachman,et al. A Framework for Information Systems Architecture , 1987, IBM Syst. J..
[3] Jeffrey O. Kephart,et al. The Vision of Autonomic Computing , 2003, Computer.
[4] Jaap Gordijn,et al. E-service design using i* and e/sup 3/ value modeling , 2006, IEEE Software.