Prev Next

Business Goals and Objectives Modeling

Business Goals and Objectives Modeling is arguably the most important input to the development of an architecture, as it sets the right context for the alignment of architecture with the business strategy.

Enterprise Architect can be used to model the Goals and Objectives and relate them to each other, with each Goal being decomposed into a number of Objectives that can be measured. Stereotypes can be used to create Goal and Objective elements, and these can be added to any number of diagrams. The Project Browser provides a way of structuring the Goals, adding the Objectives as child elements placed under the applicable Goal. The Specification Manager is a useful tool for creating, viewing or presenting the Goals and Objectives in a workshop. It is a text based tool and allows the Goals and Objectives to be viewed in a word processor or spreadsheet interface.

This section lists the main tools available in Enterprise Architect that can be used to perform Business Goals and Objectives Modeling. There is also a wide range of additional tools that a modeler might find suitable when applying the technique in a particular context. The complete list of tools is available from the topics: Meet the Enterprise Architecture Tools and Additional Enterprise Architecture Tools.

Specification Manager

The Specification Manager is a powerful tool for working with lists of elements including Business Goals and Objectives; it provides a Word Processor- or Spreadsheet-like interface for entering, maintaining and viewing these elements. The Goals and Objectives and other elements such as Business Drivers can be viewed as a catalog and detailed descriptions and a range of properties can be added directly through the interface. Changing these elements in the Specification Manager will change them in all other places in the repository, such as diagrams and windows. The Specification Manager can be used with any set of model elements such as Requirements, and applications where viewing the elements in a list is preferred, but it is particularly useful for creating and managing content in the Business Architecture where users might not be as familiar with diagrammatic representations.

Learn More: Specification Manager

Project Browser

Business Goals and Objectives can be created and added to a catalog directly in the Project Browser, without the need to create the elements on a diagram. Elements created on a diagram will always be visible in the Project Browser, and changing them in one location will automatically update them everywhere in the repository. The elements can be ordered in the Project Browser using the Up Arrow button or Down Arrow button in the Project Browser header. They can also be grouped into categories by the use of Packages, to make the list more manageable.

Learn More: Project Browser

Requirements Diagram

The Requirements diagram can be used to create a visual representation of the relationship between Goals and Objectives and other elements in the model, including Principles, Business Drivers, Constraints, Business Rules, Use Cases, User Stories, design Components and more. For architects who are accustomed to working with lists in a text based tool, the Requirements diagrams will provide a powerful and expressive visual representation, allowing the Goals and Objectives to be tied to elements of the business, information, application and technology architectures.

Learn More: Requirements Diagram


The Unified Modeling Language does not itself contain elements to represent Goals and Objectives, but they can be included by using stereotypes, which is a mechanism for extending the core language. These stereotypes can be applied to a base element such as a Requirement and then the stereotype can be applied to create new Goals and Objectives. The stereotype will be visible in the Project Browser and diagrams if these options have been set. These stereotyped elements can become available if other Technologies or profiles have been enabled.

Learn More: Stereotyping

Traceability Window

The Traceability Window is a useful window that allows a modeler to visualize the connections between elements in the repository. This is useful to show how Goals and Objects relate to each other and how they are connected to other elements in the model and in turn how those elements are connected. Business Goals and Objectives can be related to a wide range of elements including Policies, Requirements, Business Process and more and all of these relationships would be visible through the Traceability window.

Learn More: Traceability Window