Top Banner
Enterprise Architecture Toolkit Scenarios Scenarios 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.
27

Enterprise Architecture Toolkit Scenarios

May 13, 2015

Download

Technology

Mike Walker

The series of scenarios that the EATK is based on.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Enterprise Architecture Toolkit Scenarios

Enterprise Architecture ToolkitScenariosScenarios

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

Page 2: Enterprise Architecture Toolkit Scenarios

ScenariosScenarios1.1. Describing an Architecture with Current ToolsDescribing an Architecture with Current Tools

2.2. Building a Collaborative Solution Architecture DesignBuilding a Collaborative Solution Architecture Design

3.3. Extend Architecture Meta-Data into the Visio Modeling Extend Architecture Meta-Data into the Visio Modeling Environment Environment

4.4. Deriving to an Architecture with a series of Deriving to an Architecture with a series of Architecture Decisions Architecture Decisions

5.5. Architecture Management Architecture Management

1.1. Understanding Architecture Policy Understanding Architecture Policy

2.2. Managing an Architecture Life CycleManaging an Architecture Life Cycle

6.6. Navigate and Explore Approved IT Patterns Navigate and Explore Approved IT Patterns

7.7. Navigate and Explore Existing IT ArchitecturesNavigate and Explore Existing IT Architectures

8.8. Obtaining the information for IT Strategy ManagementObtaining the information for IT Strategy Management

9.9. Determining the Total Cost of Ownership of an Determining the Total Cost of Ownership of an ArchitectureArchitecture

10.10.Manage and publishing of Principles, Policies and Manage and publishing of Principles, Policies and StandardsStandards

Page 3: Enterprise Architecture Toolkit Scenarios

1. Describing an Architecture with1. Describing an Architecture withCurrent ToolsCurrent Tools

GoalsGoalsLeverage current investmentsLeverage current investments

Reduce training costsReduce training costs

Reduce the learning curveReduce the learning curve

Increase productivityIncrease productivity

PersonasPersonasEnterprise Architect – Oversight of the architecture and reviewEnterprise Architect – Oversight of the architecture and review

Solution Architect – Owner and designer of architectureSolution Architect – Owner and designer of architecture

Domain Architects – Contributes and reviews the architectureDomain Architects – Contributes and reviews the architecture

Project Manager – Assigns work to the solution architectProject Manager – Assigns work to the solution architect

Desired OutcomeDesired OutcomeMeta models will allow for free flow of information between Meta models will allow for free flow of information between documents and other toolingdocuments and other tooling

Information will be saved to Repository where it can be used in Information will be saved to Repository where it can be used in the futurethe future

Extensions will save the architect time in researchExtensions will save the architect time in research

Systematic reuse of patternsSystematic reuse of patterns3

Page 4: Enterprise Architecture Toolkit Scenarios

Describing an Architecture withDescribing an Architecture withCurrent Tools - ProcessCurrent Tools - Process

SolutionArchitect

PM

Design Build | Stabilize| Deploy

Envision

SDLCSDLC

2. Open MS Word.

4. Enter Architecture Meta Data

5. Start Architecture Scoping

1. Allocates

6. Document Architecture w/ Current info 7. Click on Arch Patterns Ribbon

8. Research areas of interest to current effort

9. Select appropriate pattern

13. Design additional architecture components

12. Review / Modify and add additional information

11. Import pattern by Double-Clicking

10. Select document region in which to import

14. Get feedback on other architecture domains

15. Prepare for architecture review

3. Open Arch Template

Page 5: Enterprise Architecture Toolkit Scenarios

Describing Architectures with Describing Architectures with Current ToolsCurrent Tools

5

Page 6: Enterprise Architecture Toolkit Scenarios

2. Building a Collaborative Solution2. Building a Collaborative SolutionArchitecture DesignArchitecture Design

GoalsGoalsFoster proactive communication with architectsFoster proactive communication with architects

Streamline communicationsStreamline communications

Reduce complexity of collaborationReduce complexity of collaboration

PersonasPersonasSolution Architect – Owner and designer of architectureSolution Architect – Owner and designer of architecture

Network and Hardware Architects – Contributes and reviews the Network and Hardware Architects – Contributes and reviews the architecturearchitecture

Project Manager – Enters in architect resources information into Project Manager – Enters in architect resources information into PPM toolPPM tool

Desired OutcomeDesired OutcomeFoster better communication and community with architectsFoster better communication and community with architects

Improve overall quality of the architecturesImprove overall quality of the architectures

Solve issues early in the process rather than laterSolve issues early in the process rather than later

Reduce risk in architecture efforts by identifying potential Reduce risk in architecture efforts by identifying potential impacts of other domains of architecturesimpacts of other domains of architectures

