Mike Walker's Ramblings about Industry Architecture

Zachman Updates

In recent letter from Zachman International they have announced two updates the popular Zachman Framework. They are relatively small. Here are the details:

1. Engagement and Market Strategy will change in 2009. The ZIFA organization has been dissolved. 
2. There was a minor update to the framework. This brings the framework to version 2.0.

All in all, there are minor impacts on this announcement. The operations angle is a fairly obvious one as the Service Management (i.e., Operations) World is converging with EA disciplines so it makes sense that EA frameworks meet in the middle. I haven't yet seen anything revolutionarily, more like evolutionary. As you can see from the model above there are no radical changes that would greatly impact enterprises already using this framework.

Also to keep constant, this doesn't change my opinion on where Zachman fits into the greater EA Framework and Standards arena. From my post on Making Sense of Architecture Standards, Zachman is still very much at the "Decision Framework" level. See below:

Letter from John Zachman

Dear Friends of ZIFA,

Thank you so much for your many years of support and interest in The Zachman Framework™. I have had the pleasure to meet many of you personally at seminars and conferences, and I appreciate your contributions to my understanding of Enterprise Architecture. By making sure you are registered on my ZachmanInternational.com website, you will be assured of continuing contact with me.

I wanted to take an opportunity to make some significant new announcements about Zachman International and what you can expect from me in the future.

As many of you know, ZIFA was an informal collaboration between my company Zachman International and Sam Holcman of Pinnacle Business Group. I provided the theoretical basis and evangelism for Enterprise Architecture and Sam provided the marketing, operations and his planning methodology. Sam has since moved on to a new organization, EACOE, presumably to focus on training and marketing his Enterprise Architecture planning methodology. Sam has recommended, and I have agreed, that we dissolve ZIFA at the end of the current calendar year, 2008. I appreciate Sam's contributions toward advancing the visibility of Enterprise Architecture and I wish him well in his new endeavor.

As CEO of Zachman International, I will continue my Enterprise Architecture talks worldwide, while expanding the "Zachman Certified™" deployment. In order to consolidate the authorized framework materials, schedules, and use of the Zachman™ brand, I have asked my son, John P. Zachman, to bring his decade and a half of marketing experience and become the Vice President of Marketing at Zachman International.

Stan Locke will continue to be Managing Director and President of Zachman Framework Associates, relating the client implementation practice to the classification theory through standards development, elaboration and sample models. David Kingston will become the Vice President of Customer Support Systems responsible for systems operations in Toronto which handles all our business transactions, security and ecommerce facilities. Each of us is available via our web site or toll-free number if you have any questions. We are expecting a significant number of other folks to be joining us over the next year, but the aforementioned people here will be the principal contacts, at least for the present.

Live Mesh: More Slots Available, No Wait List

In April Live Mesh was announced at the Web 2.0 conference and opened it up for people to try out our platform experience -- the first evidence of what scenarios our platform is capable of enabling. Today the Mesh Team are increasing the number of available slots in the Live Mesh Technology Preview, and expanding the list of countries that will allow sign-up without a wait list to include Canada, India and Ireland!

I have been personally using Live Mesh for awhile now and absolutely love it. It's a great way to keep everything in sync. Not only is it a great way to keep all of your computers up to date but also adds the following benefits and distinguishing points:

1. Not just another sync tool, it's a platform w/ real hooks into the OS and application space. The benefits for this point alone is incredible.
2. Integration w/ the file system is a no as simple as it gets
3. Sync w/ the cloud OR backup...
4. Remote Desktop abilities. This is both good and bad from a corporate security perspective.
5. Updates, updates, and more updates. this platform promises a compelling road map with integration to many platforms such as Windows Mobile and Apple's OS X platform.

Mary Jo Foley wrote an excellent post on Ten things to know about Microsoft’s Live Mesh. It's worth a read if you are not familiar with the Live Mesh technology.

Note: This is in addition to the availability we’ve previously announced for USA, UK, Australia and New Zealand (see coverage map).

The experience you see today is just tip of the iceberg! To see what the Live Mesh platform is capable of, check out the Channel 9 videos, try out the user experience. We’re eager for you help to keep pushing our scale, and your feedback!

We do still have a maximum limit on the number of users we’ll allow into the Technology Preview, but as long as we’re below the limit, anyone in the countries above can sign-up today with no delays or wait list.

The Microsoft Certified Architect Board Member Unravels the Process

