Student Attendance Management System

ATTENDANCE MANAGEMENT SYSTEMUnder the guidance of Ms. Snehal Ramanathan

TEAM MEMBER DETAILS

Virendra Manuji Chavda (9) Vinit Loonchand Chopra(10) Shubhangi Satishchandra Desai (11) Anilkumar Hasmukhbhai Patel (34)

PROJECT PROFILE

Attendance Management System is software developed for daily student attendance in schools, colleges and institutes.

It facilitates to access the attendance information of a particular student in a particular class. The information is sorted by the operators, which will be provided by the teacher for a particular class.

This system will also help in evaluating attendance eligibility criteria of a student.

CURRENT SYSTEM

Existing Attendance Management System of the Institute is totally working manually. All the Information’s are handled manually in the registers or other documents.

The process of the work is mainly divided in two parts, first is to take attendance on sheet & enter details into the registers. And then at the end of the session or semester attendance is calculated manually & reports are generated

LIMITATIONS OF THE CURRENT SYSTEM

Wastage of time Wastage of the human resource Security of data is less Accessing any data from the manual

system is very difficult Possibility of occurrence of errors

means accuracy is less

PROPOSED SYSTEM

This Application is built for automating the processing of attendance. It also enhances the speed of the performing attendance task easily.

It also generates periodic reports to keep a check on the students who are regular & who are not

This system is very useful to the office staff also because they can generate various types of reports and submit them to respective faculties also or also can be submitted to the College Coordinator.

ADVANTAGES OF PROPOSED SYSTEM

A Computer can work more efficiently then compared to a human being so human resources are saved

Data accuracy is maintained

Data can be accessed easily and randomly

Unauthorized persons cannot access the data

Saves the time utmost

HARDWARE & SOFTWARE SPECIFICATIONS

Hardware Requirements Pentium 90 MHZ or Faster and 96 MB Ram (Client) Pentium 133 MHZ or Faster and 128 Ram (Server)

Operating System Windows 9x, Windows XP or any above Windows

operating systems

Software Requirements Microsoft Visual Studio Asp.NET

FEASIBILITY STUDY

FEASIBILITY STUDY

A feasibility study is a short, focused study, which aims to answer a number of questions Does the system contribute to the overall

objectives of the Organization? Can the system be implemented using current

technology and within given cost and schedule constraints?

Can the system be integrated with systems which are already in place?

FEASIBILITY STUDY (CONT..)

All systems are feasible, given unlimited resources and infinite time. It is both necessary and prudent to evaluate the feasibility of the project at System study phase itself. The feasibility study to be conducted for this project Involves.1. Technical Feasibility2. Operational Feasibility3. Economic Feasibility

FACT FINDING TECHNIQUES

FACT FINDING TECHNIQUES USED…

For the development of the Student Attendance Management System, we have used three fact-finding techniques. Observation Record Review Interview

REQUIREMENT SPECIFICATIONS

According to the requirements the system should minimum generate following kinds of reports. Semester wise AttendanceDaily AttendanceAttendance for extra classSubject wise attendanceLeave reports

ApprovedNot approvedMedical leaves

Black listed below 50%Black listed below 80%

FEATURES PROVIDED Admin

Add & Modify details of student faculty subject (if required)

Office Staff Generate various types of reports Send notice to black listed Students

Faculty Attendance on basis of

subject day by day

Check various generated Reports 

SYSTEM ANALYSIS & DESIGN

DESIGN OF AN INFORMATION SYSTEM

SYSTEM DEVELOPMENT LIFE CYCLE System development life cycle (SDLC) is an

organizational process of developing and maintaining systems.

Following are the different phases of software development cycle:1. System study2. Feasibility study3. System Analysis4. System Design5. Coding6. Testing7. Implementation8. Maintenance

ENTITY RELATIONSHIP DIAGRAM

DATA FLOW DIAGRAM

CONTEXT LEVEL DIAGRAM

FIRS

T LE

VEL

DIA

GR

AM

DATA DICTIONARY

1. LOGIN

SR. NO FIELD NAME DATA TYPE DESCRIPTION1. Username varchar2(30) Primary Key2. Password varchar2(20)3. Usertype varchar2(10)

Description : Login table stores details for authentication

2. STUDENT DETAILS

SR. NO FIELD NAME DATA TYPE DESCRIPTION1. stud_id varchar2(5) Primary Key2. Stud_name varchar2(40)3. Address varchar2(50)4. contact_details varchar2(12)5. Course varchar2(3)6. Semester number7. Batch varchar2(9) eg : 2009-2012

Description : Stores students’ details

3. FACULTY DETAILS

SR. NO FIELD NAME DATA TYPE DESCRIPTION1. faculty_id varchar2(5) Primary Key2 faculty_name varchar2(50)3. contact_details varchar2(40)4. Username Varchar2(30) Foreign Key

Description : Stores faculties’ details

4. OFFICE STAFF DETAILS

SR. NO FIELD NAME DATA TYPE DESCRIPTION1. staff_id varchar2(5) Primary Key2 member_name varchar2(50)3. designation varchar2(40)4. Username Varchar2(30) Foreign Key

Description : Stores office staff members’ details

5. ATTENDANCE DETAILS

SR. NO FIELD NAME DATA TYPE DESCRIPTION1. attend_id varchar2(5) Primary Key2 Date date/time3. Time varcahr2(10)4. faculty_id varchar2(5)5. present_students varchar2(MAX) All the present

students’ id are stored as a

string Eg : “1-2-5-8-10-

11”6. sub_code varchar2(5)

Description : Stores attendance details

6. SUBJECT DETAILS

SR. NO FIELD NAME DATA TYPE DESCRIPTION1. sub_code varchar2(5) Primary Key2 sub_name varchar2(50)3. semester varchar2(5)

Description : Stores subject Details

7. EXTRA CLASS ATTENDANCE DETAILS

SR. NO FIELD NAME DATA TYPE DESCRIPTION1. attend_id varchar2(5) Primary Key2 Date date/time3. Time varcahr2(10)4. faculty_id varchar2(5)5. present_students varchar2(MAX) All the present

students’ id are stored as a

string Eg : “1-2-5-8-10-

11”6. sub_code varchar2(5)

Description : Stores attendance details for the extra classes taken

8. LEAVE DETAILS

SR. NO FIELD NAME DATA TYPE DESCRIPTION1. leave_id varchar2(5) Primary Key2 Date date/time3. from_date Date/time4. to_date Date/time5. stud_id varchar2(5)6. Type varchar2(10) i.e. : Medical or

General7. Status Boolean Approved – True

Not Approved – False

Description : Stores leave details

THANK YOU…