Log communications effectivelyLog communications effectively

Reduce issues at Architecture Review Board functionsReduce issues at Architecture Review Board functions6

Page 7: Enterprise Architecture Toolkit Scenarios

2. Building a Collaborative Solution2. Building a Collaborative SolutionArchitecture Design - ProcessArchitecture Design - Process

SolutionArchitect

PM

DesignEnvision

SDLCSDLC

2. Open MS Word.

4. Enter Architecture Meta Data

5. Start Architecture Scoping

6. Document Architecture w/ Current info

7. Architect starts to query about other impacts

8. Selects the Architect Finder Ribbon

12. SA asks where the application should be hosted based on criteria

11. Office Communicator appears with an IM to HA

10. SA clicks on the IM for the Hardware Architect (HA)

9. Architect Finder Populates task pane with all the architects assigned

13. HA answers and is sent a workflow request to modify the architecture

14. Additional information is sent to the HA’s My Site for the SA

3. Open Arch Template

1. Assigns architects to project in PPM tool

15. SA reviews and modifies architecture

16. Process is repeated with other architects.Repeat steps 8 - 15

Page 8: Enterprise Architecture Toolkit Scenarios

2. Building a Collaborative Solution2. Building a Collaborative SolutionArchitecture DesignArchitecture Design

8

Page 9: Enterprise Architecture Toolkit Scenarios

3. Extend Visio Models3. Extend Visio Models

GoalsGoalsMake Visio shapes into more meaningful modelsMake Visio shapes into more meaningful models

Use a low cost solution for architecture effortsUse a low cost solution for architecture efforts

Extend the Visio environmentExtend the Visio environment

Surface rich information from the Architecture Metadata Surface rich information from the Architecture Metadata RepositoryRepository

PersonasPersonasSolution Architect – Owner and designer of architectureSolution Architect – Owner and designer of architecture

Desired OutcomeDesired OutcomeProvide models that are more meaningful to reviewers and other Provide models that are more meaningful to reviewers and other architects and developersarchitects and developers

Lower the cost of ownership on architecture modelingLower the cost of ownership on architecture modeling

Decrease the learning barrier while increasing the quality of Decrease the learning barrier while increasing the quality of architecture modelingarchitecture modeling

Reuse of patterns and information stored in the AMRReuse of patterns and information stored in the AMR

Reduce training of new toolsReduce training of new tools9

Page 10: Enterprise Architecture Toolkit Scenarios

2. Extend Visio Models - Process2. Extend Visio Models - Process

SolutionArchitect

Design

SDLCSDLC

2. Open MS Visio

4. Copy Server Shapes to the canvas

5. Open External Links Pane

6. Select the “Approved DMZ Hardware List”

7. Review list of selections that may be appropriate for the solution 11. Import

information into System Architecture Document

10. Save diagram on to portal share

9. Repeat as necessary

8. Select suitable hardware information and drag it onto the shape

3. Select stencils

Page 11: Enterprise Architecture Toolkit Scenarios

4. Deriving to a Series of 4. Deriving to a Series of Architecture DecisionsArchitecture Decisions

GoalsGoalsProvide a tool to address the journey to an architectureProvide a tool to address the journey to an architecture

Provide process guidance on deriving to decisionsProvide process guidance on deriving to decisions

Provide information to architects on how architecture decisions Provide information to architects on how architecture decisions were madewere made

Increase architecture awareness by understanding the decisions Increase architecture awareness by understanding the decisions mademade

PersonasPersonasSolution Architect – Creator of architecture decisions Solution Architect – Creator of architecture decisions

Domain Architects – Contributes and reviews the architecture Domain Architects – Contributes and reviews the architecture decisionsdecisions

Desired OutcomeDesired OutcomeArchitecture decisions will have a formalized and repeatable Architecture decisions will have a formalized and repeatable process process

Future decisions will be easier to make as there will be a Future decisions will be easier to make as there will be a knowledge baseknowledge base

Reduce time and effort of decisionsReduce time and effort of decisions

Architectural risk will decrease as decisions will be linked with Architectural risk will decrease as decisions will be linked with non-functional requirements non-functional requirements

Full transparency of decisions will empower architects in the Full transparency of decisions will empower architects in the futurefuture

11

Page 12: Enterprise Architecture Toolkit Scenarios

4. Deriving to a Series of 4. Deriving to a Series of Architecture DecisionsArchitecture Decisions

12

Page 13: Enterprise Architecture Toolkit Scenarios

5. Architecture Management5. Architecture ManagementGoalsGoals

Manage the process of architecture workManage the process of architecture work

Provide an online inventory of existing architecture descriptionsProvide an online inventory of existing architecture descriptions

