Enterprise Architecture Library

Enterprise Architecture is the description of a system in terms of its components and their interactions with each other and their environment.

The description covers four specific domains. Each description is prepared covering a baseline and target. The target articulates the system that will provide the desired organization and the gap between the baseline and the target identifies what needs to be done.

The materials here help us understand how to describe the system in useful terms.

Flexible Thinking

"How to Think Like Leonardo da Vinci: Seven Steps to Genius Every Day" by Michael J. Gelb is about helping us tap our unused resources of intelligence and ability.

Of Gelb's seven critical principles we see five that are the minimum set for Enterprise Architecture:

 

  • Curiosita: An insatiably curious approach to life
  • Dimonstratzione: A commitment to test knowledge through experience
  • Sfumato: A willingness to embrace ambiguity, paradox, and uncertainty
  • Arte/Scienza: The development of the balance between science and art, logic and imagination ("whole-brain thinking")
  • Connessione: A recognition and appreciation for the connectedness of all things and phenomena; "systems thinking."

Visual Communications

Dan Roam's "The Back of the Napkin: Solving Problems and Selling Ideas with Pictures"

Systems

The Fifth Discipline's Systems Thinking encourages us to use a holistic view of the organization and its environment. In addition to introducing us to systems thinking Fifth Discipline Peter Senge's main thesis is that a 'Learning Organization' must embrace five disciplines:

  • Building Shared Vision
  • Use acknowledged Mental models
  • Enable Team Learning
  • Embrace Personal Mastery
  • Use Systems Thinking

Enterprise Architecture Maturity Models

Best practice indicates that organizations should manage their Enterprise Architecture efforts utilizing a capability maturity model. The Capability Maturity Assessment enables an organization to objectively assess its ability and create a roadmap to capability required to acheive desired outcomes.

Many disciplines have developed capability maturity models designed to support process improvement.  Most capability maturity models are directly or indirectly are based upon he Software Engineering Institute's (SEI) Capability Maturity Model.These Capability Maturity Models describe the practices that must be performed and allow an assessment of the level of capability demonstrated within each practice. Typically the assessmnet considers five levels, each level representing an increased ability to control and manage the required practice.

Sample Architecture Capability Maturity Models

Two sample Architecture Capability Maturity Models are provided for reference.

The first is the US Department of Commerce Architecture Capability Maturity Model (ACMM 1.2), which is very focused on driving strong linkage to procurement and development practice.

The second is the NASCIO Enterprise Architecture Maturity Model. NASCIO represents chief information officers from the 50 states, six U.S. territories and the District of Columbia. The NASCIO model is focused on ensuring a strong architecture development and compliance process is developed.

DOC_ACMM_v1.2.doc

330 K

DOC_ACMM_v1.2.pdf

593 K

NASCIO-EAMM.pdf

2.1 M

US Federal Architecture

US Federal Architecture

fedarch1.pdf

3.0 M


These resources provide guidance on thinking about the world, with an aim to quietly challenging your world-view.

Some are aligned with our focus areas, some of general interest. The intent is to help you understand how you think about and understand your world. All of the books are available from Amazon and Chapters.

Disclaimer

Please note these resources may not be always be helpful - some of them might be wrong. Terms of use