ATTENDANCE MANAGEMENT SYSTEM PROJECT REPORT

PROJECT REPORT

ATTENDANCE MANAGEMENT SYSTEM PROJECT REPORT

PROJECT SOURCE CODE

ATTENDANCE MANAGEMENT  SYSTEM PROJECT SOURCE CODE

FREE DOWNLOAD ALL THE PROJECT REPORTS WITH SOURCE CODE FROM HERE

STUDENT AND EMPLOYEE ATTENDANCE MANAGEMENT SYSTEM PROJECT REPORT

This document is meant for describing all the features and procedures that were followed while developing the system.

This document specially mentions the details of the project how it was developed, the primary requirement, as well as various features and functionalities of the project and the procedures followed in achieving these objectives.

Attendance System forms the lifeline of the business institute to manage the Employee and its salary. It is very essential for an Institute to handle the Salary and their scale. It is very useful for an Institute to test its employee attendance continuously for their mutual development.

The IT initiatives have encouraged various Organizations to develop systems to facilitate their day to day operations. The Attendance System will include various parts (Salary, Employee Entry, Salary Scale Entry, etc) for conducting salary Sheet. This system helps in conducting Attendance quickly and can thus help in saving time and the operations will be carried out efficiently.

With the effective use, any Institute can apply the “Attendance Management System” for conducting quick attendance and getting better results in less time.

Ø Introduction:-

Attendance Management System is software developed for daily student attendance in schools, colleges and institutes. If facilitates to access the attendance information of a particular Employee in a particular industry. The information is sorted by the operators, which will be provided by the employee for a particular working day. This system wills also help in evaluating attendance eligibility criteria of a employee.

Ø Purpose:-

The purpose of developing attendance management system is to computerized the tradition way of taking attendance. Another purpose for developing this software is to generate the report automatically at the end of the session or in the between of the session.

Ø Scope:-

The scope of the project is the system on which the software is installed, i.e. the project is developed as a desktop application, and it will work for a particular institute or organization. But later on the project can be modified to operate it online.

Ø Employee Profile:-

Employee Personal information: Name, Date of Birth, Age, Marital Status, address (permanent and present) and contact person details, Email, Contact no., Blood group, Nationality, Category, employee profile, Date of joining, Service up to, employee current position and job profile, family background details, employee local address and references details, Passport No., PF No, ESI No, Bank A/c No., Qualification details and previous work experiences.

Ø Leave Management:-

Manage leaves of all types for employees Manage different types of employee leave status: permanent, rolling contract and contract Leave ledger of employee Leave application management to be handled by HR Leave structure and policy management.

Ø Time Management :-

  Prior intimation to HR in case of late coming, early going, absence due to travel on duty Management of shifts Managing overtime of employee Manual attendance entries in the system by HR in case of scanner failure

The benefits of using a time and attendance management solution at your workplace can not be underestimated. With thousands and thousands of employees working in many companies around the world, the need of an efficient organizational system or programs are getting more and more vital. Therefore, there are many companies implementing time management solutions in order to improve productivity.

              Attendance Management System covers the requirements of the Personnel Department in terms of Manpower Analysis, day-to-day monitoring of the Attendance, Maintaining Statutory Registers, Monitoring of Leave Records, Calculation of Overtime and transfer of relevant information to the Payroll System. It also works well as a member database. You can create customized attendance reports, event schedules, membership rosters, and attendance forms. The program is easy to use, and it's well suited for any organization that needs to keep track of attendance.

STUDENT ATTENDANCE MANAGEMENT SYSTEM PROJECT

                                                          

Ø  Create a Window application to be used in place of old paper based user Employee Salary manage process.

Ø  Use .NET and SQL Server technology to create strong and secured database connectivity.

Ø  Incorporate the server software within the code.

Ø  Runtime package and deployment instructions are given.

The scope of the project is the system on which the software is installed, i.e. the project is developed as a desktop application, and it will work for a particular institute or organization. But later on the project can be modified to operate it online.

The intention of developing Attendance Management System is to computerized the tradition way of taking attendance. Another purpose for developing this software is to generate the desired reports automatically at the end of the session or in the between of the session as they require. This project is basically a desktop application which means self contained software runs on the system on which it has been installed under the user control and it will work for a particular institute or college only.

Software Process Model:

To solve actual problems in an industry, software developer or a team of developers must incorporate a development strategy that encompasses the process, methods and tools layers and generic phases. This strategy is often referred to as process model or a software developing paradigm. A process model for software developing is chosen based on the nature of project and application, the methods and tools to be used, and the controls and deliverables that are required. All software development can be characterized as a problem solving loop in which four distinct stages are encountered: Status quo, Problem definition, technical development and solution integration. Regardless of the process model that is chosen for a software project all of the stages coexist simultaneously at some level of detail.

Our Project Follows the Waterfall Model: ATTENDANCE MANAGEMENT SYSTEM PROJECT

