IT规划方法教程分析.ppt

* * Any recommendations you propose are of major value because they can become requirements and form the basis for architecture principles. * The customers strategies indicate capabilities, at high level. These should be reviewed before you perform an IT Assessment. If it is a standalone service engagement, then you must assess the implications of the strategies before scoping the IT Assessment service engagement. If you cannot assess and verify the strategies and their output, you must, at a min, assess business and user needs. However, these inputs may vary from almost note to very extensive, depending upon the customers situation and the goal of the IT Assessment. The customers current infrastructure provides a basis for understanding the required systems. It is reviewed during the IT Assessment. The area above the dotted line represents the customers area of responsibility. When the IT Assessment is delivered as a standalone service engagement, IT Architecture Principles are not involved (created). When its is delivered as part of an EITA engagement, IT Architecture Principles are assessed with Business and User Needs. The gap analysis may indicate that the IT Architecture Principles should be modified or refined. Certainly, the implications need to be reconsidered. * The EITA Model consists of a strategic layer (EITA Principles and IT Strategy) and 7 sub-architectures. These sub-architectures may be combined or may be omitted, depending on the engagement situation. * The relationships in this diagram are generic interdependencies. The level of support and/or management varies from one service engagement to another. Also, the significance of an architecture varies according to the service engagement. In general the application and data sub-architectures are the gighest level and guide the technology and communications subarchitectures. In a very process-oriented environment, the application architecture is more significant. In a very information-oriented envir