Loud Sigh who just joined the Microsoft Certified Architect (MCA) Review Board wrote a great post on how to prepare for the review board, why you should do it and share his own experience going through the MCA certification process.

I do like how Loud points out that the certification isn't just an exam on specific data points it more about how you have handled situations that require years of experience and knowledge.

The key points to me are:

• MCA is not only about you your technical skills but also your soft skills. How you handle situations, can you negotiate, do you demonstrate leadership, etc.
• You have to go through your experience by demonstrating evidence and then talk walk through the architecture trade-offs
• The board doesn't expect you to know everything but would like to understand if you know how to find the answer, if you can delegate or mitigate a concern.

It's worth a read if you are not familiar with the MCA process. Who knows, you may even want to take it after reading it.

For more information:

• Microsoft Certified Architect (MCA) Site
• Read the MCA blog posted on TechRepublic
• One year in: An update on the Microsoft Certified Architect program

Is the pervasiveness of information making us stupid?

There is a great article from Nicholas Carr that is worth a read called "Is Google Making Us Stupid?". There is a similar article on the New York Times site as well called "Literacy Debate: Online, R U Really Reading?"

There is a common thread here, and that is information overload. Is this good, bad or indifferent? This is still subject to debate on the long term effects. Personally, I think that this is an issue. Information management will be the key in this digital age.

Thoughts?

Creating a Enterprise Asset Roadmap Strategy

Recently I was asked to chime in on how to setup a global enterprise asset roadmap strategy. This was a fully loaded question and also a tricky one to answer. It is not an easy task as there is a number of forces at play and are extremely dynamic based on organizational culture, dynamics, structure and business objectives.

Lot of thoughts were communicated but I thought I would share my high level thoughts and considerations to keep in mind when developing an enterprise strategy. I am not going to go into the micro level detail here with templates and structures as this is an activity that is somewhat tailored to a specific customer and requires a lot of deliverables.

With an activity like this it is critical that you EA’s are pragmatic and focus on delivery as soon as possible to show results. The core principle that should be employed here should be:

“Think strategically, act tactically”

The majority of the challenges will not be technical in nature. But rather it will be primarily people oriented. This is not to say that the people are necessarily incompetent. It only means that the value proposition isn't always obvious to all parties and there will be some level of education and persuasion on the EA's part.

Some of these challenges include:

• Adoption – This factor accounts for the majority of the issues that you will face when driving out a strategy. For most enterprises there are a number of people based factors that include:
• Poor Perception - or lack of willingness to understand value proposition. There have been some great studies around this from Gartner and Forrester.
• Understanding or Training – Coupled with perception, this factor hinders adoption due to the lack of understanding on why this activity should be performed
• Incentive – Most employees in enterprises are not incented to do these activities. So if they are not incented, they will not do it. This does not always happen but can be used as a general rule of thumb.
• Information – Many of the challenges of doing a current to future state architecture is the lack of information to do so. This problem needs to be solved to effectively figure out where an organization should go. The point here is that the future is always in motion. I recommend iterative strategies to develop “Transition State Architectures”. These are architectures that lend themselves to a set of principles defined for where they want to take a solution of capability. By delivering in an iterative way they don’t boil the ocean and are able to course correct if needed.
• Tools – To be effective tools enterprises really need tools that empower the process and deliver critical information that empowers architects and developers.
• The challenges is that many of the EA tools are intrusive and require a great deal of training. They also often require users to learn how they do things that may or may not be aligned with how development in that enterprise has been done in the past.
• Most of these are proprietary even though they have plug-ins to extend
• These tools are also high cost which enterprises starting out EA practices struggle with

From a tooling perspective, it should support the first two challenges. We have one orchestration of technologies that aids in this called the Enterprise Architecture Toolkit. It by no means solves all these challenges but does provide a pragmatic way of addressing these areas by focusing on automating and enriching the solution architecture development process. As mentioned before on my blog, it is a solution accelerator for supporting the architecture process within mid to large size enterprises. The EATK includes both architecture guidance and supporting code base to run the toolkit.

The key scenarios support architectural strategy with the following scenarios:

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

Keep in mind that this effort requires a great deal of work. There needs to be established:

• Organizational Structures
• Operating Models
• Incentives
• Definitions for Success Criteria
• Savvy resource that can handle political maneuvering
• New range of Architecture Operating Models
• A great deal of Facilitation to help IT / Business / Operations work optimally together