Set policy on how architectures should be usedSet policy on how architectures should be used

Provides ways to visualize inventoried architectures Provides ways to visualize inventoried architectures

PersonasPersonasEnterprise Architect – Architecture Policy, Administration, Enterprise Architect – Architecture Policy, Administration, Strategy Development based on ArchitecturesStrategy Development based on Architectures

Solution Architect – Creator of architecture descriptionsSolution Architect – Creator of architecture descriptions

Domain Architects – Policy and standards stewards, Creators of Domain Architects – Policy and standards stewards, Creators of architecture descriptionsarchitecture descriptions

Desired OutcomeDesired OutcomeFoster systematic reuse of existing architectures to lead to Foster systematic reuse of existing architectures to lead to enabling SOA and S+S activitiesenabling SOA and S+S activities

Reduce complexity through Policy and Standards by showing Reduce complexity through Policy and Standards by showing how and when to use an architecturehow and when to use an architecture

Increased awareness of how to leverage or change an Increased awareness of how to leverage or change an architecturearchitecture

Accurate technology strategy planning and CIO awarenessAccurate technology strategy planning and CIO awareness13

Page 14: Enterprise Architecture Toolkit Scenarios

5. Architecture Management5. Architecture Management

14

Page 15: Enterprise Architecture Toolkit Scenarios

6. Navigate and Explore Approved6. Navigate and Explore ApprovedIT PatternsIT Patterns

GoalsGoalsIncrease understanding of how patterns should be usedIncrease understanding of how patterns should be used

Increase reusability of approved patterns in the enterpriseIncrease reusability of approved patterns in the enterprise

Show interdependent software solutions or existing Show interdependent software solutions or existing architecturesarchitectures

Present information in context to the consumer of the patternsPresent information in context to the consumer of the patterns

PersonasPersonasEnterprise Architect – Consumer and contributor of patternsEnterprise Architect – Consumer and contributor of patterns

Solution Architect – Consumer of patternsSolution Architect – Consumer of patterns

Domain Architects – Consumer and contributor of patternsDomain Architects – Consumer and contributor of patterns

Desired OutcomeDesired OutcomeArchitects will have better aligned architectures with the overall Architects will have better aligned architectures with the overall vision of ITvision of IT

Patterns will save time and effort on solution workPatterns will save time and effort on solution work

Elimination of duplicate functionality will reduce risk and cost to Elimination of duplicate functionality will reduce risk and cost to ITIT

Process to create and enhance patterns will emerge to further Process to create and enhance patterns will emerge to further streamline ITstreamline IT

15

Page 16: Enterprise Architecture Toolkit Scenarios

6. Navigate and Explore Approved6. Navigate and Explore ApprovedIT PatternsIT Patterns

16

Page 17: Enterprise Architecture Toolkit Scenarios

7. Navigate and Explore Approved7. Navigate and Explore ApprovedIT AssetsIT Assets

GoalsGoalsIncrease understanding of existing architecturesIncrease understanding of existing architectures

Increase reusability existing architectures in the enterpriseIncrease reusability existing architectures in the enterprise

Show interdependent software solutions or existing Show interdependent software solutions or existing architecturesarchitectures

Present information in context to the consumer of the assetsPresent information in context to the consumer of the assets

PersonasPersonasEnterprise Architect – Classifies and sets policy around Enterprise Architect – Classifies and sets policy around architecturesarchitectures

Solution Architect – Consumer and creators of IT Asset Solution Architect – Consumer and creators of IT Asset architecture descriptionsarchitecture descriptions

Desired OutcomeDesired OutcomeArchitects will have better aligned architectures with the overall Architects will have better aligned architectures with the overall vision of ITvision of IT

Understanding trade-offs and decision criteria on existing Understanding trade-offs and decision criteria on existing architectures will save time and effort on solution workarchitectures will save time and effort on solution work

Elimination of duplicate functionality will reduce risk and cost to Elimination of duplicate functionality will reduce risk and cost to ITIT

Support for architecture efforts such as S+S or SOASupport for architecture efforts such as S+S or SOA

17

Page 18: Enterprise Architecture Toolkit Scenarios

7. Navigate and Explore 7. Navigate and Explore Architectures Architectures

SolutionArchitect

MaintainMaintain

1. Navigates to EA Portal

2. Click on Architecture Mgmt Link

3. User presented with listing of architectures

4. User clicks on architecture name

5. Architecture detail page opens

6. User clicks on Lifecycle link

7. Architecture lifecycle information is presented

Page 19: Enterprise Architecture Toolkit Scenarios

8. Obtain IT Strategy Information8. Obtain IT Strategy Information

GoalsGoalsIncrease the visibility into IT environmentIncrease the visibility into IT environment

