Database System Design Payroll system Content | Title| Page| 1. 0| Analysis the Payroll System’s data and application requirement| | | * Introduction| 3| | * System Request| 3-4| | | | 2. 0| Analysis the Requirement| | | * Functional Requirement| 5| | * Non-Functional Requirements| 6-7| | | | 3. 0| Database Design| | | * Data Flow Diagram| 8-9| | * Use case Description| 10-`12| | * ER diagram| 13| | * Relation Data Model| 14| | * System catalog| 15-16| | | | 4. 0| Marks| 17| 1. 0 Analysis the Payroll System’s data and application requirement
Introduction The people in related with the system are staff and members. After research, the current system not clearly states the employee salary and working hour. That will make the company paid wrong to the employee, And the employee id and detail should also be record correctly. In our system, we have improved. For the sake of all, we will display the detail to the company, and the employee also can check their information through the system According this payroll system, users can edit own profile, check their salary and working hour.
Users can be split into the category of users and employee. The users . The payroll staffs will record their variety when they registered and the system can defined their identity are student or lecturer. The payroll staffs can use the system to help users register account and preview users’ profile. They can manage return and borrow books, preview users details. They can also add, update and delete books. System Request Some facilities of the payroll system are requires the following information: Save Time By using our system, we can calculate the employee salary more accurate.
When user want to check the employee working hour or salary, they just need to search with the system. After searching, we can immediately know the employee current working hour, basic salary. If the user want more information also can continue click into in for the employee information. When register become a user, the payroll staff can just key in the user details into the system and no need to base on paper form the user filled in. More accurate When the employee needs to update their status, they can send he request to the system, after the system apply the request, they can simple update their information.
The system will immediately show out the data after update. This can make the employee finish their updated with a lot of accurate. Security By using the system, only the proper user can log in into the account with the password. With this, it can prevent others people from illegal log in into your account and doing some illegal action without your knowing. It have also prevent others people to see your account information. The employee may also get well control with the system. For example, only the employee themselves can modify and update their information. Improved services ) The computer processing will be more effective management compare with manually processing to ensure that the data is more secure in the new system. b) The computerized system also can have a better performance than manually system. It is easier to update or delete the data in database. c) The information system can reduce the cost by saving the paper for the documentation. It also can reduce the time to process other than using the traditional manually system. d) Computerized system can provide a stronger control to user, it is more protective than traditional manually system. ) New system has greater performance than manually system, other than that, administration can update the data such like insert or delete data in database. f) The users can enter the detail into computer directly, no like the handwriting which needs to enter information by manually and sign the form. g) The new system can save more space in the database, prevent the system overload. 2. 0 Analysis the Requirement Functional Requirement Functional requirement is describe that what are the process must be provided by the system. For example, how inputs to be handled and what are the output to perform.
Functional requirement are include: Input a) The employee can use the system to view the current status and edit profile by entering the details. b) Employee enters their details into the digital application format forms. c) The system can allow employee to insert their details via internet. d) The system can allow the employee to view, approve and input information data into the system. Process a) After the employee has finished update, the data will be store in the database. b) Database will create all users’ own account and record all information. ) The employee key in the word they want to find out, the system will retrieve data from the database. Control a) Employee can only edit their profile, view borrow history and search books. Output a) Employee can use the network (internet or intranet) to view all the information. b) The system will provide a search engine to the employee. Performance The system can operate on 365 days, also means that the system can works on every day with non-stopping. Calculate the employee current salary based on working hour. Update/Delete
After stored the employee’ details, the employeestill can edit their or delete the users’ profile. They can update current information. Non-Functional Requirements The non-functional requirements is explain aspects of the system are concerned with well it how well it support the functional requirements. Interface The system is a typical designed performance, developed for all users to help in a quick transition period. Performance If reduce the time which employee enter and retrieve information of the users detail. Operating The system must operate 365 day. Platform Server i. Operating System:
Server will run Microsoft Windows XP (not recommend) or Windows 7 as it operating system (OS) because Windows XP and Windows 7 is a robust and completive system for this setting. Furthermore, the Microsoft Window is the common operate system now. ii. Memory: Memory is available for such a low cost at present, and we must have make sure the computer process speed can’t effect the computer processing, so the computer should be equipped with at least 1GB. But better common suggestion is using 2GB. iii. Storage: The hard disk must can’t less than 100GB. Because it is must store all the user data.
Furthermore, if developer wants to develop more structures, the storage can handle the future task. iv. Central Processing Units(CPU) User can use at least a 3. 0GHz Pentium IV CPU or higher. v. Network The system requires 100Mbps Ethernet network and is connected by high-speed switches. User System i. Operating System (OS): The minimum requirement of operating system is Windows XP. Because some browsers like the Internet Explorer (IE), Firefox or Google Chrome, the problems will decrease as less as possible. Our suggestion is using the Windows XP. ii. Memory: Base requirement memory is available 256MB.
But common suggestion memory is using 512MB. iii. Storage: The user’s hard disk drives storage is not important. Because system are all using online just need install browser like the IE-Internet Explorer or Firefox. iv. Central Processing Units(CPU) Processor must be at least an 800MHz Pentium III CPU or above v. Network Can using the 56Kb modem because we are using the online system. And our system also supports the LAN or Wireless LAN around the company. 3. 0 Database Design Data Flow Diagram User 0 Payroll System Employee renew status record employee details aying money transferring money hours of working record hours of working hours of working payroll report 4. 0 Emp. Data Emp. Information Give Personal Information Record Emp. Details User 3 Transferring Money 1 Employee Info D1 Emp. File Transfer money D3 Money Transfer Record Employee Receive money Record amount 2
Work Hours Record after money transferred Give Salary Depending of Work hours Record work hour of employee Works Hours D2 File Give Work Hoursrenew Work Hours Data work hours User case description 1. 0 Maintain Employee Information 1. 1 Brief Description This use case allows the Payroll Administrator to maintain employee information. This includes adding, changing, and deleting employee information from the system. 1. 2 Flow of Events 1. 2. 1 Basic Flow
This use case starts when the Payroll Administrator wishes to add, change, and/or delete employee information from the system. 1. The system requests that the Payroll Administrator specify the function he/she would like to perform (either Add an Employee, Update an Employee, or Delete an Employee) 2. Once the Payroll Administrator provides the requested information, one of the subflows is executed. If the Payroll Administrator selected “Add an Employee“, the Add an Employee subflow is executed. If the Payroll Administrator selected “Update an Employee“, the Update an Employee subflow is executed.
If the Payroll Administrator selected “Delete an Employee“, the Delete an Employee subflow is executed. 1. 2. 1. 1 Add an Employee 1. The system requests that the Payroll Administrator enter the employee information. This includes: – name – employee type (hour, salaried, commissioned) – phone number – hourly rate (for hourly employees) – salary (for salaried and commissioned employees) 2. Once the Payroll Administrator provides the requested information, the system generates and assigns a unique employee id number to the employee and sets the paycheck delivery method to default of “pickup”.
The employee is added to the system. 3. The system provides the Payroll Administrator with the new employee id. 1. 2. 1. 2 Update an Employee 1. The system requests that the Payroll Administrator enter the employee id. 2. The Payroll Administrator enters the employee id. The system retrieves and displays the employee information. 3. The Payroll Administrator makes the desired changes to the employee information. This includes any of the information specified in the Add an Employee sub-flow. 4. Once the Payroll Administrator updates the necessary information, the system updates the employee record ith the updated information. 1. 2. 1. 3 Delete an Employee 1. The system requests that the Payroll Administrator specify the employee id. 2. The Payroll Administrator enters the employee id. The system retrieves and displays the employee information. 3. The system prompts the Payroll Administrator to confirm the deletion of the employee. 4. The Payroll Administrator verifies the deletion. 5. The system marks the employee record for deletion. The next time the payroll is run, the system will generate a final paycheck for the deleted employee and remove the employee from the system. 1. 2. 2 Alternative Flows . 2. 2. 1 Employee Not Found If in the Update an Employee or Delete an Employee sub-flows, an employee with the specified id number does not exist, the system displays an error message. The Payroll Administrator can then enter a different id number or cancel the operation, at which point the use case ends. 1.. 2. 2. 2 Delete Cancelled If in the Delete An Employee sub-flow, the Payroll Administrator decides not to delete the employee, the delete is cancelled and the Basic Flow is re-started at the beginning. 1. 3 Special Requirements None. 1. 4 Pre-Conditions
None. 1. 5 Post-Conditions Payments for each employee eligible to be paid on the current date have been processed. 1. 6 Extension Points None. 2. Run Payroll 2. 1 Brief Description The use case describes how the payroll is run every Friday and the last working day of the month. 2. 2 Flow of Events 2. 2. 1 Basic Flow The use case begins when it’s time to run the payroll. The payroll is run automatically every Friday and the last working day of the month. 1. The system retrieves all employees who should be paid on the current date. . If the payment delivery method is direct deposit, the system creates a bank transaction and sends it to the Bank System for processing. 3. If the payment delivery method is by cheque , the system will record the delivered date , time , employee name , employee id , account number and cheque number. 2. 2. 2 Alternative Flows 2. 2. 2. 1 Bank System Unavailable If the Bank System is down, the system will attempt to send the bank transaction again after a specified period. The system will continue to attempt to re-transmit until the Bank System becomes available. 2. 2. 2. Deleted Employees After the payroll for an Employee has been processed, if the employee has been marked for deletion (see the Maintain Employee use case), then the system will delete the employee. 2. 3 Special Requirements None. 2. 4 Pre-Conditions None. 2. 5 Post-Conditions Payments for each employee eligible to be paid on the current date have been processed. 2. 6 Extension Points None. ER Diagram Money Transfer bank(P. K) account transferamount transferDate receiveDate 0.. * Work Hours workID(P. K) workdate parttime fulltime holiday ickleave TransfersEmployee employeeID(P. K) employeeName gender DOB telNo dateofwork department accountID Manages 1.. 11.. 1 User userID(P. K) userName password gender DOB telNo 1.. * Records 0.. *Works1.. * 1.. * 0.. * Employs Relation Data Model User(userID, userName, password, gender, DOB, telNo) Primary Key: userID Money Transfer(bank, account, transferamount, transferdate, receivedate) Primary Key: bank Foreign Key : userID references User(userID) Foreign Key : workID references Work Hours(workID) Work Hours (workID, workDate, partTime, fullTime, holiday, sickLeave) Primary Key : workID
Foreign Key : employeeID references Employee(employeeID) Employee (employeeID, employeeName, gender, DOB, telNo, dateofwork, department, accountID) Primary Key : employeeID Foreign Key : userID references User(userID) Foreign Key : bank references Money Transfer(bank) System Catalog User Field| Type| Length| userID| varchar| 11| userName| varchar| 255| password| int| 11| gender| int| 11| DOB| varchar| 255| telNo| varchar| 255| Money transfer Field| Type| Length| bank| varchar| 11| account| Int| -| transferamount| Int| -| transferdate| float| -| receivedate| float| -| Work Hours Field| Type| Length| orkID| varchar| 11| workDate| varchar| 11| partTime| Varchar| -| fullTime| Varchar| | holiday| Float| | sickLeave| Float| | Employee Field| Type| Length| employeeID| varchar| 12| employeeName| varchar| 255| gender| varchar| 15| DOB| varchar| 255| telNo| varchar| 14| dateOfWork| int| 11| department| varchar| 11| accountID| int| | 4. 0 Marks Analysis the Payroll System’s data and application requirement| 20| DFD| 10| ER/EER diagram| 20| Relational Data Model and System Catalog| 20| User Menu, Source Code| 10| Critical appraisal/Creative/presentation skill/other| 20| System Design| 50| Total| 150|