Having clearly defined engagement and operating model should enable your organization to have a repeatable process for making decisions and delivering on artifacts at the right level of quality and consistency. 

Can you Easily Compare EA Frameworks?

Have you ever tried to compare EA frameworks? How do you compare and are all frameworks the same. The reader digest version of the answer is: No... Not all frameworks are the same but rather have there own definitions of what they are to deliver.

I have in the past and I have found it very challenging because it is a bit like comparing apples and oranges. When I talk to customers and folks internally about EA frameworks there is a great deal of confusion with current comparisons found online. Below is a common example:

source: http://www.mkern.com/whatisea/frameworks.html

This comparison  really doesn't tell us much detail. Although there is a whitepaper called A Comparison of the Top Four Enterprise-Architecture Methodologies on the MSDN EA Architecture Center we have the same issue with comparing these framework with the same base criteria:

This isn't to say these don't provide value, they do from a macro level. However, the real challenge here is that these frameworks are fundamentally trying to solve different problems all together.

I see that there are two major types of frameworks:

• General Purpose Frameworks - What sets these types of frameworks apart from others is that they are trying to solve the broader problem the enterprises are having. These frameworks do so by being agnostic to any specific implementation. They have no specific business drivers (enterprise specific) but rather are capability based. These frameworks are generally driven by industry consortia such as Open Group.
• Domain Specific Frameworks - Frameworks that are derived from an EA effort are refereed to as Domain Specific. These frameworks were derived with a predefined set of business concerns in mind because they originated from an EA office or process improvement effort in a government or an enterprise. Largely these frameworks are driven by government agencies such as the US government or other geographies.

So how does the actual frameworks fit into these buckets.

Should you eliminate one of these types form your efforts? Absolutely not. These frameworks have very specific value propositions. But we first need to know how they are fundamentally different.

As shown above there are two basic characteristics. We look at the allowable level of customization vs. prescriptive guidance. These frameworks slide down the continuum from the level and ability to customize to the level of prescriptive guidance. The general purpose framework has a greater level of flexibility as it is attempting to solve all problems. Whereas the Domain Specific Framework is solving the problem with a series of predefined set of forces and attributes.

For example: A government based framework such as FEAF / TEAF / FEAF will be based on the specific government based regulatory laws (region based), a set of operating and organizational models that is specific to that agency. These will drive out the process and artifacts required to fulfil these base business drivers.

So what do you get with these different types of frameworks? With these two classifications of frameworks there are a set of artifacts, methods and tools that are derived. These are derived on the the base problem sets defined earlier. Since these are derived, the outputs can be very different. See below:

General Purpose Frameworks:

• Defines an open and consistent definition of terminology through taxonomies and ontology.
• Agnostic to organizational structure
• Low level process agnostic
• SDLC
• PMO
• Service Management
• etc.
• Very configurable to enterprises

Domain Specific Frameworks:

• Prescriptive guidance for:
• Organizational structures
• Processes
• Artifacts
• Usually deliver lots of templates
• Lots of real world examples

Is the comparison of EA Frameworks like comparing Apples and Oranges? Yes it is. When you compare these frameworks they should not be treated the same nor should be judged based on the same criteria. Rather they should be correlated with your specific requirements. 

19th Enterprise Architecture Practitioners Conference: Day 1 Highlights

For those who didn't get the updates. Here is a summary of the activates at the Open Group Conference in Chicago.

The Open Group’s 19th Enterprise Architecture Practitioners Conference kicked off on Monday, July 21st in Chicago.  Industry leaders from near and far convened at the historic InterContinental Chicago Hotel to share their insights on the latest enterprise architecture trends, challenges and opportunities facing federal government organizations as well as global businesses.  Below, please find highlights from Day One.

Allen Brown, President and CEO, The Open Group, kicked off the Day One “Frameworks for Federated Architectures” plenary session with open remarks. Mr. Brown welcomed several hundred attendees from around the globe.

Following Mr. Brown’s opening remarks Wing Commander Shaun Harvey, Department Director, United Kingdom SAF/XCPA, delivered his presentation, “Architecting for Interoperability using Fit For Federation Criteria.” Wing Commander Harvey prefaced that much like complex, highly distributed businesses, the Department of Defense (DoD) is comprised of many interdependent components. These include the Air Force, Army, Navy, and Marines, each of which shares common integration and interoperation issues. While the DoD and the Air Force use Architecture Federation to help address integration, the Wing Commander explained the Air Force’s development of an Architecture Federation approach called “Fit For Federation” to specifically support interoperation.

