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 from by Dev Studio by clicking Configure > Application > Profile > Requirements.

What are requirements?

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"

Using the requirements list

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.

  1. Use filters to narrow down results:
    • Application — Specify the application name(s) whose requirements you want to see. By default, only your current application is selected.
    • Importance — Select which importance levels to include in the results. All values are selected by default.
    • Status — Select the specification status. For example, you may only want to see InProgress specifications or ignore Withdrawn ones. By default, all status values are selected.
    • Search — Enter a string in the search box to only see requirements with a matching name or short description.
  2. Revert all your filter selections by using the Clear Filters button. You can reset individual filter selections by clicking on the filter name and selecting the Clear All option.
  3. Choose the presentation mode that best suits your needs:
    • List view — displays requirements in a simple list format, without headers. This is the default view.
    • Grid view — displays each requirement in a formatted table with labeled columns.
  4. Create or edit requirements on an individual basis.
  5. Use the Actions menu to export or import requirements in bulk.
  6. Click Reload to update the table with your changes.

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:

  • Name — A unique identifier for the specification.
  • Short Description - The specification's label, typically describing its purpose.
  • Status — The current development status.
  • Importance — A numeric value indicating priority order for a requirement.
  • Release - The target release.
  • Iteration - The target iteration.
  • Updated By — The operator who last updated the specification. Click to view the OperatorID form.
  • Updated - The time in days when this specification was last updated, relative to the current system time.
  • Associations - Click the icon to open 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 Developer Studio. A number appears next to the association icon to indicate the number of links to a requirement. Not all requirements will have associations.

Click the gear icon to see the 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 Withdrawn and remove it from the grid.
Note: When viewing requirements in a list mode, you can click View Related Attachments icon to launch the attachments modal.