Please enable JavaScript.
Coggle requires JavaScript to display documents.
Functional and Non-Functional Requirements (Reservation (Functionial (User…
Functional and Non-Functional Requirements
Reservation
Functionial
User registration: User must be able to register by filling in a form including all the necessary details e.g. email. All the details will be stored in a database.
User Login: User should be able to login with a username and password, if they had always registered.
Contact the company: User should be able to contact the company with any queries they may have about their reservation.
Booking: User should be able to book and check the availability.
Non-Fuctional
Usability: The system should be easy to use regardless of technical ability
Performance: The reservation system should enable the person booking to complete a reservation in x minutes.
Manageability: System to prevent double booking should warn user clearly that a double-booking attempt is in progress.
Payroll
Non-Functional
Security- Having protected software ensures there is no tampering of information of employees' wages.
Manageability - Ease of keeping track of records for all staff and all their different pay rates.
Efficiency- Integration means that relevant data is only entered once.
Performance – Wages need to be added to the employee’s accounts on time.
Functional
Business Requirements
Pay your employees in either a weekly or monthly payment schedule
Calculate the total amount of money that a company pays to its employees
Make exception report so that if an error occurs during the processing the error is corrected
Regulatory/Compliance Requirements
Generate electronic fund transfers
Calculate commission amounts
Calculate payroll taxes
Report tax deduction to the revenue service
Utility Billing
Functionial
Software shall provide the ability to have different rate structures
Software shall provide the ability to bill for a selected group of customers quarterly
Software shall provide the ability to bill more than one party for the same account
Software shall provide real-time access to customer account activity, to include payment activity performed with web functions
Non-Fuctional
Integrity: Ensure there are no duplicate bills or missed bills for customers.
Performance: A full bill run should take no more than 4 hours.
Availability: System should be available 99% of the time.
Stock Control
Functionial
When the shock level for a product falls below its re-order level, a re-order request should automatically be generated.
Enable accountability for stock, at any time;
Enable the provision of up-to-date information about all stock in the care of the organization
Provide the current location of each object.
Non-Fuctional
Performance: the sale of an item at a POS terminal should be recorded in the database within x seconds.
Usability- someone who is new, learn how the control system works easily and without any problems
Security- accessible and usable only in authorized ways by authorized users.
Manageability - ease of keeping track of records and changes to them.
The definitions of functional and non-functional requirements
The definition of a functional requirement is to specify the activities that a system must be able to perform or provide for users.
The definition of a non-functional requirement is to describe how the system works and can also be measured