Goal Oriented Thinking

GQM & StrategiesとArchiMate Motivation Extensionとの関係を考えてみた。

Vision Requirement & System Requirement

UMLを、要求定義まで拡張する手法もあるが、ArchiMateは、要求分析ー要求定義ーアーキテクチャ設計（システム設計）までを一貫した記述ができるという特徴がある。

アーキテクチャ設計（システム設計）は、システム間・アプリケーション間のアーキテクチャ（構造）のDesignと、ITでは捉えがちだが、要件から一貫してアーキテクチャ（構造）を、Modelingすることが、AgileなDesignに求められる考え方であるといえる。

つまり、Agileでは、ビジネス目標ベース（Vision Architecture）から、ビジネスプロセスーシステム要求までを一貫して、連続的に変化させていけることが求められる。

AgileのVision設計では、ビジネスモデル等の言葉で、Business Model Campusなどが用いられる。ArchiMateでは、Modeling LanguageでArchitectureをModelとして表現することが可能となる。

ArchiMate Element :

Driver : 

An external or internal condition that motivates an organization to define its goals and implement the changes necessary to achieve them.

Goal :

A high-level statement of intent, direction, or desired end state for an organization and its stakeholders.

Outcome :

An end result that has been achieved. Outcomes are high-level, business-oriented results produced by capabilities of an organization.

Assessment :

The result of an analysis of the state of affairs of the enterprise with respect to some driver.

An assessment may reveal strengths, weakness, opportunities, or threats for some area of interest. 

Value :

The relative worth, utility, or importance of a core element or an outcome.

A value can be associated with all core elements of an architecture, as well as with outcomes.

Requirement :

A statement of need that must be met by the architecture. 

Requirements model the properties of these elements that are needed to achieve the "ends" that are modeled by the goals. In this respect, requirements represent the "means" to realize goals.

Meaning :

The knowledge or expertise present in, or the interpretation given to, a core element in a particular context.

Principle :

A qualitative statement of intent that should be met by the architecture. Similar to requirements, principles define intended properties of systems. However, in contrast to requirements, principles are broader in scope and more abstract than requirements.

Constraint :

A factor that prevents or obstructs the realization of goals. In contrast to a requirement, a constraint does not prescribe some intended functionality of the system to be realized, but impose a restriction on the way it operates or may be realized.