Mike The Architect

Microsoft Enterprise Architecture Framework?

Your puzzled by the title aren't you? In a recent e-mail discussion the question came up regarding enterprise architecture frameworks. The questions was “Does Microsoft have an EA framework similar to TOGAF or Zachman”?  I decided to post this here on my blog because it might be useful information to you if you ever wondered the same.

There was a lot of people that had very interesting things to say about the topic but few answered the question. Some of the dialog included:

• The frameworks we do have and how they align
• Personal opinions on frameworks in general
• Services roadmaps
• Why we should/should not have an EA framework
• etc.

Today, Microsoft does not have an EA framework, methodology or a EA product as such. What Microsoft does have is some key pieces to the EA puzzle. One example of how this is directly demonstrated in the Enterprise Architecture Toolkit (EATK). The EATK shows customers how Microsoft can help make their EA efforts actionable through Microsoft technologies. The EATK which is a solution accelerator not a product, does have unique methodology and process components that could be contributed to an open standards bodies such as IASA, Open Group, EACOE or Zachman as examples. But is it a framework? No it is not. It is one tool in the EA Toolbox.

To further this notion, below is a snapshot of a mapping matrix on how the EATK aligns with TOGAF’s Architecture Development Method (ADM):

ADM Phase	ADM Steps	Scope	Alignment with EATK
A. Architecture Vision	1. Project Establishment	Limited	Integration with Project Portfolio Server
	2. Identify Business Goals and Drivers	In	Principles, Policies and business drivers that are captured at the corp. level and at the solution levels
	3. Review Architecture	In	Captured in the System Architecture Document Discoverable through the Architecture Metadata Repository (AMR) Collaboration mechanisms for sharing and validation of architectures
	4. Review Architecture Principles and Business Principles	In	EATK allows users to review Principles, Policies and Standards on the EA Portal.
	5. Define Scope - Breadth of architecture coverage - Level of detail to be defined - Domains that should be covered - Schedule concerns - Assets to be leveraged	In	Currently covered in the System Architecture Document AMR Pattern References allow for access to patterns
	6. Define constraints - Time, Schedule or Resources	Limited	Covered by Office Portfolio Server for PPM Practice
	7. Identify Stakeholders and concerns, Business Requirements, and Architecture Vision	Limited	Covered by Office Portfolio Server for PPM Practice
	8. Document the Architecture Statement of Work	In	Currently covered in the System Architecture Document. However this is a manual activity with little automation
	9. Get Approval for Architecture Statement of Work	In	Currently covered in the System Architecture Document. However this is a manual activity with little automation. Windows Workflow foundation is setup to do this task.
B. Business Architecture	1. Develop baseline architecture description	In	Supports the document management and workflow aspects however there is limited automation to these tasks.
	2. Identify reference models, viewpoints, and tools	In	Supports the document management and workflow aspects however there is limited automation to these tasks.
	3. Create Business Architecture Models	In	Supports the document management and workflow aspects however there is limited automation to these tasks.
	4. Select Business Architecture Models	In	Supports the document management and workflow aspects however there is limited automation to these tasks.
	5. Conduct a formal checkpoint review of models with stakeholders	In	Supports the document management and workflow aspects however there is limited automation to these tasks.
	6. Review non-functional criteria	In	Supports the document management and workflow aspects however there is limited automation to these tasks.
	7. Complete the business architecture	In	Supports the document management and workflow aspects however there is limited automation to these tasks.
	8. Perform gap analysis and create report	In	Supports the document management and workflow aspects however there is limited automation to these tasks.
