ArchiMate - Motivation Concepts

  • Stakeholder

  • Driver

  • Assessment

  • Goal

  • Requirement

  • Constraint

  • Principle

Stakeholder

Stakeholder is the role of an individual, team, or organisation (or classes thereof) that represents their interests in, or concerns relative to, the outcome of the architecture. Based on definition from TOGAF. Examples are CEO, Board, Shareholders, Customers, businesses. In other words an Actor can also be a Stakeholder. Name should be a noun.

Motivation Extension - Stakeholder Notation

Example

This example models the stakeholders, the internal and external drivers for change, and the assessments (in terms of strengths, weaknesses, opportunities, and threats) of these drivers. Also, the links to the initial (high-level) goals that address these concerns and assessments may be described. These goals form the basis for the requirements engineering process, including goal refinement, contribution and conflict analysis, and the derivation of requirements that realize the goals.

Image result for stakeholder archimate visual paradigm

Note That

  • Stakeholder composed, aggregated of other Stakeholders

  • Stakeholder associated with all other elements

Driver

Driver is something that creates, motivates, and fuels the change in an organisation. Drivers can be internal (Customer satisfaction, Compliance to Legislation), or External (economic climate, legislation). Name should be a noun.

ArchiMate - Driver Notation

Example

The example illustrates the modeling of goals to address the assessments of the driver Costs: the applications costs and the costs of employees are too high. The former assessment is addressed by the goals Reduce maintenance costs and Reduce direct application costs (of usage). The latter assessment is addressed by the goal Reduce workload employees, which is decomposed into Reduce manual work and Reduce interaction with customer.

Image result for driver archimate visual paradigm

Note That

  • Driver composed, aggregated of other Drivers

  • Driver associated with or influences other Motivation elements Contains material extracted from the ArchiMate

Assessment

Assessment is the outcome of some analysis of some driver. An Assessment is made by analysing drivers, then doing a SWOT analysis. Strengths and Weaknesses need to be exploited or minimised. Opportunities need to be capitalised on and threats mitigated. Together these will result in Goals being set. Name could be a noun, or short statement / sentence.

ArchiMate - Assessment Notation

Example

This example models the stakeholders, the internal and external drivers for change, and the assessments (in terms of strengths, weaknesses, opportunities, and threats) of these drivers. Also, the links to the initial (high-level) goals that address these concerns and assessments may be described. These goals form the basis for the requirements engineering process, including goal refinement, contribution and conflict analysis, and the derivation of requirements that realize the goals.

Note That

  • Assessment composed, aggregated of other Assessments

  • Assessment associated with or influences other Motivational elements

Goal

Goal is an end state that a stakeholder intends to achieve. A Goal is a target to aim for. Often recognize by the use of qualitative words, such as “increase sales”. Goals can be decomposed into several levels.

ArchiMate Goal Notation

Example

This example models the refinement of (high-level) goals into more concrete goals, and the refinement of concrete goals into requirements or constraints that describe the properties that are needed to realize the goals. The refinement of goals into subgoals is modeled using the aggregation relationship. The refinement of goals into requirements is modeled using the realization relationship.

In addition, the principles may be modeled that guide the refinement of goals into requirements.

Image result for goal archimate visual paradigm

Note That

  • Goal composed, aggregated of other Goals

  • Goals associated with or influences other Motivational elements

Requirement

Requirement is a statement of need that must be realised by a system. Requirements represent the means to achieve the ends (Goals). Higher-level requirements address goals, but eventually they can reach a more detailed level where requirements are associated with the system itself. Requirements can be decomposed into potentially many levels of detail.

ArchiMate - Requirement Notation

Example

Image result for requirement archimate visual paradigm

Note That

  • Requirement composed, aggregated of other Requirements or Constraints

  • Requirement realizes Goal or Principle

  • Requirement associated or influences remaining Motivational elements

Constraint

Constraint is a restriction on the way in which a system is realized. Constraints impose restrictions at a system level, and often relate to time, cost, resources, platform, and skills.

ArchiMate - Constraint Notation

Example

For the realization of a new portfolio management application, two constraints are imposed, as shown in the model below: for the realization of the application, Java should be used, and the budget of the implementation project is limited to 500k Euro.

Image result for constraint archimate visual paradigm

Note That

  • Constraint composed, aggregated of other Constraints or Requirements

  • Constraint realises Goal or Principle

  • Constraint associated or influences remaining Motivational elements

Principle

Principle is a normative property of all systems in a given context, or the way in which they are realized. Principles are a more general form of requirement, and are thus applicable over all systems. They are therefore much more stable and enduring in their nature. However, they are refined into more specific requirements when applied to individual systems. A principle is motivated by a Goal, e.g. Goal = “no instances of being sued”, Principle = “abide by the law”.

ArchiMate - Principle Notation

Example

This example illustrates the use of principles. Principle Systems should be customer facing is modeled as a means to realize the goals Reduce interaction with customer and Reduce manual work. The principle is further specialized into the requirements Provide on-line portfolio service and Provide on-line information service to apply the principle to the actual systems (architecture) under design.

ArchiMate - Principle Example

Note That

  • Principle composed, aggregated of other Principles

  • Principle realizes a Goal