Vous êtes sur la page 1sur 83

Institute Attendance Management System

  • 1 Description of Organization: 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 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.

1.1 Objectives of Organization.

The main objective is checking the report of the Students and employees. 1.) Security 2.) Report maintenance 3.) Searching 4.) Spacious (lot of entries can be done) 5.) Checking the regularity of students & teachers. 6.) Checking how many lectures of the teacher in a day. 7.) Checking how many lectures they are attending.

1

Institute Attendance Management System

1.2 ORGANIZATIONAL STRUCTURE

CHAIRMAN DIRECTOR CO-ORDINATORS HEAD OF HEAD OF DEPARTMENT DEPARTMENT FACULTY SUPPORT STAFF STUDENT
CHAIRMAN
DIRECTOR
CO-ORDINATORS
HEAD OF
HEAD OF
DEPARTMENT
DEPARTMENT
FACULTY
SUPPORT STAFF
STUDENT

Fig 1.1 Block diagram of the Organisational Structure

2

Institute Attendance Management System

  • 1.3 KEY RESULT AREAS (KRAs)

1) Attendance report will be maintained with at least 75% attendance, if less than this then results in loss of marks for the exam.

2) Director will take action against the student or if specified then with the employees for any such reason.

  • 1.4 FUNCTIONS OF ORGANIZATION

    • Login Process

    • Student entry Process

    • Attendance report Process

    • Action/ Response Process

    • Marks Process

3

Institute Attendance Management System

2 DESCRIPTION OF PROPOSED INFORMATION SYSTEM

A brief description of all processes & sub processes in narrative form

  • 2.1 LOGIN PROCESS: This process includes the procedure for logging into the system based on the admin privileges. Here, the admin login into the system by providing User_Name and password. If the username & password are correct then, the operator will be able to access the system otherwise he will not.

  • 2.2 STUDENT ENTRY PROCESS: In this process, enter the student details, store all student details.

  • 2.3 ATTENDANCE REPORT PROCESS: This process taking attendance of the student and generating the attendance report.

  • 2.4 MARKS PROCES: In this process marks allotment is done all student.

  • 2.5 ACTION/ RESPONSE PROCESS: In this process action taking against the defaulter student who's attendance is low.

4

Institute Attendance Management System

  • 3 SOFTWARE REQUIREMENT SPECIFICATIONS

3.1

INTRODUCTION

The following subsections of Software Requirement Specifications Document should facilitate in providing the entire overview of the Information system “Institute Attendance Management System” under development. This document aims at defining the overall software requirements for your end users. Efforts have been made to define the requirements of the Information system exhaustively and accurately.

  • 3.1.1 PURPOSE

The main purpose of Software Requirement Specifications Document is to describe in a precise manner all the capabilities that will be provided by the Software Application Institute Attendance Management System”. It also states the various constraints which the system will be abide to. This document further leads to clear vision of the software requirements, specifications and capabilities. These are to be exposed to the

development, testing team and end users of the software.

  • 3.1.2 SCOPE

The software product “Institute Attendance Management System” will be an application that will be used for maintain the records in an organized manner and to replace old paper work system. The application will manage the information about student details, attendance details, etc. It is also designed to calculate the attendance marks. Specific reports will also be generated regarding the student attendance and marks details.

5

Institute Attendance Management System

3.1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

Following abbreviations have been used throughout this document:

IEEE

: The Institute of Electrical and Electronics Engineers, Inc.

SRS

: Software Requirements Specification

3.1.4

REFERENCES

http://www.google.com

www. Institute Attendance Management System com

3.1.5

OVERVIEWS

The rest of this SRS document describes the various system requirements, interfaces, features and functionality in detail. This document has been prepared in accordance with the IEEE STD 830-1998, IEEE Recommended Practice for Software Requirements Specification. [IEEE 830-1998 (1998)]. It provides the information of Product perspective, Product functions, User characteristics, Constraints, Assumptions and

dependencies and specific requirement.

6

Institute Attendance Management System

3.2 THE OVERALL DESCRIPTION

This section of the SRS describes all general factors of the product and its requirements.

3.2.1 PRODUCT PERSPECTIVE

The application will be a window-based, self contained and independent software

product.

Front end client

application (with data

entry/update/delete/

view and reporting

facility)

Backend Database
Backend
Database

3.2.1.1 SYSTEM INTERFACES

None.

3.2.1.2 USER INTERFACES

The application that will be developed will have a user friendly and menu based interface. Following screens will be provided:

A login screen for entering the username and password, so that the authorized user can have an access without any problems. 1.) There will be a screen which will be displaying the major tasks that the system will be performing i.e. Maintain attendance , View report student wise, Update marks according to attendance report, Student entry, Total lectures in a month , Response to the attendance report

7

Institute Attendance Management System

  • 3.2.1.3 SOFTWARE INTERFACES:

Front-end -- VB --

Back-end

oracle, SQL Server

Platform

Windows XP/NT 32x , 64x , Windows Vista

-- Primary memory--Minimum requirement 256MB

PROCESSOR--PENTIUM 4

  • 3.2.1.4 HARDWARE INTERFACES:

Screen resolution of at least 800*600- required for proper and complete viewing of screen. Higher resolution would not be a problem. Support for printer (dot-matrix/DeskJet/inkjet etc. - any will do) - that is, appropriate drivers are Installed and printer connected printer will be required for printing of reports.

  • 3.2.1.5 COMMUNICATIONS INTERFACES

None.

  • 3.2.1.6 MEMORY CONSTRAINTS

At least 72MB RAM and 4GB space on hard disk will be required for running the

application.

8

Institute Attendance Management System

  • 3.2.1.7 OPERATIONS

