Quality-check requirements

Important:

This feature is currently part of an audit process and is not to be considered part of the FedRAMP Authorization until the review is finalized. See here the full list of features currently under review.

This page lists guidelines for evaluating requirements in Test Manager.

Additional instructions

This section provides guidelines for enabling Autopilot^TM to evaluate the quality of a requirement.

Guide Autopilot^TM by providing additional instructions in the Provide Additional Guidance screen. Use the out-of-the-box prompts from the Prompt Library, which help analyze requirements for performance-related aspects, analyze requirements for security-related aspects, and analyze requirements from many different perspectives such as consistency, clarity, and completeness. Add your own custom prompts to the Prompt Library, especially those you frequently use for evaluating the quality of your requirements. For example, create prompts for other software quality attributes. To generate a specific number of enhancement suggestions Autopilot^TM should generate for your requirement, instruct Autopilot with commands like "Generate the top 20 enhancement suggestions for this requirement and rank them by priority".

Supporting documents

This section lists various types of supporting documents you can provide to Autopilot^TM. Consider these documents as additional information that enhances the description of a requirement in Test Manager. Because these documents complement the requirement description, Autopilot also offers suggestions to enhance their quality. Essentially, the definition of your requirement is shaped by both requirement description and all associated supporting documents.

Security guidelines

Consider providing security guidelines, policy documents, or security audit findings. Autopilot will review these documents to check for any inconsistencies or discrepancies within them or between these documents and the security aspects outlined in the requirement description to ensure that security criteria are both comprehensive and accurately represented.

Accessibility guidelines

Consider providing accessibility guidelines, audit reports, or user accessibility specifications. Autopilot will evaluate these supporting documents to cross-check their alignment with the accessibility criteria stated in the requirement description. This evaluation helps confirm that the guidelines are effectively integrated into the requirement and are free of contradictions.

Compliance checklists

Consider providing compliance checklists, regulatory summaries, or compliance requirements relevant to your industry. Autopilot will assess these checklists to ensure that they are consistent with the compliance criteria described in the requirement description. This helps in identifying any potential inconsistencies or gaps in regulatory adherence.

Functional limitations

This section outlines the current limitations of Autopilot^TM.

Supported file types

You can only upload the following file extensions, from which Autopilot processes only the text content:

• DOCX
• XLSX
• TXT
• CSV
• PNG
• JPG
• PDF
• BPMN

Note: Autopilot processes only the text content in the files. Images within the files are not processed.

Input token capacity

The input token capacity of Autopilot is 128,000 tokens, which is equivalent to approximately 96,000 words, or 512,000 characters.

Ensure that your requirement description and supporting documents do not exceed these limits.

Tip: From our observations, 100 tokens roughly translate to approximately 75 words or 400 characters.

To check the approximate token count of your documents, open the document as a TXT file and copy the content into the Open AI Tokenizer tool The provided token count is an approximate. The actual token count can be higher.

Suggestion generation

Autopilot can generate a maximum number of 50 suggestions at a time. If a number of suggestions is not specified, then Autopilot generates the top 15 suggestions.