Microsoft Architectural Frameworks Informational Session & Discussion Gurpreet S. Pall Sr. Director D&PE Architecture Strategy Microsoft Corporation.

Microsoft Architectural Microsoft Architectural FrameworkFrameworkssInformational Session & DiscussionInformational Session & Discussion

Gurpreet S. PallSr. DirectorD&PE Architecture StrategyMicrosoft Corporation

AgendaAgenda Why architecture, enterprise architectureWhy architecture, enterprise architecture Industry models Industry models Microsoft models Microsoft models Example - using models to deliver artifactsExample - using models to deliver artifacts Microsoft platform valueMicrosoft platform value Microsoft Operations FrameworkMicrosoft Operations Framework Microsoft Architectural Framework – proposalMicrosoft Architectural Framework – proposal

----------------------------------------------------------- ----------------------------------------------------------- Discussion – 15-20 minutesDiscussion – 15-20 minutes

The Need of ArchitectureThe Need of ArchitectureThe Winchester “Mystery” HouseThe Winchester “Mystery” House

38 years of construction – 147 builders 0 architects38 years of construction – 147 builders 0 architects 160 rooms – 40 bedrooms, 6 kitchens, 2 basements, 950 doors160 rooms – 40 bedrooms, 6 kitchens, 2 basements, 950 doors 65 doors to blank walls, 13 staircases abandoned, 24 skylights in floors65 doors to blank walls, 13 staircases abandoned, 24 skylights in floors No architectural blueprint existsNo architectural blueprint exists

Why Enterprise ArchitectureWhy Enterprise Architecture IT costs too muchIT costs too much Costs of managing complexityCosts of managing complexity Eliminate redundancyEliminate redundancy Growing IT ecosystemGrowing IT ecosystem Demanding rate of changeDemanding rate of change Need for info sharingNeed for info sharing Outsourcing (BPO)Outsourcing (BPO) Future-proofingFuture-proofing

If you don’t have strong architecture strategy, everyone does their own If you don’t have strong architecture strategy, everyone does their own thing and you end up with six kinds of servers and (software) thing and you end up with six kinds of servers and (software) platforms … you get silos of everything and that explodes your costs” platforms … you get silos of everything and that explodes your costs”

Andy Miller VP of Technical Architecture, Corporate ExpressAndy Miller VP of Technical Architecture, Corporate Express

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.

Definition of Enterprise ArchitectureDefinition of Enterprise Architecture

Does Your IT Architecture Look Like…Does Your IT Architecture Look Like…

(needed a) …blueprint to bring order to “spaghetti layer of (needed a) …blueprint to bring order to “spaghetti layer of applications, boxes and wires”applications, boxes and wires” Toby Redshaw VP of Strategy & Architecture MotorolaToby Redshaw VP of Strategy & Architecture Motorola

Why do I need a framework?Why do I need a framework?

ComplexityComplexity ScaleScale Other?Other?

Many Schools of ThoughtMany Schools of Thought

Industry modelsIndustry models Zachman FrameworkZachman Framework Meta – Enterprise ArchitectureMeta – Enterprise Architecture

Microsoft modelsMicrosoft models Microsoft solutions framework modelMicrosoft solutions framework model Software factoriesSoftware factories Module map & Motion MethodologyModule map & Motion Methodology

Using a model to deliver artifactsUsing a model to deliver artifacts Enterprise Architectural Space Organizing Table Enterprise Architectural Space Organizing Table

(EASOT)(EASOT)

Understanding the Zachman Understanding the Zachman Framework for EAFramework for EA

Scope (Ballpark) viewScope (Ballpark) view

Owners View (Enterprise Model) Owners View (Enterprise Model)

Designers View (System Model) Designers View (System Model)

Builder’s View (Technology Model) Builder’s View (Technology Model)

Out of Context View (Detailed Model) Out of Context View (Detailed Model)

Operational View (Functioning) Operational View (Functioning)

DataData(What)(What)

FunctionFunction(How)(How)

NetworkNetwork(Where)(Where)

PeoplePeople(Who)(Who)

TimeTime(When)(When)

MotivationMotivation(Why)(Why)

Enterprise Architecture Enterprise Architecture Meta GroupMeta Group

Enterprise Strategy

BusinessProcesses

Bus

ines

sB

usin

ess

Arc

hite

ctur

eA

rchi

tect

ure

Applications Information Infrastructure

App

licat

ion

App

licat

ion

Por

tfol

ioP

ortf

olio

Info

rmat

ion

Info

rmat