The product release will not cover any automated attendance aspects of the database. The DBA at the client site (i.e. the student) will be responsible for manually deleting old/non required data. Database backup and recovery will also have to be handled by the DBA.

  • 3.2.1.8 SITE ADAPTATION REQUIREMENTS

The terminals at client side will have to support the hardware and software interfaces

specified.

  • 3.2.2 PRODUCT FUNCTIONS

The system will allow access only to authorized users entering the appropriate password. A summary of the major function that the software will perform are as follows:

A login facility to allow only the authorized users to have an access to the software system. This prevents the unauthorized users to misuse the software.

  • 3.2.3 USER CHARACTERISTICS

Educational level: Director should be comfortable with English language.

Experience: The director should be well versed about the processes of the Institute.

Technical expertise: Director should be comfortable in using general purpose applications on a computer.

9

Institute Attendance Management System

 

3.2.4

CONSTRAINTS

GUI is only in English.

Login and password is used for identification of director and there is no facility for student.

3.2.5

APPORTIONING OF REQUIREMENTS

Not required.

  • 3.3 SPECIFIC REQUIREMENTS

This section contains the software requirements to a level of detail sufficient to enable

designers to design the system and the tester to test that system.

  • 3.3 EXTERNAL INTERFACES

This interface will be the actual interface through which the user will communicate with

the application and perform the desired tasks. The following screens will be provided:

  • 3.1 USER INTERFACES

The following screens will be provided:

  • 3.1.1 SOFTWARE INTERFACES:

Refer to 3.2

10

Institute Attendance Management System

  • 3.1.2 HARDWARE INTERFACES:

Refers to 3.3

  • 3.1.3 COMMUNICATION INTERFACES

None

  • 3.2 SYSTEM FEATURES MODULE NAME

    • Login Process

    • Student entry Process

    • Attendance report Process

    • Action/ Response Process

    • Marks Process

DESCRIPTION

  • LOGIN PROCESS: This process includes the procedure for logging into the system based on the admin privileges. Here, the admin login into the system by providing User_Name and password. If the username & password are correct then, the operator will be able to access the system otherwise he will not. Validity Checks

Unique admin username.

Password should have 10 digits not less then it.

Can’t leave username and password blank.

11

Institute Attendance Management System

  • STUDENT ENTRY PROCESS: In this process, enter the student details, store all student details. Validity Checks

For each student enrollment number will be unique

Enrollment no. will always be in numeric form.

Student name cannot be blank.

Student name will always accept character.

Year cannot be blank.

Course name cannot be blank

  • ATTENDANCE REPORT PROCESS: This process taking attendance of the student and generating the attendance report. Validity Checks

Roll_no should not blank.

Total_lect should not blank

Total_attendance should not blank.

Roll-no, total_lect, total_attendance are in a numeric form.

  • MARKS PROCESS:

In this process marks allotment is done all student.

Validity Checks

It is a auto generated after checking the total attendance.

12

Institute Attendance Management System

It is in a numeric form.

  • ACTION/ RESPONSE PROCESS: In this process action taking against the defaulter student whose attendance is low. Validity Checks

Director takes action and response.

Attendance should be low for taking the action.

3.3 PERFORMANCE REQUIREMENTS

None

3.4 LOGICAL DATABASE REQUIREMENTS

The proposed information system contains the following data tables in its database

collection.

Student table : S_name, Roll No, Course, Semester

Attendance table: Total_Attendance, Total_lect, Roll_no

Mark sheet table: Lecture attended, Marks, Total_Marks, RollNo

3.5 DESIGN CONSTRAINTS

None

13

Institute Attendance Management System

3.6 SOFTWARE SYSTEM ATTRIBUTE

  • Reliability

This application is a reliable product that produces fast and verified output of all its processes.

  • Security

The application will be password protected. The director will have to enter the correct

user name and password in order to access the software.

  • Maintainability

The system will be designed in a maintainable order. The system can be easily modified

and renewed according to the need of the user.

  • Portability

The system will be easily portable on any windows based application that has oracle

installed.

  • Availability

This application will be available to use for your end users and help them to carry out

their operations conveniently.

3.7 OTHER REQUIREMENTS

None

14

Institute Attendance Management System

  • 2.1 PHYSICAL DESIGN

The Information System under study is Attendance Management system”. This is an attempt to computerize the day to day activities of the Institute. The information system includes the activities like student records, institute activities, attendance report, marks report, student attendance etc. The system must provide the flexibility of generating the required documents on screen as well as on printer as and when required. This information system consists of various processes which imbibe in themselves the various goals of Attendance management. Some of these processes function independently whereas as a few others are linked to each other. The entire description of each process with related inputs, outputs and data item will be illustrated in depth in this session. The system generates various reports which consist of overall student records, attendance report, student marks report etc.

  • 2.2 BLOCK DIAGRAM

A block diagram is a specialized, high-level type of flowchart. Its highly structured form presents a quick overview of major process steps and key process participants, as well as the relationships and interfaces involved. Block diagram is a diagram of a system, in which the principal parts or functions are represented by blocks connected by lines that show the relationships of the blocks. Identification of all elements during the initial stage of a process helps to ensure that the team contains all the people necessary to continue with the task. In many cases detailed drawings and/or hardware are not available and the block diagram serves to visualize the system and identify its interdependencies. It is a simple pictorial representation of a system/sub-systems linked

15

Institute Attendance Management System

ustrate the relationships between components/subsystems. A block diagram of the information system under study with all operational processes has been drawn below:

Block Diagram

