functional-requirements

To generate functional requirements from customer needs, you can use a Problem-Based SRS methodology process that transforms each Customer Need and the software vision into individually traceable Functional Requirements.

In a Problem-Based SRS, Functional Requirements define what the system SHALL DO to address Customer Needs, while Non-Functional Requirements capture necessary quality attributes like performance, security, and usability.

Traceability between customer needs and software requirements is established by generating per-CN FR and NFR files along with index files, linking each requirement artifact directly to its originating Customer Need.

Yes, you can create non-functional requirements for performance and security by identifying and capturing necessary quality attributes derived from the customer needs and the overarching software vision.

Before generating functional and non-functional requirements, you need to prepare structured Customer Needs and a defined Software Vision to serve as the foundational inputs for the requirement transformation process.

You should use a problem-based approach for software requirement specification when your project requires a strict hierarchy where Customer Needs drive FRs and NFRs with built-in traceability for validation and auditing.