- Количество слайдов: 40
Microsoft Architectural Frameworks Informational Session & Discussion Gurpreet S. Pall Sr. Director D&PE Architecture Strategy Microsoft Corporation
Agenda Why architecture, enterprise architecture l Industry models l Microsoft models l Example - using models to deliver artifacts l Microsoft platform value l Microsoft Operations Framework l Microsoft Architectural Framework – proposal -----------------------------l Discussion – 15 -20 minutes l
The Need of Architecture The Winchester “Mystery” House l l 38 years of construction – 147 builders 0 architects 160 rooms – 40 bedrooms, 6 kitchens, 2 basements, 950 doors 65 doors to blank walls, 13 staircases abandoned, 24 skylights in floors No architectural blueprint exists
Why Enterprise Architecture l IT costs too much Costs of managing complexity Eliminate redundancy Growing IT ecosystem Demanding rate of change Need for info sharing Outsourcing (BPO) l Future-proofing l l l If you don’t have strong architecture strategy, everyone does their own thing and you end up with six kinds of servers and (software) platforms … you get silos of everything and that explodes your costs” Andy Miller VP of Technical Architecture, Corporate Express
Definition of Enterprise Architecture The enterprise architecture is the organizing logic for a firm’s core business processes and IT capabilities captured in a set of principles, policies and technical choices to achieve the business standardization and integration requirements of the firm’s operating model.
Does Your IT Architecture Look Like… (needed a) …blueprint to bring order to “spaghetti layer of applications, boxes and wires” Toby Redshaw VP of Strategy & Architecture Motorola
Why do I need a framework? l l l Complexity Scale Other?
Many Schools of Thought l Industry models Ø Ø l Microsoft models Ø Ø Ø l Zachman Framework Meta – Enterprise Architecture Microsoft solutions framework model Software factories Module map & Motion Methodology Using a model to deliver artifacts Ø Enterprise Architectural Space Organizing Table (EASOT)
Understanding the Zachman Framework for EA Data Function Network People Time Motivation (What) (How) (Where) (Who) (When) (Why) Scope (Ballpark) view Owners View (Enterprise Model) Designers View (System Model) Builder’s View (Technology Model) Out of Context View (Detailed Model) Operational View (Functioning)
Enterprise Architecture Meta Group Information Architecture Technology Architecture Business Processe s Application Portfolio Business Architecture Enterprise Strategy Application s Information Infrastructu re The Meta Group Enterprise Architecture
Microsoft Solutions Framework Strata In Microsoft Model Contextual Aimed at business executives Conceptual Aimed at business process owners Logical Physical Aimed at architects and designers Aimed at designers and developers
Adding Views Business strategies & processes Conceptual Logical Physical Technology View Information View Applications View Business View Contextual Applications to facilitate business process Information needed to manage business Technology to support business & application needs
Logical Stratum Models l l l l What type of applications do we need to put in place to support the business processes? Who are the stakeholders in these applications? What does the normalized data model look like for these applications? Which application will create, read, update or delete data? What types of technology do we need to enable these applications? What is the distributed systems architecture going to look like? What standards do we need to put in place?
Logical Stratum Models • Entity Relationship Models • Class Models • XML Schemas • CRUD Affinity Matrices Application Architecture Logical Data Model Distributed Systems Architecture • Function/Application Affinity Matrices • Technology Services Portfolio • Distributed Systems Architecture Model
Viewpoints DSLs Patterns Design Assess Plan Processes Frameworks Strategic Components Business Aspects Objectives Business Processes Transforms and Entities Constraints Implement Run Manual Procedures Services, Messages, Contracts, Schedules XML, Database, Classes, Code IT Technology Architecture Logical Data Center Physical servers and segments
Set Of Related View Points… and artifacts for Model Driven Development Business Capabilities Reconciliation Manual Procedures Business Processes and Entities Technology Architecture Constraints Reconciliation Services, Messages, Applications, Endpoints Constraints Abstraction/ Refinement Physical servers & segments XML, Projects, DBs, Classes, Code packaged into Logical Data Center Deployment Units deployed on Abstraction/ Refinement
Merging Models Business Applications Business Capabilities Contextual Reconciliation Information Manual Procedures Business Processes Conceptual and Entities Technology Architecture Constraints Reconciliation Logical Services, Messages, Applications, Endpoints Constraints Abstraction/ Refinement Physical servers & segments XML, Projects, DBs, Classes, Code packaged into Logical Data Center Deployment Units deployed on Abstraction/ Refinement
Module Map – Business Capabilities Custome rs Customer Facing Channel Partners Enterpris e 1. Develop Product / Service Suppliers 2. Generate Demand 5. Collaboration 3. Fulfill Demand 4. Plan & Manage Enterprise 3. 1. Provide Service 3. 2. Advanced Planning 3. 3. Procurement 3. 3. 1 Sourcing and Supplier Contract Management 3. 3. 2 Purchasing Level 4 3. Fulfill Demand 3. 3 Procurement 3. 3. 2 Purchasing 3. 4. Produce - Request Product Resources - Create Purchase Requisitions Request Resources Create Purchase Requisitions 3. 3. 3 Receiving of Indirect / Capital Goods and Services 3. 5. Logistics Providers Financial Service Providers
Motion starts with a high-level, objective view of business, and allows capability decomposition HIGH-LEVEL VIEW DECOMPOSITION FRAMEWORK EXAMPLE DECOMPOSITION
Example - Model For Pattern Identification Business Architecture Integration Architecture Application Architecture Operational Architecture Development Architecture Extended Platform
Add Interrogatives … Purpose Data Function Timing Network People Scorecard (Why) (What) (How) (When) (Where) (Who) Business Architecture Integration Architecture Application Architecture Operational Architecture Development Architecture (Test)
Add Roles …
Enterprise Architectural Space Organizing Table
Enterprise Architectural Space Organizing Table
MOF Process Model and SMF’s
What Did We Learn? l l l l Business and IT alignment Stakeholders, viewpoints Architects need to understand other views, and translate Strata – and need for details Domain specific needs There is no end to detail Flexible – agile Need to project views in the world of connected systems
Other EA concerns l l l l Journey vs. destination Evolutionary vs. revolutionary approach IT – fixed asset or liquid asset Leading change Cross-cutting concerns Model and methodology Your EA is unique
So Why “YAF” yet another framework? l l l Common context for conversation Context for delivering guidance/artifacts Meta context for existing frameworks Ageless, timeless Demonstrate power of software
Reconciling IT and Business IT Business strategy judgment insight tradeoffs Business Practice oversight change Applications Infrastructure Business Functions
The Agile Business Decide Insight Act Collaborate Oversight Business Practice Applications Business Applications Functions Infrastructure
Business Imperatives “Consistency” Operational Efficiency Product Leadership “Understanding” Core Business Practices Customer Intimacy Value Chain “Sense & Act” “Innovation” “Scale”
Top-line Software Strategies Agile Infrastructure “Consistency” Operational Efficiency Product Leadership Digital Customer Relationships “Understanding” Core Digital Business Practices “Sense & Act” “Innovation” Software Enrichment Customer Intimacy Value Chain “Scale” Information Supply Chain
Microsoft Architectural Framework Business: Application: “Innovation” used in the Act” “Consistency” portfolio organization “Scale” “Sense & Digital Information: Software data entities and relationships Agile Business Supply Chain Enrichment Practice Technology: software, hardware, etc. Customer Intimacy “Understanding” Digital Customer Infrastructure Relationship Software Strategies Transformation Value Chain Business Imperatives objectives, functions, processes Core Operational Product Business Efficiency Leadership Practice
Value Chain “Scale” Business Imperatives Core Operational Product Business Efficiency Leadership Practice “Innovation” “Sense & Act” Business “Consistency” Customer Intimacy “Understanding” RFID Application Enabled Supply Chain Information Integration & Interoperability Using WS Technology Information Supply Chain Software Enrichment Digital Business Practice Agile Infrastructure Software Strategies Digital Customer Relationship Transformation Compliance Systems
Discussion l l l l Have you adopted an architectural frameworks? Which one(s) and why? Did you change/modify it? Can you live with multiple frameworks from Microsoft? What do you think of MAF? Is it easy to understand? What would you change/add/remove?
© 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.