Next, Marc Othersen, Senior Analyst, Forrester Research, delivered his presentation “Compliance Frameworks: The Foundation of IT-GRC.” According to Othersen, business imperatives, increased regulatory pressure, and customer demands are forcing many CIOs to adopt a structured, enterprise wide approach to deal with IT governance, risk, and compliance (GRC). Because IT GRC initiatives have traditionally been scattered across organizations without much coordination, many companies are looking for solutions that can help them create a unified approach to managing information risk and IT compliance requirements while ensuring good governance at the same time. Marc outlined Forrester’s view on IT GRC and gave recommendations for developing a robust IT GRC program.
To access additional information on Marc’s presentation, including a free report from Forrester, entitled “Defining IT GRC”, please visit: www.forrester.com/opengroup2008.

Ron Schuldt, Senior Staff Systems Architect, Lockheed Martin Enterprise Business Services, next presented on “An Open Group Standard for Building Your Controlled Vocabulary.” Mr. Schuldt began his address by explaining that TOGAF™ does a great job of identifying the processes necessary for defining an enterprise architecture, but it does not assure “Boundaryless Information Flow” across organizations. The Open Group standard that provides the foundation framework for a controlled vocabulary, known as the Universal Data Element Framework (UDEF) is part of the solution, argued Schuldt. His presentation provided a detailed demonstration on UDEF and highlighted the role of this critical standard within the enterprise. For more information on the UDEF standard, visit: http://www.opengroup.org/udefinfo/.
An in-depth UDEF Training is open to all conference attendees on Wednesday, July 23^rd at 9:00am.
The day’s last plenary presentation, “Standardize Architecture Delivery in a Federated Architecture using TOGAF,” was given by Peter Van Hoof, Principal Enterprise Architect, Sasol, South Africa. Sasol, South Africa’s largest industrial company, has a strongly entrenched federated business model and utilizes a deeply embedded business project methodology across its many diverse business units, called the Business Development and Implementation Model (BD&IM). Mr. Van Hoof’s presentation covered how Sasol aligned TOGAF with the BD&IM – a great example of how to standardize architecture delivery in a federated architecture environment using TOGAF.
Kicking off the afternoon’s Government Enterprise Architecture Track was Robert Weisman, Partner & Executive Consultant, Global Enterprise Architecture Practice Leader, CGI, with “TOGAF Case Studies in Government.” Mr. Weisman highlighted several applications of TOGAF in selected US State and Canadian Federal Government engagements. The presentation provided recommendations for future use of TOGAF within a government environment and also discussed how TOGAF works in conjunction with other EA frameworks, including Zachman, EA Tool, Australian Government Outcome Based Planning and Australian Government Architecture.

In the TOGAF Track, Matt Vandenbush, Enterprise Architect, Brady Corporation, presented a case study “Preparing the Enterprise for a Successful Architecture Program Based on TOFAF.” Mr. Vandenbush began his presentation with a poignant statement, “Almost half of EA groups are dissolved within two years and many more do not meet stakeholder expectations.” This is more often the outcome of poor internal advocacy- architects within their organizations need to prove the value of EA as a tool for making better decisions; and TOGAF has served as Brady Corporation’s guide to achieve this level of success. Mr. Vandenbush made recommendations on the three most important activities to make EA matter within any organization: getting your governance processes under control; prepare to use the TOGAF architecture development method (ADM); and focus on “delivery”.

Later in the Government Enterprise Architecture Track, Eduardo Castro, Architect, Grupo Asesor en Informatica, Costa Rica, presented on “Digital Government Strategy in Costa Rica.” He covered the strategy followed by Costa Rica to implement a massive EA initiative in order to bring better services to the public institutions, providers and citizens.
In the SOA Track, Pinaki Ghosh, Lead Architect Specialist, The Dow Chemical Company, delivered a lively presentation on “Developing Enterprise Business Object Libraries to Support SOA.” Mr. Ghosh began his session arguing that the main competitive advantage in information architecture comes down to a well constructed information footprint model within an EA framework, such as TOGAF, Zachman or DoDAF. During the transition from legacy architecture to SOA, however, one of the critical things most companies neglect is the preparation of an Enterprise Object Library. Such a library contains both business and IT objects categorized by international standards, unique artifact numbers and database identities. Pinaki’s presentation delved into The Dow Chemical Company’s use of a business object library to better align IT services with the business.