.Admin Attendance Details Student details Attendance Student entry Attendance User Name report Process Process and Password
.Admin
Attendance
Details
Student details
Attendance
Student entry
Attendance
User Name
report
Process
Process
and
Password
Attendance Details
Login Process
Attendance
Details
Marks Details
Action
Marks Process
Process
Marks Details
Marks report

Fig No 2.1: Block Diagram of the System

16

Institute Attendance Management System

  • 2.3 LIST OF PROCESSES INCLUDED IN THE INFORMATION SYSTEM

UNDER STUDY

Login process

Student Entry Process

Attendance Report Process

Marks Process

Action and Response Process

  • 2.4 LIST OF INPUTS AND OUTPUTS FOR EACH PROCESS IDENTIFIED

SNO

PROCESS

INPUT

OUTPUT

1.

LOGIN PROCESS

USERNAME AND PASSWORD

VERIFICATION

2.

ATTENDANCE REPORT

STUDENT ROLL NO.

STUDENT

PROCESS

REPORT

3.

STUDENT ENTRY PROCESS

STUDENT DETAILS

STUDENT ROLL NO.

4.

MARKS PROCESS

STUDENT ROLL NO.

MARKS REPORT

5.

ACTION AND RESPONSE

STUDENT ROLL NO.

ACTION TAKEN

17

Institute Attendance Management System

1.4 USE CASE DIAGRAM

What is a Use Case Diagram?

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral

diagram defined by and created from a Use-case analysis. Its purpose is to present a

graphical overview of the functionality provided by a system in terms of actors, their

goals (represented as use cases), and any dependencies between those use cases.

The main purpose of a use case diagram is to show what system functions are

performed for which actor. Roles of the actors in the system can be depicted.

ELEMENTS OF A USE CASE DIAGRAM:

1.

Actors:

An actor portrays any entity (or entities) that perform certain roles in a given

system. The different roles the actor represents are the actual business roles of

users in a given system. An actor in a use case diagram interacts with a use case.

An Actor is represented by:

Institute Attendance Management System 1.4 USE CASE DIAGRAM What is a Use Case Diagram? A use

18

Institute Attendance Management System

  • 2. Use Case: A use case in a use case diagram is a visual representation of distinct business functionality in a system. The key term here is "distinct business functionality." To choose a business process as a likely candidate for modelling as a use case, you need to ensure that the business process is discrete in nature. A Use Case is represented by:

Institute Attendance Management System 2. Use Case: A use case in a use case diagram is
  • 3. System Boundary: A system boundary defines the scope of what a system will be. A system cannot have infinite functionality. So, it follows that use cases also need to have definitive limits defined. A system boundary of a use case diagram defines the limits of the system. The system boundary is shown as a rectangle spanning all the use cases in the system. Represented as: For example:

Institute Attendance Management System 2. Use Case: A use case in a use case diagram is

19

Institute Attendance Management System

4.

Relationships:

There are several types of relationships that may appear on a use case diagram:

An association between an actor and a use case.

An association between two use cases.

A generalization between two actors.

A generalization between two use cases.

The relationships are shown by the one headed arrows in a use case diagram:

Institute Attendance Management System 4. Relationships: There are several types of relationships that may appear on

20

Institute Attendance Management System

Institute Attendance Management System Login Add/update student details View student Admin Add/update attendance Allot marks Marks/attendance
Login Add/update student details View student Admin Add/update attendance Allot marks Marks/attendance report View marks report
Login
Add/update student
details
View student
Admin
Add/update attendance
Allot marks
Marks/attendance
report
View marks
report

Fig. 2.2 USE CASE DIAGRAM OF THE SYSTEM

21

Institute Attendance Management System

1.4 DATA FLOW DIAGRAMS

A data-flow diagram (DFD) is a graphical representation of the "flow" of data

through an information system. DFDs can also be used for the visualization of data

processing (structured design).On a DFD, data items flow from an external data

source or an internal data store to an internal data store or an external data sink, via an

internal process.

Context Diagram- Level 0 DFD

On the context diagram (also known as the Level 0 DFD) the system's interactions

with the outside world are modeled purely in terms of data flows across the system

boundary. This level shows the overall context of the system and its operating

environment and shows the whole system as just one process.

Student Details Attendance Report INSTITUTE Marks Report Marks Details ATTENDANCE Admin MANAGEMENT Attendance Details SYSTEM
Student Details
Attendance Report
INSTITUTE
Marks Report
Marks Details
ATTENDANCE
Admin
MANAGEMENT
Attendance Details
SYSTEM

Fig. 2.3 LEVEL 0 DFD

22

Institute Attendance Management System

DFD level 1

The Level 1 DFD shows some of the detail of the system being modeled. It shows how

the system is divided into sub-systems (processes), each of which deals with one or more

of the data flows to or from an external agent, and which together provide all of the

functionality of the system as a whole. The purpose of this level is to show the major and

high-level processes of the system and their interrelation. The level 1 DFD of Attendance

management system is given below: Student details 2 Student Student Update attendance 3 attendance admin 1
management system is given below:
Student details
2
Student
Student
Update attendance
3
attendance
admin
1
Attendance
Login
Attendance report
Update marks
4
Marks
Marks
Marks report
5
Action &
response

Fig.2.4 DFD 1 LEVEL

23

Institute Attendance Management System

1.6 ERD

It is a detailed logical representation of data for an organization and uses four main constructs:

Relationships It is a reason for associating 2 entities, also called binary relations

because they involve 2 entity types. Data Entries An entity is a fundamental component of an organization about which

data may be maintained. Related attributes - Each entity type has a set of attributes associated to it. An

attribute is a property or characteristic of an entity that is of interest to an organization. Keys and identifiers They are attributes or set of attributes that distinguish one instance of an entity type from other instances.

