Project Requirement Specifications (PRS).
Typical content would include:
Overview of the project, its purpose, and the context in which it will be implemented.
Project Scope defining the boundaries of the project, including what is included and what is excluded.
Functional Requirements of the project including interactions with users or other systems.
Non-functional Requirements such as criteria related to compliance, performance, reliability, security & usability.
Technical Requirements providing detail about the equipment and technology proposed for the project.
Constraints or restrictions that need to be considered during the development process.
Dependencies on external factors that the project may rely upon.
Assumptions made during the requirement gathering process.
Acceptance Criteria that must be met for the project to be considered successfully completed.
Identification and assessment of potential risks that may impact the project.