STUDENTS ATTENDANCE MAINTANANCE SYSTEM

ABSTRACT

Student Attendance maintenance system deals with the maintenance of the

student’s attendance details. It is generates the attendance of the student on basis of
presence in class. It is maintained on the daily basis of their attendance. The staffs will be
provided with the separate username & password to make the student’s status. The Student
Attendance Maintenance System (SAMS) deals with all kinds of student details, course details,
batch details ,attendance details other resources. It tracks all the details of a student from the day
one to the end of his course which can be used for all reporting purpose, tracking enrolment,
progress in the course, completed semesters years, and all these will be available for future
references too.The staffs handling the particular subjects responsible to make the
attendance for all students. Only if the student present on that particular period, the
attendance will be calculated. The students attendance reports based on weekly and
consolidate will be generated.
 CHAPTER-1

INTRODUCTION

With the advent of new technology, the world is now witnessing an easy way to keep
information / data. Hence the introduction of computer is one of the greatest challenges facing
man today. 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 lecturer for a particular class. This system will also help in evaluating attendance
eligibility criteria of a student. Since ages, attendance system has remained one of the most
important systems for evaluating the working time of students in any college or school. In short,
this project is used to mark the number of days present/absent in any academic year of students
in a college, school etc. The software system also helps in evaluating the examination eligibility
criteria for a student in the sense that only those students with attendance above And this system
will also help in evaluating attendance eligibility criteria of a student. In schools, attendance is
important and mandatory. Nowadays, due to the large number of students, it is efficient to use
attendance management system to manage attendance in schools.

AIMS AND OBJECTIVES

This report describes the capabilities that will be provided by the Software application
“Student Attendance Management System”. The purpose of developing this attendance
management system is to computerize the traditional way of taking attendance in classes and also
manage student information along with their classes and subjects. Another purpose for
developing the software is to generate the reports automatically whenever required,-in between
the semester or after the semester.
PROBLEM DEFINITION:

This system developed will reduce the manual work and avoid redundant data. By maintaining
the attendance manually, then efficient reports can not be generated. The system can generate
efficient weekly, consolidate report based on the attendance. As the attendances are maintained
in registers it has been a tough task for admin and staff to maintain for long time. Instead the
software can keep long and retrieve the information when needed.

PURPOSE

The project is about to handle all the information of the student regarding attendance . Also it
manages resources which were managed and handled by manpower previously. The main
purpose of the project is to integrate distinct sections of the organization into consistent manner
so that complex functions can be handled smoothly by any technical or non-technical persons.

The project aims at the following matters:

 Assistance in decision-making.
 To manage information of student, faculty and courses.
 Consistently update information of all the students.
 Reports- To gather all the related information .

All the above-mentioned matters are to be incorporated in the application along with some
additional requirements.
 SYSTEM ANALYSIS

EXISTING SYSTEM:

The Existing system is a manual entry for the students. Here the attendance will be
carried out in the hand written registers . It will be a tedious job to maintain the record for the
user. The human effort is more here . The retrieval of the information is not as easy as the
records are maintained in the hand written registers.

This application requires correct feed on input into the respective field. Suppose the
wrong input are entered, the application resist to work. So the user find it difficult to use.

PROPOSED SYSTEM:

To overcome the drawbacks of the existing system, the proposed system has been
evolved. This project aims to reduce the paper work and saving time to generate accurate results
from the student’s attendance. The system provides with the best user interface. The efficient
reports can be generated by using this proposed system.

Advantages of Proposed System:

 It is trouble-free to use
 It is a relatively fast approach to enter attendance
 Is highly reliable, approximate result from user
 Best user Interface
 Efficient reports
PROJECT OVERVIEW

Attendance Management System basically has two main modules for proper functioning .

 Admin module is has rights for creating any new entry of faculty and student details.

 User has a rights of making daily attendance, generating report. Attendance report can be
taken by given details of student details, date, class.

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.

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.
FEATURES:
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.
 SOFTWARE SPECIFICATION

Software Requirements

 Language : C#.NET
 Technologies : ASP.NET, ADO.NET
 IDE : Visual Studio 2012
 Backend : SQL Server 2008
 Operating System : Microsoft Windows XP
 SYSTEM STUDY

