Capstone Project Time and Attendance System
Project Code: FUTAS Project Supervisor: Phạm Thanh Tùng Team Members: TTạ Minh Việt NNguyễn Quang Huy TTrương Ngọc Sơn Tùng ĐĐoàn Việt Anh VVũ Ngọc Anh Time and Attendance System
Contents 3 Introduction 1 Project Management Plan 2 System Requirement Specification 3 System Detail Design 4 1 Testing 5 5
Introduction Initial ideas o Nowadays, with the development of economic, the salary of employees is rising. But the employees ’s worked hours are difficult to collect o Overpayment may be made and there can be a lot of money wasted. This is time to build a time and attendance system to calculate accurate employees ‘s performance and reduce the work involved in preparing hours for payroll 4
Benefit of system expect 5 FUTAS Save money and time Increase productivity Enhance consciousness Accurate Fair
Project Management Plan Tool and environment 6
Process Model Waterfall process model 7
Project Plan 8
Risk Management 9 Risk typeRisk descriptionSolution HumanTeam member get sick or attendance fail Conflict between idea of members Other team member have to support work part of that member Team building HardwareBorrow just only 1 reader Use carefully Create virtual reader TechnologyDeveloper is not C# &.Net professional Study C# &.Net from instructor ProcessCan not meet deadlineCheck milestone
System Requirement Specification 10 Functional Requirement System Requirement Non-functional Requirement.
Main Function 11 Core Management View Information Employee Shift Group Payroll Time Keeping Export
Module Function 12 Delete Edit Cancel Save Add Form
Use Case Diagram 13
Non-functional Requirement 14 Performance The system must be nimble enough to allow for easy changes The response time for install system should be less than 24 hours Reliability If the system broken, 24 hours is available to get the system back up again Information entered yesterday in the system should be there today Security The system must be secured and the information will be kept safe Admin is only person should permitted to view and edit information in the database of the system
Non-functional Requirement 15 Availability Database servers will operate 24 hours a day, 7 days a week System Management Database backup should be done often and be extremely secure.The downtime will be between 2.00 am to 4.00 am
System Detail Design System Overview 16
Client-Server Model 17
Class Diagram 18
Sequence Diagram Add new 19
Sequence Diagram Delete 20
Sequence Diagram Validate input 21
Sequence Diagram Next ID 22
Entity Relationship Diagram 23
Database Design 24
User Interface 25
Testing Test Model 26
Test Report 27
28