1. Project Report Human Resources Database
Jenny Jung, Sabrina Hill, Jordan Dameron, Shiryra Crabb
Trickum Ops LLC dba Bojangles’
Discovery Process:
To start the human resource database at Trickum Ops LLC doing business as Bojangles’,
we needed supporting documents and interviews to understand what our primitives needed to be.
We were able to interview Rhonda Dameron, a representative of Bojangles’ Human Resource
Manager. She provided vital informations to help us identify the issue for current database and
guided what she wanted us to do for redesigning the database. One of the current database’s
incapability was the hiring process. They use two database system to complete the hiring
process: ADP Workforce & Sysdine. Currently, the company uses both ADP and sysdine
systems because they need Sysdine’s applicants form for ADP’s outsourcing. When an
application is turned in to Sysdine, Rhonda has to manually add Sysdine’s data to ADP system.
After the interview, our objectives are to drop Sysdine application process and to combine the
two processes into one database system. Being able to interview an insighter from Bojangles HR
management, we were able to structure out how we would need to create the companies
database. After analyzing the company with information provided to us by the company we are
in the process of creating an ERD structure that would incorporate the business structure into
one.
Meeting Minutes:
First Meeting February: Upon receiving information about the company, we discussed what
types of operation we would undertake for the project. As our initial task, it was critical for us to
meet with Rhonda Dameron and ask her a list of questions for Jordan to pose to Rhonda (See
attached sample questions). Our group also scheduled next group discussion through Skype.
Brief Skype Discussion: Team members were able to assess information and share information
over conference call. Rhonda’s responses gave us a significant amount of materials through
Jordan. We scheduled to meet face to face for further processing because it was challenging to
brainstorm through conference call.
Second Meeting February: Members met to discuss more details on how to integrate ADP and
Sysdine, and build ERD with given information (ERD will be shown later in the report).
2.
3. Entity Definition:
Employee Application: Represents the employee’s application.
- Applicant ID: Unique identification number of future applications.
- Application type: The type of position the applicant is applying.
- Cover letter: Resume from the applicant.
- Applicant date: The date when the applicant applied for employment position.
Employee Interview: Represents the information related to every potential employees
interview.
- Emp ID: Unique identification number of the interviewer.
- Applicant ID: Unique identification number of the applicant.
- Description: How the interview was conducted whether through skype, phone, or in
person.
- Interview Date: Date of potential employee interview.
Employee: Represents important information related to the employee
- EmpID: Unique identification number of the employee.
- Fname: The first name of the applicant.
- Lname: The last name of the applicant.
- Address: Home address of the applicant.
- Type: Hourly/Salary: Either true or false (BOOLEAN), true indicates salary.
- ManagerID: Unique identification number for each manager.
- Hire Date: Date employee was hired.
- Pay Rate: Rate of pay that each employee is paid. Ex. $7.50 per hr.
Employee Position: Represents an employee's position within the company
- Employee PositionID: Unique identification number of employees positions within the
company.
- Position ID: Unique identification number of position available within the company.
- Emp ID: Unique identification number of the employee.
- Part/Full time: Either true or false (BOOLEAN), true indicates full-time.
Position: Represent the different job position that may be obtained within Bojangles.
- Position ID: Unique identification number for each job position.
- HR manager: Human Resource manages and organizes employee’s performance.
- Cashier: Manages the cash register.
- Drive through: Manages the drive through by taking orders.
4. - Cook: Manages the kitchen and cooks food.
- Biscuit maker: Position dedicated solely to making biscuits.
- Griller: Manages all cooking equipments in the kitchen.
- Logistics: Manages back of house operations within the company.
- Shift leader: Manages two ten hour shifts.
- Assistant Manager: Manages the operations of the company.
- Trainer: Manages and trains all new and existing employees.
- General manager: Manages the shift leader and operations within the company.
- Accountant: Manages finances pertaining to the companies needs.
Employee_Benefit: Represents the benefits an employee may have depending on their
employee’s position.
- Health insurance: An employee’s health insurance depends on part/full time type.
- Vacation pay: An employee’s vacation pay depends on position of their employment.
- Bonus: An employee’s bonus depends on job’s position.
- Commission: An employee’s commission depends on services rendered.
- Position ID: Unique identification number for each job position.
Justification for ERD:
Based on the interview we conducted with Rhonda and the forms she provided, we were able to
conclude that these are the entities we will need to build our database:
• Position: The position entity is associated with the employee position table and employee
benefit table. The importance of this table is that it describes exactly what the employee does.
• Employee Position: The employee position table identifies if the employee is full time or part
time.
• Employee Benefit: The employee benefit is associated with the tables position and employee
position because it depends on what the employee does that determines the type of benefits they
receive.
Employee Interview: This table describes the type of interview that will be conducted. It also
has a one to many relationship with the employee table because an employee can have multiple
interviews.
Employee Application: An employee’s application can be used in multiple interviews.
Employee: This table is listed with the employee’s general information.
5. We determined the relationships for the ERD by examining the logical relation each entity has
with one another. Listed below is our rationale for each relationship in our ERD:
● Employee Application has a one to many relationship with employee interview. One
application can lead to many interviews.
● Emp_Interview has a many to one relationship with employee. Many interviews can
lead to becoming an employee at Bojangles.
● Employee has a one-to-many recursive relationship with itself. This is known because an
employee can be managed or they can manage other employees.
● Employee has a one-to-many relationship with employee position because an employee
can work many different position.
● Employee Position has a one to many relationship with position because an employee
can have many positions.
● Employee Benefit has one to many relationship with position because an employee can
have many benefits from one position.
6. APPENDIX A
Interview notes with human resources representative
HR Director– Rhonda
What DBMS are you currently using?
ADP Workforce & Sysdine
What type of data does the database store? The online database holds all of their personal
information. According to Rhonda the HR Director, this database stores “pay rate (hr/salary),
liens, workers compensation, paycards/direct deposit, deductions, tax withholdings, personal and
employee profiles, and employment information, and much much more”.
Once you hire a new employee, how does the information get into your system? The
applicant fills out their own information in an online database called Sysdine, Rhonda then
transfers the information from Sysdine to ADP. Once this is complete, all employee information
is readily available. She is then able to hire, fire, and even transfer employees to a different
location if need be. Due to the size of the company (approximately 300 employees), employees
are normally searched via last name.
Where does the data come from?
New applicants fill out all of their information on Sysdine. Once this is complete, Rhonda then
manually transfers all data over to ADP Workforce. All new employee information comes from
forms except for notes that might be manually typed in. For promotions or position changes,
Rhonda can easily change via ADP. Employees do however have access to change specific
information such as W-2 forms, address,or past pay-stubs.
Will different groups of users need different accesses? Rhonda is the only one who is
currently an administrator in regards to access. The CPA has limited access to all of their
quarterly reports. Other than that, employees have basic entry to personal information. As far as
she knows, these are the only people who have access other than the business owner himself.
Within the individual business segments there are different levels of access, depends on user’s
role (types of accesses: read only, read/write, supervisor, administrator)
In terms of forecasting; how does the company predict this particular department to grow
in “X” amount of years? According to Mrs. Rhonda, Trickum Ops has signed a contract with
Bojangles (Co). That being said, they have to fulfill their side of the deal which consist of
building twenty restaurants by the year 2020. Currently, they have 5 locations built and have 2
more planned to go under construction this year. She believes that the DBMS they are currently
using is plenty big enough to suffice even after they fulfill their contract, yet it could be
aggravating with that many employees to manage.
7. Is there any data that is being gathered that is considered unnecessary or redundant?
Rhonda- “I don’t see how it could be considered redundant, but there is an easier way rather than
manually transferring employee information from Sysdine to ADP”. Rhonda also said that ADP
should outsource hiring so that there is no need to transfer information and they could
immediately hire employees through ADP.
How many different forms & reports are generated by this department? Can we access
them?
The different types of forms are payroll related in Company’s SmartStream application,
performance reviews, and general employee files for the online company directory.
How many people receive reports from HR?
All employees can have some version of a report generated from the database, such as their pay-
stub and W-2 forms. As for other reports, Rhonda and the CPA are the only people with access.
