James Smith’s Java Oracle Blogs – Author
Architecture Capability Maturity Model
Follow me on above links
Joe Said …Well … , We Architects proposed to use online Order Booking Process to be developed using Java Server Faces Technology,
the Management later told them that most of the Order Booking People were NOT very comfortable with Internet or Computers and they are very much Comfortable using Order Booking Books and ledgers, and the Developers that they have are more of Graphic Designers who maintain their company website than anyone having experience in developing Online Order Management System … sounds similar … may be yes
So , before proposing something Joe’s team should have analysed if the Customer were CAPABLE of doing what they proposed …..
Architecture Elements and Maturity Levels
Enterprise Organizations undergoes major Business and Architectural transformations mainly due to changes in the business dynamics and/or entry into new and emerging markets which can result in new mergers and acquisitions, added complexity to their business and efforts in setting up new Business ventures.
As an Architect it becomes essential to understand their current “Architecture capability maturity model” and how we can work with our customers to enable them reach that “Measured Level” from their existing level so that they can do their business better and we can add Value for our engagement with the customers and the solutions that we can suggest them.
The Department of Commerce Architecture Capability Maturity Model consists of six maturity levels and nine architecture elements
The nine Enterprise Architecture Elements are:
1. Architecture Process,
2. Architecture Development
3. Business Linkage
4. Senior Management Involvement
5. Operating Unit Participation
6. Architecture Communication
7. IT Security
8. Architecture Governance
9. IT Investment and Acquisition Strategy
The six levels are:
If an Organization is rated from 0 to 5, it means as told below
Level 0. None, No Enterprise Architecture at all, No Architect to Speak but a very good profitable business – A Company which runs and keep on running , No matter who architects or not, like a chicken shop which runs on a principle of “Catch it, Cut it , Clean it and Forget it ” ….. .
Implications In these cases it would be very difficult to Architect the solutions that their business needs and they might need to under go a major Architecture and Business transformation with in themselves guided by their CTO and Architecture Board. even before anyone can help them further.
Level 1. Initial, Ad Hoc Process, Success depends on individual effort .. some one takes initiative only then things work, Architecture is minimally linked to Business and IT strategy, They follow No standards, No Governance, and are Ad Hoc Run Company, But still some Architecture Process are defined, Documents and Standards are established but no one really cares ..
Level 2. Under Development, IT Vision, Principles, Business Linkages, Baseline Architecture are identified. Architecture standards exist, but not necessarily linked to Target Architecture, Management awareness of Architecture effort. Little or no formal governance of IT investment and acquisition strategy, Architecture Linking to Business strategy is missing, Management is aware of Architecture effort
3. Defined, Defined Enterprise Architecture [EA] Including Detailed Written Procedures and Technical Reference Model, Well Defined and Well Connected IT and Business Units, Gap Analysis and Migration Planning done, Senior Management Supports Initiative.
4. Managed, EA is a part of the Culture, with in the Organization ,Quality metrics associated withthe architecture process are captured, Senior-management team directly involved in the architecture review process
5. Measured and Optimized, Continuous Improvement of Enterprise Architecture Process, Senior management involvement in optimizing process improvements in Architecture development and governance. Architecture documents are used by every decision maker in the organization for every IT-related business decision, No unplanned IT investment or acquisition activity