A functional requirement document defines the functionality of a system or one of its subsystems. It also depends upon the type of software, expected users, and the type of system where the software is used. Functional user requirements may be high-level statements of what the system should do but functional system requirements should also describe clearly the system services in detail


1. It should be a user-friendly and comfortable system. 

2. Must be able to use the Internet. 

3. Employee details should be available. 

4. Employee details should be able to be updated. 

5. Inventory information should be available. 

6. Inventory should be able to be identified separately.

7. Inventory information should be editable. 

8. Must be able to change or retrieve inventory prices. 

9. Information about services should be available. 

10. New services must be able to be added. 

11. It should be possible to change or obtain prices for services. 

12. Customer details should be available. 

13. Customer details should be changeable. 

14. Customers should be able to book services. 

15. Customers should be able to opt out of booked services. 

16. Employees must be able to provide services. 

17. Employees should also be able to opt out of providing services. 

18. Details about the cashier should be available. 

19. Must be able to confirm cashier transactions. 

20. Customer payment details should be available.




***