ion

Arc

hite

ctur

eA

rchi

tect

ure

Tec

hnol

ogy

Tec

hnol

ogy

Arc

hite

ctur

eA

rchi

tect

ure

The Meta Group Enterprise Architecture

Microsoft Solutions Framework Microsoft Solutions Framework Strata In Microsoft ModelStrata In Microsoft Model

ContextualContextual

ConceptualConceptual

LogicalLogical

PhysicalPhysical

Aimed at business Aimed at business executivesexecutives

Aimed at business Aimed at business process ownersprocess owners

Aimed at architects Aimed at architects and designersand designers

Aimed at designers Aimed at designers and developersand developers

Adding ViewsAdding Views

Business strategies & Business strategies & processesprocesses

Applications to facilitate Applications to facilitate business processbusiness process

Information needed to Information needed to manage businessmanage business

Technology to support Technology to support business & application business & application needsneeds



LogicalLogical

PhysicalPhysical

Bu

sin

ess

Vie

w

Ap

pli

cati

on

s V

iew

Info

rmat

ion

Vie

w

Tec

hn

olo

gy

Vie

w

Logical Stratum ModelsLogical Stratum Models What type of applications do we need to put in place to What type of applications do we need to put in place to

support the business processes?support the business processes? Who are the stakeholders in these applications?Who are the stakeholders in these applications? What does the normalized data model look like for these What does the normalized data model look like for these

applications?applications? Which application will create, read, update or delete data?Which application will create, read, update or delete data? What types of technology do we need to enable these What types of technology do we need to enable these

applications?applications? What is the distributed systems architecture going to look What is the distributed systems architecture going to look

like?like? What standards do we need to put in place?What standards do we need to put in place?

Logical Stratum ModelsLogical Stratum Models

LogicalLogicalApplicationApplicationArchitectureArchitecture

Logical DataLogical DataModelModel

DistributedDistributedSystemsSystems

ArchitectureArchitecture

• Entity Relationship Models• Class Models• XML Schemas

• Technology Services Portfolio• Distributed Systems Architecture Model

• CRUD Affinity Matrices

• Function/Application Affinity Matrices

ViewpointsViewpoints

AssessAssess DesigDesignn

ImplemenImplementt

PlanPlan RunRun

BusinessBusiness

ITIT

Strategic Strategic ObjectivesObjectives

Strategic Strategic ObjectivesObjectives

TechnologyTechnologyArchitectureArchitecture


Business Processes Business Processes and Entitiesand Entities


Logical Logical Data CenterData Center


Physical servers Physical servers and segmentsand segments

Services, Messages, Services, Messages, Contracts, SchedulesContracts, Schedules

Services, Messages, Services, Messages, Contracts, SchedulesContracts, Schedules

XML, Database, Classes,XML, Database, Classes,CodeCode

XML, Database, Classes,XML, Database, Classes,CodeCode

Manual ProceduresManual ProceduresManual ProceduresManual Procedures

DSLsDSLsPatternsPatternsProcessesProcessesFrameworksFrameworksComponentsComponentsAspectsAspectsTransformsTransformsConstraintsConstraints

Set Of Related View Points…Set Of Related View Points…and artifacts for Model Driven Developmentand artifacts for Model Driven Development

Business Business CapabilitiesCapabilities


Manual Manual ProceduresProcedures




ConstraintsConstraints

ReconciliationReconciliation

Services, Messages, Services, Messages, Applications, EndpointsApplications, Endpoints


XML, Projects, XML, Projects, DBs, Classes, CodeDBs, Classes, Code




Physical servers Physical servers & segments& segments

DeploymentDeploymentUnitsUnits


Abstraction/Abstraction/RefinementRefinement


packaged intopackaged into deployed ondeployed on





Merging ModelsMerging Models



LogicalLogical

PhysicalPhysical

BusinessBusiness ApplicationsApplications InformationInformation TechnologyTechnology















Physical servers Physical servers & segments& segments





packaged intopackaged into deployed ondeployed on





1. Develop Product / Service 2. Generate Demand

5. Collaboration

3. Fulfill Demand 4. Plan & Manage Enterprise

Customers Suppliers

Logistics Providers Financial Service Providers

Customer Facing Channel Partners

Enterprise

3.1. Provide Service

3.2. Advanced

Planning3.3. Procurement

3.4. Produce

Product

3.5. Logistics

3.3.1 Sourcing and Supplier Contract Management

3.3.3 Receiving of Indirect / Capital Goods and Services

3.3.2 Purchasing

