Requirements Specification

In this section, the functional, non-functional, hardware and software requirements

of the system are to be discussed.
Functional Requirements
1. Registration of the administrator to the database
1.1. The user accounts must be registered to the database first for the system to be
connected on the database.
1.2. Registration on the database composed of the server name (given name for the
database), username and password and the roles and permissions given..
1.3. The admin need to enter username and password that he or she registered to the
system and the roles and permissions given.
2. Registration of admin to the system
2.1. The admin must be registered together with their information.
2.2. Admin information must be composed of first name, middle name, last name,
address, date employed, age, contact number, position, fingerprint scan, and photo
for the identification.
2.3. Admin need username and password for entering to the system and the roles and
permissions given.
3. Registration of employee/user
3.1. The user must be registered together with their information.

3.2. User information must be composed of first name, middle name, last name,
address, date employed, age, contact number, position and fingerprint scan, and
photo for the identification.
4. Information of Employees in the system
4.1. The employee information must be input in the system.
4.2. Employee records form must be composed of employee id, employee name, age,
address, contact, position, and date employed.
5. Viewing of Records
5.1 To view DTR Printing form, the admin, who had the permission to open the
system, can use the searching tab, the day, month, date and year to view employee
record
5.2 The record form composed of employee id, employee name, time in, time out,
date, hours worked.
6. Printing of reports
6.1 Employee records must be input in the system.
6.2 Show Report button will allow seeing all the records needed.
6.3 After seeing the records needed and ready to print, a Print button will allow to
provide a hardcopy of all reports needed.
Non-Functional Requirements
The researchers of the study considered the Non-Functional Requirements of the
system in order to create a better outcome of the study. These requirements specify

criteria that were used to judge the systems operation and are just critical as the
functional features as it assures the usability and efficiency of the entire system. These
are the following non-functional requirements that were done by the researchers of this
study.
1. Security
The system at any given time can only be used by an authorized user,
administrator. The database must be secured from unauthorized access. The
system will only have users inside Hearty Beverage Options, Inc.
2. Performance
The system is expected to provide information needed which is only
registered on the system. Responses of system on a users request identification
for information shall not take more than a minute to load.
3. Reliability
The system is expected to handle errors and prevent data loss and long
downtime period. The time to recover if an error occurs depends upon the
situation, but is expected to recover as soon as possible.
4. Availability
The system is available 24 hours because of shifting hours of workers in the
company.
5. Maintainability
The system should be easy to use by the Hearty Beverage Options, Inc
personnel for they are the main users of the program. It should also be easy for
the personnel in charge with the maintenance to use.