Roll no. Semester No. Of lectures attended Course Roll no Name No. of lectures not attended
Roll no.
Semester
No. Of lectures
attended
Course
Roll no
Name
No. of lectures
not attended
Description
m
m
Student
Has
Attendance
m
Get
m
Lecture percentage Roll no. Marks Action
Lecture
percentage
Roll no.
Marks
Action
Total marks
Total marks

24

Fig no 2.5-:Entity Relationship Diagram

Institute Attendance Management System

2. DATABASE DESIGN

The information system of “Attendance Management System” performs its function

with the help of the data store in certain repositories called Databases of the system.

Detailed descriptions of the various databases included in the information systems are

tabulated as follows:

  • 1. STUDENT TABLE

FIELD NAME

FIELD TYPE

FIELD SIZE

DESCRIPTION

       

ROLLNO

NUMBER

10

Roll no. of student , Primary key

       

STNAME

VARCHAR2

30

Student Name , Not null

       

COURSE

VARCHAR2

3

Course taken by Student,

Not null

       

SEMESTER

NUMBER

1

Semester of Student,

Not null

       
       

Table 2.1.Student table

25

Institute Attendance Management System

  • 2. ATTENDANCE TABLE

       

FIELD NAME

FIELD

FIELD SIZE

DESCRIPTION

TYPE

ROLLNO

NUMBER

10

Roll no. of student , Foreign key

       

LECTURES_ATTENDED

NUMBER

3

No. of Lectures attended

       

LECTURES_NOT_ATTENDED

NUMBER

3

No. of Lectures not attended

       
       

DESCRIPTION

VARCHAR2

30

Response according to the attendance,

Not null

       

Table 2.2. Attendance table

26

Institute Attendance Management System

  • 3. MARKS TABLE

       

FIELD NAME

FIELD

FIELD SIZE

DESCRIPTION

TYPE

ROLLNO

NUMBER

10

Roll no. of student , Foreign key

       

LECTURES_PER

NUMBER

3

Lectures percentage

       
       

MARKS

NUMBER

1

Marks allotted

       
       

TOTALMARKS

NUMBER

1

Total marks

allotted,

Not null

       

ACTION

VARCHAR2

30

Action taken as per attendance

       

Table 2.3. Marks Table

27

Institute Attendance Management System

2.1 DATA DICTIONARY

A data dictionary is metadata repository or a centralized repository of information

about data such as meaning, relationships to other data, origin, usage and format. The

term may have one of several closely related meaning pertaining to databases and

database management systems (DBMS):

A document describing a database or collection of databases.

An integral component of DBMS that is required to determine its structure.

A piece of middleware that extends or supplants the native data dictionary of a

DBMS.

  • 1. STUDENT:

Institute Attendance Management System 2.1 DATA DICTIONARY A data dictionary is metadata repository or a centralized
  • 2. ATTENDANCE;

Fig2.6 Student table

Institute Attendance Management System 2.1 DATA DICTIONARY A data dictionary is metadata repository or a centralized

Fig2.7 Attendance table

28

Institute Attendance Management System

3.

MARKS

Institute Attendance Management System 3. MARKS Fig 2.8 Marks table 29

Fig 2.8 Marks table

29

Institute Attendance Management System

3. INTERFACE DESIGN

The interface design consists of the input and output source layouts. i.e. the input

forms and screens and the report layouts that form as a source of outcome and income

in the design and implementation of the information system under study

3.1 INPUT DESIGN

The input specifications of the existing information system include the illustration of

the detailed characteristics of contents included in each Input Screen and documents.

The description for each graphical user interface has been mentioned.

EXISTING SYSTEM DESIGN (Graphical User Interface)

1. LOGIN

Institute Attendance Management System 3. INTERFACE DESIGN The interface design consists of the input and output

Fig.2.9 login form

Description

The system maintains the name and Passwords of all the authenticated users who

are to operate the system.

30

Institute Attendance Management System

  • 2. ADD STUDENT RECORD.

Institute Attendance Management System 2. ADD STUDENT RECORD. Fig.2.10 Add student record form Description This system

Fig.2.10 Add student record form

Description

This system will maintain student details from where we can easily add new

details of the student.

  • 3. STUDENT DELETE/UPDATE

Institute Attendance Management System 2. ADD STUDENT RECORD. Fig.2.10 Add student record form Description This system

Fig.2.11 update/delete student form

31

Institute Attendance Management System

Description

This system will maintain student details from where we can easily delete and

update details of the student.

  • 4. VIEW / SEARCH STUDENT DETAILS

Institute Attendance Management System Description This system will maintain student details from where we can easily

Fig.2.12 view/search student details

Description

This system will maintain student details from where we can easily view and

search details of the student.

32

Institute Attendance Management System

  • 5. ADD ATTENDANCE DETAILS

Institute Attendance Management System 5. ADD ATTENDANCE DETAILS Fig.2.13 ADD ATTENDANCE DETAILS Description This system will

Fig.2.13 ADD ATTENDANCE DETAILS

Description

This system will maintain attendance details of the student from where we can

easily add attendance of the student.

33

Institute Attendance Management System

  • 6. VIEW ATTENDANCE DETAIL

Institute Attendance Management System 6. VIEW ATTENDANCE DETAIL Fig.2.14 VIEW ATTENDANCE DETAILS FORM Description This system

Fig.2.14 VIEW ATTENDANCE DETAILS FORM Description

This system will maintain attendance details from where we can easily view and

search attendance details of the student.

  • 7. ADD MARKS DETAILS

Institute Attendance Management System 6. VIEW ATTENDANCE DETAIL Fig.2.14 VIEW ATTENDANCE DETAILS FORM Description This system