Level 4Level 43. Fulfill Demand3. Fulfill Demand3.3 Procurement3.3 Procurement3.3.2 Purchasing3.3.2 Purchasing- Request- RequestResourcesResources - Create- Create PurchasePurchase RequisitionsRequisitions

Request Resources

Acquire/Purchase Resources

CreatePurchase

Requisitions

PurchaseDirect

Materials &Supplies

PurchaseIndirect

Materials

PurchaseOutsideVendor

Services

PurchaseCapitalGoods

ConsolidateApproved

Requisitionsby Supplier

CreatePurchase

Orders

Choose orDefault

Supplier forGoods

ManageRFI/RFQ/

RFPprocess

ManageOpen to

Buy/BlanketPOs

Verify/Negotiate

Price

ManageRequisition

ApprovaProcessl

PerformEncumbrance

Check

Track OpenPOs

Manage Suppliers

ManageSupplier

Relationships

TrackSupplier

Commitments

MaintainSupplierCatalog

ManagePurchase

ItemCatalog

CreateAuction Bids

ManageAutomaticReplenish-

ment

ManagePurchasing

Methods

Approve& ValidateContract

Payments

ManageBuyer

Performance

Provide SupplierSelf-Help

CreatePurchase

Requisitions

Request Resources

Module Map – Business CapabilitiesModule Map – Business Capabilities

EXAMPLE DECOMPOSITION

Motion starts with a high-level, objective view of Motion starts with a high-level, objective view of business, and allows capability decompositionbusiness, and allows capability decomposition

HIGH-LEVEL VIEW

DECOMPOSITION FRAMEWORK

Example - Model For Pattern Example - Model For Pattern IdentificationIdentification

Business Architecture

Integration Architecture

Application Architecture

Operational Architecture

Development Architecture

ExtendedPlatform

Add Interrogatives …Add Interrogatives …

Business Architecture

Integration Architecture

Application Architecture

Operational Architecture

Development Architecture

Purpose

(Why)

Data

(What)

Function

(How)

Timing

(When)

Network

(Where)

People

(Who)

Scorecard

(Test)

Add Roles …Add Roles …

* Non-Functional Requirements

Architecture FrameworkMicrosoft Confidential

-Build quality and quantitymetrics-Reports

Source code, compile timedependencies, test data,

results,

Compilers, build tools,system admin tools, test

tools

Operational metrics- Directory Implementation- Backup and recovery

Batch files, scripts, utilities

-Performance against SLA’s- Operational metrics

-Directory Design-Data storage design

-Monitoring and tuning-Remote management

Activity metricsSpecific data inputs,

processing and outputsTask and activity based

process models

%UtilizationDefect RatesCycle TimesStep Count

Process control dashboard Application process models

P&LDSO

Operational dashboardBusiness unit process

models

Balanced scorecardEVA, ROE, ROA

Enterprise level dashboard Enterprise process models

Development process,events and schedule

Fault management andrecovery

Event management

Activity specific events,collaborations and state

transitions

Process schedule, events,collaborations and state

transitions

Business unit masterschedule

Business events and cycles

Development team, systemadmin team, configuration

mgmt team

Development, test, andstaging environment

locations and accounts

User administration- Detailed network models- Network monitoring

Users, roles, permissions,security requirements

High level network modelsTraffic analysis

Specific roles, accounts,passwords and permissions

Activitiy specific devices andlocations

Process level actors withroles and permissions

Communication links anddevices needed for process

automation

Business unit org chart withroles, security permissions

and skill sets

Business unit logisticnetwork

(nodes and links)

Organizational unitsLocations where theenterprise operates

Asset management metrics-Repository-Dependency maps

Batch files, scripts, utilities-Restore knownconfigurations-Promote code


Logical and physical deviceinformation

-Quality and predictabilitymetrics-Reports

-Test Cases-Test Data-Repository

Automated test suites- integration- acceptance- performance

Test plan with schedule andtest cases

Development team,buildmaster, Config mgmt

team, QA mgmtTest environment

-Software developmentefficiency and effectiveness-Reports

- Repository- Test Data

- IDE- Bug Tracking Tools- Debugging Tools- Test Tools- Modeling tools

-Iteration plan with scheduleand features- Integration schedule

Users, roles and permissionsDevelopment environment

including integrationmachine(s)

Buildmaster

ConfigMgmt Engineer

System Engineer

SystemsArchitect

Process Worker

Process Owner

General Mgr

CEO

Test Engineer

Developer


Non functional requirements- detailed level

