03 - user interface and database

8/3/2019 03 - User Interface and Database

1/25

MIS 122: DATABASE SYSTEM DEVELOPMENT, SECTION A, D

Employee and Payroll

Management SystemProcess and DataGroup: Overclocked

Jic Lim, Romwel Mina, Mikey Paras, Jason San Diego, Allen Tai

01/30/2009


2/25

PROCESS REQUIREMENTS & USER INTERFACE DESIGN

Inputs and Outputs Design Specifications

Employee and Payroll Management System

Screen Specifications

I. Narrative Overview

Screen: Input New Employee InformationUsers: AuditorFunctions: To take the data in the respective fields and put them into

a database.Controls: The numerous textfields are meant for the user to type in

specific data indicated by the label. The dropdown menus are mostly

used for error-proofing, and are used for the dates and the job position.And the radio buttons are there for simple choosing of choices betweengender and marital status.

II. Sample Design

Page 2 of25


3/25

Employee and Payroll Management SystemReports Specifications


Report: View Employee InformationUsers: RetailerDescription: The dropdown menu shows all the available employee

numbers to choose from. Choosing one employee number and clickingon the generate button will generate the employee information in thetext area.

II. Sample Design

Page 3 of25


4/25

Employee and Payroll Management SystemScreen Specifications


Screen: Input Employees DeductionsUsers: Team LeaderFunctions: Takes down the deductions made by employees and saves

them in the database.Controls: The dropdown menus are for the date and employee

number error-proofing, while the text field is for the amount theemployee deduction is. Clicking the create button will save thededuction.

II. Sample Design

Page 4 of25


5/25

Employee and Payroll Management SystemReports Specifications


Report: View Payroll SummaryUsers: RetailerDescription: Choose the date desired from the dropdown menu and click

generate. This will show the payroll summary of that date within thetext area.

II. Sample Design

Page 5 of25


6/25

Use Cases

CASE: Input Employee InformationUse Case Name: Input Employee Information

Actor/s: AuditorDescription: The Auditor adds new employee and information to the employee

databaseTrigger: Press the Add Employee button on the Employee Database Page.

Preconditions: 1. Employee forms must be at hand.2. Auditor must be successfully logged in.

Postconditions: 1. Employee database updatedNormal Flow: Actor System

1. Auditor presses the AddEmployee button on theEmployee Database Page

2. Display form with empty fieldsto be filled out

3. Fill up information fields4. Press OK button 5. Update database

6. Close form with fields7. Display employee databasepage

AlternativeFlows:

Actor System

Notes andIssues:

CASE: Edit Employee InformationUse Case Name: Edit Employee Information

Actor/s: AuditorDescription: The Auditor edits employee information in the employee database

Trigger: Press the Edit employee information button on the EmployeeDatabase Page.

Preconditions: 3. Employee must already have information in the database..4. Auditor must be successfully logged in.

Postconditions: 2. Employee information is edited and updated.3. Employee database updated.

Normal Flow: Actor System8. Auditor presses the edit

employee informationbutton on the EmployeeDatabase Page

9. Display previously filled upforms

10. Edit specified fields11. Press OK button 12. Update database13. Close form with fields14. Display employee database

pageAlternative

Flows:Actor System

Notes and

Page 6 of25


7/25

Issues:

Page 7 of25


8/25

CASE: Delete Employee InformationUse Case Name: Delete Employee Information

Actor/s: AuditorDescription: The Auditor deletes employee information from the employee

database

Trigger: Press the Delete Employee button on the Employee DatabasePage.

Preconditions: 5. Employee must already have information in the database.6. Auditor must be successfully logged in.

Postconditions: 4. Employee information is deleted from the employee database.5. Employee database updated.

Normal Flow: Actor System15. Auditor presses the delete

employee informationbutton on the EmployeeDatabase Page

16. Display list of employees in thedatabase

17. Chooses the name ofemployee to be deleted

4. Ask for the confirmation fordeletion

18. Press OK button 19. Displays message thatemployee has beensuccessfully deleted from thedatabase

6. Press OK button 7. Update employee database.8. Display employee database

pageAlternative

Flows:Actor System

Notes andIssues:

CASE: Input Hours WorkedUse Case Name: Input Hours Worked

Actor/s: Team LeaderDescription: The Team Leader inputs the Hours Worked by employees for the

day.Trigger: Press the Input Employee Hours button.

Preconditions: 7. Hours Worked must be updated.8. Team Leader must be successfully logged in.

Postconditions: 6. Hours Worked for employees are recorded7. Hours Worked are sent to the gross salary computations

Normal Flow: Actor System

20. Team Leader presses theInput Employee Hoursbutton.

21. Display form for inputtinghours worked

22. Press OK button. 23. Display confirmation of havingrecorded the hours worked

AlternativeFlows:

