Non-Functional Requirements

As part of the PRD creation, PRD-AI generates Non-Functional Requirements (NFRs) to identify and capture areas (such as scalability, compatibility, and maintainability) that need to be considered during app development.

NFRs are provided in their own category called Non-Functional Requirements at the bottom of Phase 1 on the Phases & Features tab. Each NFR area (or type) looks and functions just as any other feature. 

Note: Syncing Azure Costs Estimates and PRD NFRs

Azure Costs Estimation and the NFRs in the PRD synchronize to ensure consistency between resource planning and cost calculations.

• If you edit criteria in the Azure Cost Estimate, PRD-AI automatically updates all impacted NFRs in the PRD upon save. You don't need to do anything else.

• If you update an NFR acceptance criteria that affects the Azure Cost Estimate (such as concurrent users or active users), when you view the Azure Costs Estimation, you get a prompt to refresh because the estimates are out of sync with the PRD.

This synchronization can take a few moments to propagate. Watch for notifications in the upper-right corner of the window.