The methods featured in this section help architects analyze their enterprises, facilitate shared understanding in their organizations, and lead conversations about prioritization and change. Each method is a lens focused on a few selected themes, usually resulting in a visual summary that aids communication and supports decision making.
Architectural methods focus on themes that may not be well represented in methods for project management, business analysis, or technical analysis. These themes include:
A brick diagram organizes technology services and components, so an organization can describe and enforce standards, services, and capabilities for a given technology domain. The diagram also describes the lifecycle of technology components - each component will be in one or more of the following: tactical, strategic, retirement, containment, baseline, or emerging. A brick can comprise one or more solutions/implementations in which an enterprise invests to support its capabilities.
A business capability, or simply a “capability,” defines what a business does. It does not communicate or expose where, why, or how something is done — only what is done. Specifically, the business capability is “a particular ability or capacity that a business may possess or exchange to achieve a specific purpose or outcome (Cutter)." Business capability modeling captures the core functional model for an organization without the bias imposed by the organization's structure itself.
A Case for Action should be done to help synthesize the major artifacts, lessons, and recommendations for next steps after an EA engagement. This artifacts summarizes what has been learned / accomplished in the engagement, and helps stakeholders organize/move to deliver on the outcomes identified in the engagement.
The Core Diagram is a hybrid tool that brings together value chains, capabilities and conceptual data objects in one view. It represents the information technology constructs that enable interaction between a service provider and a service consumer. The consumers' functional tasks are chained together on a timeline across the top horizontal, the providers functional tasks are chained together on a timeline across the bottom horizontal, and the technology solutions are organized in the center by logical groupings.
This is a dependency graph that overlays some kind of optimization diagram. It can easily be created on the fly to clarify the relationships among various initiatives. The top two quadrants contain business items of business value. The two right quadrants contain personal or local items of value. The top right contains the primary target. The lower left are necessary underpinnings that are not obvious per se as business goods.
An Investment Value Matrix (aka Engagement Value Matrix) facilitates discussion of solutions or initiatives in terms of business value and architectural value. It can be used to guide or make a case for prioritization of investment, or to evaluate existing solutions.
The MESA visually expresses both the architectural approval (whether it is recommended) and the lifecycle of a thing in a given environment. The life-cycle is indicated by the position of the icon on a curve shaped like a "mesa" with a plateau in the middle. Things typically enter the environment and travel up the left slope of the mesa and exit the environment on the right slope of the mesa. The thing that is described with a “mesa” may be a technology, service, or other.
"Pace-Layered Application Strategy is a methodology for categorizing, selecting, managing and governing applications to support business change, differentiation and innovation, [based on the rate of change of the application]" (Gartner). Pace-layering differentiates the rate of change into three categories - Systems of Record (slow change), Systems of Differentiation (medium change), and Systems of Innovation (high change).
Process maps provide a shared high level understanding of end-to-end business processes in a business domain. The method focuses on what activities take place, rather than how, and helps identify all kinds of opportunities for improvement (not limited to technology changes).
A Roadmap shows a path from current state to a desired future state. The roadmap method builds consensus on vision, goals, milestones, and deliverables. The roadmap can be used to rally a community around a plan for action as well as manage expectations for outcomes over time.
A semantic data model describes the concepts that are important to an organization along with their meanings and relationships to other important concepts. It is something like an authoritative Glossary of Terms along with diagrams or other ways of showing the relationships between different data. A semantic model has an emphasis on relationships and meaning and how the data relate to the real world.
A Strategy on a Page is a single-page summary of an organization's current strategy. It is intended to be easy to create, share, consume, and update. Compared with traditional longer strategy documents created by committee (and then typically rarely referred to), the Strategy on a Page method is meant to encourage active communication about living, changing strategy.
A portfolio investment decision making tool used with stakeholders with regard to a constantly changing time dimension. Used to create alignment of IT investments with institutional strategy. Provides transparency into the decision making process. The core TIME diagram shows three dimensions: business value, technical quality/condition, and time.
The pages in this section were drafted by the participants in the ITANA Spring Face2Face 2015 meeting. Many thanks to the the participants and to everyone who contributed methods for consideration!