Non functional requirements- high level

-Activity objectives

Process control objectives

Operational goals andobjectives

- Strategic scope- Economic intent

- Change impact analysis- Rollbacks- Asset retention



BusinessArchitecture

OperationalArchitecture

DevelopmentArchitecture

A

D

C

B

O

N

M

L

P

Q

Scorecard(Test)

Data(What)

Function(How)

2 3 74

Timing(When)

People(Who)

Network(Where)

65

ViewpointsPurpose

(Why)

1

Unit TestsUser Adoption

Database instances , storedprocs, etc.

Source codeImplemetation units,

Executables

J1 realizationsIntegration testsInterfaces definedReuse

Tables, indexes, views,queries

Design level classes,component, subsystem and

QoS

I1 realizationsAcceptance testsApp SLA metricsReuse

Application level data models

Application level-Domain models-Analysis model

-H1 realizations-Cross application integrationtest-SLA metrics-Reuse

- Enterprise data models- Data distribution strategies

Enterprise level domainmodel and logical services

Executable(vertical / horizontal slices)

Design level collaborationmodels

(sequence and interaction)

Analysis levelcollaboration

model

Enterprise level collaborationmodels


Intuitive, easy to useexecutable interface relevant

to user needs

-Processes allocated toprocessors - Production environ- NFR* met

Visual designs, wire frames,site maps

Design level systemarchitecture- addresses-subnets-processors

Information architecture,interaction maps, story

boards, securityrequirements

Application level systemarchtecture- Nodes, devices- Links and segments- Processors

Enterprise level user profilesincluding demographics,

psychographics,technographics

Enterprise level systemarchitecture-Nodes-Links-Locations

Developer

Designer

Architect

EnterpriseArchitect

- Abbreviated use casedescriptions- Implement interfaces

System level use casesMechanismsNFR*

Application level use casesMechanismsNFR

Enterprise level use casesProcess refactoringsNFR*

ExecutableArchitecture

H

K

J

I

EE integration tests- Reuse- Transaction metrics

XML Schemas, HalfMaps,ETL, Batch feeds

Design level service,component, and subsystemmodels

- EE acceptance test- Performance against SLAs- Onboarding costs

Enterprise level data flowsand replication strategies

EAI (API, method, data, userinterface)- B2B integration-Global (GXA)- Message broker


Define business processmodels

-BPEL4WS-Rosetta PIPs

Roles, permissions, securityrequirements

- Integration NFR* met

Partners. customers,suppliers, system actors

-URI’s for all trading partners-Integration servers andfirewalls

Designer

EnterpriseArchitect

System level use cases

- Extended enterprise usecases- EAI use cases

IntegrationArchitecture

F

E

Unit tests, system testsProfiles, database instances,

stored procs

XLANG, source code,scripts, batch files,executables

XLANGExecutable vertical and

horizontal slicesUsers mapped to roles within

organizationsProcess mapped toprocessors, links, protocols

DeveloperAbbreviated use casedescriptionsImplement interfaces

G

Enterprise Architectural Space Organizing Table Enterprise Architectural Space Organizing Table

* Non-Functional Requirements

Architecture FrameworkMicrosoft Confidential


Source code, compile timedependencies, test data,

results,

Compilers, build tools,system admin tools, test

tools

Operational metrics- Directory Implementation- Backup and recovery

Batch files, scripts, utilities

-Performance against SLA’s- Operational metrics

-Directory Design-Data storage design

-Monitoring and tuning-Remote management

Activity metricsSpecific data inputs,

processing and outputsTask and activity based

process models

%UtilizationDefect RatesCycle TimesStep Count

Process control dashboard Application process models

P&LDSO

Operational dashboardBusiness unit process

models

Balanced scorecardEVA, ROE, ROA

Enterprise level dashboard Enterprise process models

Development process,events and schedule

Fault management andrecovery

Event management

Activity specific events,collaborations and state

transitions

Process schedule, events,collaborations and state

transitions

Business unit masterschedule

Business events and cycles

Development team, systemadmin team, configuration

mgmt team

Development, test, andstaging environment

locations and accounts

User administration- Detailed network models- Network monitoring


High level network modelsTraffic analysis

Specific roles, accounts,passwords and permissions

Activitiy specific devices andlocations

Process level actors withroles and permissions

Communication links anddevices needed for process

automation

Business unit org chart withroles, security permissions

and skill sets

Business unit logisticnetwork

(nodes and links)

Organizational unitsLocations where theenterprise operates

Asset management metrics-Repository-Dependency maps