PRELIMINARY INVESTIGATION

The first and foremost strategy for development of a project starts from the thought of
designing a mail enabled platform for a small firm in which it is easy and convenient of sending
and receiving messages, there is a search engine ,address book and also including some
entertaining games. When it is approved by the organization and our project guide the first
activity, ie. preliminary investigation begins. The activity has three parts:

 Request Clarification

 Feasibility Study

 Request Approval

REQUEST CLARIFICATION

After the approval of the request to the organization and project guide, with an
investigation being considered, the project request must be examined to determine precisely what
the system requires.

Here our project is basically meant for users within the company whose systems
can be interconnected by the Local Area Network(LAN). In today’s busy schedule man need
everything should be provided in a readymade manner. So taking into consideration of the vastly
use of the net in day to day life, the corresponding development of the portal came into
existence.
FEASIBILITY ANALYSIS

An important outcome of preliminary investigation is the determination that the system

request is feasible. This is possible only if it is feasible within limited resource and time. The
different feasibilities that have to be analyzed are

 Operational Feasibility
 Economic Feasibility
 Technical Feasibility

Operational Feasibility
Operational Feasibility deals with the study of prospects of the system to be developed.
This system operationally eliminates all the tensions of the Admin and helps him in effectively
tracking the project progress. This kind of automation will surely reduce the time and energy,
which previously consumed in manual work. Based on the study, the system is proved to be
operationally feasible.

Economic Feasibility

Economic Feasibility or Cost-benefit is an assessment of the economic justification for a

computer based project. As hardware was installed from the beginning & for lots of purposes
thus the cost on project of hardware is low. Since the system is a network based, any number of
employees connected to the LAN within that organization can use this tool from at anytime. The
Virtual Private Network is to be developed using the existing resources of the organization. So
the project is economically feasible.
Technical Feasibility
According to Roger S. Pressman, Technical Feasibility is the assessment of the technical
resources of the organization. The organization needs IBM compatible machines with a graphical
web browser connected to the Internet and Intranet. The system is developed for platform
Independent environment. Java Server Pages, JavaScript, HTML, SQL server and WebLogic
Server are used to develop the system. The technical feasibility has been carried out. The system
is technically feasible for development and can be developed with the existing facility.

REQUEST APPROVAL

Not all request projects are desirable or feasible. Some organization receives so many
project requests from client users that only few of them are pursued. However, those projects that
are both feasible and desirable should be put into schedule. After a project request is approved, it
cost, priority, completion time and personnel requirement is estimated and used to determine
where to add it to any project list. Truly speaking, the approval of those above factors,
development works can be launched.
SYSTEM DESIGN AND DEVELOPMENT

INPUT DESIGN

Input Design plays a vital role in the life cycle of software development, it requires very
careful attention of developers. The input design is to feed data to the application as accurate as
possible. So inputs are supposed to be designed effectively so that the errors occurring while
feeding are minimized. According to Software Engineering Concepts, the input forms or screens
are designed to provide to have a validation control over the input limit, range and other related
validations.

This system has input screens in almost all the modules. Error messages are developed to
alert the user whenever he commits some mistakes and guides him in the right way so that
invalid entries are not made. Let us see deeply about this under module design.

Input design is the process of converting the user created input into a computer-based
format. The goal of the input design is to make the data entry logical and free from errors. The
error is in the input are controlled by the input design. The application has been developed in
user-friendly manner. The forms have been designed in such a way during the processing the
cursor is placed in the position where must be entered. The user is also provided with in an
option to select an appropriate input from various alternatives related to the field in certain cases.

Validations are required for each data entered. Whenever a user enters an erroneous data,
error message is displayed and the user can move on to the subsequent pages after completing all
the entries in the current page.
OUTPUT DESIGN

The Output from the computer is required to mainly create an efficient method of
communication within the company primarily among the project leader and his team members,
in other words, the administrator and the clients. The output of VPN is the system which allows
the project leader to manage his clients in terms of creating new clients and assigning new
projects to them, maintaining a record of the project validity and providing folder level access to
each client on the user side depending on the projects allotted to him. After completion of a
project, a new project may be assigned to the client. User authentication procedures are
maintained at the initial stages itself. A new user may be created by the administrator himself or
a user can himself register as a new user but the task of assigning projects and validating a new
user rests with the administrator only.

