Goal Realization Viewpoint

The Goal Realization Viewpoint pattern creates elements and a diagram that models the relationships between goals including the decomposition to sub-goals. The goals are realized by a Principle which behaves like a more abstract and broader requirement. Finally the Principle is realized by a Requirement indicating specific properties that the system must exhibit. 

Figure 1. Show the decomposition of Goals and their relationship to Principles and Requirements.

Discussion
To provide a designing and deciding view for business managers, enterprise and technical architects, business analysts, requirements managers and other stakeholders who are concerned with the relationship between Goals (and their sub-goals) and the way these are realized by requirements and constraints that define properties the system must exhibit.

The pattern is typically used in the strategic and business design phases of an initiative. The goals and their decomposition and relationship to Principles may be modeled early on and the realizations to Requirements are more commonly modeled as an initiative progresses.

The following is a list of some things you may want to do when working with this pattern.
·	Change the name of the Goals, Principle and Requirement to suit the initiative.
·	Add additional Goals, Principles and Requirements and add other relationships as required.

The following is a list of next steps you may want to perform after working with this pattern.
·	Further decompose the Requirements into more detailed expressions in preparation for further analysis.
Resolve conflicts or overlaps between the Goals with the appropriate stakeholders ensuring that any changes meet the needs of the entire group of stakeholders. 

Reference
The following help topics will assist you learn about how to work with this pattern.
Archimate Technology
Diagram Layout
Tools you may find useful
The following are some of the tools that will be helpful when working with this pattern.
Document Generator
The Document Generator is a powerful facility in Enterprise Architect that allows a Database Engineer or other stakeholder to create high quality corporate or technical documentation directly from the model, suitable for internal or external audiences. For more details see the Documentation help topic.
Specification View
The Specification View can be used as a way of working with the Components and Interfaces particularly when there are a large number of elements as is typically the case when describing a system of any appreciable size. For more details see the Specification View help topic
Relationship Matrix
The Relationship Matrix provides a spreadsheet like view of two groups of elements and the relationships that exist between them. It can be a used as a powerful analysis mechanism to visually indicate how elements are related to each other and to discover which elements are missing relationships. For more details see the Relationship Matrix  help topic.
Traceability Window
The Traceability Window automatically displays the relationships that exist between Use Cases and other model elements including up-process and down-process elements. The traceability tree view can be conveniently expanded to see deeper relationships and elements displayed in the window can be located in all diagrams in which they appear. For more details see the Traceability Window  help topic.

© 2000 - 2018  Sparx Systems Pty Ltd.  All rights Reserved.