TRIBHUVAN UNIVERSITY ADVANCED COLLEGE OF ENGINEERING AND MANAGEMENT

Kupondole, Lalitpur

A FEASIBILITY REPORT ON Biometric Attendance And Leave Management System (BALMS)

Submitted To: Er. Pranita Upadhaya DEPARTMENT OF ELECTRONICS AND COMPUTER ENGINEERING Submitted By: Ajay Gopal Shrestha (2008/BCT/504, azrock_143@hotmail.com) Sabanam Lakhey (2008/BCT/533, luckey_matina @hotmail.com) Sajana Shakya (2008/BCT/536, aykahsanjas@gmail.com) KATHMANDU, NEPAL January, 2012

The Group
Ajay Gopal Shrestha Sabanam Lakhey Sajana Shakya

The Client
Advanced college of engineering and management Acem@edu.np

The Task to be Undertaken

This project is to design Biometric Fingerprint Attendance and Leave Management System. The system will be developed as a single functional unit a standalone system to automate the major processes: Enter the personal information of the staffs Attendance of the staffs Leave management process

From the proposed system it is expected to accumulate the personal info of the staffs which is done manually. System is expected that it will reduce the paper work and manages staffs attendance and leave management process. Finally the system has to generate the reports of employees attendance and leave monthly, in end of every semester and yearly.

A preliminary requirement analysis

The system needs to meet the following functional and non-functional requirements: Functional Requirements The attendance of the permanent, contract and casual employees will be taken via fingerprint readers and all data should be stored to the database for ease of access. The system should be able to search all the information details of employees. System should consist of functionalities for add, delete and update details. With use of leave management module user should be able to calculate the no. of leave and the no. of days of each employee for a given period and also display the no. of days left one can take leave.

The system has to generate reports such as leaves of part-time employees monthly, leave of academic staffs monthly, and annually.

Non-functional Requirements Total security to the employee details database should be maintained. Performance speed should be maximized. Ease of access and ease in report generation for each employee. Easy to upgrade.

Benefits
Saving on time and tedious paper works for manually entering the data and generate reports thus improve in communications. Improved personal info details and calculations in leave management reducing human errors. Improved employees services- ease in applying leaves, obtain their information quickly and obtain other information related to no pays, short leave and half days from the website. Data redundancy and security issues will be improved due to backups and security in the system. Better employee motivation and flexibility due to improved ease in working with user friendly interfaces. Environment Friendly Reduces paper and other resource requirements.

Process Model:
This project follows the Prototyping Approach as the client has changing needs and is not very sure about what technically the features he needs in the system . Since prototype model gives the following benefits: State of the project is clearly visible and timeline of the project is controllable. Software is created using lots of user feedbacks. In every prototype created, users could give their honest opinion about the software.Slowly the program is created with the customer in mind.

Suggested Deliverables
Management Deliverables Requirements Analysis: A document and a presentation to go over the formal requirements of the project. This deliverable ensures that the group is working on a system that closely matches to the wishes of the client. Design Documents: A document and a presentation to go over the design of the system. Source Code: A document, presentation along with the source code of the final completed project will be hosted in Source forge. Technical deliverables
1. A database with required tables to support the system: a database to store the data of bandwidth usages. 2. A User Interface to display the data in graphical way.

Outline Plan

1. Milestone 1(Dec 11, 2011): An initial draft of the requirements analysis was done after gathering with the Client. 2. Milestone 2(Jan 5, 2012): A final draft of the requirements analysis along with a presentation will be prepared. 3. Milestone 3(Jan 9, 2012): An initial draft of the Software Architecture and Design will be shown and a meeting will be conducted with the Client to get feedback on the design of the system. 4. Milestone 4(Feb 25, 2012): A final draft of the Software Architecture and Design and a presentation will be prepared for the Client. 5. Milestone 4(Feb30, 2012): Database- The database will be created to store the data of the bandwidth usage of the network. 6. Milestone 5(March 15, 2012): GUI - the GUI will be developed to display the data of the bandwidth usage of the network. 7. Milestone 6(April 6, 2012): Testing, Debugging and Integration - The system will be tested and debugged. As the system will be accepted then it will be integrated to the actual production system. 8. Milestone 7(April 8, 2012): Project Deadline - The project source code will be handed over to the Client and a presentation will be presented to the Client.