Fig.2.15 ADD MARKS DETAILS

34

Institute Attendance Management System

Description

This system will maintain attendance marks details of the student from where we

can easily add attendance marks of the student.

  • 8. View Marks Details

Institute Attendance Management System Description This system will maintain attendance marks details of the student from

Fig.2.16 VIEW MARKS DETAILS FORM

Description

This system will maintain attendance marks details from where we can easily view attendance marks details of the student.

35

Institute Attendance Management System

3.2 Output Design

The output specifications of the existing information system include the detailed

characteristics of contents included in each Report. The description for each Visual

Basic Output Report has been mentioned.

1. REPORT 1

MARKS REPORT AND ATTENDANCE REPORT

Institute Attendance Management System 3.2 Output Design The output specifications of the existing information system include

36

Institute Attendance Management System

Brief description about System development and implementation

PURPOSE

The main purpose of the formulation of this document is to carry out the activities of writing

actual program, their debugging, testing and validations.

3.1

Institute Attendance Management System Brief description about System development and implementation PURPOSE The main purpose of

PROGRAMME DEVELOPMENT

Code to login

Private Sub Command1_Click()

Fig 3.1 LOGIN FORM

If text1.Text = "admin" And text2.Text = "admin" Then

37

Institute Attendance Management System

MsgBox "login successful!!!"

Unload Me

MDIForm1.Show

ElseIf text1.Text = "" Or text2.Text = "" Then

MsgBox "fields Cannot be left blank!!!"

text1.Text = ""

text2.Text = ""

text1.SetFocus

Else

MsgBox "invalid ID and Password"

text1.Text = ""

text2.Text = ""

text1.SetFocus

End If

End Sub

38

Institute Attendance Management System

Institute Attendance Management System Fig 3.2 ADD STUDENT FORM 39

Fig 3.2 ADD STUDENT FORM

39

Institute Attendance Management System

Code to add student

Dim rs As New ADODB.Recordset

Private Sub cmdAddSave_Click()

Set rs = New ADODB.Recordset

rs.Open "select * from student where rollno='" & Val(text1.Text) & "'", cn, adOpenKeyset,

adLockOptimistic

If rs.RecordCount > 0 Then

MsgBox "This Record is already added!!"

Else

insertdata

End If

End Sub

Private Sub insertdata()

Dim s As String

s = "insert into student values('" & text2.Text & "','" & Combo2.Text & "','" & Combo1.Text & "','"

& text1.Text & "')"

cn.Execute s

MsgBox "Data Saved Successfully!!!"

40

Institute Attendance Management System

Unload Me

End Sub

Private Sub cmdCancel_Click()

Unload Me

End Sub

Private Sub cmdReset_Click()

text1.Text = ""

text2.Text = ""

text4.Text = ""

End Sub

Private Sub Form_Load()

con

End Sub

Private Sub Form_Unload(Cancel As Integer)

cn.Close

End Sub

41

Institute Attendance Management System

Institute Attendance Management System Fig 3.3 UPDATE /DELETE THE STUDENTFORM Code to update/delete Option Explicit Dim

Fig 3.3 UPDATE /DELETE THE STUDENTFORM

Code to update/delete

Option Explicit

Dim rs As ADODB.Recordset

Private Sub cmdCancel_Click()

Unload Me

End Sub

42

Institute Attendance Management System

Private Sub Command1_Click()

text2.Text = ""

If text1.Text = "" Then

MsgBox "Please enter the roll number!!!"

Else

Set rs = New ADODB.Recordset

rs.Open "select * from student where rollno='" & text1.Text & "'", cn, adOpenKeyset,

adLockOptimistic

If rs.RecordCount > 0 Then

text2.Text = rs.Fields("stname")

Combo2.Text = rs.Fields("semester")

Combo1.Text = rs.Fields("course")

Else

MsgBox "record not found"

End If

End If

End Sub

Private Sub Form_Load()

43

Institute Attendance Management System

con

End Sub

Private Sub Form_Unload(Cancel As Integer)

cn.Close

End Sub

Private Sub cmdAddSave_Click()

Dim str As String

Set rs = New ADODB.Recordset

rs.Open "select * from student", cn, adOpenForwardOnly, adLockOptimistic

If text1.Text = "" Then

MsgBox "Field should not be left blank "

Else

rs.MoveFirst

Do While Not rs.EOF

If rs!ROLLNO = text1.Text Then

rs!STNAME = text2.Text

rs!SEMESTER = Combo2.Text

rs!COURSE = Combo1.Text

44

Institute Attendance Management System

rs.Update

MsgBox "Data successfully Updated!!"

End If

rs.MoveNext

Loop

Unload Me

End If

End Sub

Private Sub cmdReset_Click()

Dim str As String

Set rs = New ADODB.Recordset

rs.Open "select * from STUDENT", cn, adOpenForwardOnly, adLockOptimistic

If text1.Text = "" Then

MsgBox "Field should not be left blank "

Else

rs.MoveFirst

Do While Not rs.EOF

If rs!ROLLNO = text1.Text Then

45

Institute Attendance Management System

rs!STNAME = text2.Text

rs!SEMESTER = text3.Text

rs!COURSE = Combo1.Text

rs.Delete

MsgBox "Data successfully Deleted!!"

End If

rs.MoveNext

Loop

Unload Me

End If

End Sub

46

Institute Attendance Management System

Institute Attendance Management System Code to search Fig 3.4 SEARCH THE STUDENT Private Sub cmdCancel_Click() Unload

Code to search

Fig 3.4 SEARCH THE STUDENT

Private Sub cmdCancel_Click()

Unload Me

End Sub