Actor System

Notes and

Page 8 of25


9/25

Issues:

Page 9 of25


10/25

CASE: Input DeductionsUse Case Name: Input Deductions

Actor/s: Team LeaderDescription: The Team Leader inputs the deductions incurred by employees for

the day.

Trigger: Press the Deductions button.Preconditions: 9. Deductions report must be updated.

10. Team Leader must be successfully logged in.Postconditions: 8. Deductions for employees are recorded

9. Deductions are sent to the net salary computationsNormal Flow: Actor System

24. Team Leader presses theDeductions button.

25. Display form for inputtingdeductions

26. Press OK button. 27. Display confirmation of havingrecorded the deductions

AlternativeFlows:

Actor System

Notes andIssues:

CASE: Print Employee InformationUse Case Name: Print Employee Information

Actor/s: RetailerDescription: Retailer prints out a copy of an employees information.

Trigger: Press the Print button on employees information page.Preconditions: 11.Employee Records must be updated.

12. Retailer must be successfully logged in.Postconditions: 10.Employee Information printed

Normal Flow: Actor System28. Retailer presses the Print

button on employeesinformation page.

29. Display print set-up

30.Press OK button. 31.Display data being formattedfor printing

32. Display confirmation of havingprinted the employeeinformation

33. Press OK button. 7. Printer prints out hard copy of an employees information

AlternativeFlows:

Actor System

Notes andIssues:

Page 10 of25


11/25

CASE: Print Payroll SummaryUse Case Name: Print Payroll Summary

Actor/s: RetailerDescription: Retailer prints out a copy of the payroll summary.

Trigger: Press the Print button on payroll summary page.

Preconditions: 13. Payroll must be updated on a daily and/or hourly basis.14. Retailer must be successfully logged in.

Postconditions: 11.Payroll summary printedNormal Flow: Actor System

34. Retailer presses the Printbutton on payrollsummary page.

35. Display print set-up

36.Press OK button. 37.Display data being formattedfor printing

38. Display confirmation of havingprinted the payroll summary

39.Press OK button. 7. Printer prints out hard copy of the payroll summary.

AlternativeFlows:

Actor System

Notes andIssues:

CASE: Set System SettingsUse Case Name: Set System Settings

Actor/s: RetailerDescription: Retailer sets the date and time settings or payroll settings of the

system.

Trigger: Press the System Settings button on employees information page.Preconditions: 15.Retailer must be successfully logged in.

Postconditions: 12.System settings are set accordingly.Normal Flow: Actor System

40. Retailer presses theSystem Settings buttonon the home page.

41. Display system settings form,with the current systemsettings.

42. Retailer edits the settingsthat he or she would liketo change.

43.Press OK button. 5. The system confirms thechange with a pop-up messagebox.

6. Press OK button.Alternative

Flows:Actor System

Notes andIssues:

Page 11 of25


12/25

CASE: Generate System AlarmUse Case Name: Generate System Alarm

Actor/s: TimeDescription: The system generates an alarm, either birthday or contract

expiration, and sends it to the Retailer.

Trigger: The date corresponds to either the date of a contract expiration ofan employee or a birthday of an employee.

Preconditions: 16.The system settings must be set.17. The employee database must be updated.18. Retailer must be successfully logged in.

Postconditions: 13.Alarm is sent to the retailer.Normal Flow: Actor System

44. The system detects acorrespondence betweendates.

45. The system determineswhether its a contractexpiration or birthday.

46. The system sends the alarm tothe home screen as a reminderon the message box at theside of the home screen, afterthe retailer has logged-in.

AlternativeFlows:

Actor System

Notes andIssues:

Page 12 of25


13/25

DATABASE REQUIREMENTS

Conceptual Data Model

1. Input New Employee Information

Page 13 of25


14/25

2. Input Hours

Page 14 of25


15/25

3. Input Deductions

Page 15 of25


16/25

4. Input Bonus

Page 16 of25


17/25

Overall

Page 17 of25


20/25

employee NoFirst_Name First Name of

employeeN

N/A 30 charNo

Middle_Name Middle Nameof employee

NN/A 20 char

No

City_Address Employeesaddress at acity

NN/A 100 char

Yes

City_Phone Contactnumber atemployeescity residence

N

N/A 7 digit integer

Yes

Provincial_Address

Employeesaddress at aprovince

NN/A 100 char

Yes

Provincial_Phon

e

Contact

number atemployeesprovincialresidence

N

N/A

+ZZ XXXXXXX

(where Z is aninteger digit ofthe area codeX is an integer

digit of thephone number)

Yes

Email Email addressof employee

NN/A 45 char

Yes

Birthdate Date of birth of employee

N 01/01/2009

DD/MM/YYNo

Birthplace City/Municipalit

y of birth ofemployee

N

N/A 15 char

