Welcome to BrainStormCentral.org

Please note: You must be a current Member to access BrainStormCentral.org.

Problems logging in? Request your login information here.
Not a member? Take a tour and join today!

Business Architecture Blog by Business Architecture Bloggers

Regular Blog postings by the Business Architecture Institute

Posts: 6 | Created on January 11, 2010 |  

In the article I wrote last September, I gave an example of business information diagramming that I typically use to describe a business situation and to frame potential solutions. The diagramming is biased by my background as a linguist and semanticist. It uses English verbs to designate actions or processes, nouns to designate people, other objects, concepts and data, and relationships to designate the roles that the people, concepts, data and people play in the actions or processes. I get useful insights about information flow and information lifecycles from these diagrams, and they are easy to present to both technical and business audiences.

The purpose of this blog entry is to start a discussion in this community about the kinds of diagrams and other models that you find to be useful in your work. I’m not looking for tool endorsements. I am looking for representational ideas and the value that can be derived from them. And, I’d like to keep the focus on information, as opposed to business processes or services or capabilities. There are already discussion groups for these other topics.

I suspect that many of you that do this kind of modeling, do it informally on pieces of paper or using generic tools like UML or general purpose diagram editors like Visio. If you have an interesting diagram example, scan it or turn it into a jpeg and make it a part of your discussion entry. However, please make sure that you anonymize the diagram or have permission to publish it. I’ve seen unfortunate things happen when web postings exposed client intellectual property.

Jim Rhyne


Some recommended reads, discussions...


Business Semantics – Information Alignment
Take Your Visio(r) based Business Process Analysis Project to the Next Level

 

There still seems to be quite a bit of discussion on what exactly is the value of business architecture (BA) to an organization.  While it is great to be having more and more discussions around business architecture, it is still disappointing that the value business architecture brings to an organization is not better understood.

Over the next few posts I will discuss the reasons why the value is not better understood as well as the actual value proposition of business architecture.

The lack of understanding of what is business architecture is probably the greatest contributor to the confusion on the value it brings.  There are several "camps" out there still that believe business architecture is about a certain domain or meant for a specific purpose.  For example, there are those that say BA is only about the processes or BA is about defining the business strategy or it is about showing the implications of a business strategy and those that feel BA is there for IT. 

The value proposition each of those are trying to achieve is vastly different and then the disagreement begins (sometimes heated too!) 

More next week on how to bring the disagreements together.

There was a good discussion lately on whether or not a business architect must have a MBA.  In order to look at this question, one needs to understand the qualities they are looking for in a business architect and then determine if a MBA is what helps you develop these qualities.  Using the article 'Defining a Great Business Architect' from the CUTTER IT JOURNAL March 2008, these are attributes that can be used to define a business architect:

  • Creative/Innovative
  • Persuasive
  • Commands Respect
  • Thinks "Big Picture"
  • Has a Grasp of Technology
  • Strategic
  • A Good Communicator

Clearly getting a MBA would help someone develop their skills in being strategic and a good communicator, but the other 5 attributes are often best developed through experience.  Currently, there are certification programs for becoming a business architect that are wrapped into MBA programs (there is also an offering to take outside of the MBA program as well), but learning from a book, does not prepare one for all the challenges a business architect will face.

In summary, I do not believe that a MBA is required to be a good business architect. Is it helpful? Yes it can be, but some of the best, most creative, innovative and respected business architects I have worked with do not have MBA's, they have deep experience in problem solving.

The Jan. 2010 bulletin has an upcoming article that I wrote titled "What's up with the business architecture tool vendors?" (View the article here.) In this article, I have outlined the current state of BA tooling and what steps vendors should take this year in order to provide more useful tooling to the business architecture community.

The issues outlined in my article address the visibility of vendors in the BA marketplace, the challenges associated with repository customization, visualization issues, and how vendors can do some simple things to make their tools more useful to business architecture teams.

If you are a business architect and share similar frustrations, I would like to hear from you. What have your BA tooling experiences been and what would you recommend that tool vendors do to address current limitations?

If you are a tool vendor and fall into the category of tool I describe in the article, then let me know what your plans are for BA tool support in 2010. How are you addressing the needs of the business architecture community?

William Ulrich, Editorial Director, Business Architecture Insitute


Some recommended reads, discussions...


What's Up With Business Architecture Vendors?

What's Up With Business Architecture Vendors?

As many of you know, I moderate the Business Architecture discussion group on LinkedIn.  Over the last couple of years, several great topics have been discussed, but I usually abstain from commenting during the open threads.  Over the next several months I will bring forward many of the best and most active threads from the discussion boards and post my thoughts on the topic here in this blog.  Some of the topics will include:

  • What is the Value of a Business Architecture to an organization?
  • The skill sets of an Effective Business Architect.
  • Relationship between Business Architecture and Requirements.
  • Business Architecture Governance.
  • Where does Business Architecture belong in an organization?

If you have any other suggestions or preferences, let me know. Greg

2009 brought us in business architecture many good things.  We are seeing greater acceptance of business architecture across organizations and in industries such as insurance, financial services and the government.  Groups such as the Business Architecture Institute, Forrester, Gartner, OMG and the Open Group have not only engaged in the discussion around business architecture.  And, the tool vendors are beginning to make their software products better fit the needs of a business architect.

All the positive momentum will require us in the community of business architects to work closer together to develop best practices and even standards or we will end up with a fragmentation of the profession and the discipline.  Working together can bring great things for us business architects in 2010!

Share this page with your network:

Share/Bookmark