Ø The Waterfall Model:

                 The steps of the typical Waterfall Model are:

1.      Requirement Definition.

2.      System & Software Design.

 3. Implementation.

 4. Integration & System Testing.

 5. Operation and Maintenance.

There have been some variations from the typical waterfall model for this project  life cycle.

 They are:

1.      Maintenance has been omitted from the current project.

2.      Not all testing methods which are present in theoretical model are implemented.

 3 .1 User Characteristics

This system will be used in one User Modules which are Administrator. As all of these have different requirements the modules are designed to meet their needs and avoid any type of confusion. The Uses of all three User Modules have been described below.

                            

                      

[1]    System User can do the following functions in the System.

Ø  Add , Edit & Delete Attendance Detail

Ø  Add , Edit & Delete Employee Detail

Ø  Add , Edit & Delete Salary Detail

Ø  Add , Edit & Delete Holiday Detail

Ø  Add , Edit & Delete Salary Scale Detail

Ø  View Results

Ø  Generate Reports

                                

Hardware:

Ø  Pentium IV.

Ø  700 MB Hard Disk Space.

Ø  256 MB RAM.

                         

Software:

Ø  Operating System: Windows XP or later.

Ø  Front End: C#. Net (VISUAL STUDIO 2008).

Ø  Back End: MS SQL SERVER 2005.

3.3.1 Security and Reliability Requirements: ATTENDANCE MANAGEMENT SYSTEM PROJECT

1.    Housework:
      Hours of work can be defined employee wise or shift wise.

2.    Shifts:

Shifts are user definable. Grace Time, both at the Start and End of the shift can be defined for individual shifts.

3.     Type of Shifts:

Shifts can be either as per a predefined roster, open shift or a break shift.

4.     Duty Roster Generation:

Based on the pre-defined shifts you can generate a pattern of work             known as a DUTY ROSTER. These DUTY ROSTERS can then become a template for future roster generation.

5.     Weekly offs:

Weekly off days can be defined employee wise or roster wise.

6.   Holidays:
      Holidays can either be general holidays for all staff or it can be defined for a set of employees.

7.    Overtime:

Overtime hours are calculated by the system based on punch timings. The said overtime hours are transferred to payroll only after the departmental head has sanctioned it. The system allows the user to specify which employee or a set of employees is eligible for overtime.

 3.3.2 Organizational Requirements:

Ø Implementation Requirements:

It requires good skill for implementation of project. As This project is using 3- tier business architecture. All the classes, Functions, procedures and objects are created in the system wise Architecture. The three tiers are given below.

                   1) GUI

                   2) Business Logic Layer

                   3) Data Access Layer

         Entire coding will be done using Microsoft Visual .Net 2005 and Microsoft SQL Server 2005. Soft copy for the Documentation is provided in Microsoft Word Format. Entire Coding would not be shown to the client for any reasons.  Implementation does not require any more software support without as mentioned below in the system requirements.

Ø Standards Requirements:

Industry standards will be followed by us in any Negotiation or deal related to the product software. Coding, Documentation and final product delivery will be followed by the standards.

 3.3.3   External Requirements:

Ø Ethical Requirements:

Product Software should be negotiated with human Ethics and it is wished that the software should be used with Ethical requirements. Any non ethical use of this software will be at the user’s own risk.

Ø Legislative Requirements:

(1) Privacy Requirements:

 Privacy of any particular things and strategy will be served based on prior negotiation and it should be cleared purposed for that requirement.

(2) Safety Requirements:

 Safety will be provided based on the requirement of the members and necessary critical points.

4.1 STUDY & WEAKNESSES OF CURRENT SYSTEM - EMPLOYEE ATTENDANCE MANAGEMENT SYSTEM PROJECT

   Current System

In the present system all work is done on paper. The whole session attendance is stored in register and at the end of the session the reports are generated. We are not interested in generating report in the middle of the session or as per the requirement because it takes more time in calculation. So, We are not able to get employees regularity report and take necessary action on employees whenever we want because of having very time consuming process.

   Weaknesses in Current System

1.     Not User Friendly:

The existing system is not user friendly because the retrieval of data is very slow and data is not maintained efficiently.

2.     Difficulty in report generating:

We require more calculations to generate the report so it is generated at the end of the session. And the employee not gets a single chance to improve their Attendance.

3.     Manual control:

All calculations to generate report are done manually so there is greater chance of errors.

4.     Lots of paperwork:

Existing system requires lot of paper work. Loss of even a single register/record led to difficult situation because all the papers are needed to generate the reports.

5.     Time consuming:

            Every work is done manually so we cannot Generate report in the middle of the session or as per the requirement because it is very time consuming.

 4.2 Requirements of New System:

 4.2.1 User Requirements.

               The User requirements for the new system are to make the system fast, flexible, less prone to errors and reduce expenses and save time.

Ø  Time can be saved in scheduling the salary if it were available to make question banks to store questions for different Employee in advance and can be used as per required.

