Prompt Template for Generating an FRD

Please generate a Functional Requirements Document (FRD) for a web development project based on the details provided below. The FRD should be clear, structured, and detailed enough to serve as a blueprint for development. 

Project Name: [INSERT PROJECT NAME HERE]

Business Requirements:
[INSERT THE BUSINESS REQUIREMENTS (project points) HERE]

Planned Features:
[INSERT A DESCRIPTIVE LIST OF THE FEATURES THE LEARNER IS PLANNING TO DEVELOP]

Guidelines:
- **Introduction & Project Overview:** Summarize the project, its purpose, and key objectives.
- **Objectives & Goals:** Clearly outline what the project aims to achieve.
- **Functional Requirements:** Provide a detailed description of each planned feature, explaining how each will function and interact with the system.
- **Non-Functional Requirements:** Include requirements related to performance, scalability, security, and usability.
- **Assumptions & Constraints:** List any assumptions, limitations, or dependencies that could impact development.
- **Acceptance Criteria:** Define the conditions that must be met for the project to be considered complete.
- **Additional Notes:** Any further details or clarifications that can help in understanding the project requirements.

Please structure the FRD with clear headings and subheadings to ensure readability for both developers and team leads.

Example

Please generate a Functional Requirements Document (FRD) for a web development project based on the details provided below. The FRD should be clear, structured, and detailed enough to serve as a blueprint for development.

Project Name: Student Result Management System

Business Requirements:
📚 Imagine a magic notebook where teachers can write down students’ grades and update them anytime. This system will:
- Let teachers add, change, or remove student records easily.
- Keep all student data safe in a digital box (MongoDB).
- Have a special login so only teachers or school staff can see and change the grades.

Planned Features:
- Easy Login and Logout: Allow teachers and school staff to sign in and out safely.
- Managing Student Records: Provide simple ways to add, update, view, and remove student information.
- Safe Digital Storage: Save all student details in a secure digital storage system.
- Smooth System Communication: Create simple connections so different parts of the system can work together easily.
- Keeping Things Secure: Make sure that only the right people can see and change the records.
- Helpful Error Messages: Show clear and friendly messages if something goes wrong.
- Clear Instructions: Write easy-to-understand guides and notes on how each part of the system works.

Guidelines:
- **Introduction & Project Overview:** Summarize the project, its purpose, and key objectives.
- **Objectives & Goals:** Clearly outline what the project aims to achieve.
- **Functional Requirements:** Provide a detailed description of each planned feature, explaining how each will function and interact with the system.
- **Non-Functional Requirements:** Include requirements related to performance, scalability, security, and usability.
- **Assumptions & Constraints:** List any assumptions, limitations, or dependencies that could impact development.
- **Acceptance Criteria:** Define the conditions that must be met for the project to be considered complete.
- **Additional Notes:** Include any further details or clarifications that can help in understanding the project requirements.

Please structure the FRD with clear headings and subheadings to ensure readability for both developers and team leads.