微软 IT规划Enterprise Architecture.pptVIP

CHRAFTC.H. Robinson Architecture for TransformationEnterprise Architecture Overview Enterprise Architecture Much like an individual application, an Enterprise needs an “architecture” We define Enterprise Architecture to be: A desired future state for business and IT systems A common roadmap for analyzing and implementing business and technology change Includes all aspects of the organization, not just IT Enterprise Architecture For enterprise IT, our key goals are: Speed to Market Customer Experience Reliability Total Cost of ownership All key architectural decisions point back to these goals The right balance of trade-offs made Enterprise Architecture(Key design pillars) Unification Semantics, UI, Business Logic, Data Speed to Market, Customer Experience, TCO Composability New Applications and Services Speed to Market, Customer Experience Adaptability Scale on Demand, Planned resource usage Reliability, TCO, Customer Experience Autonomy Crisp Boundaries, Agility, Flexibility TCO, Speed to Market Approach Break into smaller distinct “Architectural Domains” Currently have defined 6 of them Each domain is a self contained area of interest Most likely different subject matter experts Most likely at different stages of maturity Based primarily on META (Gartner) Groups BAIT model Business, Application, Information, Technology Approach (Cont.) Some elements of other Enterprise Architecture frameworks Some new thinking around Business Architecture Updated to reflect new areas of focus and complexity Integration and Development Domains Architecture Domains Business Architecture Information Architecture Application Architecture Integration Architecture Infrastructure Architecture Development Architecture Business Architecture Business Goals and Objectives expressed via: Business Requirements Business Data Model Business Capabilities Modeled using “Microsoft Motion” A new Business Architecture Mapping Methodology Strong Executive support and participation Business Archi