Adventures in Consulting

B|D|A|T|S(TM) Architecture Methodology

After several years of developing and using architectures we developed our B|D|A|T|S™ architecture methodology.  "B|D|A|T|S” symbolizes the business, data, application, technical, and security views of an architecture. We expanded the core methodology to cover and federate four levels of architecture: enterprise, integration, solutions, infrastructure.  Enterprise architecture looks across the entire organization as well as the eco-system of suppliers and customers.   Integration architecture looks at a family of systems and end-to-end processes whiles solutions architecture address a single system.  Infrastructure architecture deals the shared data centers and core services.  This level is more applicable if you’re building the "cloud" instead of using it.   

One the biggest problems we encounter, is that everyone has a different take on what architecture means to them.  One person’s enterprise architecture can be another person’s solution architecture.      Applying B|D|A|T|S™ views across the four levels really helps us overcome the ambiguous meaning of architecture and define its purpose and scope (“fit for purpose”).  For example, the business view of enterprise architecture is very different from the business view of infrastructure architecture.  The enterprise layer would look at the business model and capabilities while the infrastructure layer would focus on service catalogs and levels The other important aspect of the methodology is the ability to federate or link across the layers.  This provides line of site from the business model to the individual applications and projects.  It allows different architects to maintain the right level of abstract to suit their objectives - but still have the ability, when needed, to drill down to more detail or drill up for a bigger picture.

   

Federation is an important concept since most enterprise architectures are simply too large and complex to be described within a single integrated architecture (and by a single architectural team). A single architecture would be either too abstract and wouldn't be useful (30,000 feet and climbing anti-pattern), or would need to compile massive amounts of data that would be impractical (boiling the ocean anti-pattern).  The federation approach allows for distributing, linking, and discovering architectural information across disparate teams.

Slide Library

Microsoft SharePoint 2007 (MOSS 2007) has an interesting new Slide Library feature that we're testing out.  It allows you to publish a power point presentation to SharePoint.  Each slide becomes its own document allowing you to version control each  slide independently.  You can then easily resemble just the slide you want for a presentation.  We're trying this out initially for our marketing material. 

This could be a real benefit for organizations, like consulting companies, that rely a lot on power point for deliverables (not just presentations).  Power Point is still the best low cost desktop publishing  & diagramming tool.      

Tech Ed 2008 Observations

I had three interesting observations from Microsoft’s TechEd 2008 conference earlier this summer:

1. Advancing the Architecture Profession
2. SOA was passé
3. Bill Gates is bullish on architecture modeling

Advancing Architecture

There were a lot of seminars on architects and the architecture profession.  Overall, everyone felt the trend was the increasing importance of architects.  The top three take-aways:

1. Architecture will become increasing important as other IT skills get commoditized and outsourced (infrastructure, development, etc.). 
2. An architect’s soft skills are as, if not more, important than technical skills.  Architects really need old fashion consulting skills.  Not a new insight, but Microsoft and TOGAF and defining nice competency models.    
3. Architecture is a very young discipline as compared to engineering or computer science.   Old analogies about buildings and city planning aren’t helping communicate the role of the architect.

SOA was passé 

While there was a major SOA track, the focus was more on where the services would reside, in the “cloud”, in a local data center, or rented via SaaS.  No one was really talking about how SOA was going to revolutionize business and how to add SOA to your company.  This change in direction is good for the industry.  The abstract talk combined with vendor marketing was creating a backlash. 

Architecture Modeling

During Bill Gate’s last speech at Microsoft, he talked about two software areas that he was really excited about.  One of these was architecture modeling (the other was robotics).   Microsoft’s next generation of tools (visual studio) will include a “federated” repository to store and link various models from across the enterprise.   Visual studio will also include modeling and visualization tools.  Microsoft has been pushing Model Driven approaches is various ways over the years (BizTalk, SSIS, Operations Center, SML, etc.) but now they are working a unifying strategy. 

Given the industry weight of Microsoft and IBM (through Rational and Telelogic) we may really see advanced in modeling as it applies to EA.  This can only be a good thing given the pain around current Enterprise Architecture tools.

Consulting not Contracting

Consulting not Contracting.  This has become a mantra here at Exalt Consulting Group.   In the IT field, especial in the Government Sector, there is a plethora of contractors that provide technical services.  But it is rare to find individuals and firms that provide "professional" consulting services - people that hold themselves and their work to a higher standard.  It’s not to say that there is anything wrong with contractors or contracting.  There is a need for the contracting role - just not all the time and not for our firm. 

One of our goals is to exalt or elevate IT consulting, especially architecture, into a true profession.  The following quote really summaries my feelings on the subject. 

"The professions are a noble calling, providing the opportunity to serve and contribute to others and make a difference in the world beyond one life."

          -  Paul Dunn, Ronald J. Baker

Personally, I want to see IT consulting achieve the same professional prestige as doctors and lawyers (well maybe not all lawyers).