Link architecture descriptions with other enterprise processesLink architecture descriptions with other enterprise processes

Expose architecture information dashboards for enterprise Expose architecture information dashboards for enterprise architects architects

Provide a repository that can be used to base decisions off of. Provide a repository that can be used to base decisions off of.

PersonasPersonasEnterprise Architect – Consumer of informationEnterprise Architect – Consumer of information

Desired OutcomeDesired OutcomeEnterprise Architects will leverage information to create more Enterprise Architects will leverage information to create more accurate future state architecturesaccurate future state architectures

Policies and life cycles will surface usage patterns that will aid in Policies and life cycles will surface usage patterns that will aid in recycling or termination of a series of architecturesrecycling or termination of a series of architectures

Operational impacts can be seen and correlated with an IT Operational impacts can be seen and correlated with an IT architecturearchitecture

Application Portfolio Management and Project Portfolio Application Portfolio Management and Project Portfolio Management links provide ties into the portfolio planning Management links provide ties into the portfolio planning processesprocesses

Streamlining of IT Service lines can be achievedStreamlining of IT Service lines can be achieved

19

Page 20: Enterprise Architecture Toolkit Scenarios

8. Obtain IT Strategy Information8. Obtain IT Strategy Information

20

Page 21: Enterprise Architecture Toolkit Scenarios

10. Manage Principles, Policies10. Manage Principles, Policiesand Standardsand Standards

GoalsGoalsProvide mechanisms to create Principles, Policies and Standards Provide mechanisms to create Principles, Policies and Standards (PPS)(PPS)

Create ways to correlate PPS with architecture decisions, Create ways to correlate PPS with architecture decisions, architectures, patterns and other IT related assetsarchitectures, patterns and other IT related assets

Surface information into analytic toolsSurface information into analytic tools

PersonasPersonasCxO– Consumers and Reviewers of informationCxO– Consumers and Reviewers of information

Enterprise Architects – Creators and Facilitators of PPSEnterprise Architects – Creators and Facilitators of PPS

Domain Architects - Creators of PPSDomain Architects - Creators of PPS

Solution Architects - Consumers of informationSolution Architects - Consumers of information

Desired OutcomeDesired OutcomeArchitects understand why IT decisionsArchitects understand why IT decisions

PPS provide alignment with CxO and business strategiesPPS provide alignment with CxO and business strategies

Solving complexity and confusion with traceability of Solving complexity and confusion with traceability of architecture workarchitecture work

21

Page 22: Enterprise Architecture Toolkit Scenarios

IT StandardsIT Standards

Enterprise Architect

1. Navigates to EA Portal

2. Click on IT Standards Link

3. User presented with listing of standards

4. User clicks on standard

5. Architecture detail page opens

6. User modifies the guidance

Page 23: Enterprise Architecture Toolkit Scenarios

10. Manage Principles, Policies10. Manage Principles, Policiesand Standardsand Standards

23

Page 24: Enterprise Architecture Toolkit Scenarios

9. Determining the Total Cost 9. Determining the Total Cost of Ownership of Architecturesof Ownership of Architectures

GoalsGoalsProvide reports that show the various costs of an architectureProvide reports that show the various costs of an architecture

Span across Architecture, Business Architecture, Service Span across Architecture, Business Architecture, Service Management, APM, PPM and development to realize total cost Management, APM, PPM and development to realize total cost of ownershipof ownership

PersonasPersonasEnterprise Architect – Consumer of informationEnterprise Architect – Consumer of information

CxO – Consumer of informationCxO – Consumer of information

Desired OutcomeDesired OutcomeProvide CxO’s real-time metrics on the financial health of their IT Provide CxO’s real-time metrics on the financial health of their IT environmentenvironment

Increase awareness of the cost of an architecture(s)Increase awareness of the cost of an architecture(s)

Understand the impacts of dependencies of architecturesUnderstand the impacts of dependencies of architectures

Focus resources on problem areasFocus resources on problem areas

24

Page 25: Enterprise Architecture Toolkit Scenarios

CIO

1. Navigates to EA Portal

2. Click on IT Reports > Cost of My Architectures

3. User enters the “ATM” search criteria

4. Report is generated with the total cost of the ATM Architecture

Results Pane

Search Web Part

Architecture Drop Down

SearchSearch

xCalculate Dependencies Operational Tables

Operational Tables

DevelopmentTables

DevelopmentTables

Service Management

Tables

Service Management

Tables

Mock TablesProject Server

Total Cost of OwnershipTotal Cost of Ownership

Page 26: Enterprise Architecture Toolkit Scenarios

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 27: Enterprise Architecture Toolkit Scenarios

© 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.