Getting Started with Requirements

The Getting Started section provides a high-level description on how to use requirements. For detailed procedures on using requirements, see the How To section.

Requirements are business features or functions that describe how your application should work. When the Certify processes are executed against the application that you are testing, the pass/fail status of the execution determines whether or not the requirement is satisfied.

Certify supports a wide set of information for each requirement, including:

Risk
Priority
Estimated and actual efforts
Percent complete for your project

Furthermore, you can attach an associated source document from your local network and open it from Certify. This feature allows you to further customize the information associated with a requirement by recording the information as a user-defined attribute.

Requirements can be exported to a comma-separated value (CSV) file for use in reporting or in other applications.

If a requirement is locked, you are only able to view the requirement. When you select a locked requirement, a message appears stating that the requirement has been locked and cannot be edited.

Understanding Child Requirements

You can create any number of levels of parent and child requirements, but no two requirements can have the same name at the same level. Requirements are linked only at the process level. During process execution, a parent requirement will only be fulfilled if all of the child requirements have been met.

When child requirements are created, they share the same attribute values as the parent requirement. These values can be changed for each child requirement you create.