Creating custom values for specifications and requirements
On the Application Profile landing page, you can create and modify specifications and requirements. You can customize some menu items on these forms to better represent the methodology and terminology of your project.
Requirement and Specification status values
Both requirements and specifications have a Status value that indicates its current implementation status in the project development cycle.
To add custom values to the list of standard status values, create a field value in one of your application rulesets:
- Applies To : For specifications, enter Rule-Application-UseCase; for requirements, enter Rule-Application-Requirement
- Field Name : For specifications, enter pyCategory; for requirements, enter pyStatus
- Field Value : [Your custom value for this field]
To prevent the standard status values from appearing as menu choices at all, save copies of these field values into one of your application rulesets and change the
availability
from
Available
to
Blocked
:
Value as it appears in menus | Specification standard field values | Requirement standard field values |
---|---|---|
Complete
|
Rule-Application-UseCase.pyCategory.Complete | Rule-Application-Requirement.pyStatus.Complete |
New
|
Rule-Application-UseCase.pyCategory.New | Rule-Application-Requirement.pyStatus.New |
InProgress
|
Rule-Application-UseCase.pyCategory.Open | Rule-Application-Requirement.pyStatus.Open |
Withdrawn
|
Rule-Application-UseCase.pyCategory.Withdrawn | Rule-Application-Requirement.pyStatus.Withdrawn |
Pending-Development
|
Rule-Application-UseCase.pyCategory.Pending-Development | Rule-Application-Requirement.pyStatus.Pending-Development |
Pending-Deferred
|
Rule-Application-UseCase.pyCategory.Deferred | Rule-Application-Requirement.pyStatus.Deferred |
Pending-Blocked
|
Rule-Application-UseCase.pyCategory.Pending-Blocked | Rule-Application-Requirement.pyStatus.Pending-Blocked |
Pending-Details
|
Rule-Application-UseCase.pyCategory.Pending-Info | Rule-Application-Requirements.pyStatus.Pending-Info |
Requirement importance values
Requirements are assigned an Importance value which indicates its priority relative to other requirements in the application.
To add custom values to the list of standard status values, create a field value in one of your application rulesets:
- Applies To : Rule-Application-Requirement
- Field Name : pyImportance
- Field Value : [Your custom value for this field]
To prevent the standard status values from appearing as menu choices at all, save copies of these field values into one of your application rulesets and change the
availability
from
Available
to
Blocked
:
- Rule-Application-Requirement.pyImportance.1-Critical
- Rule-Application-Requirement.pyImportance.2-Very Important
- Rule-Application-Requirement.pyImportance.3-Important
- Rule-Application-Requirement.pyImportance.4-Desirable
- Rule-Application-Requirement.pyImportance.5-Useful
Requirement category values
To add custom values to the list of standard requirement Category values, create a field value in one of your application rulesets:
- Applies To : Rule-Application-Requirement
- Field Name : pyCategory
- Field Value : [Your custom value for this field]
To prevent the standard status values from appearing as menu choices at all, save copies of these field values into one of your application rulesets and change the
availability
from
Available
to
Blocked
:
- Rule-Application-Requirement.pyCategory.Business Rule
- Rule-Application-Requirement.pyCategory.Change Control
- Rule-Application-Requirement.pyCategory.Enterprise Standard
- Rule-Application-Requirement.pyCategory.Functional
- Rule-Application-Requirement.pyCategory.Non Functional