C. Information Systems Architecture	1. Develop baseline architecture description(s) - Conceptual Data Model - Logical Data Model (views of information relevant to arch) - Data Management Models (life cycle, management view, etc)	In	This is accomplished in many ways: 1. System Architecture Document - This document template provides the mechanism in which to document your baseline descriptions. The document conforms to TOGAF from a method and artifact perspective and IEEE 1471 from an information model. The document uses a 1471 supported custom XML schema to represent information inside the document. 2. Architecture Meta-Data Repository (AMR) - This facility provides the architect with the right information to support the creation of a baseline description. 3. EATK Collaboration Mechanisms - Architectures have multiple viewpoints which means that there will most likely be more than one architect working on a particular architecture. There are built in collaboration features to aid in developing the architecture baseline.
	2. Review and validate principles, select reference models, viewpoints, and tools	In	1. AMR Pattern References - The core to this task is being able to surface this information to the architect. The AMR provides this facility by integrating both into Microsoft Word System Architecture Document and through SharePoint Portal for architects. 2. EATK Custom Workflows - Validation can occur through the sample architecture review and Architecture Review Board (ARB) processes.
	3. Create Architecture Models	In	There are a variety of activities have to occur to create architecture models. 1. System Architecture Document - First you need a place to describe those modes. The EATK uses the System Architecture document for this task. 2. Visio - Most architects and developers use Visio to model their architectures. The EATK has linked valuable information from the AMR so that the shapes in the model link to real assets and patterns. 3. AMR Pattern References - The AMR provides the facility for storing assets and building blocks that an organization has standardized upon.
	4. Select Architecture Models	In	Selection of a model usually entails the architect has a way to view the current approved building blocks and then must go through an approval process to validate the selection. The EATK does this through two key components: 1. System Architecture Document Patterns Browser Task Pane / EA Portal 2. Architecture Review Board Process
	5. Identify Candidate Applications	In	AMR Pattern References
	6. Conduct a formal checkpoint review of the Architecture Model and Building Blocks with stakeholders	In	Architecture Review Board Process AMR Pattern References EATK Collaboration Mechanisms EATK Custom Workflows (Sample WF provided)
	7. Review Non-Functional Criteria	In	Document Templates in document libraries
	8. Complete Architecture	In	Integration of System Architecture Document into workflow
	9. Conduct Checkpoint/Impact Analysis	In	Architecture Review Board Process AMR Pattern References EATK Collaboration Mechanisms EATK Custom Workflows (Sample WF provided)
	10. Perform Gap Analysis and Create Report	In	Template in a document library
D. Technology Architecture	1. Develop Baseline Technology Architecture Description	In	There are a variety of activities have to occur to create Architecture Descriptions. 1. System Architecture Document - First you need a place to describe those modes. The EATK uses the System Architecture document for this task. 2. Visio - Most architects and developers use Visio to model their architectures. The EATK has linked valuable information from the AMR so that the shapes in the model link to real assets and patterns. 3. Metadata Repository Integration - XML Web services layer to allow third party tools to submit architecture descriptions to repository. 4. Architecture Decision Template - A tool used to iteratively build a series of decision against an architecture.
	2. Create Target Technology Architecture	In	Same as above in baseline technology architecture
	3. Create a Baseline Technology Architecture Reference Models, Viewpoints and Tools	In	Same as above in baseline technology architecture
	4. Consider an Architecture Model of Building Blocks	In	Same as above in baseline technology architecture
	5. Select the Services Portfolio per Building Block	In	Same as above in baseline technology architecture
	6. Confirm that the Business Goals and Objectives are Met	In	Mapping to business architecture is supported but will need to be custom developed through the UI of choice.
	7. Choose the Criteria for Specification Selection	In	Same as above in baseline technology architecture
	8. Complete the Architecture Definition	In	Same as above in baseline technology architecture
	9. Conduct Gap Analysis	In	Gap analysis supported with repository placeholders to correlate that information with an architecture

As shown above, Microsoft can be an enabler of these EA practices. There are similar mappings with other industry adopted EA frameworks. In general Microsoft has always been an enabler with their products. Microsoft has a real opportunity to bring these solutions together by orchestrating the platform in a meaningful way.

So my take on this is that Microsoft really shouldn’t be in the business of creating EA frameworks. There isn’t a whole lot of value for Microsoft to do that. If you look around at the industry, you will see that most of the players that did create EA frameworks are now consolidating them into standards bodies. Those include:

• IBM
• Cap Gemini
• SAP
• EA Tool Vendors
• Governments like the Netherlands
• etc.

We should leave this up to the industry to define, they have the expertise here. I think there are particular aspects to an EA framework Microsoft can contribute and innovate to, but owning and building from scratch is something I feel isn’t a good idea.

Martin Sykes, a senior architect in the UK had summed it up perfectly:

Customers rarely ask us to provide them with a complete EA framework and methodology but they do want to know how we can help them improve what they have – and this has meant we need to be able to judge the situation, identify the weaknesses and then apply the right combination of perspectives from business, solution, technology, governance, portfolio mgmt etc.

However, there are many other examples on how Microsoft is helping provide thought leadership, guidance and tools in the Enterprise Architecture space. Below are direct and indirect examples:

