Requirement Element

What are Requirement Elements?

A Requirement Element is an individual requirement for the Project. Requirement Elements can be categorised as either Functional or Non Functional.

Requirement Elements can reference Design Elements and an Ensure Traceability Tool exists within the Design Phase of the Phase Progression to help highlight omissions and fix any missing references.

Requirement Element Properties

Name Description Possible Values
ID Unique Element reference number. Number - Generated by the application.
Requirement Full description of the Requirement. Text.
Acceptance Criteria Full description of the standard to which the Requirement is to meet. Text.
Type Used to classify Requirements. Non Functional or Functional.
Priority Used to prioritise Requirements using MoSCoW Method. Must, Should, Could or Won't.
Owner The person who has been assigned ownership of the Requirement. User with Project access or text.
Originator The person who requested the Requirement. User with Project access or text.
Design References Traceability links to Design Element's of the Solution Design. Selection of Design Elements references.
Attachments Files in support of the Requirement Element. List of Attachments.

Locating Requirement Elements

Requirement Elements can be located in the following Documents:

Document Can Manage
Requirements Specification
Design Approach Plan
Design Specification

Managing

Requirement Elements may be edited directly in the TreeList. Single-clicking on a cell of the currently selected item will put that cell into "Edit Mode". Double-clicking a cell of an item that is not currently selected will achieve the same result (first click selects item, second click enables edit mode).

The Owner and Originator properties of a Requirement Element can be set to reference a User or text. If a User is selected from the drop-down any previously entered text will be removed and vice versa.

Because the TreeList features "Inline Editing", changes are not saved directly after they have been made like most of the application, they must be managed by the use of the Document Save and Document Cancel features located at the bottom right of the Document.

The Document Save feature can be used to save any changes to the Requirement Elements. Navigating to different tabs or triggering a child window to open will also trigger a save for any changes made.

The Document Cancel feature can be used to cancel any changes to the Requirement Elements, this includes rejecting any changes to elements that have yet to be saved, reinserting removed elements and removing newly created ones.

Upon successful completion of saving changes a success message will display at the bottom of the application.

Creating a new Requirement Element

Clicking on the New button will create a new Requirement Element directly underneth the current selection.

Indenting Requirement Elements

Selecting a Requirement Element and clicking on the Indent button will indent that Requirement Element making it a child of the element above it.

In order to indent the selected Requirement Element there must be a element directly above it that is not already the parent.

The same can be achived by using the drag-drop feature of the Treelist, see Reordering.

Outdenting Requirement Elements

Selecting a Requirement Element and clicking on the Outdent button will outdent that Requirement Element removing it from the child collection of the parent element above it.

The currently selected Requirement Element must be a child of another element in order to outdent.

The same can be achived by using the drag-drop feature of the Treelist, see Reordering.

Reordering Requirement Elements

Requirement Elements can be reodered in the list using the drag-drop feature of the Treelist.

Dragging a Requirement Element over the others in the list will display a small overlay underneth the cursor that will indicate where to "drop" the element. There are 3 options displayed depending on the position of the cursor against the row it is hovering over:

  • Before - drops the element before the element the cursor is hovering over.
  • Inside - drops the element inside, making it a child of the element the cursor is hovering over.
  • After - drops the element after the element the cursor is hovering over.

Removing Requirement Elements

Selecting the Requirement Element to remove and clicking on the Remove button will display a removal confirmation window. If Cancel is clicked the confirmation window will close and the Requirement Element will not be removed. If Yes is clicked the selected Requirement Element will be removed from the TreeList.

Managing Attachments

Clicking on the Manage button will display the Manage Requirement Element Attachments child window for the currently selected Requirement Element. From here new files can be attached and existing Attachments can be downloaded or removed. See Attachment for features.

Managing Design References

Selecting a Requirement Element and clicking on the Manage button will display the Manage Requirement Element References child window.

The Manage Requirement Element References child window will display a DataGrid listing the current Project's Design Elements with an extra Reference column.

Referencing a Design Element can be achieved by checking the corresponding checkbox in the Reference column.

Once all references are set, the Close button can be clicked to close the child window.

If any Design Elements are referenced using this feature the Requirement Element will count as being edited.

Importing Requirement Elements

The Requirements Specification has the ability to import Requirement Elements from other Projects via the Import feature of the Document.

Clicking the Import button will display the Import Document child window.

In order to view and import Requirement Elements from another Project, a Project must be selected from the "Import from Project" drop-down at the top. The drop-down is populated with any other Projects in the application.

From the import button there are two options for importing Requirement Elements within the Requirements Specification:

Import Current Tab - Imports all data on the currently selected tab. If the intention is to import Requirement Elements, the selected tab must be the Requirements tab.

Import All - Imports all Document data, including any Requirement Elements identified on the Requirements tab.

Upon successful import the Import Document child window will close, a success message will be displayed at the bottom of the application and the last of the newly imported Requirement Elements will be selected.