INDEX

SR NO. 1 2 3 4 5 6 7

8 9 10 11 12 13 14

CONTENTS ACKNOWLEDGEMENT PROBLEM DEFINITION SCOPE OF THE SYSTEM PROPOSED SYSTEM FACT FINDING TECHNIQUES FEASIBILITY STUDY ENTITY RELATIONSHIP DIAGRAM DATA FLOW DIAGRAM TABLE DESIGN INPUT/OUTPUT SCREEN OUTPUT SCREEN REPORT LAYOUT CONCLUSION BIBLIOGRAPHY

PAGE NO. 2 3 4 5 6 8 10 11 15 18 25 29 30 31

ACKNOWLEDGEMENT The satisfaction that accompanies that the successful completion of any task would be incomplete without the mention of people whose ceaseless cooperation made it possible whose constant guidance and encouragement crown all efforts with [Link] are grateful to our project guide Mrs. Irfana Patel for her guidance, inspiration and constructive suggestions that helped us in preparing this project .We also thank our classmates who have helped us to complete this project.

PROBLEM DEFINITION Attendance Management System is for daily student attendance in schools, colleges and institutes to access attendance information of a particular student of 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.

SCOPE OF THE SYSTEM The scope of the system is that it will work for colleges, schools and institutes. It can be modified according to the demand of the user.

PROPOSED SYSTEM The purpose developing attendance management system is to computerize the way of taking attendance. Another way of developing this system is to generate the report automatically at the end of the session or in between of the session.

FACT FINDING TECHNIQUES This process includes gathering of information for various aspects related to the project. It is done stepwise so as to reduce confusions and everything is done in an organized way. The Fact Finding Technique has many sections which includes the following: QUESTIONNAIRES: Questions based on this project were asked. We used this technique in the initial and final phases of our project. In the initial phases we prepared questionnaires to get some information about the system. Questions asked were both open ended and closed ended which were related to the system, updation and rules for record maintainance.

OBSERVATIONS: It allows the analyst to gain information. They cannot be obtained by any other fact finding technique. Observation shows the analyst what would happen.

FEASIBILITY STUDY The Feasibility Study should examine the following 3 main areas: Economical Feasibility Technical Feasibility Behavioural Feasibility ECONOMICAL FEASIBILITY The system being developed is economic with respect to school or colleges point of view. It is cost effective in the sense that has eliminated the proper 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 users requirement. The result obtained contains minimum errors and highly accurate as the data is required.

TECHNICAL FEASIBILITY The technical requirement for the system is economic and does not use any other additional hardware or software.

BEHAVIOURAL 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.

ENTITY RELATIONSHIP DIAGRAM

1 Student Attends

M Lecture

Records

M Teacher

Conducted by

M M Attendance Defaulters

10

DATA FLOW DIAGRAM CONTEXT LEVEL DFD

details Student teacher Teachers details Subject details Student file Student details Student System 0.0

records Student details Teacher details Subject Student attendance details Attendance file

11

1ST LEVEL DFD

Student entity

2.0 Lecture Teacher details

Teacher entity details

Teacher

12

Teacher details Subject Teacher 3.0 Subject details conduct details details lecture Teacher-Subject

Subject-wise Month-wise attendance

4.0 Creating Attendance Record

accept

Teacher Attendance Record

13

4.1 Defaulters List Defaulters Attendance Report

defaulters H.O.D report

details Student details Attendance details Teacher Reports 5.0

attendance H.O.D report

14

TABLE DESIGN ADMIN TABLE Sr no 1 2 3 Field name Data type description User name text User type administrator password text Use type administrator User type text User type administrator/user TEACHER TABLE Sr no 1 2 Field name T_id T_name Data type int text description Primary key User type administrator

15

ATTENDANCE TABLE

SR NO 1 2 3 4 5

FIELD NAME S_name Status

DATA TYPE Text Int

DESCRIPTION User type administrator Primary key of attendance table Primary key User type administrator User type administrator

Semester Int Subject Text Month Text

LECTURE TABLE SR NO 1 2 3 FIELD NAME Code Lecture name Semester DATA TYPE Int Text Int DESCRIPTION Primary key User type administrator Primary key

16

STUDENT TABLE SR NO 1 2 3 4 FIELD NAME S_id S_name Course Semester DATA TYPE Int Text Text Int DESCRIPTION Primary key User type administrator User type administrator Primary key

17

INPUT OUTPUT SCREENS

ADD FORM

18

STUDENT FORM

STUDENT TABLE S_id S_name course sem

SAVE

CLEAR

CANCEL

19

TEACHER FORM

TEACHER INFORMATION T_id T_name

SAVE

CLEAR

EXIT

20

USER FORM

21

ATTENDANCE FORM

22

DEFAULTERS FORM

23

ATTENDANCE STATUS FORM

24

OUTPUT SCREEN

STUDENT FORM

STUDENT TABLE S_id S_name course sem

01 ZEBA B.C.S I

SAVE

CLEAR

CANCEL

25

STUDENT FORM

STUDENT TABLE S_id S_name course sem

02 JENNIFER B.C.S II

SAVE

CLEAR

CANCEL

26

TEACHER FORM

TEACHER INFORMATION T_id T_name 01 LUBNA

SAVE

CLEAR

EXIT

27

TEACHER FORM

TEACHER INFORMATION T_id T_name 02 SARAH

SAVE

CLEAR

EXIT

28

REPORT LAYOUT STUDENT FORM

1 2

01 02

ZEBA B.C.S JENNIFER B.C.S

I II

EXIT

TEACHER FORM
SR NO. 1 2 T_ID O1 02 T_NAME LUBNA SARAH

EXIT

29

CONCLUSION This helped us in understanding how actually the Attendance Management System works and how all the documents, record keeping and handling of queries in the existing system is done.

30

BIBLIOGRAPHY [Link]

Database system Thomas. M. Connolly Carolyn .E. Begg Software Engineering Roger Pressman

31