Managing tagged elements

Basic hierarchy

Before marking any elements in your Word document, a basic hierarchy already exists, as shown in the screenshot below (this window is opened by clicking on the icon in the Scope Manager toolbar).

The basic hierarchy window

Key:

1. The basic hierarchy of elements, consisting of:

· a root for property sets

· a root for enumerations

· a root for requirements

· a root for goal containers

· a root for business rules

· a root for dictionaries

2. A field which shows the description of an element.

3. A "Generate XML file" button, used to launch generation of the XML file which can then be imported into Objecteering.

4. A "Refresh" button, used to refresh the view.

Defining the properties of a marked element

When marking elements in a Word document, you can select where you wish the element to be located.

Requirement containers can be located either under the root requirement container or under a requirement container already marked in the document.

Dictionaries can be located either under the root dictionary or under a dictionary already marked in the document.

Goal containers can be located either under the root goal container or under a goal container already marked in the document.

Business rule containers can be located either under the root business rule container or under a business rule container already marked in the document

Requirements can be located either under the root requirement container or under a requirement container already marked in the document.

Terms can be located either under the root dictionary or under a dictionary already marked in the document.

Goals can be located either under the root goal container or under a goal container already marked in the document.

Business rules can be located either under the root business rule container or under a business rule container already marked in the document.

For example, the figure below illustrates the marking of a requirement and the selection of its location.

Marking a requirement in the "First example requirement container" requirement container

Steps:

1. In the Word document, select the text you wish to use as the definition of the new requirement.

2. In the toolbar, click on the "Requirement" icon. The "Mark requirement" window appears.

3. Enter a name for the new requirement.

4. Select the requirement container which will contain the new requirement.

5. Click on "OK" to confirm.

The new requirement is then located inside the selected requirement container in the hierarchy window, as shown in the screenshot below.

The hierarchy window now shows the new requirement

Key:

1. Everything marked by you (in other words, everything which is not the basic hierarchy) appears in green.

2. The description of the marked element appears in the "Description/Definition" field.

Note: If you click on an element in the hierarchy window, the element is automatically selected in the Word document. This can be particularly useful if you are working with large documents.

Modifying the properties of a marked element

If you want to change the properties (name and location) of a marked element, the properties window is used. This window is opened by clicking on a marked element and then clicking on the "Display properties" icon in the toolbar.

For example, let's imagine we want to change the name and location of the requirement marked in the previous example. Simply carry out the steps shown below.

Modifying the properties of a requirement

Steps:

1. Click on the highlighted text in the Word document.

2. Click on the "Display properties" icon in the toolbar. The "Requirement properties" window then appears.

3. Modify the name of the requirement in the "Name of the element" field.

4. Modify the location of the requirement from "First example requirement container" to "Second example requirement container".

5. Click on "OK" to confirm.

These changes can be seen in the hierarchy window.

Note: If the hierarchy window is already open when modifications are made, it must be closed and then re-opened before changes become visible.