Visibility Plan:
1. Internal(within project members) The Group will have day to day interaction with each other about the progress of the project and discuss about the change in plans and prototype. 2. External(with client) Once in two weeks via meetings, phones and email for further discussion and describe the progress of the project, review the software and get more feedback and updating the prototype in more improved version.

Technical feasibility
Available Resources Programming Language: .NET with C#, Java, Visual Basic, Ruby Database: Oracle 11g, Sql Server 2008 R2, MySQL 5.5 Used Resources Programming Language: Java Database: MySQL 5.5 The reason behind selecting Java and MYSQL is that they are open source software and are legally free to use and develop. They are renowned software with high programming capabilities with latest frameworks and easy to work on. It is easy to implement various securities to the design.

Operational Feasibility
Easy navigation for attendance Add-Delete-Modify is managed through admin page easy to learn and maintain graphical view. Automatic Backup System helps to save the data on daily basis without engagement of any personnel. Every record and error is logged. Feedback Report is automatically generated every month. It can be forwarded through mails to developers to gain constraint control over the software. Security and software updates can be updated without losing any data. Only authorized personnel are allowed to use admin page.

Leave and no pays are managed within the software and alerts concerning it are automatically send to admin and are automatically written in monthly report Biometrics is well known method for fingerprint analysis so accuracy with the system is quite high.

Economic Feasibility
Economic feasibility is the most frequently used method for evaluating the effectiveness of a new system. More commonly known as cost/benefit analysis, the procedure is to determine the benefits and savings that are expected from a candidate system and compare them with costs. If benefits outweigh costs, then the decision is made to design and implement the system. Cost-Benefit Analysis: Projected development cost for the proposed system Expenses: Reason Other softwares cost System analyst cost Programmer Database Administrator cost Designer Image Scanner(Hardware) Training for staff Total Projected Annual Operating Cost Expenses: Reason Maintenance cost Data entry and employee cost Total Price Rs.30,000 Rs.20,000 Rs.50,000 Price Rs.10,000 Rs.1,00,000 Rs.1,00,000 Rs.40,000 Rs.30,000 Rs.10,000 Rs.10,000 Rs.3,00,000

ScheduleFeasibility
S.No Task Name 1 Identifying Project 2 Requirement Gathering 3 Prepare The project Proposal 4 Feasibility Study Software Requirement 5 Analysis 6 Software Design 7 Prototype Design 8 Prototype Demonstration Duration 3 5 3 17 21 38 7 1 Start Date 2Dec 7Dec 11Dec 15Dec 7Jan 4Feb 26Mar 6Apr Finish Date 4-Dec 11Dec 15Dec 7-Jan 4-Feb 25Mar 4-Apr 8-Apr

2-Dec 23-Dec 13-Jan 3-Feb 24-Feb16-Mar 6-Apr 27-Apr Identifying Project Requirement Gathering Prepare The project Proposal Feasibility Study Software Requirement Analysis Software Design Prototype Design Prototype Demonstration

Alternative System
Web-based System: In this system, a web server is installed for getting data from various parts and sending it through web services and stores it in the database. All the notification and alerts are sending through email to the respective person and admin team. Developers may also have close look to the system through the feedback that are send through them in an email. All the reports are generated in an

internal website and are available for staff to look at. This can be used in an closed network or over the internet. Purchase Commercial package software: According to user requirements, user can purchase commercial package software from the software developers. From this solution users are unable to get the maintain privileges. The user can get guidance and support for the user of package but it is a high cost solution as well.

Risk Analysis
1. System Crash: Risk: The proposed system is standalone system and hence the entire database related to employees personal info, attendance and leave will reside in a single computer. In case of system failure there will be risk of losing all these databases. Alert system might not be effective. Backups are done in the same system has no effect when system gets crashed. Solution: automatic backup after any updates to any external data storage will be effective. 2. Changing Requirements: Risk: The Client may have different ideas about the system during the course of the project. Solution: Prototyping Model helps to redefine customer model and helps clarify the visibility plan. 3. Lack of skill to use the system Risk: It is possible for the personnel to find it difficult to use. And may have use wrong way to use the system. Solution: Initial training is provided. And provide complete user manual to use the system.

Conclusion:
Based on the analysis carried out from this feasibility study, the group has collectively agreed that the project is feasible and the group is willing to take effort on the above mentioned project.