Batch files, scripts, utilities-Restore knownconfigurations-Promote code


Logical and physical deviceinformation


-Test Cases-Test Data-Repository

Automated test suites- integration- acceptance- performance

Test plan with schedule andtest cases

Development team,buildmaster, Config mgmt

team, QA mgmtTest environment


- Repository- Test Data

- IDE- Bug Tracking Tools- Debugging Tools- Test Tools- Modeling tools

-Iteration plan with scheduleand features- Integration schedule

Users, roles and permissionsDevelopment environment

including integrationmachine(s)

Buildmaster

ConfigMgmt Engineer

System Engineer

SystemsArchitect

Process Worker

Process Owner

General Mgr

CEO

Test Engineer

Developer


Non functional requirements- detailed level

Non functional requirements- high level

-Activity objectives

Process control objectives

Operational goals andobjectives

- Strategic scope- Economic intent

- Change impact analysis- Rollbacks- Asset retention



BusinessArchitecture

OperationalArchitecture

DevelopmentArchitecture

A

D

C

B

O

N

M

L

P

Q

Scorecard(Test)

Data(What)

Function(How)

2 3 74

Timing(When)

People(Who)

Network(Where)

65

ViewpointsPurpose

(Why)

1

Unit TestsUser Adoption

Database instances , storedprocs, etc.

Source codeImplemetation units,

Executables

J1 realizationsIntegration testsInterfaces definedReuse

Tables, indexes, views,queries

Design level classes,component, subsystem and

QoS

I1 realizationsAcceptance testsApp SLA metricsReuse

Application level data models

Application level-Domain models-Analysis model

-H1 realizations-Cross application integrationtest-SLA metrics-Reuse

- Enterprise data models- Data distribution strategies

Enterprise level domainmodel and logical services

Executable(vertical / horizontal slices)



Analysis levelcollaboration

model

Enterprise level collaborationmodels


Intuitive, easy to useexecutable interface relevant

to user needs

-Processes allocated toprocessors - Production environ- NFR* met

Visual designs, wire frames,site maps

Design level systemarchitecture- addresses-subnets-processors

Information architecture,interaction maps, story

boards, securityrequirements

Application level systemarchtecture- Nodes, devices- Links and segments- Processors

Enterprise level user profilesincluding demographics,

psychographics,technographics

Enterprise level systemarchitecture-Nodes-Links-Locations

Developer

Designer

Architect

EnterpriseArchitect

- Abbreviated use casedescriptions- Implement interfaces

System level use casesMechanismsNFR*

Application level use casesMechanismsNFR

Enterprise level use casesProcess refactoringsNFR*

ExecutableArchitecture

H

K

J

I

EE integration tests- Reuse- Transaction metrics

XML Schemas, HalfMaps,ETL, Batch feeds

Design level service,component, and subsystemmodels

- EE acceptance test- Performance against SLAs- Onboarding costs

Enterprise level data flowsand replication strategies

EAI (API, method, data, userinterface)- B2B integration-Global (GXA)- Message broker


Define business processmodels

-BPEL4WS-Rosetta PIPs

Roles, permissions, securityrequirements

- Integration NFR* met

Partners. customers,suppliers, system actors

-URI’s for all trading partners-Integration servers andfirewalls

Designer

EnterpriseArchitect

System level use cases

- Extended enterprise usecases- EAI use cases

IntegrationArchitecture

F

E

Unit tests, system testsProfiles, database instances,

stored procs

XLANG, source code,scripts, batch files,executables

XLANGExecutable vertical and

horizontal slicesUsers mapped to roles within

organizationsProcess mapped toprocessors, links, protocols

DeveloperAbbreviated use casedescriptionsImplement interfaces

G

Enterprise Architectural Space Organizing Table Enterprise Architectural Space Organizing Table

Pattern ModelPattern Model

Integration TopologiesIntegration Topologies

MOF Process Model and SMF’sMOF Process Model and SMF’s

What Did We Learn?What Did We Learn?

Business and IT alignmentBusiness and IT alignment Stakeholders, viewpointsStakeholders, viewpoints Architects need to understand other views, Architects need to understand other views,

and translateand translate Strata – and need for detailsStrata – and need for details Domain specific needsDomain specific needs There is no end to detailThere is no end to detail Flexible – agileFlexible – agile Need to project views in the world of Need to project views in the world of

connected systemsconnected systems

Other EA concernsOther EA concerns