The application starts running when it is executed for the first time. The server has to be started
and then the internet explorer in used as the browser. The project will run on the local area
network so the server machine will serve as the administrator while the other connected systems
can act as the clients. The developed system is highly user friendly and can be easily understood
by anyone using it even for the first time.
 SOFTWARE REQUIREMENT SPECIFICATION

LANGUAGE SPECIFICATION

DOTNET TECHNOLOGY

Microsoft .NET is a set of Microsoft software technologies for rapidly building and
integrating XML Web services, Microsoft Windows-based applications, and Web solutions. The
.NET Framework is a language-neutral platform for writing programs that can easily and
securely interoperate. There’s no language barrier with .NET: there are numerous languages
available to the developer including Managed C++, C#, Visual Basic and Java Script. The .NET
framework provides the foundation for components to interact seamlessly, whether locally or
remotely on different platforms. It standardizes common data types and communications
protocols so that components created in different languages can easily interoperate

THE .NET FRAMEWORK

The .NET Framework is a new computing platform that simplifies application development in
the highly distributed environment of the internet

The .NET Framework has two main parts:

1. The Common Language Runtime (CLR).

2. A hierarchical set of class libraries.

Common language runtime

The CLR is described as the “execution engine” of .NET. It provides the environment within
which programs run. The most important features are:

 Conversion from a low-level assembler-style language, called Intermediate Language

(IL), into code native to the platform being executed on.
 Memory management, notably including garbage collection.
 Checking and enforcing security restrictions on the running code.
Loading and executing programs, with version control and other such features

The following features of the .NET framework are also worth description:

Managed Code - is code that targets .NET, and which contains certain extra
information - “metadata” - to describe itself. Whilst both managed and unmanaged code can run
in the runtime, only managed code contains the information that allows the CLR to guarantee,
for instance, safe execution and interoperability.

Managed Data - With Managed Code comes Managed Data. CLR provides memory
allocation and Deal location facilities, and garbage collection. Some .NET languages use
Managed Data by default, such as C#, Visual Basic.NET and JScript.NET, whereas others,
namely C++, do not. Targeting CLR can, depending on the language you’re using, impose
certain constraints on the features available. As with managed and unmanaged code, one can
have both managed and unmanaged data in .NET applications - data that doesn’t get garbage
collected but instead is looked after by unmanaged code.

Common Type System - The CLR uses something called the Common Type System
(CTS) to strictly enforce type-safety. This ensures that all classes are compatible with each other,
by describing types in a common way. CTS define how types work within the runtime, which
enables types in one language to interoperate with types in another language, including cross-
language exception handling. As well as ensuring that types are only used in appropriate ways,
the runtime also ensures that code doesn’t attempt to access memory that hasn’t been allocated to
it.

Common Language Specification - The CLR provides built-in support for language
interoperability. To ensure that you can develop managed code that can be fully used by
developers using any programming language, a set of language features and rules for using them
called the Common Language Specification (CLS) has been defined. Components that follow
these rules and expose only CLS features are considered CLS-compliant.

Class library

.NET provides a single-rooted hierarchy of classes, containing over 7000 types.

The root of the namespace is called System; this contains basic types like Byte, Double, Boolean,
and String, as well as Object. All objects derive from System. Object. As well as objects, there
are value types. Value types can be allocated on the stack, which can provide useful flexibility.
There are also efficient means of converting value types to object types if and when necessary.

The set of classes is pretty comprehensive, providing collections, file, screen, and
network I/O, threading, and so on, as well as XML and database connectivity.

The class library is subdivided into a number of sets (or namespaces), each providing distinct
areas of functionality, with dependencies between the namespaces kept to a minimum

ASP.NET Windows Forms

XML WEB SERVICES

Base Class Libraries

Common Language Runtime

Operating System

Fig 3.2: .NET Framework

FEATURES OF ASP.NET

ASP.NET

ASP.NET is the .NET framework layer that handles Web requests for specific types of files,
namely those with (.aspx or .ascx) extensions. The ASP.NET engine provides a robust object
model for creating dynamic content and is loosely integrated into the .NET framework.

ASP.NET is part of the .NET framework. ASP.NET programs are centralized