1. Guidance on the Microsoft Enterprise Architecture Portal
2. Guidance and Thought Leadership on Blogs from Microsoft Employees:
1. Nick Malik
2. Gabriel Morgan
3. Mike Walker (Me) – [EA Specific]
4. Full list of Microsoft architect blogs here and architecture community blogs
3. Development and Operations frameworks such as Microsoft Operations Framework (MOF), which also include the Microsoft Solutions Framework (MSF)
4. Methodologies and tools to tackle capability modeling and analysis through Microsoft Business Architecture (MSBA)
5. Tools and Platform Products that aid with Service Management, ALM, Operations and PPM. Some of these  that include (not going to list them all):
1. Project Portfolio Server – APM and PPM
2. SharePoint – Centralized Process/Workflow, Collaboration, ECM, Portal, etc.
3. Visual Studio Team System – Development asset repository, development process support, class modeling through new UML support, etc.
4. Systems Center – Operational / Service management
5. Dynamics – Incident management, Green IT dashboards, etc.
6. Oslo – Model driven development support and deployment

 

So in summary, where I think Microsoft can add value is by enabling these industry frameworks through our unique products, platforms, thought leadership, frameworks and guidance by orchestrating them in a meaningful way. The EATK does this by rationalizing the platform assets with EA specific business knowhow on top of a extensible platform we can address key EA scenarios. By extending this toolkit and other like it (MSBA, MOF, MSF, etc. ) I think we can make these EA frameworks much more actionable.

What do you think?

Technorati Tags: Enterprise Architecture,Frameworks,Microsoft,MSF,MOF,EATK

Presentations Uploaded

As followers of my blog know, I do many speaking engagements. Often times I get requests for those decks from the conference or event. Instead of sharing with a select few I thought I would share with everyone. You can find some of the major presentations under my Slideshare profile:

http://www.slideshare.net/mikejwalker

Here is a quick list of the presentations:

• Enterprise Architecture Toolkit Screenshots
• Improving on How Architectures are Described
• Enterprise Architecture Toolkit Scenarios
• Enterprise Architecture Toolkit Overview
• Enabling Lending Business Imperatives with Office
• Loan Origination Reference Architecture Deep Dive
• Office Developers Conference - Financial Services O...
• End to End Vertical OBA's
• Composite Applications and OBA Architecture
• Composite Applications Speaking Tour - Lap Around O...
• Composite Applications Speaking Tour – Keynote
• Office Business Applications in Financial Services
• Microsoft Insurance Solutions Keynote Presentation ...
• Enterprise Architecture Toolkit – English
• Financial Services Component Library

More to come…

Technorati Tags: Presentations,Enterprise Architecture,Composite Applications,OBA,Financial Services,EA,EATK

Share this post :

Using the EATK to Capture Architecture Descriptions

The EATK makes Microsoft Word 2007 a first class citizen in the architecture description area. As I described in  my recent post called "Do Office Tools Still Play a Role in Architecture Design?" I talked in length how at least for the time being we are still using productivity tools for describing our architectures. Since this is the case more often than not, the EATK uses Word to articulate these architectures.

In this post I will give you a brief summary of how the EATK helps with documenting architecture descriptions.

There are a series of problems that the EATK is trying to solve by leveraging Microsoft Word 2007. I will not go into length in all of them but highlight some key areas.

The first is to make the creation of architecture descriptions much more intuitive and easy to do. Even though tools such as Word are easy to use we still see complexity here. That complexity comes in the form of:

• Duplicate data entry
• Template overload
• Limited ability to control quality of descriptions
• etc.

 

 

As shown above, we are adding more and more documents to an already large portfolio of documents that need to be completed. In the past this was manageable but now documents can be bloated and information has a higher probability of being duplicated. Often times this is a result of tightly coupling a document with a process step that results in a great deal of redundancy.

So how does the EATK attempt to solve these challenges? It does so by changing the context in which Word is used. Changing the context is a sometimes not an intuitive task. It takes some investigative work both on the capabilities you want to expose and potential development to the tooling.

The underlining goal is to change the role of Word from simply a word processor to more of a User Interface (UI) for designing architectures. Applying structured UI concepts to Microsoft Word provide many benefits to the architecture document.

• Structured Content – Information can be better described in the document. The reason we want to do this is because of the challenges mentioned regarding how information doesn’t integrate well with process or future design activities. One example is the process of importing a model into an architecture document. Often times we import a picture that represents a model of a specific view point of an architecture. If we had an information model we could specific that the model imported is indeed the logical model, rather than a generic image file.
• Extensible – With a little more structure information has meaning and definition. This makes that information extensible to other processes downstream.
• Consumable – Abilities to consume external content is also possible with a more structured interface. As an example, if you choose to you could import external architecture information from other systems to automate you design efforts.

 