Private Sub Command1_Click()

text2.Text = ""

text3.Text = ""

text4.Text = ""

47

Institute Attendance Management System

If text1.Text = "" Then

MsgBox "Please enter the roll number!!!"

Else

Set rs = New ADODB.Recordset

rs.Open "select * from student where rollno='" & text1.Text & "'", cn, adOpenKeyset,

adLockOptimistic

If rs.RecordCount > 0 Then

text2.Text = rs.Fields("stname")

text3.Text = rs.Fields("semester")

text4.Text = rs.Fields("course")

Else

MsgBox "record not found"

End If

End If

End Sub

Private Sub Form_Load()

con

End Sub

48

Institute Attendance Management System

Private Sub Form_Unload(Cancel As Integer)

cn.Close

End Sub

Institute Attendance Management System Private Sub Form_Unload(Cancel As Integer) cn.Close End Sub Code to add attendance

Code to add attendance

Private Sub insertdata()

Dim s As String

Fig.3.5 ADD ATTENDANCE FORM

s = "insert into attendance values('" & Val(text1.Text) & "','" & Val(text2.Text) & "','" &

Val(text3.Text) & "','" & text4.Text & "')"

49

Institute Attendance Management System

cn.Execute s

MsgBox "Data Saved Successfully!!!"

Unload Me

End Sub

Private Sub cmdAddSave_Click()

Set rs = New ADODB.Recordset

rs.Open "select * from marksheet where rollno='" & Val(text1.Text) & "'", cn, adOpenKeyset,

adLockOptimistic

If rs.RecordCount > 0 Then

MsgBox "This Record is already added!!"

Else

insertdata

End If

End Sub

Private Sub cmdCancel_Click()

Unload Me

End Sub

Private Sub cmdReset_Click()

50

Institute Attendance Management System

text2.Text = ""

text3.Text = ""

text4.Text = ""

End Sub

Private Sub Command1_Click()

text2.Text = ""

text3.Text = ""

text4.Text = ""

Frame1.Enabled = False

If text1.Text = "" Then

MsgBox "Please enter the roll number!!!"

Else

Set rs = New ADODB.Recordset

rs.Open "select * from student where rollno='" & text1.Text & "'", cn, adOpenKeyset,

adLockOptimistic

If rs.RecordCount > 0 Then

MsgBox "Record Found!!"

Frame1.Enabled = True

51

Institute Attendance Management System

Else

MsgBox "record not found"

End If

End If

End Sub

Private Sub Form_Load()

con

End Sub

Private Sub Form_Unload(Cancel As Integer)

cn.Close

End Sub

52

Institute Attendance Management System

Institute Attendance Management System Code to view attendance Fig.3.6 VIEW ATTENDANCE Private Sub cmdCancel_Click() Unload Me

Code to view attendance

Fig.3.6 VIEW ATTENDANCE

Private Sub cmdCancel_Click()

Unload Me

End Sub

Private Sub Command1_Click()

text2.Text = ""

text3.Text = ""

text4.Text = ""

53

Institute Attendance Management System

If text1.Text = "" Then

MsgBox "Please enter the roll number!!!"

Else

Set rs = New ADODB.Recordset

rs.Open "select * from attendance where rollno='" & Val(text1.Text) & "'", cn, adOpenKeyset,

adLockOptimistic

If rs.RecordCount > 0 Then

'

MsgBox "record found"

text2.Text = rs.Fields("LECTURES_ATTENDED")

text3.Text = rs.Fields("lectures_not_attended")

text4.Text = rs.Fields("description")

Else

MsgBox "record not found"

End If

End If

End Sub

Private Sub Form_Load()

con

54

Institute Attendance Management System

End Sub

Private Sub Form_Unload(Cancel As Integer)

cn.Close

End Sub

Institute Attendance Management System End Sub Private Sub Form_Unload(Cancel As Integer) cn.Close End Sub Code to

Code to allocate marks

Fig.3.7 ALLOCATE MARKS FORM

roll num

Dim rs As New ADODB.Recordset

Private Sub cmdAddSave_Click()

Set rs = New ADODB.Recordset

55

Institute Attendance Management System

rs.Open "select * from marksheet where rollno='" & Val(text1.Text) & "'", cn, adOpenKeyset,

adLockOptimistic

If rs.RecordCount > 0 Then

MsgBox "This Record is already added!!"

Else

insertdata

End If

End Sub

Private Sub insertdata()

Dim s As String

s = "insert into MARKSHEET values('" & Val(text1.Text) & "','" & Val(text2.Text) & "','" &

Val(text3.Text) & "','" & Val(text4.Text) & "','" & Text5.Text & "')"

cn.Execute s

MsgBox "Data Saved Successfully!!!"

Unload Me

End Sub

Private Sub cmdCancel_Click()

Unload Me

56

Institute Attendance Management System

End Sub

Private Sub cmdReset_Click()

text2.Text = ""

text3.Text = ""

text4.Text = ""

End Sub

Private Sub Command1_Click()

text2.Text = ""

text3.Text = ""

text4.Text = ""

Dim i As Integer

Dim j As Integer

Dim per As Integer

Dim marks As Integer

If text1.Text = "" Then

MsgBox "Please enter the roll number!!!"

Else

Set rs = New ADODB.Recordset

57

Institute Attendance Management System

rs.Open "select * from ATTENDANCE where ROLLNO='" & Val(text1.Text) & "'", cn,

adOpenKeyset, adLockOptimistic

If rs.RecordCount > 0 Then

'

MsgBox "record found"

i = Val(rs.Fields("LECTURES_ATTENDED"))

j = Val(rs.Fields("LECTURES_not_ATTENDED"))

