49
Enterprise Architecture Toolkit Changing the Role of Architecture Changing the Role of Architecture Documents Documents Mike Walker Mike Walker http://blogs.msdn.com/MikeWalker Global Architecture Strategist Global Architecture Strategist Platform Architecture Team Platform Architecture Team Microsoft Corp. Microsoft Corp.

Improving on How Architectures are Described

Embed Size (px)

DESCRIPTION

The EATK has automated architecture description mechinisms built into Microsoft Word. With hooks into a metadata repository and process integration it solves traditional problems with existing tooling.

Citation preview

Page 1: Improving on How Architectures are Described

Enterprise Architecture ToolkitChanging the Role of Architecture Changing the Role of Architecture DocumentsDocuments

Mike WalkerMike Walkerhttp://blogs.msdn.com/MikeWalker Global Architecture Strategist Global Architecture Strategist Platform Architecture TeamPlatform Architecture TeamMicrosoft Corp.Microsoft Corp.

Page 2: Improving on How Architectures are Described

What are We Talking About?What are We Talking About?

Fundamentally improve how architectures are described, consumed and maintained

Page 3: Improving on How Architectures are Described

ChallengesChallenges

Page 4: Improving on How Architectures are Described

ChallengesChallenges

Complexity

Page 5: Improving on How Architectures are Described

ChallengesChallenges

Tooling

Complexity

Page 6: Improving on How Architectures are Described

Complexity Complexity

Page 7: Improving on How Architectures are Described

Complexity Complexity

Document Overload

Page 8: Improving on How Architectures are Described

Documentation OverloadDocumentation Overload

Page 9: Improving on How Architectures are Described

Complexity Complexity

Document Overload

Information Drain

Page 10: Improving on How Architectures are Described

Information DrainInformation Drain

Page 11: Improving on How Architectures are Described

Information Grave YardInformation Grave Yard

Page 12: Improving on How Architectures are Described

Information Grave YardInformation Grave Yard

Scenario: File Share Grave Yard Scenario: File Share Grave Yard

Architecture

Document

Architecture

Document

Server File Share

Page 13: Improving on How Architectures are Described

Complexity Complexity

Document Overload

Information Drain

Suboptimal Process

Page 14: Improving on How Architectures are Described

Suboptimal ProcessSuboptimal Process

Page 15: Improving on How Architectures are Described

Suboptimal ProcessSuboptimal Process

Page 16: Improving on How Architectures are Described

Suboptimal ProcessSuboptimal Process

Compartmentalized Information

Page 17: Improving on How Architectures are Described

Suboptimal ProcessSuboptimal Process

Compartmentalized Information

One Man Army Syndrome

Page 18: Improving on How Architectures are Described

ChallengesChallenges

Complexity

Page 19: Improving on How Architectures are Described

Tooling Challenges Tooling Challenges

Page 20: Improving on How Architectures are Described

Tooling Challenges Tooling Challenges

Tool Landscape

Page 21: Improving on How Architectures are Described

Tool LandscapeTool Landscape

Page 22: Improving on How Architectures are Described

Tool LandscapeTool Landscape

EA Tools are Niche and EA Tools are Niche and FragmentedFragmented

Source: Source: http://www.enterprise-architecture.info/EA_Tools.htm

Page 23: Improving on How Architectures are Described

Enterprise Architecture ToolkitEnterprise Architecture ToolkitSystem Architecture DocumentSystem Architecture Document

Page 24: Improving on How Architectures are Described

ObjectivesObjectives

Page 25: Improving on How Architectures are Described

ObjectivesObjectives

Leverage Existing Tools

Empower Architects

Foster Transparency

Page 26: Improving on How Architectures are Described

ObjectivesObjectives

Empower Architects

Foster Transparency

Page 27: Improving on How Architectures are Described

Leverage Existing ToolsLeverage Existing Tools

Page 28: Improving on How Architectures are Described

Leverage Existing ToolsLeverage Existing Tools

Page 29: Improving on How Architectures are Described

Leverage Existing ToolsLeverage Existing Tools

Page 30: Improving on How Architectures are Described

Leverage Existing ToolsLeverage Existing Tools

System Architecture Document Template

Page 31: Improving on How Architectures are Described

Leverage Existing ToolsLeverage Existing Tools

System Architecture Document Template

Extend the User Interface

Page 32: Improving on How Architectures are Described

Leverage Existing ToolsLeverage Existing Tools

System Architecture Document Template

Extend the User Interface

Support EA Tasks

Page 33: Improving on How Architectures are Described

Leverage Existing ToolsLeverage Existing Tools

Page 34: Improving on How Architectures are Described

ObjectivesObjectives

Leverage Existing Tools

Foster Transparency

Page 35: Improving on How Architectures are Described

Empower ArchitectsEmpower Architects

Page 36: Improving on How Architectures are Described

Empower ArchitectsEmpower Architects

Page 37: Improving on How Architectures are Described

Empower ArchitectsEmpower Architects

Collaborative Tools

Page 38: Improving on How Architectures are Described

Empower ArchitectsEmpower Architects

Collaborative Tools

Enable a Proactive Architecture Process

Page 39: Improving on How Architectures are Described

Empower ArchitectsEmpower Architects

Collaborative Tools

Enable a Proactive Architecture Process

Support Architecture Decision Making

Page 40: Improving on How Architectures are Described

Empower ArchitectsEmpower Architects

Page 41: Improving on How Architectures are Described

ObjectivesObjectives

Leverage Existing Tools

Empower Architects

Page 42: Improving on How Architectures are Described

Foster TransparencyFoster Transparency

Page 43: Improving on How Architectures are Described

Foster TransparencyFoster Transparency

Page 44: Improving on How Architectures are Described

Foster TransparencyFoster Transparency

Views into Existing Assets

Page 45: Improving on How Architectures are Described

Foster TransparencyFoster Transparency

Views into Existing Assets

Workflow Hosted

Page 46: Improving on How Architectures are Described

Foster TransparencyFoster Transparency

Views into Existing Assets

Workflow Hosted

Decision Making Templates

Page 47: Improving on How Architectures are Described

More InformationMore Information

Page 48: Improving on How Architectures are Described

More InformationMore Information

Microsoft Architecture Portalhttp://msdn.microsoft.com/architecture

Microsoft Enterprise Architecture Portalhttp://msdn.microsoft.com/architecture/EA

Mike Walker’s Bloghttp://blogs.msdn.com/MikeWalker

Microsoft Architecture Portalhttp://msdn.microsoft.com/architecture

Microsoft Enterprise Architecture Portalhttp://msdn.microsoft.com/architecture/EA

Mike Walker’s Bloghttp://blogs.msdn.com/MikeWalker

Page 49: Improving on How Architectures are Described

© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the

date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.