Chang Peng, Enterprise Architect, MoneyGram International, closed out Day One’s EA Best Practice Management Track with his presentation “Enterprise Architecture in Support of Business Strategy.” The goal of Mr. Peng’s presentation was to extend enterprise architecture beyond the IT walls to support corporate business strategy. Chang’s presentation demonstrated how MoneyGram International re-aligned their traditional EA model to encompass deep rooted business logic and link with several tangible business strategies. As a result “enterprise architecture” is now a part of the common vocabulary among MoneyGram’s senior executive management team.

Microsoft Strategic Architect Forum 2008

For those interested, the 2008 Microsoft Strategic Architect Forum (SAF) will happen again this year. Each year my team organizes this conference so that top architects from around the world can get together to collaborate on key challenges in the industry. This year, it will be held in downtown San Francisco instead of back at Redmond (like all other years). The tone of the conference will still be the same with a great line up of speakers and round table discussions.

What is SAF?

I have blogged about this before you can find the post here. You can get the slides and recorded video from last years SAF.

SAF 2007 Recorded Sessions

SAF is Microsoft’s premier gathering of 350 strategic architects and other key influencers from enterprises, ISVs, and start-ups from around the globe.  Each year, SAF is an invigorating and lively event, with key technology leaders from across Microsoft sharing their vision with customers and listening closely to their business needs. 

SAF, which follows the Microsoft Professional Developers Conference (PDC) by a month, is designed to be complimentary to the PDC – SAF will dig into the strategic architectural issues posed by bringing together the various products and technologies detailed at the PDC into the solutions our customers care about most. 

More information will be forth coming.

Open Group SOA Ontology

The Open Group has recently released a draft version of a SOA ontology. They have been developing a formal ontology for SOA for some time now. You can find the ontology described in OWL-DL also. This should give the ontology a more complete level of description.

Open Group explains the benefits as:

1. It defines the concepts, terminology and semantics of SOA in both business and technical
terms, in order to:

• Create a foundation for further work in domain-specific areas,
• Enable communications between business and technical people,
• Enhance the understanding of SOA concepts in the business and technical
  communities, and
• Provide a means to state problems and opportunities clearly and unambiguously
  to promote mutual understanding.

2. It potentially contributes to model-driven SOA implementation. The ontology is designed for use by:

• Business people, to give them a deeper understanding of SOA, and its use in the
  enterprise;
• Architects, as metadata for architectural artifacts; and
• Architecture methodologists, as a component of SOA metamodels.

The full draft can be found here:

http://www.opengroup.org/projects/soa-ontology/doc.tpl?gdid=16940

Tags: Enterprise Architecture

Seven Cloud-Computing Security Risks

In a recent article on Network World they highlight security issues with the cloud. Jon Brodkin extracts his thoughts from a Gartner report titled “Assessing the Security Risks of Cloud Computing.” If you had seen my last post on Challenges moving to the Cloud you can see many synergies with our thoughts.

Key Nuggets in the article include:

• Gartner defines as a type of computing in which “massively scalable IT-enabled capabilities are delivered ‘as a service’ to external customers using Internet technologies.”
• Ask questions related to the qualifications of policy makers, architects, coders and operators; risk-control processes and technical mechanisms; and the level of testing that’s been done to verify that service and control processes are functioning as intended, and that vendors can identify unanticipated vulnerabilities.
• Customers are ultimately responsible for the security and integrity of their own data, even when it is held by a service provider.
• Even if you don’t know where your data is, a cloud provider should tell you what will happen to your data and service in case of a disaster. “Any offering that does not replicate the data and application infrastructure across multiple sites is vulnerable to a total failure,” Gartner says
• Ideally, your cloud computing provider will never go broke or get acquired and swallowed up by a larger company. But you must be sure your data will remain available even after such an event.

There is an emerging trend with the challenges associated with Cloud based computing, it is less about the technology rather more about the business and operational sides of solution development. Even here when we talk about security there is very little mention about security protocols, encryption, authentication providers and so on.

Just like with any other architectural decision, there is a trade-off when moving your applications/services outside the firewall.  Enterprise should take the lessons learned from the previous models like B2B, ASP or Managed Services. These previous methods ran into the same challenges and I would bet that there are some lessons that can be learned by digging up the past.

For more see: http://www.networkworld.com/news/2008/070208-cloud.html

Microsoft Architecture Journal Issue 17 - Call For Papers

