Using the Application Profile Requirements tab |
The Requirements tab in the Application Profile landing page allows you to review, create, and delete application requirements. Additional options allow you to view associations and export or import requirements using Excel.
Access this tab by selecting the > Application > Profile > Requirements menu item.
Think of a set of requirements as the inventory of events, conditions, or functions that must be satisfied and tracked in your development project. A good requirement describes a need in business terms, has an identified category type, is testable, and indicates an implementation state (such as ‘Open’ or ‘Withdrawn’).
Examples of requirements include:
"The remaining budget must be calculated to two decimal points"
"The Routing Transit Number must be 9 digits long"
The requirements table is an interactive list that helps you quickly assess the state of your requirements and make modifications without switching context. Unless otherwise noted below, all available options are selected by default. Get started with the following steps:
1-Critical
to 5-Useful
. All values are selected by default.InProgress
requirements or ignore Withdrawn
ones. By default, all status values are selected.
When using the grid view, the requirements table is organized into the following columns. Click on any row to launch the Add/Edit Requirement dialog:
Column |
Description |
Name | A unique identifier for the requirement. |
Short Description | The requirement's label, typically describing its purpose. |
Status |
The current development status. |
Importance | A numerical value indicating priority order for a requirement. Importance can range from 1-Critical to 5-Useful . |
Updated By | The operator who last updated the requirement. Click to view the OperatorID form in the work area of the Designer Studio. |
Updated | The time this requirement was last updated (in days), relative to the current system time. |
Associations |
A list of rule types (flows and specifications) linked to this requirement. Click any rule name ruleset version to open it in the work area of the Designer Studio. A number appears next to the association icon to indicate the number of links to a requirement. Not all requirements will have associations. |
A menu of possible actions you can take on a requirement, depending on its state. Select Discard to undo the current checkout of this requirement. Select Delete to set the availability of this requirement to |
Note: When viewing requirements in a list mode, you can click to launch the attachments modal.
The Add/Edit Requirement dialog can be launched by clicking the Create Requirement button at the top of the requirements table or by clicking on any entry (row) in the table itself. Once you have entered the desired information, click OK to save your changes and refresh the requirements table.
Only requirements in unlocked ruleset versions may be modified. If you launch the modal by clicking on a requirement that is in a locked ruleset version, the fields will display in read only mode.
Guidance on entering values in the main modal:
Field name |
Guidance |
Requirement Name |
Required. The name you specify here becomes a key part of the requirement and uniquely identifies the rule. For example, Once a requirement is created, its name cannot be changed and displays as a link; click to open the rule in the work area of the Designer Studio. If you provide a name with spaces, the system will automatically create a concatenated string with camel case formatting. |
Ruleset |
Required. The name of the ruleset that will contain the requirement. Choose from the list of rulesets available to your current application stack. Once a requirement is created, its ruleset name cannot be changed and displays as a link; click to open the rule in the work area of the Designer Studio. |
Ruleset Version |
Required. A version number corresponding to the specified ruleset name. Choose from the list of available, unlocked versions. Once a requirement is created, its ruleset version cannot be modified; it displays as part of the ruleset name link. |
Guidance on entering values in the Details tab:
Field name |
Guidance |
Short Description |
Required. Provide a brief description of the requirement (typically its purpose). A short description may be updated at any time. |
[All other fields] | All other fields on this tab of the modal map to fields found on the Definition tab of the requirement rule itself. |
Guidance on using values in the Associations tab:
How to import, export, and update requirements in bulk |