Nội dung cho những bạn không giỏi nghe tiếng Anh (mà có thể đọc hiểu tiếng Anh :-)

1 INTRODUCTION
• Follow the BABOK definition
• 3 broad types of requirements • Business requirements • User requirements • Solution requirements

2 BUSINESS REQUIREMENTS
• Describe needs of the organisation as a whole
• Statements that provide vision, scope and direction of the project
• Express why the project is being undertaken
• Can’t be directly implemented in the system • “To meet obligations to key international conventions, the business must deliver annual reports on the collection, management and disposal of hazardous waste in Australia." 

3 USER REQUIREMENTS
• Serve one or more business requirements
• Also called stakeholder requirements
• Express how users need to interact with the solution 
• The bridge between business requirements & solution requirements

• Examples: • View a waste report by date range, jurisdiction and waste category. • Submit a report for delegate approval to be published.

4 SOLUTION REQUIREMENTS
• Describe the capabilities of the system
• CAN be directly implemented in the system
• Functional requirements - describe the behaviour of the system, or what the system is supposed to do
• Non-functional requirements - describe the conditions of the system, or how the system is supposed to be

• Examples of functional requirements • Display report data by date parameters (to and from) • Display report data by jurisdiction • Display report data by waste category • Save a report as draft • Notify a delegate of a pending review • Publish a report to PDF

• Examples of non-functional requirements • Capable of operating within the organisation’s Desktop Standard Operating Environment • Integrate with Active Directory to enable single sign-on • Be available during standard production /business hours • Respond within 2 seconds to direct manipulation of user interface objects by the user 

5 TRACEABILITY
• All requirements should link together in a traceability matrix
• This forms the full scope of the solution
• Any left over requirements may need to be removed from scope
• Achieve fully traceable set of requirements

Keywords: business requirements, user requirements, stakeholder requirements, solution requirements, functional requirements, non-functional requirements, requirements traceability, business analysis, requirements analysis