applications hosted on one or more Web servers that respond dynamically to client requests. The
responses are dynamic because ASP.NET intercepts requests for pages with a specific extension
(.aspx or .ascx) and hands off the responsibility for answering those requests to just-in-time (JIT)
compiled code files that can build a response “on-the-fly.”
 ASP.NET deals specifically with configuration (web.config and machine.config)
files, Web Services (ASMX) files, and Web Forms (ASPX) files. The server doesn’t “serve” any
of these file types—it returns the appropriate content type to the client. The configuration file
types contain initialization and settings for a specific application or portion of an application.
Another configuration file, called machine.web, contains machine-level initialization and
settings. The server ignores requests for web files, because serving them might constitute a
security breach.

Client requests for these file types cause the server to load, parse, and execute
code to return a dynamic response. For Web Forms, the response usually consists of HTML or
WML. Web Forms maintain state by round-tripping user interface and other persistent values
between the client and the server automatically for each request.

A request for a Web Form can use View State, Session State, or Application State
to maintain values between requests. Both Web Forms and Web Services requests can take
advantage of ASP. Net’s integrated security and data access through ADO.NET, and can run
code that uses system services to construct the response. So the major difference between a static
request and a dynamic request is that a typical Web request references a static file. The server
reads the file and responds with the contents of the requested file.

ASP.NET uses .NET languages. ASP.NET code exists in multithreaded JIT

compiled DLL assemblies, which can be loaded on demand. Once loaded, the ASP.NET DLLs
can service multiple requests from a single in-memory copy.

ASP.NET supports all the .NET languages (currently C#, C++, VB.NET, and
JScript, but there are well over 20 different languages in development for .NET), so you will
eventually be able to write Web applications in your choice of almost any modern programming
language.

In addition to huge increases in speed and power, ASP.NET provides substantial

development improvements, like seamless server-to-client debugging, automatic validation of
form data.
 Fig 3.3 Interoperability

ASP.NET EVENTS are cool

Every time an ASP.NET page is viewed, many tasks are being performed behind
the scenes. Tasks are performed at key points ("events") of the page's execution lifecycle.

The most common events are

OnInit

The first event in our list to be raised is OnInit. When this event is raised, all of
the page's server controls are initialized with their property values. Post Back values are not
applied to the controls at this time.
On Load

The next event to be raised is On Load, which is the most important event of them
all as all the pages server controls will have their Post Back values now.

Post Back Events

Next all the Post Back events are raised. These events are only raised when the
page view is the result of a Post Back. The order that these events are raised can't be defined or
relied upon; the only consistency with the order that Post Back events are raised is that they are
all raised between the Unload and OnPreRender events.

OnPreRender

This event is raised just prior to the page or server control's html output being
written into the response stream that's sent to the client web browser. This is last chance you
have to make any modifications. By this point, all the server controls on the page have the final
data applied.

On Unload

This is the last event in our list to be raised and you should destroy any un-
managed objects and close any currently open database connection at this point. It is not possible
to modify any controls on the page at this point as the response stream has already been sent to
the client web browser.

As each event of the page is raised it also automatically tells all its child controls
to raise their own implementation of the same event.Then execution flow is passed back to the
main page class to continue onto the next event and the process is repeated for that event.
MAIN FEATURES OF ASP.NET

Successor of Active Server Pages (ASP), but completely different architecture

• Object-oriented

• Event-based

• Rich library of Web Controls