Let's take a look at this from a technical perspective. Below illustrates how the EATK separates areas of concerns with the implimentation in Microsoft Word.

• Tool - The mechanism of Microsoft Word is referred to here. The tool provides extensibility into the user interface that provides Office Ribbons to execute tasks easily with a level of context and Office Task Panes that extend the UI with additional entry or listings of information.
• Document - The document provides the way in which a user can enter in architecture descriptions. This is different in the EATK as the document acts as the glue between the Tool and the information itself. This is accomplished through a architecture document template and the use of word custom controls.
• Information - The information in the document is managed completely different than in a traditional document. All information typed into the document is linked back to an XML node behind the scenes. This fully qualifies what is typed the information. Not only is the information rich but it is extensible.

 

Let's take a look at the implementation in the EATK. Below you can see how Ribbons, Meta-Data Properties and Task Panes are implemented. The EA Toolkit Ribbon shows at the top of the screen. These represent the functionality the functionality in this tool.

The meta-data properties provide context around the document or high-level architecture itself. There are the following fields: Title, SDLC Phase, Architecture ID, Architecture name, Project ID. This information is utilized in throughout the implementation from integration to the workflow to surfacing information in context.

Task panes shown below are able to make architecture information as transparent as possible. It allows the EATK to surface information from the architecture meta-data repository. With a double click on a pattern or asset that information is populated in the document. The document tracks if an existing pattern is used so the governance process can track reuse (among a series of other benefits).

 

The new OOXML features in Office 2007 allows us to separate the information from the document in a much cleaner way. With the new formats, the entire document is XML based. The document itself is a zip compressed file with the extension of .docx. In these files are a series of file folders.

The customXML folder is used in the EATK. Below we see that item1.xml is the system architecture XML file used for storing architecture information. All information entered into the System Architecture Document will be stored here.

 

 

Additional Screen Shots

 

 

 

Technorati Tags: Enterprise Architecture,EATK,Solution Architecture

Do Office Tools Still Play a Role in Architecture Design?

I thought I would write this potentially controversial post about how traditional productivity tools such as Microsoft Office (Word, Excel, PowerPoint and Visio) can still play a role in the architecting process.

Whether we like it or not the Office tooling is used throughout the architect community as a tool to describe architectures. This topic comes up quite a bit in my conversations with customers. I still find that the overwhelming majority of enterprises still use productivity tools for architecture design and descriptions. I recently did an informal survey at the Open group Practitioner conference in January. What I found from this informal survey was that 90% of enterprises use these tools day to day for architecture. I found similar results at Gartner EA summit and FSTC EA Forum the year before.

The Enterprise Architecture Toolkit (EATK) is set out to help in this area. It provides a series of templates and add-ins to the productivity tools to enhance the architecting process.

Changing the Way we Describe Architecture Designs

Today many enterprises use the Office tools for different purposes. There isn't a one size fit all. Shown below is how we see many enterprises using the productivity tools.

Traditionally architects have been forced to develop architectures in a restrictive and monolithic way. Meaning that the input mechanisms for architecture require a set of fairly sequential steps in which the information is derived. The question now is; are the existing tools we use for architecting, been outgrown or outdated for the tasks at hand. The answer here is no, the current tools are still used for mainstream development of architectures.

The underlining goal is to change the role of Word from simply a word processor to more of a User Interface (UI) for designing architectures. Applying structured UI concepts to Microsoft Word provide many benefits to the architecture document.

• Structured Content – Information can be better described in the document. The reason we want to do this is because of the challenges mentioned regarding how information doesn’t integrate well with process or future design activities. One example is the process of importing a model into an architecture document. Often times we import a picture that represents a model of a specific view point of an architecture. If we had an information model we could specific that the model imported is indeed the logical model, rather than a generic image file.
• Extensible – With a little more structure information has meaning and definition. This makes that information extensible to other processes downstream.
• Consumable – Abilities to consume external content is also possible with a more structured interface. As an example, if you choose to you could import external architecture information from other systems to automate you design efforts.

Why not a Model Driven Approach?

So the next question that is probably in most of your minds is, what about Model Driven Development (MDD)? Through these same surveys my findings found that MDD as an architectural practice is very difficult. There are a variety of reasons for this:

• Education - There is a substantial learning curve to learning an ontology, tools, notations, process, etc. Also, there is the issue of un-learning what you have been doing for so long.
• Tooling Maturity - There are a lot of great tools for modeling but these tools are still not as mainstream as they need to be. There are many tools that are proprietary in nature. There needs to be more standards support.
• Adoption - Usability and complexity comes into play here. I have seen revolts against a structured modeling tool because it wasn't as intuitive or easier to learn as other shape (not modeling) based tools.

Does this mean that we not go down the MDD approach? Of course not. We just have some challenges to overcome. To overcome these challenges we need to take a pragmatic and iterative approach.

Meaning, not all organizations are ready for the MDD approach right away. For these organizations they should take a "baby steps" towards MDD. The big bang approach has proven to be a painful and perilous route to take when trying to change how an organization develops.

If an organization is ready for a MDD approach, that's great and should do so. The role of documents changes again, right? Of course, now the document can be used as a report or can be used to describe the models at the meta level. The role may become smaller but still can play a role.

 

Tags: Enterprise Architecture

The Enterprise Architecture Toolkit

Over the past month there has been a flurry of interest in what is referred to as the Enterprise Architecture Toolkit (EATK). The last mention of the EATK was in my post recapping the Japan Strategic Architecture Forum I mentioned the launch of the EATK.

What is the EATK

So what exactly is the EATK? Well simply put it is a set of tools that will aid Enterprise, Solution and Domain Architects with their architecture efforts in a pragmatic way. The EATK does so by providing a set of base tools built in existing products that they may already have or use for the same purpose. The value of how the EATK rationalizes these solutions is by extending common interfaces used in enterprises such as Microsoft Word and Visio.

Below is a summary of what the EATK is:

• Solution Accelerator for Enterprise Architecture
• Series of Add-Ins to Existing Products
• Set of Smart Architecture Templates
  • System Architecture Document
  • Architecture Decisions
  • Architecture Review Board
  • Architecture Viability Assessment
• Architecture Portal which includes:
  • Hosted Process and Collaboration Workflow
  • Knowledge Management System
  • Asset Management System
• Based on Industry Standards
  • Supports IEEE 1471
  • Supports TOGAF ADM
• Provides a Bill of Materials
  • Source Code
  • Whitepapers
  • Rich Media

 

Why the EATK

You maybe wondering, "why build on top of existing tools such as Word?". Well the answer is simple, from our research most architects are using these tools. The issue is that they are not used in the context of describing architectures but rather simple word processors.

There is an opportunity to still leverage many of the great features of these tools with out the baggage of a word processor. It's a matter of changing the context of the usage of the tools from a word processor to a User Interface for describing architectures.

The goals of the EATK are to:

• Introduce New  and Creative Capabilities to Architecture
•  Simplify and Consolidate Solutions for Architecture Design
•  Leverage the Tools You Have
•  Simplify the process
• Introduce Collaboration into the Architecting Process
•  Surface Information in the Scope and Context of the Architect

 

Scenarios EATK is Based on:

The EATK was built not as a fully featured product but rather concentrated on a series of common architecture scenarios. The reason for this was because I wanted to go deep on these aspects rather than go broad and shallow.

Ten common scenarios where defined by talking with customers around the world, informal surveys and what I have observed through forums, blogs and analyst reports. 

1. Describing an Architecture with Current Tools
2. Building a Collaborative Solution Architecture Design
3. Extend Architecture Meta-Data into the Visio Modeling Environment
4. Deriving to an Architecture with a series of Architecture Decisions
5. Architecture Management
   1. Understanding Architecture Policy
   2. Managing an Architecture Life Cycle
6. Navigate and Explore Approved IT Patterns
7. Navigate and Explore Existing IT Architectures
8. Obtaining the information for IT Strategy Management
9. Determining the Total Cost of Ownership of an Architecture
10. Manage and publishing of Principles, Policies and Standards

Key Technologies Used

• Microsoft SharePoint 2007 – Architecture Portal
  • Hosted Windows Workflow Foundation
  • Web Parts
  • Enterprise Content Management
• Microsoft Office 2007 – Templates and Add-Ins
  • Word
  • PowerPoint
  • Visio
• Web Services – Architecture Message Bus
• SQL Server – Architecture Meta-Data Repository

Complements Existing Products

One of the most common questions I get is if the EATK conflicts or competes against existing development tools at Microsoft. The short answer is no. It actually complements the capabilities of the following areas:

• Development
  • Visual Studio
• Project Portfolio Management 
  • Project Server
• Application Portfolio Management
  • Portfolio Server
• Service Management
  • Systems Center
• Methodologies
  • Microsoft Operations Framework
  • Microsoft Solutions Framework

Over the course of several months there will iterative enhancements done to the EATK that will introduce new materials, templates and integration points.

Tags: Enterprise Architecture

Japan's Largest Publisher talks about the Enterprise Architecture Toolkit (EATK)

Sorry, this is only in Japanese. However you can try out the new Live Translator Service to view the page in Jap-Glish.

http://www.windowslivetranslator.com/BV.aspx?ref=LandingPage&MKT=en-US&lp=ja_en&a=http%3A%2F%2Fitpro.nikkeibp.co.jp%2Farticle%2FNEWS%2F20080414%2F298870%2F

 

「EA（Enterprise Architecture）を支援するツールのユーザー・インタフェースは今後， Microsoft Office Wordが主流にな

る」。こう語るのは，米MicrosoftのMike Walker氏（Architecture Strategy Team，Financial Services Architecture Strategist，写真）だ。Walker氏は，同社が無償で提供するEAの支援ツール「Microsoft Enterprise Architecture Tool Kit（EATK）」の普及に携わっている。

EATKは，EAを定義する業務標準や開発標準に関する情報を管理するソフト。論理，物理，ネットワーク，セキュリティといった様々な観点でまとめられたアーキテクチャに関するデータを整理して管理する。パターン化された業務フローやソフトウエア・コンポーネントなどの情報も管理対象にできる。Walker氏が言及しているのは，EATKを採用したときのユーザー・インタフェースのことだ。

http://itpro.nikkeibp.co.jp/article/NEWS/20080414/298870/

 

 

Tags: Enterprise Architecture

Japan Strategic Architecture Forum - Day 2

So I am a little late with this content...  But I have a good excuse :) The post is a bit delayed as there has been very limited internet connection at the resort. I guess in Japan a resort is really meant to be a resort. Meaning no connections with work. I like that idea...

The second and last day of the of the Japan Strategic Architecture Forum (SAF) had two keynotes from both a customer and Microsoft on the future of S+S.

 

Unfortunately the majority of the sessions were in Japanese so I can't give you a great recap of the events but I can share with you what the announcement was from my presentation.

Enterprise Architecture Toolkit Alpha Announcement

The Enterprise Architecture Toolkit (EATK) was announced at the the forum. The EATK pre-release is in Alpha release form. Initially, we will offering the EATK to a limited set of customers that are interested in the solution accelerator.

 

The EATK capabilities include:

• Repository - Meta-data repository for uniting enterprise processes, storing existing architecture assets and a catalog for patterns (Software Factories in Microsoft terms or Architecture Building Blocks (ABB) in TOGAF ADM terms)
• Architecture Management - Portal and Workflow assets that aid in the processes and govern architecture creation through the SDLC or through post production service management processes.
• Strategy Management - Portal and Workflow that aid in the creation of as-is or current state architecture, to-be or future state architectures and the management of technology life cycles of architectures.
• Community - Portal technologies that aid in the communication and collaboration, vetting of ideals through-out the enterprise, communication of Principles, Policies, Standards and Design Patterns, Add-Ins and Templates for architecture development.
• Modeling - Usage scenarios for how to leverage Microsoft Visio to correlate architecture information from the Architecture Meta-Data Repository to Visio diagrams and shapes.

Since this is a solution accelerator the EATK capabilities are implemented as a series of scenarios.

Over the course of the next several months I will be publishing content to both the Microsoft Enterprise Architecture Portal and to my blog on how I feel the EATK addresses the various challenges of the EA space.

If you are interested in providing feedback, piloting or just having a conversation into this process, it isn't too late. Please send me an e-mail request at mikewalk [at] microsoft.com. We have a limited number of early adopter slots for both the Japanese and America geographies.

I have included my presentation in both Japanese and English below. I would encourage you to take a look and provide feedback to the overview of the tooling and concepts presented below. I may also include audio at some point.

 

Local Japanese Content

Below is the localized Japanese content for the customers and partners that attended the Strategic Architecture Forum.

EATK Poster

Presentation

| View | Upload your own

 

English Version of Content

Poster

 

Presentation

| View | Upload your own

Tags: Enterprise Architecture

 

English Version of Content

Poster

 

Presentation

| View | Upload your own

Tags: Enterprise Architecture