Book a Demo
Prev Next

Governance Toolbox

The 'Governance' Toolbox page provides icons to create project management elements and Artifacts, to generate Requirement, Maintenance and Review elements and documents and structures to show what development either should be performed or has been performed.

Types of Governance Artifact



See also


A Requirement element captures the details of a system requirement.

Requirements Diagram


A Change element represents a change in the defined requirements for the current system and can be used to request and manage the change process.



An Issue element represents an item of concern that might or might not arise, or a failure to meet a defined requirement in the current system.



A Review element enables you to define a formal review of a part of the model, in particular a small number of elements and/or diagrams. Each Review element enables you to define when the review should start and end, and which members of the team are responsible for performing the review.

Model Reviews

Discussion Artifact

The Discussion Artifact provides a place to host a discussion about a particular part of a model, rather than discussing a specific element.

Drag the Discussion Artifact onto a diagram where you want to discuss some aspect of the model, and give the Artifact a name. You might want to outline the purpose and scope of the discussion in the Notes and perhaps even add a Linked Document where you record decisions resulting from the discussion.

Model Discussions

Checklist Artifact

A Checklist Artifact provides the facility for generating a list of items, each with a checkbox, to be used as a checklist. You can set each checkbox to default to being selected or unselected, and set all selected options to be grayed out or struck through, so that the unselected options are more prominent. The end users can then work with the element to tick off items that have been obtained or activities that have been completed.

A version of this Artifact - the Requirements Checklist - is available in the 'Extended Requirements' Toolbox page. This automatically contains ten characteristics of a good Requirement, for a Requirement author to tick off as they check that their Requirement has been set up to show those characteristics.

Requirements Checklist Using the Checklist and Audited Checklist Artifacts

Audited Checklist Artifact

The Audited Checklist is an extension of the Checklist Artifact, having an associated 'Audit Records' page. It is a useful tool for Project Management, providing the facility to monitor accountability and track completion of tasks.

Using the Checklist and Audited Checklist Artifacts

Matrix Specification Artifact

A Matrix Specification Artifact encapsulates a Relationship Matrix Profile definition. When you have created the element on the diagram, you double-click on it to display the 'Matrix Specification' dialog, in which you create the Profile definition. The Profile takes the name of the element. The Profile defined in the Artifact is independent of the Package that contains the Artifact element, and therefore could specify source and target Packages other than the parent Package.

After you create the Profile definition, each time you double-click on the Artifact element the Relationship Matrix displays with the Profile applied.

To edit the Profile, right-click on the Artifact and select the 'Documentation | Edit Matrix Profile' option.

Create Matrix Profile

Feature Mapping Artifact

The Feature Mapping Artifact saves a profile that represents a particular combination of field values specified in a Feature Matrix.

The Artifact is usually created by clicking the Options button on a Feature Matrix view, then choosing the option 'Profiles | Save as new Profile'. The Artifact is added to the diagram's parent Package as an <<EAFeatureMapping>> Artifact, and the profile name displays at the end of the 'Profiles' sub-menu.

If you drag the icon from the Toolbox page onto a diagram, a Feature Matrix template displays and you can adjust the field values to create the profile. Note that in this context you drag the source and target elements from the Browser window into the 'Source' and 'Target' fields, ensuring that they have relationships between attributes, operations or receptions..

The Feature Matrix

Learn More