requirement types allow a user to create special type of requirements, each type with its own numbering, security, and required fields and default values. This offers a powerful customization tool for users with specific project needs.
New TestTrack projects are created with the three requirement types listed in the following screenshot. You can use these, modify them to your own needs, or delete them if desired. However, you need at least one requirement type in order to create a requirement.
Creating requirement types
You can create new requirement types from the Tools > Administration menu. Selecting Requirement Types will display a window with your current requirement types. You can use this dialog to change the order the types are displayed in lists. You can also add, edit, delete or inactivate requirement types.
There are several things you can define when creating a requirement type. The name gives a quick label for your type. The description allows you to provide some definition on how you expect this requirement type to be used. You can also select an icon to represent your requirement type in TestTrack.
Finally, you can give your type a tag prefix and suffix. The Tag field is available on the requirement list window and in other places in TestTrack. The prefix and suffix is appended to the requirement number to create the tag. So, if the requirement type has a prefix of “BR-” and a suffix of “s”, then a requirement of this type with a number of 100 would have a tag of “BR-100s”.
Configuring security settings
Once you have your requirements types created, you can create specialized security settings for each type. Security for a requirement type works exactly like security for a requirement. By default, a new requirement type will adopt the common security settings of requirements. However, you can override these settings for each requirement type.
To override security, go to the Security Group list and find the desired security group. Open it for edit and select Requirements under Command Security or Field Security. (The following screenshot sets Command Security for a requirement type, but you would follow similar steps for Field Security). When you navigate to a specific requirement type, a “Use values from” option appears. This is selected by default, meaning the selected requirement type shares the same security settings as a regular Requirement. Clearing this option will create a separate set of security options for the selected requirement type. You can now set security for the selected requirement type.
Configuring Required Fields & Default Values
The other thing you can do with requirement types is configure specific required fields and default values for each requirement type. This is done through the Required Fields & Default Values dialog.
As with security, when you navigate to a specific requirement type, a “Use values from” option appears. Clear this option to create a separate set of values for required fields and their default values for the requirement type.
Finally, you can also create your own custom types by using custom fields with field security. First, create your business types as requirement types. Next, open the Custom Fields dialog and create the fields you want for all the custom types. Then, go to the Security Group list and configure field security so the custom fields you created that are not related to a particular requirement type are hidden by field security. Do this for all of your requirement types. Voila! You now have business types in the Requirements list with unique fields that can be used for specialized purposes.
Do you have any suggestions about how to use requirement types? Have you created any special business objects using requirement types for your own company?