Your SlideShare is downloading. ×
Enterprise Architecture Toolkit Scenarios
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Enterprise Architecture Toolkit Scenarios

4,285
views

Published on

The series of scenarios that the EATK is based on.

The series of scenarios that the EATK is based on.

Published in: Technology, Design, Business

0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
4,285
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
367
Comments
0
Likes
5
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • April 8-9 2004 © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Windows Embedded Design Review
  • Transcript

    • 1. Enterprise Architecture Toolkit Scenarios Mike Walker http://blogs.msdn.com/MikeWalker Global Architecture Strategist Platform Architecture Team Microsoft Corp.
    • 2. Scenarios
        • Describing an Architecture with Current Tools
        • Building a Collaborative Solution Architecture Design
        • Extend Architecture Meta-Data into the Visio Modeling Environment
        • Deriving to an Architecture with a series of Architecture Decisions
        • Architecture Management
          • Understanding Architecture Policy
          • Managing an Architecture Life Cycle
        • Navigate and Explore Approved IT Patterns
        • Navigate and Explore Existing IT Architectures
        • Obtaining the information for IT Strategy Management
        • Determining the Total Cost of Ownership of an Architecture
        • Manage and publishing of Principles, Policies and Standards
    • 3. 1. Describing an Architecture with Current Tools
      • Goals
        • Leverage current investments
        • Reduce training costs
        • Reduce the learning curve
        • Increase productivity
      • Personas
        • Enterprise Architect – Oversight of the architecture and review
        • Solution Architect – Owner and designer of architecture
        • Domain Architects – Contributes and reviews the architecture
        • Project Manager – Assigns work to the solution architect
      • Desired Outcome
        • Meta models will allow for free flow of information between documents and other tooling
        • Information will be saved to Repository where it can be used in the future
        • Extensions will save the architect time in research
        • Systematic reuse of patterns
    • 4. Describing an Architecture with Current Tools - Process 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 Solution Architect PM Design Build | Stabilize| Deploy Envision SDLC
    • 5. Describing Architectures with Current Tools
    • 6. 2. Building a Collaborative Solution Architecture Design
      • Goals
        • Foster proactive communication with architects
        • Streamline communications
        • Reduce complexity of collaboration
      • Personas
        • Solution Architect – Owner and designer of architecture
        • Network and Hardware Architects – Contributes and reviews the architecture
        • Project Manager – Enters in architect resources information into PPM tool
      • Desired Outcome
        • Foster better communication and community with architects
        • Improve overall quality of the architectures
        • Solve issues early in the process rather than later
        • Reduce risk in architecture efforts by identifying potential impacts of other domains of architectures
        • Log communications effectively
        • Reduce issues at Architecture Review Board functions
    • 7. 2. Building a Collaborative Solution Architecture Design - Process 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 Solution Architect PM Design Envision SDLC
    • 8. 2. Building a Collaborative Solution Architecture Design
    • 9. 3. Extend Visio Models
      • Goals
        • Make Visio shapes into more meaningful models
        • Use a low cost solution for architecture efforts
        • Extend the Visio environment
        • Surface rich information from the Architecture Metadata Repository
      • Personas
        • Solution Architect – Owner and designer of architecture
      • Desired Outcome
        • Provide models that are more meaningful to reviewers and other architects and developers
        • Lower the cost of ownership on architecture modeling
        • Decrease the learning barrier while increasing the quality of architecture modeling
        • Reuse of patterns and information stored in the AMR
        • Reduce training of new tools
    • 10. 2. Extend Visio Models - Process 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 Solution Architect Design SDLC
    • 11. 4. Deriving to a Series of Architecture Decisions
      • Goals
        • Provide a tool to address the journey to an architecture
        • Provide process guidance on deriving to decisions
        • Provide information to architects on how architecture decisions were made
        • Increase architecture awareness by understanding the decisions made
      • Personas
        • Solution Architect – Creator of architecture decisions
        • Domain Architects – Contributes and reviews the architecture decisions
      • Desired Outcome
        • Architecture decisions will have a formalized and repeatable process
        • Future decisions will be easier to make as there will be a knowledge base
        • Reduce time and effort of decisions
        • Architectural risk will decrease as decisions will be linked with non-functional requirements
        • Full transparency of decisions will empower architects in the future
    • 12. 4. Deriving to a Series of Architecture Decisions
    • 13. 5. Architecture Management
      • Goals
        • Manage the process of architecture work
        • Provide an online inventory of existing architecture descriptions
        • Set policy on how architectures should be used
        • Provides ways to visualize inventoried architectures
      • Personas
        • Enterprise Architect – Architecture Policy, Administration, Strategy Development based on Architectures
        • Solution Architect – Creator of architecture descriptions
        • Domain Architects – Policy and standards stewards, Creators of architecture descriptions
      • Desired Outcome
        • Foster systematic reuse of existing architectures to lead to enabling SOA and S+S activities
        • Reduce complexity through Policy and Standards by showing how and when to use an architecture
        • Increased awareness of how to leverage or change an architecture
        • Accurate technology strategy planning and CIO awareness
    • 14. 5. Architecture Management
    • 15. 6. Navigate and Explore Approved IT Patterns
      • Goals
        • Increase understanding of how patterns should be used
        • Increase reusability of approved patterns in the enterprise
        • Show interdependent software solutions or existing architectures
        • Present information in context to the consumer of the patterns
      • Personas
        • Enterprise Architect – Consumer and contributor of patterns
        • Solution Architect – Consumer of patterns
        • Domain Architects – Consumer and contributor of patterns
      • Desired Outcome
        • Architects will have better aligned architectures with the overall vision of IT
        • Patterns will save time and effort on solution work
        • Elimination of duplicate functionality will reduce risk and cost to IT
        • Process to create and enhance patterns will emerge to further streamline IT
    • 16. 6. Navigate and Explore Approved IT Patterns
    • 17. 7. Navigate and Explore Approved IT Assets
      • Goals
        • Increase understanding of existing architectures
        • Increase reusability existing architectures in the enterprise
        • Show interdependent software solutions or existing architectures
        • Present information in context to the consumer of the assets
      • Personas
        • Enterprise Architect – Classifies and sets policy around architectures
        • Solution Architect – Consumer and creators of IT Asset architecture descriptions
      • Desired Outcome
        • Architects will have better aligned architectures with the overall vision of IT
        • Understanding trade-offs and decision criteria on existing architectures will save time and effort on solution work
        • Elimination of duplicate functionality will reduce risk and cost to IT
        • Support for architecture efforts such as S+S or SOA
    • 18. 7. Navigate and Explore Architectures Maintain 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 Solution Architect
    • 19. 8. Obtain IT Strategy Information
      • Goals
        • Increase the visibility into IT environment
        • Link architecture descriptions with other enterprise processes
        • Expose architecture information dashboards for enterprise architects
        • Provide a repository that can be used to base decisions off of.
      • Personas
        • Enterprise Architect – Consumer of information
      • Desired Outcome
        • Enterprise Architects will leverage information to create more accurate future state architectures
        • Policies and life cycles will surface usage patterns that will aid in recycling or termination of a series of architectures
        • Operational impacts can be seen and correlated with an IT architecture
        • Application Portfolio Management and Project Portfolio Management links provide ties into the portfolio planning processes
        • Streamlining of IT Service lines can be achieved
    • 20. 8. Obtain IT Strategy Information
    • 21. 10. Manage Principles, Policies and Standards
      • Goals
        • Provide mechanisms to create Principles, Policies and Standards (PPS)
        • Create ways to correlate PPS with architecture decisions, architectures, patterns and other IT related assets
        • Surface information into analytic tools
      • Personas
        • CxO– Consumers and Reviewers of information
        • Enterprise Architects – Creators and Facilitators of PPS
        • Domain Architects - Creators of PPS
        • Solution Architects - Consumers of information
      • Desired Outcome
        • Architects understand why IT decisions
        • PPS provide alignment with CxO and business strategies
        • Solving complexity and confusion with traceability of architecture work
    • 22. IT Standards 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 Enterprise Architect
    • 23. 10. Manage Principles, Policies and Standards
    • 24. 9. Determining the Total Cost of Ownership of Architectures
      • Goals
        • Provide reports that show the various costs of an architecture
        • Span across Architecture, Business Architecture, Service Management, APM, PPM and development to realize total cost of ownership
      • Personas
        • Enterprise Architect – Consumer of information
        • CxO – Consumer of information
      • Desired Outcome
        • Provide CxO’s real-time metrics on the financial health of their IT environment
        • Increase awareness of the cost of an architecture(s)
        • Understand the impacts of dependencies of architectures
        • Focus resources on problem areas
    • 25. Total Cost of Ownership Results Pane Operational Tables Development Tables Service Management Tables Mock Tables Project Server 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 Search Web Part Architecture Drop Down Search x Calculate Dependencies
    • 26. More Information Microsoft Architecture Portal http://msdn.microsoft.com/architecture Microsoft Enterprise Architecture Portal http://msdn.microsoft.com/architecture/EA Mike Walker’s Blog http://blogs.msdn.com/MikeWalker
    • 27. © 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.