No

Height Height of employee

N00 ft

X X where Xis int

No

Weight Weight of employee

N0 lbs

X lbs, where Xis int

No

Religion Religion ordenominationof employee

NN/A 15 char

No

Marital_Status Marital statusof employee

NSingle

Single, Married,Divorced/Separ

ated

No

Citizenship Citizenship of employee

NN/A 15 char

No

Spouse_Name Name of employee'sspouse

NN/A 50 char

Yes

Page 20 of25


21/25

Spouse_Address Residenceaddress ofemployee'sspouse

N

N/A 100 char

Yes

Spouse_Occupa

tion

Occupation of

employee'sspouse

N

N/A 15 char

Yes

Father_Name Name of employee'sfather

NN/A 50 char

No

Father_Address Residenceaddress ofemployee'sfather

N

N/A 100 char

No

Father_Occupation

Occupation ofemployee's

father

NN/A 15 char

No

Mother_Name Name of employee'smother

NN/A 50 char

No

Mother_Address Residenceaddress ofemployee'smother

N

N/A 100 char

No

Mother_Occupation

Occupation ofemployee'smother

NN/A 15 char

No

Parents_Address

Residenceaddress ofemployee'sparents (Ifparents are notliving together,choose one)

N

N/A 100 char

Yes

Parents_Phone Residencephone numberof employee'sparents (Ifthere are morethan one,choose one; itshould be thenumber to thegiven parents'address)

N

N/A

+ZZ XXXXXXX(where Z is aninteger digit ofthe area codeX is an integer

digit of thephone number)

Yes

Page 21 of25


22/25

Prefered_Language

Preferedlanguage ordialect ofemployee inwriting and

oralcommunication

N

N/A 15 char

No


Work Hours


Contains number of hours worked by an employee

Attribute Name Description Prima

ryKey?

Default

Value PossibleValues

Can

beNull?

Date Date of hoursworked

Y 01/01/2009

DD/MM/YYNo

Employee_Number

Assigned numberto an employee

YN/A

4 digitinteger

No

Number_of_Hours

Amount of hoursduring the date

N0

2 digitinteger

No


Deduction


Shows deductions incurred by an employee. Contains date,amount, reason and witness for deduction

Attribute Name Description PrimaryKey?

DefaultValue

PossibleValues

CanbeNull?

Report_Number Assigned numberto the deductions

report

YN/A

6 digitinteger

No

Employee_Number


YN/A

4 digitinteger

No


N 01/01/2009

DD/MM/YYYY

No

Amount Amount deducted N0.00

7 digitdouble

No

Reason Reason for N N/A 50 char No

Page 22 of25


23/25

deductionWitness Witness to the

deductionN

N/A 25 charNo

Entity/

RelationshipName:

Bonus


Shows the bonus pay an employee receives


DefaultValue

PossibleValues

CanbeNull?

Report_Number Assigned numberto the bonus

report

YN/A

6 digit

integer

No

Employee_Number


YN/A

4 digitinteger

No


N 01/01/2009

DD/MM/YYNo

Amount Bonus Amount N0.00

7 digitdouble

No

Reason Reason for bonus N N/A 50 char NoWitness Witness to the

bonusN

N/A 25 charNo


Net Pay


Shows the pay that is due to employees


DefaultValue

PossibleValues

CanbeNull?

Employee_Number Assigned numberto an employee Y N/A 4 digitinteger No

Month Month that netpay is due

N

Jan

Jan, Feb,Mar, Apr,May, Jun,Jul, Aug,Sep, Oct,Nov, Dec

No

Page 23 of25


24/25

Year Year that net payis due

N2000

4 digitinteger

No

Net_Pay Amount of netpay due

N0.00

8 digitdouble

No

Page 24 of25


25/25

DATABASE TECHNOLOGY COMPONENTS

Comparison of DBMSThe teams attention and goal, in terms of the database management, is toprovide the client given to proper database management to ease the access

of data. And based on the teams research, businesses that use MS Accessbegin to look for an alternative database management system which allowsbetter database performance, higher reliability, higher flexibility and yetinexpensive.

Besides the fact that the team are introduced and being oriented with MySQLas a part of the course curriculum, MySQL's flexibility allows the client toinstall and organize it across various platforms, unlike MS Access where in itcan only be deployed in MS Windows, and also allows multiple concurrentusers, versus MS Access single user application.

Storage Estimate

Entity: EmployeeSub-Total: 8072 bytes

Work HoursSub-Total: 48 bytes

DeductionSub-Total x2: 1456 bytes

BonusSub-Total: 720 bytes

Net PaySub-Total: 120 bytes

Total: roughly 16240 bytes or 16.24Kb per employee

16240Kb x 50employees = 812000bytes or 812kb

Page 25 of25

03 - user interface and database

Documents