ATTENDANCE MANAGEMENT SYSTEM

1.Introduction

1.1 Purpose
The document provides detailed information about functional and non-
functional requirements of Attendance Management System. The purpose of this document is
to describe all the details which is to be implemented as a part of System Implementation.

1.2 Scope
The system allows the faculties to fill up and maintain the attendance of the
students on the daily basis. Also Faculties can send SMS to the parents of the students
informing them about the absence of their child in the class. The system also provides various
reports of attendance like Daily Reports, Weekly Reports, Monthly Reports etc.

1.3 Overview
The system provides an easy solution to track and maintain student’s attendance
and its statistics.

2. General Description
The attendance management system replaces traditional and manual
attendance system by which a lot of papers were wasted. The faculty can directly fill up the
attendance using his/her laptop/pc. The Faculty can edit the attendance of the student as per
his/her wish. The system also provides various reports to find various statistics. Also the system
allows to send SMS to the absent student’s parents.

The primary requirement for the faculty is that he/she should have Laptop/PC to
install the system and Internet Connection to send SMS.

2.1 User Manual

The user manual should be provided with all the description of the system. It
should describe the working flow of the system. It should be able to guide the user of the
system and make its usage easy and user friendly.
3. Functional Requirements

3.1 Description
The system will manage the data of the students and faculties in a well organized
database. The system will also maintain the logs of SMS sent to each student on a daily basis.
The faculty will fill the attendance by clicking the name of the student. The faculty will send
SMS to the parents by clicking the send SMS button in front the name. The system allows the
faculties to add and delete student’s data. Also it allows the edit or delete attendance of the
particular student. Overall, it manages the automatic attendance management system.

3.2 Technology
The system will be implemented using Dot Net Technology and C# Programming
Language

4. Interface Requirements

4.1 GUI
The GUI refers the layout and design which will be used by the faculties.

GUI 1: This GUI consists of main menus like ADD, EDIT, REPORTS, HELP

GUI 2: This GUI will have detailed option of ADD Menu. This Menu will help the
admin to add the details of Students and Faculties. Also this will have the menu of filling the
attendance of each student.

GUI 3: This GUI will have EDIT Menu. This Menu allows the user to edit or delete
any details of Students and Faculties. Also It allows the faculties to edit or delete attendance of
particular student.

GUI 4: This GUI will have REPORT Menu. This Menu allows the user to create
attendance reports on a daily, weekly and monthly basis.

GUI 5: This GUI will have HELP Menu. This Menu will have all the information
regarding the system. It will have guidelines on how to use the system efficiently.

4.2 Hardware Interface

The system should be easily installed in the PC/Laptop and work in all the
environments.

4.3 Software Interface

 The system generates various reports of attendance. To view the reports easily,
the PDF Reader software is required.

5. Performance Requirements
The system once installed on the PC/Laptop will work smoothly and efficiently. It
will maintain the database in a well organized manner. It will send SMS to the parents on one
click. It will generate all the reports as and when required.

6. Design Constraints
The system will be developed and deployed within 35 days.

7. Other Non-Functional Requirements

7.1 Security
The faculty should not give their LogIn Credentials to the students or other
faculties, so that no one alter the details entered by them.

7.2 Reliability
The system is reliable to use as the system is developed using latest
development tool and database softwares.

7.3 Availability
The system will be available to the faculties only in the school/college premises
to enter the details. The faculties cannot enter details from home or any other places.

7.4 Maintainability
The system should be maintained efficiently. Regular back-ups of the database
should be taken so as to recover in case of Crash.

7.5 Reusability
The system once developed and deployed to one Client can be given to other
Clients if their requirements are same or partly different than developed system.
8. Operational Scenarios
The operational scenario of the system is that it allows the faculties to manage
and maintain the attendance of the students very efficiently and in an easy way. It also allows
the faculties to send SMS to the parents to inform the absence of their child.

9. Preliminary Schedule
Design a Database : 5 Days

Design GUI : 10 Days

Back-End Code : 15 Days

System Testing : 2 Days

Total Days: : 32 Days