Journey vs. destinationJourney vs. destination Evolutionary vs. revolutionary approachEvolutionary vs. revolutionary approach IT – fixed asset or liquid assetIT – fixed asset or liquid asset Leading changeLeading change Cross-cutting concernsCross-cutting concerns Model and methodologyModel and methodology Your EA is uniqueYour EA is unique

So Why “YAF” yet another So Why “YAF” yet another framework?framework? Common context for conversationCommon context for conversation Context for delivering Context for delivering

guidance/artifactsguidance/artifacts Meta context for existing Meta context for existing

frameworksframeworks Ageless, timelessAgeless, timeless Demonstrate power of softwareDemonstrate power of software

Reconciling IT and BusinessReconciling IT and Business

ITIT BusinessBusiness

Business PracticeBusiness Practice

Business FunctionsBusiness FunctionsApplicationsApplications

InfrastructureInfrastructure

judgmentjudgment

insightinsight tradeoffstradeoffschangechange oversightoversight

strategystrategy

The Agile BusinessThe Agile Business

Business ApplicationsBusiness Applications




Business FunctionsBusiness FunctionsApplicationsApplications


CollaborateCollaborate

DecideDecide ActAct

InsightInsight OversightOversight

Business ImperativesBusiness Imperatives

CustomerCustomerIntimacyIntimacy

““Understanding”Understanding”

OperationalOperationalEfficiencyEfficiency

““Consistency”Consistency”

ValueValueChainChain

““Scale”Scale”

Core Core BusinessBusinessPracticesPractices““Sense & Act”Sense & Act”

ProductProductLeadershipLeadership

““Innovation”Innovation”

Top-line Software StrategiesTop-line Software Strategies

CustomerCustomerIntimacyIntimacy

““Understanding”Understanding”

OperationalOperationalEfficiencyEfficiency

““Consistency”Consistency”

ValueValueChainChain

““Scale”Scale”

Core Core BusinessBusinessPracticesPractices““Sense & Act”Sense & Act”

ProductProductLeadershipLeadership

““Innovation”Innovation”

AgileAgileInfrastructureInfrastructure

Software Software EnrichmentEnrichment

Information Information Supply ChainSupply Chain

Digital Customer Digital Customer RelationshipsRelationships

Digital Digital BusinessBusinessPracticesPractices

Business: objectives, functions, processes

Application: portfolio used in the organization

Information: data entities and relationships

Technology: software, hardware, etc.

Business ImperativesCore

BusinessPractice

“Sense & Act”


BusinessPractice

“Sense & Act”

ProductLeadership“Innovation”


OperationalEfficiency

“Consistency”


“Consistency”

ValueChain“Scale”


CustomerIntimacy

“Understanding”

CustomerIntimacy

“Understanding”

DigitalBusinessPractice

Software Strategies


Software Strategies

SoftwareEnrichment

SoftwareEnrichment

AgileInfrastructure

AgileInfrastructure

InformationSupplyChain


DigitalCustomer

Relationship

DigitalCustomer

Relationship

Microsoft Architectural FrameworkMicrosoft Architectural FrameworkTra

nsfo

rmatio

nTra

nsfo

rmatio

n

Business

Application

Information

Technology


Software Strategies


Software Strategies

SoftwareEnrichment

SoftwareEnrichment

AgileInfrastructure

AgileInfrastructure



DigitalCustomer

Relationship

DigitalCustomer

Relationship

Tra

nsfo

rmatio

nTra

nsfo

rmatio

n

RFIDRFIDEnabledEnabledSupplySupplyChainChain

ComplianceComplianceSystemsSystems

Integration & Integration & InteroperabilityInteroperability

Using WSUsing WS


BusinessPractice

“Sense & Act”


BusinessPractice

“Sense & Act”




“Consistency”


“Consistency”



CustomerIntimacy

“Understanding”

CustomerIntimacy

“Understanding”

Discussion Discussion

Have you adopted an architectural Have you adopted an architectural frameworks?frameworks?

Which one(s) and why?Which one(s) and why? Did you change/modify it?Did you change/modify it? Can you live with multiple frameworks from Can you live with multiple frameworks from

Microsoft?Microsoft? What do you think of MAF?What do you think of MAF? Is it easy to understand?Is it easy to understand? What would you change/add/remove?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.

Microsoft Architectural Frameworks Informational Session & Discussion Gurpreet S. Pall Sr. Director D&PE Architecture Strategy Microsoft Corporation.

Documents

need of architecture

architecture look

strong architecture

minutes slide

architectural blueprint

complexity costs

corporate express slide

artifacts example