Metrics and Key Performance Indicators (KPIs)
The Metrics and Key Performance Indicators (KPIs) pattern creates elements and a Class diagram that describe a KPI framework in the form of a hierarchy. The indicators can be used to evaluate the success of an organization or one of its activities or products such as projects, programs, systems or components.

Figure 1. Shows a hierarchy of elements all stereotyped as <<kpi>> indicating they are all elements that describe Key Performance Indicators.
Discussion
The purpose of the pattern is to allow a Business Analyst, Business Architect or other stakeholder to create a KPI framework using a hierarchy of elements in a Class diagram. A variety of line styles are used to make the hierarchy more appealing

The hierarchy (or framework as it is sometimes called) is typically created during the modeling of an enterprise and can be used across any number of initiatives as a set of indicators to track the progress or success of an endeavor.

The following is a list of some things you may want to do when working with this pattern.
·	Change the name of the diagram to suit the initiative.
Change the name of the elements to suit the initiative.
Create additional elements and adjust the hierarch of elements to suit the enterprise.
Add notes and other properties to elaborate the elements.

The following is a list of some of the next steps available when applying the pattern.
·	Deepen the hierarchy by adding an additional level.
Create trace relationships between the KPIs and other element sin the model.
Generate a wall chart using the automatic documentation generator using large format paper.
Reference
The following help topics will assist you learn about how to work with this pattern.
Metrics and Key Performance Indicators (KPIs)
Connector Styles
Business Analysis Body of Knowledge (BABOK)
Traceability Tools
Documentation

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 or the more general topic on Model Publishing.
Element Discussions
The Element Discussion facility is a fully featured collaboration tool allowing modelers and model viewers and reviewers to communicate with each other directly inside the repository. Modelers using the full client or occasional viewers using WebEA can both post and reply to discussions and communicate and engage in chat. For more details see the Element Discussions help topic.
Specification View
The Specification View can be used as a way of working with any element type in a spreadsheet or word process view. It is particularly useful 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.