Checklist: Business Architecture Document
This checklist helps make sure that the Business Architecture is complete, stable, and as small as possible.
Expand All SectionsExpand All Sections    Collapse All SectionsCollapse All Sections
CollapseRelationships  
Related Elements
Back to topBack to top
CollapseMain Description  
Back to topBack to top
CollapseCheck Items  
Expand All Check ItemsExpand All Check Items Collapse All Check ItemsCollapse All Check Items
ExpandDoes the business architecture appears to be stable  

If it is the case,  the business architecture will in general appear to be reasonable. Past experience with the architecture can be a good indicator if the rate of change in the architecture is low, and remains low as new scenarios are covered, there is good reason to believe that the architecture is stabilizing. Conversely, if each new scenario causes changes in the architecture, it isstill evolving and baselining is not yet warranted.
ExpandThe complexity of the business architecture matches the functionality and value it provides to its customers  

  • .
The conceptual complexity is appropriate given the skill and experience of its users, operators, developers  
The business has a single consistent, coherent business architecture definition  
The business has a consistent enterprise-wide security facility. All the security components work together to safeguard the business  
The products and techniques on which the business and its automation is based matches its purpose  
The business architecture provided defines clear interfaces to enable partitioning for parallel team development  
ExpandThe business designer of a model element can understand enough from the business architecture to successfully design and develop the model element  
These include business worker,  business event and business entity.
Business systems have been defined to be highly cohesive internally, while the business systems themselves are loosely coupled  
Similar solutions within the common business domain have been considered.  
The proposed solution can be easily understood by someone generally knowledgeable in the problem domain  
All people on the team share the same view of the business architecture as the one presented by the business-process analysts  
The Business Architecture Document is current  
The Business-Modeling Guidelines have been followed  
The key performance requirements (established budgets) have been satisfied  
There are routines in place for verifying the business works as specified  
ExpandThe business architecture does not appear to be overly complex  
 In particular:
  • The mechanisms in place appear to be simple enough to use.
  • The number of mechanisms is modest and consistent with the scope of the system and the demands of the problem domain.
All business use-case realizations defined for the current iteration are supported by the business architecture  
Back to topBack to top

©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.