• Separation of layout (HTML) and logic (e.g. C#)

• Compiled languages instead of interpreted languages

• GUI can be composed interactively with Visual Studio .NET

• Better state management

NAMESPACES

ASP.NET uses a concept called namespaces. Namespaces are hierarchical object

models that support various properties and methods. For example, HTML server controls reside
in "System.web.UI.HtmlControls" namespace, web server controls reside in
“System.web.UI.WebControls" namespace and ADO+ resides in "System. Data" namespace.

LANGUAGE INDEPENDENT

An ASP.NET page can be created in any language supported by .NET framework.

Currently .NET framework supports VB, C#, JScript and Managed C++.

ASP.NET SERVER CONTROLS

Using ASP.NET Server Controls, browser variation is handled because these

controls output the HTML themselves based on the browser requesting the page.
TYPES OF CONTROLS

ASP.NET has two basic types of controls: HTML server controls and Web server
controls.HTML Server Controls are generated around specific HTML elements and the
ASP.NET engine changes the attributes of the elements based on server-side code that you
provide.The ASP.NET engine takes the extra steps to decide based upon the container of the
requester, what HTML to output.

Fig 3.3 Web Controls

DATA ACCESS WITH ADO.NET

ADO.NET provides a set of classes which a script can use to interact with
databases. Scripts can create instances of ADO.NET data classes and access their properties and
methods. A set of classes which work with a specific type of database is known as a .NET Data
Provider. ADO.NET comes with two Data Providers, the SQL Server.NET Data Provider
(which provides optimised access for Microsoft SQL Server databases) and the OLEDB.NET
Data Provider, which works with a range of databases. The main ADO.NET OLEDB data access
classes are OLEDBConnection,OLEDBCommand,OLEDBDataReader and OLEDBDataAdapter.

ADO.NET offers several advantages over previos versions of ADO

  Interoperablity
 Maintainablity
 Programmability
 Performance Scalability

VISUAL STUDIO .NET

Visual studio.NET is a complete set of development tools for building ASP web applications
XML web applications ,XML web services desktop applications and mobile applications in
addition to building high performing desktop applications ,you can use visual studio’s powerful
component-based development tools and other technologies to simplify term-based design,
development and deployment of enterprise solutions. Visual basic .NET, Visual C++.NET and
visual C#,NET all use the same integrated development environment (IDE) which allows them to
share tools and facilitates in the creation of mixed language solutions .

SQL SERVER 2008

FERTURES OF SQL SERVER 2008

The OLAP Services feature available in SQL Server version 7.0 is now called
SQL Server 2000 Analysis Services. The term OLAP Services has been replaced with the term
Analysis Services. Analysis Services also includes a new data mining component. The
Repository component available in SQL Server version 7.0 is now called Microsoft SQL Server
2000 Meta Data Services.

SQL-SERVER database consist of six type of objects,

They are,

1. TABLE

2. QUERY

3. FORM
 4. REPORT

5. MACRO

TABLE:

A database is a collection of data about a specific topic.

VIEWS OF TABLE:

We can work with a table in two types,

1. Design View

2. Datasheet View

Design View

To build or modify the structure of a table we work in the table design

view. We can specify what kind of data will be hold.

Datasheet View

To add, edit or analyses the data itself we work in tables datasheet view
mode.

QUERY:

A query is a question that has to be asked the data. Access gathers data that
answers the question from one or more table. The data that make up the answer is either dynaset
(if you edit it) or a snapshot(it cannot be edited).Each time we run query, we get latest
information in the dynaset.Access either displays the dynaset or snapshot for us to view or
perform an action on it ,such as deleting or updating.
FORMS:

A form is used to view and edit information in the database record by

record .A form displays only the information we want to see in the way we want to see it. Forms

use the familiar controls such as textboxes and checkboxes. This makes viewing
and entering data easy.

Views of Form:

We can work with forms in several primarily there are two views,

They are,

1. Design View

2. Form View

Design View

To build or modify the structure of a form, we work in forms design view. We

can add control to the form that are bound to fields in a table or query, includes textboxes, option
buttons, graphs and pictures.

Form View

The form view which display the whole design of the form.

REPORT:

A report is used to vies and print information from the database. The report can
ground records into many levels and compute totals and average by checking values from many
records at once. Also the report is attractive and distinctive because we have control over the size
and appearance of it.
SYSTEM DESIGN
DATA FLOW DIAGRAM
E-R-DIAGRAM
USE CASE DIAGRAM
ACTIVITY DIAGRAM
 DATABASE DESIGN

LOGIN TABLE:
To create a login details for the table

Log in Table

Staffs Table:
To create username and password for the staff details.

Staff Details Table

Student Table:

To create table for Student personal details for our department.

Student Details Table

Time table:

To create the subject time table for a particular class.

Attendance table:

To create attendance details for particular class .

Attendance table
 SYSTEM IMPLEMENTATION

MODULE DESCRIPTION :
The system should be designed in such a way that only authorized people should be allowed to
access some particular modules. The records should be modified by only administrators and no
one else. The user should always be in control of the application and not the vice versa. The user
interface should be consistent so that the user can handle the application with ease and speed.
The application should be visually, conceptually clear.

ADMINISTRATOR MODULE:

Student Details:
In this module deals with the allocation of roll no and personal details for new batch.It will
generate of personal details of student and academic details of the students with the photos.

Staff Details:
It helps to allot the subject and the subject code to the particular staffs.
It provides the facility to have a user name and password to the staffs .

Time table details:

It will retrieve the subject information from the subject database and assign time table to the
staffs.
It will help the admin, staff to make the entry of attendance based of the subject and period
allotted to the respective staff

Attendance details:
 It will be makes to the attendance database all students. Entered attendance to stored in the
database subject ,period wise into the particular date.
It will help s to the get report of weekly and consolidate of the attendance.

Report details:
Report can be taken by daily,weekly and consolidate: weekly report get all hour details of
attendance starting date to ending date and display the status
Consolidate report get all student attendance details starting date to ending date status help for
the eligibility criteria of the student to attend the examination.

STAFFS MODULE:

Attendance details:
It assists the staff to mark attendance to the students for their subject. This will authenticate the
staff before making the entry.

Report details:
1.weekly report get particular hour details of attendance from starting date to ending date and
display the status .
2.consolidate report get all student attendance details from starting date to ending date status help
for the eligibility criteria of the student to attend the examination
 SYSTEM TESTING

TESTING METHODOLOGIES

The following are the Testing Methodologies:

o Unit Testing.
o Integration Testing.
o User Acceptance Testing.
o Output Testing.
o Validation Testing.

Unit Testing

Unit testing focuses verification effort on the smallest unit of Software design that is the
module. Unit testing exercises specific paths in a module’s control structure to

ensure complete coverage and maximum error detection. This test focuses on each module
individually, ensuring that it functions properly as a unit. Hence, the naming is Unit Testing.

During this testing, each module is tested individually and the module interfaces are
verified for the consistency with design specification. All important processing path are tested
for the expected results. All error handling paths are also tested.

Integration Testing

Integration testing addresses the issues associated with the dual problems of verification
and program construction. After the software has been integrated a set of high order tests are
conducted. The main objective in this testing process is to take unit tested modules and builds a
program structure that has been dictated by design.

The following are the types of Integration Testing:

1. Top Down Integration

This method is an incremental approach to the construction of program structure.

Modules are integrated by moving downward through the control hierarchy, beginning with the
main program module. The module subordinates to the main program module are incorporated
into the structure in either a depth first or breadth first manner.
In this method, the software is tested from main module and individual stubs are replaced
when the test proceeds downwards.

2. Bottom-up Integration

This method begins the construction and testing with the modules at the lowest level in
the program structure. Since the modules are integrated from the bottom up, processing required
for modules subordinate to a given level is always available and the need for stubs is eliminated.
The bottom up integration strategy may be implemented with the following steps:

 The low-level modules are combined into clusters into clusters that
perform a specific Software sub-function.
 A driver (i.e.) the control program for testing is written to coordinate test case
input and output.
 The cluster is tested.
 Drivers are removed and clusters are combined moving upward in the
program structure
The bottom up approaches tests each module individually and then each module is module is
integrated with a main module and tested for functionality.

User Acceptance Testing

User Acceptance of a system is the key factor for the success of any system. The system
under consideration is tested for user acceptance by constantly keeping in touch with the
prospective system users at the time of developing and making changes wherever required. The
system developed provides a friendly user interface that can easily be understood even by a
person who is new to the system.

Output Testing

After performing the validation testing, the next step is output testing of the proposed
system, since no system could be useful if it does not produce the required output in the specified
format. Asking the users about the format required by them tests the outputs generated or
displayed by the system under consideration. Hence the output format is considered in 2 ways –
one is on screen and another in printed format.

Validation Checking

Validation checks are performed on the following fields.

Text Field:
 The text field can contain only the number of characters lesser than or equal to its size.
The text fields are alphanumeric in some tables and alphabetic in other tables. Incorrect entry
always flashes and error message.

Numeric Field:

The numeric field can contain only numbers from 0 to 9. An entry of any character
flashes an error messages. The individual modules are checked for accuracy and what it has to
perform. Each module is subjected to test run along with sample data. The individually tested
modules are integrated into a single system. Testing involves executing the real data
information is used in the program the existence of any program defect is inferred from the
output. The testing should be planned so that all the requirements are individually tested.
A successful test is one that gives out the defects for the inappropriate data and produces and
output revealing the errors in the system.
Preparation of Test Data

Taking various kinds of test data does the above testing. Preparation of test data plays a vital role
in the system testing. After preparing the test data the system under study is tested using that test
data. While testing the system by using test data errors are again uncovered and corrected by
using above testing steps and corrections are also noted for future use.

Using Live Test Data:

Live test data are those that are actually extracted from organization files. After a system is
partially constructed, programmers or analysts often ask users to key in a set of data from their
normal activities. Then, the systems person uses this data as a way to partially test the system. In
other instances, programmers or analysts extract a set of live data from the files and have them
entered themselves.
 It is difficult to obtain live data in sufficient amounts to conduct extensive testing. And,
although it is realistic data that will show how the system will perform for the typical processing
requirement, assuming that the live data entered are in fact typical, such data generally will not
test all combinations or formats that can enter the system. This bias toward typical values then
does not provide a true systems test and in fact ignores the cases most likely to cause system
failure.

Using Artificial Test Data:

Artificial test data are created solely for test purposes, since they can be generated to test all
combinations of formats and values. In other words, the artificial data, which can quickly be
prepared by a data generating utility program in the information systems department, make
possible the testing of all login and control paths through the program.

The most effective test programs use artificial test data generated by persons other than
those who wrote the programs. Often, an independent team of testers formulates a testing plan,
using the systems specifications.

The package “Virtual Private Network” has satisfied all the requirements specified as per
software requirement specification and was accepted.

MAINTAINENCE

This covers a wide range of activities including correcting code and design errors. To
reduce the need for maintenance in the long run, we have more accurately defined the user’s
requirements during the process of system development. Depending on the requirements, this
system has been developed to satisfy the needs to the largest possible extent. With development
in technology, it may be possible to add many more features based on the requirements in future.
The coding and designing is simple and easy to understand which will make maintenance easier.
TESTING STRATEGY :

A strategy for system testing integrates system test cases and design techniques into a
well planned series of steps that results in the successful construction of software. The testing
strategy must co-operate test planning, test case design, test execution, and the resultant data
collection and evaluation .A strategy for software testing must accommodate low-level tests
that are necessary to verify that a small source code segment has been correctly implemented
as well as high level tests that validate major system functions against user requirements.

Software testing is a critical element of software quality assurance and represents the
ultimate review of specification design and coding. Testing represents an interesting anomaly for
the software. Thus, a series of testing are performed for the proposed system before the
system is ready for user acceptance testing.

SYSTEM TESTING:

Software once validated must be combined with other system elements (e.g. Hardware,
people, database). System testing verifies that all the elements are proper and that overall system
function performance is

achieved. It also tests to find discrepancies between the system and its original objective, current
specifications and system documentation.
UNIT TESTING:

In unit testing different are modules are tested against the specifications produced during
the design for the modules. Unit testing is essential for verification of the code produced during
the coding phase, and hence the goals to test the internal logic of the modules. Using the
detailed design description as a guide, important Conrail paths are tested to uncover errors
within the boundary of the modules. This testing is carried out during the programming stage
itself. In this type of testing step, each module was found to be working satisfactorily as regards
to the expected output from the module.

In Due Course, latest technology advancements will be taken into consideration. As part
of technical build-up many components of the networking system will be generic in nature so
that future projects can either use or interact with this. The future holds a lot to offer to the
development and refinement of this project.
CONCLUSION:

The Attendance Management System is developed using ASP.NET with C# fully meets the
objectives of the system which it has been developed. The system has reached a steady state
where all bugs have been eliminated. The system is operated at a high level of efficiency and all
the teachers and user associated with the system understands its advantage. The system solves
the problem. It was intended to solve as requirement specification.

FUTURE WORK:

Furthermore, computerization of attendance system is not just a matter of technological

innovation and development; It is a process which involves individual, organization and society
in general. The computerization of the attendance system has brought about faster access and
easier method of viewing, editing, printing (documentation) of student attendance record.