backlog prompt

Create a detailed backlog for the following requirement in my project, including user stories, actions to undertake, references between files, list of files being created, acceptance criteria, testing plan, and any other relevant details.

The backlog should include the following elements:

1. **User Story**: Write a clear and concise user story that describes the desired functionality or feature, including the user's role, goal, and expected outcome.
2. **Actions to Undertake**: Break down the user story into specific, actionable tasks that need to be completed to deliver the desired functionality. These tasks should be described in detail, including any necessary steps, inputs, and outputs.
3. **References between Files**: Identify any relationships or dependencies between files that will be created as part of the project, including data flows, APIs, or other integrations.
4. **List of Files being Created**: Provide a comprehensive list of all files that will be created as part of the project, including code files, documentation files, and any other relevant artifacts.
5. **Acceptance Criteria**: Define clear and measurable acceptance criteria for each user story, including any specific requirements or constraints that must be met.
6. **Testing Plan**: Describe the testing approach and methodology that will be used to validate the acceptance criteria, including any test cases, test data, and testing tools.
7. **Assumptions and Dependencies**: Identify any assumptions or dependencies that are being made as part of the project, including any external dependencies or third-party libraries.
8. **Non-Functional Requirements**: Describe any non-functional requirements that are relevant to the project, including performance, security, or usability considerations.

The backlog should be written in a clear and concise manner, with proper formatting and headings to facilitate easy reading and understanding.

Please include the following sections in the backlog:

* **Introduction**
* **User Stories**
* **Actions to Undertake**
* **References between Files**
* **List of Files being Created**
* **Acceptance Criteria**
* **Testing Plan**
* **Assumptions and Dependencies**
* **Non-Functional Requirements**
* **Conclusion**

Use the following format for each user story:

* **User Story [Number]**: [ Brief description of the user story]
	+ **Description**: [Detailed description of the user story]
	+ **Actions to Undertake**: [List of specific tasks to complete]
	+ **References between Files**: [List of relationships or dependencies between files]
	+ **Acceptance Criteria**: [Clear and measurable criteria for acceptance]
	+ **Testing Plan**: [Description of the testing approach and methodology]

Use the following format for each file being created:

* **File [Number]**: [File name and description]
	+ **Purpose**: [ Brief description of the file's purpose]
	+ **Contents**: [Detailed description of the file's contents]
	+ **Relationships**: [List of relationships or dependencies with other files]

Use the following format for each test case:

* **Test Case [Number]**: [ Brief description of the test case]
	+ **Test Data**: [Description of the test data used]
	+ **Expected Result**: [Description of the expected result]
	+ **Testing Tool**: [Description of the testing tool used]

Please provide a comprehensive and detailed backlog that covers all aspects of the project, including user stories, actions to undertake, references between files, list of files being created, acceptance criteria, testing plan, assumptions and dependencies, and non-functional requirements.

**Output Format**: Please provide the backlog in a markdown format, with proper headings, subheadings, and formatting to facilitate easy reading and understanding.


[start of requirements]