per = (i / (i + j)) * 100

text2.Text = per

If per > 90 Then

marks = 5

ElseIf per > 75 And per <= 90 Then

marks = 4

ElseIf per > 60 And per <= 75 Then

marks = 3

ElseIf per > 40 And per <= 60 Then

marks = 2

Else

marks = 1

58

Institute Attendance Management System

End If

text3.Text = marks

text4.Text = "5"

Else

MsgBox "record not found"

End If

End If

End Sub

Private Sub Form_Load()

con

End Sub

Private Sub Form_Unload(Cancel As Integer)

cn.Close

End Sub

Save marks

Dim rs As New ADODB.Recordset

Private Sub cmdAddSave_Click()

Set rs = New ADODB.Recordset

59

Institute Attendance Management System

rs.Open "select * from marksheet where rollno='" & Val(text1.Text) & "'", cn, adOpenKeyset,

adLockOptimistic

If rs.RecordCount > 0 Then

MsgBox "This Record is already added!!"

Else

insertdata

End If

End Sub

Private Sub insertdata()

Dim s As String

s = "insert into MARKSHEET values('" & Val(text1.Text) & "','" & Val(text2.Text) & "','" &

Val(text3.Text) & "','" & Val(text4.Text) & "','" & Text5.Text & "')"

cn.Execute s

MsgBox "Data Saved Successfully!!!"

Unload Me

End Sub

Private Sub cmdCancel_Click()

Unload Me

60

Institute Attendance Management System

End Sub

Private Sub cmdReset_Click()

text2.Text = ""

text3.Text = ""

text4.Text = ""

End Sub

Private Sub Command1_Click()

text2.Text = ""

text3.Text = ""

text4.Text = ""

Dim i As Integer

Dim j As Integer

Dim per As Integer

Dim marks As Integer

If text1.Text = "" Then

MsgBox "Please enter the roll number!!!"

Else

Set rs = New ADODB.Recordset

61

Institute Attendance Management System

rs.Open "select * from ATTENDANCE where ROLLNO='" & Val(text1.Text) & "'", cn,

adOpenKeyset, adLockOptimistic

If rs.RecordCount > 0 Then

'

MsgBox "record found"

i = Val(rs.Fields("LECTURES_ATTENDED"))

j = Val(rs.Fields("LECTURES_not_ATTENDED"))

per = (i / (i + j)) * 100

text2.Text = per

If per > 90 Then

marks = 5

ElseIf per > 75 And per <= 90 Then

marks = 4

ElseIf per > 60 And per <= 75 Then

marks = 3

ElseIf per > 40 And per <= 60 Then

marks = 2

Else

marks = 1

62

Institute Attendance Management System

End If

text3.Text = marks

text4.Text = "5"

Else

MsgBox "record not found"

End If

End If

End Sub

Private Sub Form_Load()

con

End Sub

Private Sub Form_Unload(Cancel As Integer)

cn.Close

End Sub

63

Institute Attendance Management System

Institute Attendance Management System Code to view marks Private Sub cmdCancel_Click() Unload Me End Sub Private

Code to view marks

Private Sub cmdCancel_Click()

Unload Me

End Sub

Private Sub Command1_Click()

text2.Text = ""

Fig.3.8 VIEW MARKS

64

Institute Attendance Management System

text3.Text = ""

text4.Text = ""

Text5.Text = ""

If text1.Text = "" Then

MsgBox "Please enter the roll number!!!"

Else

Set rs = New ADODB.Recordset

rs.Open "select * from marksheet where rollno='" & Val(text1.Text) & "'", cn, adOpenKeyset,

adLockOptimistic

If rs.RecordCount > 0 Then

text2.Text = rs.Fields("lecture_per")

text3.Text = rs.Fields("marks")

text4.Text = rs.Fields("totalmarks")

Text5.Text = rs.Fields("action")

Else

MsgBox "record not found"

End If

End If

65

Institute Attendance Management System

End Sub

Private Sub Form_Load()

con

End Sub

Private Sub Form_Unload(Cancel As Integer)

cn.Close

End Sub

3.2 FLOW OF EXECUTION

3.2.1 LOG IN

