Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Goals and Objectives
Goals represent the decomposition of the strategy and are aspirations that the enterprise intends to achieve. They are important because they are statements that can be used as anchor points for the architecture. Some frameworks and methods will consider these to be outside the scope of the architecture and just providing a context. Either way it is critical that they are modeled to provide a reference point for the business architecture. Once the goals are modeled it will most likely become apparent that some of them will not be able to be achieved by technology alone but will typically require pure business solutions to address them in part or in whole.
The goals will still be too high level to act as a starting point for the other architecture domains and so they need to be broken down into a series of objectives that can be stated in terms of measurable outcomes. Each goal will be an aggregate of one or more objectives and these can be related back to the parent goal.
Enterprise Architect allows both the Goals and Objectives to be modeled using the UML Extension mechanism of stereotypes and these elements can be included in diagrams and lists and related to other elements such as the Vision statement and Measures. These diagrams are compelling for senior executives and line managers who can see clearly that the architecture work and the subsequent implementation initiatives can be traced back to the Objectives and Goals and other strategic primitives.
These elements and relationships can also be visualized in a diagram which provides a welcomed view for some stakeholders particularly the executives and senior business managers.