.

Ø  A system that can automate the checking of answers which are pre-stored so that results can be generated as soon as the Employee gives the reason.

Ø  A facility that can generate result charts as per required without manual interference for providing how a task is to be done instead only asking what is to be done.

Ø  The system should have Employee & its salary records on hand which can be used as per required only by authorized personnel.

Ø  The New system should be more secure in managing Employee records and reliable enough to be used in any condition.

Ø  Finally, it should prove cost effective as compared to the current system.

 4.3 Feasibility Study: ATTENDANCE MANAGEMENT SYSTEM PROJECT

             A key part of the preliminary investigation that reviews anticipated costs and benefits and recommends a course of action based on operational, technical, economic, and time factors. The purpose of the study is to determine if the systems request should proceed further.

Ø Economically Feasibility:

              The system being developed is economic with respect to Business or point of view. It is cost effective in the sense that has eliminated the salary work completely. The system is also time effective because the calculations are automated which are made at the end of the month or as per the employee requirement. The result obtained contains minimum errors and are highly accurate as the data is required.

Ø Technical feasibility:

             The technical requirement for the system is economic and it does not use any other additional Hardware and software.

Ø Behavioral Feasibility:

             The system working is quite easy to use and learn due to its simple but attractive interface. user requires no special training for operating the system.

 4.4   Features of the New System.

             The new system has been designed as per the user requirements so as to fulfill almost all them.

1.     User Friendly: -

The proposed system is user friendly because the retrieval and storing of data is fast and data is maintained efficiently. Moreover the graphical user interface is provided in the proposed system, which provides user to deal with the system very easily.

2.     Reports are easily generated:-

Reports can be easily generated in the proposed system so user can generate the report as per the requirement (monthly) or in the middle of the session. User can give the notice to the employees to be regular.

3.     Very less paper work:

The proposed system requires very less paper work. All the data is feted into the computer immediately and reports can be generated through computers. Moreover work becomes very easy because there is no need to keep data on papers.

4.     Computer operator control:

Computer operator control will be there so no chance of errors. Moreover storing and retrieving of information is easy. So work can be done speedily and in time. 

DATA FLOW DIAGRAM - STUDENT ATTENDANCE MANAGEMENT SYSTEM PROJECT

It is a graphical representation of the data. It identifies the path the data will take, what process will take place to it from one from to another.

           A DFD is a graphical representation of the flow of data through an information   system. It can be used to provide a clear representation of any function. It doesn’t provide information about the timing of processes or about whether processes will operate in sequence. Therefore it is different from a flowchart.

Data Flow Diagrams are composed of the four basic symbols shown below.          

Ø  The External Entity symbol represents sources of data to the system or destinations of data   from the system.

Ø  The Data Flow symbol represents movement of data.

Ø  The Data Store symbol represents data that is not moving (delayed data at rest).

Ø  The Process symbol represents an activity that transforms or manipulates the data (combines, reorders, converts, etc.).

Ø  Any system can be represented at any level of detail by these four symbols.

1.     Data Flow:

         It is represented by a line arrowhead showing the direction of flow. It shows the flow of information from source to its destination. Information always flows to or from process and may be written, verbal or electronic.

                 Symbol:

           

2.     Process:

A circle represents a process. It shows the procedures those use the data in the  system.    

            

1.     External Entities :

A Rectangle represents an external entity. They either supply data or receive data.

                    They do not process data.

2.     Data Store:

A process references the data store in the system.The data flow is shown by the opened ended rectangles.

                   

               

Ø CONTEXT DIAGRAM:

                             The context diagram is a top-level view of an information system that shows the boundaries and scope. It describes the main objective of the system and the entities involved.

Project Title:

Ø  Attendance Management System.

Software Used:

Ø  Microsoft Visual Studio 2008

Ø  Microsoft SQL Server 2005

Conclusion - ATTENDANCE MANAGEMENT SYSTEM PROJECT

The main aim of this system was to put what we learnt in our software engineering class into practice. The Attendance system designated to our team allowed us to fully exercise the techniques of XP.

We were able to attain our set objectives, and this helped us again confidence in writing our own code and our own applications. In addition, the use of serialization was an experimentation to cut down the time taken in designing.

The front-ends and back-ends of applications separately. With our OOP approach and serialization, we only concentrated on designing the objects/classes, and then just serialized them on disk. So we did not spend any time on designing how to store data.

We also worked as a team, and gained some experience on how professional programmers work in the industry.

There is always room for improvement, and the software we created can also be improved. This is especially because we had to create it within a limited time. With more time, the software can be improved to include security and different types of users. This would be the first step in marking the software network-enabled, and eventually web-enabled.



This was our original after-thought to programming the software, and we had chosen XML. In addition, the software can also be improved in terms of the calculations it addition, the software can also be improved in terms of the calculations it can do, and more flexibility in the rates used in calculations per employee.