Institute Attendance Management System End Sub Private Sub Form_Load() con End Sub Private Sub Form_Unload(Cancel As

66

Institute Attendance Management System

DESCRIPTION

Fig.3.9 LOGIN

First of all we have the login process. Once the person logs in he/she has access to the system.

Initially we have the operator who is loging in to the system but we have the facility to add more

users as per the requirement.

3.2.2 ADD STUDENT

67

Institute Attendance Management System

Institute Attendance Management System Fig.3.10 ADD STUDENT DESCRIPTION Now we have the option to add more

Fig.3.10 ADD STUDENT

DESCRIPTION

Now we have the option to add more students whose details can be add in the system. The

above form shows how a new student is being added into the system. Now the details can be

saved in the system.

68

Institute Attendance Management System

3.2.3 Update / delete student

Institute Attendance Management System 3.2.3 Update / delete student Fig.3.11 UPDATE AND DELETE STUDENT FORM DESCRIPTION

Fig.3.11 UPDATE AND DELETE STUDENT FORM

DESCRIPTION

69

Institute Attendance Management System

Now we have the option to update/ delete the student’s details in the system. The above form

shows how a student is being updated/ deleted into the system. Now the details can be saved in

the system

3.2.4 SEARCH. Fig.3.12 SEARCH STUDENT FORM DESCRIPTION
3.2.4 SEARCH.
Fig.3.12 SEARCH STUDENT FORM
DESCRIPTION

70

Institute Attendance Management System

Now we have the option to search the student’s details in the system. The above form shows

how a student is being search into the system. Now the details can be saved in the system.

3.2.5 Add attendance

71

Institute Attendance Management System

Institute Attendance Management System Fig.3.13 ADD ATTENDANCE DETAILS FORM DESCRIPTION Now we have the option to

Fig.3.13 ADD ATTENDANCE DETAILS FORM

DESCRIPTION

Now we have the option to add the attendance of the student in the system. The above form

shows how a student’s attendance is being added into the system. Now the details can be saved

in the system.

72

Institute Attendance Management System

3.2.6 View attendance

Institute Attendance Management System 3.2.6 View attendance Fig.3.14 VIEW ATTENDANCE DETAILS FORM DESCRIPTION Now we have

Fig.3.14 VIEW ATTENDANCE DETAILS FORM

DESCRIPTION

Now we have the option to view the attendance of the student in the system. The above form

shows how a student’s attendance is being viewed in the system. Now the details can be saved

in the system.

73

Institute Attendance Management System

3.2.7 Allocate marks

Institute Attendance Management System 3.2.7 Allocate marks Fig.3.15 ALLOCATE MARKS FORM DESCRIPTION Now we have the

Fig.3.15 ALLOCATE MARKS FORM

DESCRIPTION

Now we have the option to allocate the marks of the student in the system. The above form

shows how a student’s attendance marks are allotted in the system. Now the details can be

saved in the system.

74

Institute Attendance Management System

3.2.8 View Marks details

Institute Attendance Management System 3.2.8 View Marks details 75

75

Institute Attendance Management System

Fig.3.16 VIEW MARKS DETAILS FORM

DESCRIPTION

Now we have the option to view the marks of the student in the system. The above form shows

how a student’s attendance marks are viewed in the system. Now the details can be saved in

the system.

3.3 Backend Description

Institute Attendance Management System Fig.3.16 VIEW MARKS DETAILS FORM DESCRIPTION Now we have the option to

Fig.3.17 STUDENT DATABASE

76

Institute Attendance Management System

STNAME

This table is for adding the student name.

SEMESTER

This table is for adding the student semester.

COURSE

This table is for adding the student’s course.

ROLLNO

This table is for adding the student’s roll no.

Attend

ance

Institute Attendance Management System STNAME This table is for adding the student name. SEMESTER This table

77

Institute Attendance Management System

ROLLNO

Fig: 3.18 ATTENDANCE DATABASE

This table is for adding the student’s roll no.

LECTURE_ATTENDED

This table is for lecture attended.

LECTURE_NOT_ATTENDED

This table is for lecture not attended.

DESCRIPTION

This table is for description.

78

Institute Attendance Management System

Institute Attendance Management System ROLLNO FIG:- 3.19 MARKS DATABASE This table is for adding the student’s

ROLLNO

FIG:- 3.19 MARKS DATABASE

This table is for adding the student’s roll no.

LECTURE_PER

This table is for lecture of percentage.

MARKS

This table is for adding the marks of the student.

TOTAL MARKS

This table is for total marks of the attendance.

ACTION

This table is for taking the action against the defaulter.

79

Institute Attendance Management System

3.4 TESTING AND DEBUGGING

This section deals with checking the various modules through test cases and debug errors. Each

test case is specified with an output and the permissible set of values in that particular process.

TESTING FOR LOGIN ACCOUNT

Institute Attendance Management System 3.4 TESTING AND DEBUGGING This section deals with checking the various modules

FIG:_ 3.20 LOGIN FORM

TESTING FOR ATTENDANCE

80

Institute Attendance Management System

Institute Attendance Management System FIG:_ 3.21 ATTENDANCE FORM TESTING FOR MARKS ALLOCATION FIG:_ 3.22 MARKS ALLOCATION

FIG:_ 3.21 ATTENDANCE FORM

TESTING FOR MARKS ALLOCATION

Institute Attendance Management System FIG:_ 3.21 ATTENDANCE FORM TESTING FOR MARKS ALLOCATION FIG:_ 3.22 MARKS ALLOCATION

FIG:_ 3.22 MARKS ALLOCATION FORM

81

Institute Attendance Management System

  • 4.1 OBJECTIVES OF THE PROJECT:

The basic objective of the project was to transform the manual system into a computerized

system which required all the manual work of the data entry operator to be changed. The

working has been made easier with all the work now on the computer, and also earlier the

storage of the records in the manual way was a hard task but now all the records are stored on

the hard disk hence, there is safety as well as secure storage of data.

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

  • 4.2 SCOPE OF IMPROVEMENT:

The improvement in a project can always be done by upgrading the present scope to a larger

one; like in the case of our project if the Institute enrolls more of the Students then the project

is capable enough to adapt to the change. And even, if the project is taken up for a university

then the system will support that even.

So, the scope of improvement is very vast as more and more modules can be added to provide

assistance to the users. Hence, improving on the project means just to upgrade the present

system.

82

Institute Attendance Management System

4.3 SUMMARY:

The aim of the project has been a system which solves the problem of attendance. So in our

project we have included various facilities to send the attendance system of the institute. First

of all in our system. The teacher can enquire about the attendance of the student. The operator

will look on the attendance of the student. In this, teacher will take the attendance of the

student and maintai9n the records. The teacher will allocate the marks of attendance of the

student according to attendance status and maintain the records. If the attendance of the

student is short than the teacher or director will take the action the defaulter whose attendance

is short. In this attendance report will be generated and marks report will be generated by the

teacher. We have the facilities also for our teachers. There are many more facilities available

with our system; this is just of what all facilities available in our system.

APPENDICES:

Appendix A (glossary)

Appendix- B (References)

Appendix-C (Survey)

83