• Dùng để trả lời câu hỏi "Why"
• Lãnh đạo, cấp quản lý

These should describe the overall goal in developing the product , high level descriptions of what the product will do, how they are aligned to business objectives, and the requirements for interaction with other systems

Provide a brief history of how the project came to be proposed and initiated , including the business issues/problems identified , and expected benefit of implementing the project /developing the product

List the business drivers that make development of this product important. These can be financial, operational, market or environmental

1. Xác định In Scope
   

2. Xác định Out of scope

Describe what work is in scope for the project, and specifically what works is out of scope .... beyond the current budget, resources and timeline as approved by the project stakeholders .This is designed to prevent "scope creep" of additional features and functions not originally anticipated

Outline all various phase of the project along with the deadline for each phase

• Phase 1 : Complete [What] by [Date]
• Phase .....

The specific business requirements elicited from stakeholders should be listed, categorized by both priority and area of functionality to smooth the process of reading and tracking them . Include links to use case documentation, and other key reference material as needed to make the requirements as complete and understandable as possible. You may wish to incorporate the functional and non-functional requirements into a traceability matrix that can be followed throughout the project

Nếu lãnh đạo cấp cao thì không cần mô tả functional và non-functional

• Dùng để trả lời câu hỏi "What"
• Nếu BRD đã mô tả chi tiết rồi thì không cần SRS
• Có thể một số bên sẽ chỉ mô tả Feature list
• PM,Subject Matter Expert

Functional Requirements

Performance and scalability.
How fast does the system return results? How much will this performance change with higher workloads?

Portability and compatibility.
Which hardware, operating systems, and browsers, along with their versions does the software run on? Does it conflict with other applications and processes within these environments?

Reliability, maintainability, availability. How often does the system experience critical failures? How much time does it take to fix the issue when it arises? And how is user availability time compared to downtime?

Security.
How well are the system and its data protected against attacks?

Localization.
Is the system compatible with local specifics?

Usability.
How easy is it for a customer to use the system?

• Dùng để trả lời câu hỏi "How"
• PM,Dev,QA/QC