As a new member of the Architecture Journal Board I would like to let everyone that reads my blog that the upcoming Architecture Journal is accepting articles from you. If you haven't seen or heard of the journal it's worth a look. For the most part we get articles from architects outside Microsoft. Check out the Architecture Journal Website for more information (www.architecturejournal.net).

The next issue of the Architecture Journal will focus on Distributed Computing. We are approaching an inflection point with today’s hardware and technologies where a vision from only a few years ago is becoming reality –from deploying applications on microscopic devices in our environment through to football-sized datacenters offering applications in the cloud. Whether small or large, distribution and concurrency of multiple services can introduce a number of challenges – the focus of this issue is to understand what these challenges are, and how they can be overcome.

If you have opinions that you would like to share with the architect community on distributed computing, here is your chance! Follow the instructions below to send an abstract before the cut-off date and you could see your thoughts and ideas shared with over 60,000 readers, translated in 5 languages, and distributed at multiple conferences around the world!

The cut-off date for abstracts for the next issue is July 28th 2008.  If you are interested in making a submission, here are the details:

Where can I get more information?

Check out this link

EA & ITIL Getting Closer Aligned?

Great post on Jeff Adkin's blog, Service Oriented Abstraction. As many of you know I have talked about this too (ITIL moving towards EA & Making Sense of EA Standards). This is further evidence that these disjointed enterprise functions are starting to come together.

Finally!

Check out "Intersection between Enterprise Architcture, ITIL and the SOA Movement". He has some high level meta-models and a study from Amazon.

What is Global Enterprise Architecture?

Recently the term Global Enterprise Architecture has been floating around. I find myself wondering if this is yet another fluffy EA term.  Is it the same as Enterprise Architecture or is there something special about it?

Well, yes and no. We are hearing more and more about Global EA with the continuing globalization efforts. Mergers and Acquisitions are occurring at an increased rate. China and India are booming with Russia, South America, Ireland and others benefiting from this trend.

With these outsourcing activities occurring to try to minimize overall cost there are a wide variety of implications. Now security and compliance issues become much more complex, different national infrastructures can also be problematic. With all of this new complexity Global organizations have realized they need something similar to EA at the global level.

So was Homer right in 900 B.C.? Is the world flat? Well if you look at his view on the right, which is the The Homeric conception of the world represented as a flat, not so much. The circular disc of land surrounded by a continuous ocean-stream didn't pan out. However, from a logical point of view yes. With transportation, communications and the Internet we might as well be one big island.

So getting back to Global EA. What is it, really? Forrester defines Global EA as:

An extension and modification of local and regional architectures and EA practices to encompass a broader set of requirements and challenges related to pursuing IT strategy on a global scale.

My personal opinion is that I agree with Forrester. Global EA is merely a way to qualify the scope of a particular EA organization. I have found that the functions stay the same, but the mix and the depth of activities change.

So does this mean that Global EA is even more abstract than traditional EA? I don't think so. In some areas they will be, in other they might go deeper. For example, I see business and information architecture having more of an emphasis in Global EA. The reason for this is  when you go across national borders technology is the least of your problems. You must deal with massive transformations of currency, numerical systems and languages. This isn't a trivial task. To compound the issue you have different regulations in each country. Some of which conflict with others.

These challenges lead Global EA's to put their business and information hat on to make recommendations and decisions based these external forces. Whereas in EA organization that were at the national level didn't have these far reaching problems.

I am sure your wondering what happens to the regional / national traditional EA organization. Does it go away? No. I think that it plays an important role in Global EA. It may not have as many people in that team as a traditional one would but nevertheless it still adds value.

We may start to see models like you see above, where you have a global EA function and possibly regional, continental or national EA bodies. All severing a purpose. Similarly to the US Government where you have the following break down:

• National
• State
• County
• City

Each servers there purpose and has a specific scope and context on how they resolve issues and make decisions. They are closely aligned however they can also make their own decisions. They have there own versions of the government at their specific layer of abstraction.

That's where I see things landing based on my conversations with customers. What are your thoughts? If there is more interest I can go deeper on this topic.

Tags: Enterprise Architecture

Loan Origination Reference Architecture v.2.0 Source

Many have asked for source code to the Loan Origination Reference Architecture and now it's on CodePlex.

Source Code

http://www.codeplex.com/los/Release/ProjectReleases.aspx?ReleaseId=15173

Home Page

http://msdn.microsoft.com/architecture/orlos

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