1.

1 OBJECTIVE
The objective of the system is:

To reduce paperwork
Data accuracy
Transparency
Availability everywhere anytime

The software package can readily be used by non-programming personal avoiding

human handled chance of error. The project is used by two types of users.
i.
ii.
iii.

Faculties
Head of Department
Students

Students can login using their Enrolled number provided by University/College.

They can see their respective attendance and also their projected Session Markings
they can get.
Students also get notified by faculties if they are having short attendance and on
portal they can view how they can overcome those.
Application can be upgraded according to users and administrators requirements
with little chances.
New features can be added as per requirement.

1.2 INTRODUCTION
Online Attendance Management System is a software developed for daily
student attendance in schools, collages 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.

Online Attendance System basically has two main modules for proper
functioning.
First module is admin which has right for creating space for new batch. Any
Entry of new faculty, Updating in subject if necessary, and sending notice.
Second module is handled by the user which can be a faulty or an operator .
User has a right of making daily attendance ,generating report . Attendance
can be taken in two ways
1.On the basic of Subject and month . Online Attendance Management
System.
2.On the basis of Class.
Online Attendance management system project is implemented in asp.net
platform. This project can be used as mini project for computer science
students. Main aim of this project is to implement a software application for
institutions to manage daily attendance of students. In existing systems
manual record books are used for managing attendance. This process require
lot of time using this application teachers can store data in database at the
time of attendance and same data can be used in future. Using this system we
can send sms to parents if student is absent.

1.3 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. But later on the project can be modified to operate it
online. Attendance Management System.
This project has large scope as it has the following features which help in
making it easy to use understand and modify it:

Automation of Classroom attendance.

No Need to do lengthy paper work.
To save the environment by using paper free work.
Management of Student Data.

Main Points are:

Simplified Management of Students Performance

Real Time Notification.
Making Campus Tech-Savvy.
Student and Faculty Interaction.

SYSTEM REQUIREMENT

2.1 HARDWARE REQUIREMENT

PC
128 MB RAM(or above)
40 Gb HARDDISK
Mouse/Keyboard
Printer

2.2 SOFTWARE REQUIREMENT

OS-Windows XP
Microsoft Visual Studio
SQL Server Manager
Android Studio
Internet

3.1 FRONT END DESCRIPTION

LANGUAGE:- ASP.NET
ASP.NET is a server-side Web application framework designed for Web
development to produce dynamic Web pages. It was developed by Microsoft
to
allow programmers to build dynamic web sites, web applications and web services.
It was first released in January 2002 with version 1.0 of the .NET Framework, and
is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is
built on the Common Language Runtime (CLR), allowing programmers to write
ASP.NET code using any supported .NET language. The ASP.NET SOAP
extension framework allows ASP.NET components to process SOAP messages.
ASP.NET Web pages, known officially as Web Forms, are the main building blocks
for application development. Web forms are contained in files with a ".aspx"
extension; these files typically contain static (X)HTML markup, as well as markup
defining server-side Web Controls and User Controls where the developers place
all the rc content for the Web page. Additionally, dynamic code which runs on the
server can be placed in a page within a block <% -- dynamic code -- %>, which is
similar to other Web development technologies such asPHP, JSP, and ASP.
With ASP.NET Framework 2.0, Microsoft introduced a new code-behind model
which allows static text to remain on the .aspx page, while dynamic code remains
in an .aspx.vb or .aspx.cs or .aspx.fs file (depending on the programming language
used). ASP.NET uses a "visited composites" rendering technique. During
compilation, the template (.aspx) file is compiled into initialization code which
builds a control tree (the composite) representing the original template. Literal text
goes into instances of the Literal control class, and server controls are represented
by instances of a specific control class. The initialization code is combined with
user-written code (usually by the assembly of multiple partial classes) and results
in a class specific for the page. The page doubles as the root of the control tree.
ASP.NET session state enables you to store and retrieve values for a user as the
user navigates ASP.NET pages in a Web application. HTTP is a stateless protocol.
This means that a Web server treats each HTTP request for a page as an
independent request. The server retains no knowledge of variable values that were
5

used during previous requests. ASP.NET session state identifies requests from the
same browser during a limited time window as a session, and provides a way to
persist variable values for the duration of that session. By default, ASP.NET
session state is enabled for all ASP.NET applications.
Alternatives to session state include the following:

Application state, which stores variables that can be accessed by all users of
an ASP.NET application.

Profile properties, which persists user values in a data store without expiring
them.

ASP.NET caching, which stores values in memory that is available to all

ASP.NET applications.

View state, which persists values in a page.

Cookies.

The query string and fields on an HTML form that are available from an
HTTP request.

JAVA : Android-based smartphones are in vogue due to the flexibility they

offer for customization. Unlike Apples iOS, Google Android offers better
user experience in terms of applications. The Android application
development kit is an open-source Linux-based operation system, which
has its own middleware and key applications. The platform for app
development in Android is Java. This means that you use the Java library
and code the applications in Java, C, and C++ programming language. But,
the most widely used programming language for android application
development is Java.

4.1 Software Analysis

4.1.1 Software Development Life cycle

Fig 4.1:- SDLC

4.1.2 DESCRIPTION OF USED MODEL

Rapid application development
Rapid
application
development (RAD)
is
a software
development
methodology that uses minimal planning in favor of rapid prototyping. The
"planning" of software developed using RAD is interleaved with writing the
software itself. The lack of extensive pre-planning generally allows software to be
written much faster, and makes it easier to change requirements.Graphical user
interface builders are often called rapid application development tools.
Rapid Application Development (RAD) is a term originally used for describing
a software development process first developed and successfully deployed during
the mid-1970s by D.Dinadasa at New York Telephone Co's Systems Development
Center under the direction of Dan Gielan. Following a series of remarkably
successful implementations of this process, Gielan lectured extensively in various
forums on the methodology, practice, and benefits of this process.
As the name suggests Rapid Application Development (RAD) model is
an incremental software process model that focuses on short development cycle
time. This model is a high-speed model which adapts many steps from waterfall
model in which rapid development is achieved by using component based
construction approach.
In case if project requirements are well understood and project scope is well known
then RAD process enables a development team to create a fully functional system
i.e. software product within a very short time period may be in days.
RAD model is like other process models maps into the common and major
framework activities.

Phases Of RAD Model :

1. Requirements Planning phase combines elements of the system planning
and systems analysis phases of the Systems Development Life
Cycle (SDLC). Users, managers, and IT staff members discuss and agree on
business needs, project scope, constraints, and system requirements. It ends
when the team agrees on the key issues and obtains management
authorization to continue.
2. User design phase during this phase, users interact with systems analysts
and develop models and prototypes that represent all system processes,
inputs, and outputs. The RAD groups or subgroups typically use a
combination of Joint Application Development (JAD) techniques and CASE
tools to translate user needs into working models.
3. Construction phase focuses on program and application development
task similar to the SDLC. In RAD, however, users continue to participate
and can still suggest changes or improvements as actual screens or reports
are developed. Its tasks are programming and application development,
coding, unit-integration and system testing.
4. Cutover phase resembles the final tasks in the SDLC implementation
phase, including data conversion, testing, changeover to the new system,
and user training.

Fig 4.2: RAD

10

4.2 SOFTWARE DESIGN

4.2.1 Data Flow Diagram
The DFD takes an input-process-output view of a system. That is, data objects flow
into the software, are transformed by the processing elements, and resultant data
objects flow out of the software. Data objects are represented by labeled arrows and
transformations are represented by circles. The DFD is represented in a hierarchical
fashion. The first DFD represents the system as a whole. Subsequent data flow
diagrams provide increasing detail with each subsequent level.

The data flow diagram enables the software engineer to develop models of the
information domain and functional domain at the same time. As the DFD is refined
into levels of greater detail, the analysts perform an implicit functional
decomposition of the system. Also DFD refinement results in a corresponding
refinement of data as it moves through the processes that embody the application.

Fig 4.3:- Zero (0) Level

11

4.2.1.2 DATA FLOW DIAGRAM

Fig4.4:- One (1) Level

12

4.2.1.3 DATA FLOW DIAGRAM

Fig 4.5: Two (2) Level

13

SYSTEM CHART

Fig4.6: System Chart

5.1 SOURCE CODE

14

CONCEPT
The concept behind the working of this application is to use the control commands
of the system and then run them through Asp .Net(C#) and Android(JavaCore).
Internet hosting provides computer-based services to customers over a network..
The most limited sense of this business is that of providing access to a particular
application program (such as customer relationship management) using a standard
protocol such as HTTP.
The application software resides on the vendor's system and is accessed by users
through a web browser using HTML or by special purpose client software
provided by the vendor. Custom client software can also interface to these systems
through XML APIs. These APIs can also be used where integration with in-house
systems is required
Android apps are written in the Java programming language. The Android SDK
tools compile your codealong with any data and resource filesinto an APK: an
Android package, which is an archive file with an .apk suffix. One APK file
contains all the contents of an Android app and is the file that Android-powered
devices use to install the app.

App components are the essential building blocks of an Android app. Each
component is a different point through which the system can enter your app. Not
all components are actual entry points for the user and some depend on each other,
but each one exists as its own entity and plays a specific roleeach one is a unique
building block that helps define your app's overall behavior.

15

SOURCE

Master Page:

<%@
Master
Language="C#"
Inherits="SampleMasterPage" %>

AutoEventWireup="true"

CodeFile="Head.master.cs"

<html>
<head id="Head1" runat="server">
<title></title>
<link href="~/Styles/HeadHome.css" rel="stylesheet" type="text/css" />
<link href="~/Styles/MasterHead.css" rel="Stylesheet" type="text/css" />
<link href="../Styles/Site.css" rel="Stylesheet" type="text/css" />
<asp:ContentPlaceHolder ID="head" runat="server">
</asp:ContentPlaceHolder>
</head>
<body background="bgcolour3.jpg">
<form id="form1" runat="server">
<div id="wrapper">
<div id="header">
<div id="logo">
<img alt="UIT-BU logo" src= "Images/uit-mono.jpg"/>
</div>
<div id="cname">
<marquee behavior="slide" direction="left" scrollamount="50">

16

<h1>
University Institute of
<br />
Technology</h1></marquee>
<div id="uname">
<%--<marquee behavior="slide" direction="down" scrollamount="12">--%>
<h1>
Barkatullah University, Bhopal</h1>
<%--</marquee>--%>
</div>
</div>

</div>
<div id="news">
<div id="newsHead">
News Feed
</div>
<div id="newsBody">
<marquee direction="up" scrollamount="2" onmouseover="this.stop();"
onmouseout="this.start();">
<ul>
<li>
<asp:Label ID="lblNews1" runat="server" Text="VIIIth Sem
Exam"></asp:Label></li>
<li>

17

<asp:Label ID="lblNews2" runat="server" Text="Internal

Dates"></asp:Label></li>
<li>
<asp:Label ID="lblNews3" runat="server" Text="Scholarship
Forms"></asp:Label></li>
<li>
<asp:Label ID="lblNews4" runat="server" Text="51 AP
Posts"></asp:Label></li>
<li>
<asp:Label ID="lblNews5" runat="server" Text="GP
Forms"></asp:Label></li>
</ul></marquee>

</div>
</div>
<div id="content">
<div id="pageName">
<asp:Label ID="lblPageName" runat="server" Text="None" Font-Size="20pt"
ForeColor="White"
Font-Names="Times New Roman"></asp:Label>
</div>
<div id="cph">
<asp:ContentPlaceHolder ID="pages" runat="server">
</asp:ContentPlaceHolder>
</div>
<div id="menu">
<ul>
18

<li><a href='#'>Menu</a>
<ul>
<li><a href="UIT.aspx">
<img src="ico/dept.ico" alt="Pic" />
<br />
<b>Home</b> </a></li>
<li><a href="UIT.aspx">
<img src="ico/dept.ico" alt="Pic" />
<br />
<b>Department</b> </a></li>
<li><a href="UIT.aspx">
<img src="ico/course.ico" alt="Pic" />
<br />
<b>Courses</b> </a></li>
<li><a href="UIT.aspx">
<img src="ico/about.ico" alt="Pic" />
<br />
<b>About</b> </a></li>
<li><a href="UIT.aspx">
<img src="ico/contact.ico" alt="Pic" />
<br />
<b>Contacts</b> </a></li>
<li><a href="UIT.aspx">
<img src="ico/result.ico" alt="Pic" />
<br />
19

<b>Result</b> </a></li>
</ul>
</li>
</ul>
</div>
</div>
<div id="footer">
</div>
</div>

</form>
</body>
</html>

20

Master Page :
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
public partial class SampleMasterPage : System.Web.UI.MasterPage
{
protected void Page_Load(object sender, EventArgs e)
{
//Session.Mode = System.Web.SessionState.SessionStateMode.InProc;
try
{
lblPageName.Text = Session["pageName"].ToString();
}
catch (NullReferenceException nre)
{
//Session["pageName"] =
string s = this.Page.ToString();
string f;
s = s.Remove(0,s.IndexOf("_")+1);
s = s.Remove(s.IndexOf("_"));
f = s.Substring(0, 1);
s = s.Remove(0, 1);
f = f.ToUpper();
s = f + s;
Session["pageName"] = s;
}
finally
{
lblPageName.Text = Session["pageName"].ToString();
// Session.Abandon();
Session.Clear();
//Session.RemoveAll();
}
}
}

Home Page:

21

<%@
Page
Title="UIT-Home"
AutoEventWireup="true"

Language="C#"

MasterPageFile="~/Head.master"

CodeFile="UIT.aspx.cs" Inherits="Pages_UIT" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" runat="Server">

</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="pages" runat="Server">
<div id="home">
<div id="tabs">
<table cellspacing="5px">
<tr>
<td colspan="4" rowspan="2" class="caption" id="gallery">
Photo Gallery
</td>
<td id = "eCampus">
<a href = "eCampus.aspx">e-Campus</a>
</td>
<td>
</td>
</tr>
<tr>
<td colspan="2" class="caption" id="director">
<a href = "">Director Desk</a>
</td>
</tr>

22

<tr>
<td colspan="2" class="caption" id="event">
<a href = "">TCS Detail Submission</a>
</td>
<td colspan="2" class="caption" id="download">
<a href = "">Downloads</a>
</td>
<td class="caption" id="library">
<a href = "">Library</a>
</td>
<td class="caption" id="cl">
<a href = "">Campus Life</a>
</td>
</tr>
<tr>
<td colspan="2" class="caption" id="rAp">
<a href = "">Research<br />
& Publication</a>
</td>
<td colspan="2" id="antiR">
<a href = ''>Anti-Ragging<br />
Campus</a>
<table>
<thead>
<tr><td>UIT Anti Ragging Committe</td></tr>
23

<tr><td>&nbsp;</td>

<%--<td>Phone:</td>--%></tr>

</thead>
<tbody>
<tr><td>Rohit RajVedya <ul><li>9876543210</li></ul></td>
<td>1234567890</td>--%></tr>

<%--

<tr><td>R. K. Sharma<ul><li>9876543210</li></ul></td>
<td>1234567890</td>--%></tr>

<%--

<tr><td>Abhishek Jain<ul><li>9876543210</li></ul></td>
<td>1234567890</td>--%></tr>

<%--

<tr><td>4<ul><li>9876543210</li></ul></td>
<td>1234567890</td>--%></tr>

<%--

<tr><td>5<ul><li>9876543210</li></ul></td>
<td>1234567890</td>--%></tr>

<%--

</tbody>
</table>
</td>
<td class="caption" id="honour">
<a href = "">Achivements</a>
</td>
<td class="caption" id="faculty">
<a href = "">Faculty Team</a>
</td>
</tr>
</table>
</div>
</div>
</asp:Content>
24

Home Page
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class Pages_UIT : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{
Session["pageName"] = "Home";
}

25

eCampus.aspx

<%@ Page Title="" Language="C#" MasterPageFile="~/Head.master" AutoEventWireup="true"

CodeFile="eCampus.aspx.cs" Inherits="eCampus" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="pages" Runat="Server">
<table style = "color: White; ">
<tr>
<td>Login ID</td>
<td>
<asp:TextBox ID="txtid" runat="server"></asp:TextBox></td>
</tr>
<tr>
<td>Password</td>
<td>
<asp:TextBox ID="txtpass" runat="server" TextMode =
"Password"></asp:TextBox></td>
</tr>
<tr>
<td colspan = "2" align = "center">
<asp:Button ID="btnLogIn" runat="server" Text="Log In"
onclick="btnLogIn_Click" /></td>
</tr>
</table> </asp:Content>

26

eCampus.aspx.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class eCampus : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{
Session["pageName"] = "eCampus";
}
protected void btnLogIn_Click(object sender, EventArgs e)
{
Session["name"] = txtid.Text;
Response.Redirect("MyData.aspx");
}
}

27

MyData.aspx
<%@ Page Title="" Language="C#" MasterPageFile="~/Head.master" AutoEventWireup="true"
CodeFile="MyData.aspx.cs" Inherits="MyData" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="pages" Runat="Server">
<table style = " color :White; " width = "35" border = "2" style = "margin-left: 300px;">
<tr style = " font-weight:bold;" >
<td width="150">Subject Name</td>
<td width="150">Faculty Name</td>
<td width="150">Days Attended</td>
<td width="150">Total Classes</td>
</tr>
<tr height = "75"> <td>Network Security </td><td>Mrs. Nitya Khare </td>
<td>8</td>
<td>15</td>
</tr>
<tr height = "75"><td>Neural Network </td><td>Ms. Pooja Ahuja </td>
<td>3</td>
<td>10</td>
</tr>
<tr height = "75"><td>Compiler Design</td><td>Mrs. Nidhi Singh </td>
<td>6</td>
<td>10</td>
</tr></table></asp:Content>
28

MyData.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class MyData : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{
Session["pageName"] = Session["name"];
}
}

29

5.2 SNAPSHOTS
Home:

Menu:

30

Other:

eCampus:

31

Login:

Mydata:

32

Interface

Menu

33

6.1 TESTING

Testing is more than just debugging. The purpose of testing can be quality
assurance, verification and validation, or reliability estimation. Correctness testing
and reliability testing are two major areas of testing. Software testing is a trade-off
between budget, time and quality.
Software Testing
Software Testing is the process of executing a program or system with the intent of
finding errors. Or, it involves any activity aimed at evaluating an attribute or
capability of a program or system and determining that it meets its required results.
Software is not unlike other physical processes where inputs are received and
outputs are produced. Where software differs is in the manner in which it fails.
Unlike most physical systems, most of the defects in software are design errors, not
manufacturing defects.
To improve qualityAs computers and software are used in critical applications, the
outcome of a bug can be severe. Bugs can cause huge losses.
For Verification & Validation (V&V)
Another important purpose of testing is verification and validation (V&V). It is
heavily used as a tool in the V&V process. Testers can make claims based on
interpretations of the testing results, which either the product works under certain
situations, or it does not work.
Software Testing Types
Black-box testing
The black-box approach is a testing method in which test data are derived from the
specified functional requirements without regard to the final program structure. It
is also termed data-driven, input/output driven or requirements-based testing. A
testing method emphasized on executing the functions and examination of their
input and output data.

34

White-box testing
Contrary to black-box testing, software is viewed as a white-box, or glass-box in white-box
testing, as the structure and flow of the software under test are visible to the tester. This
testing is based on knowledge of the internal logic of an applications code. Testing plans are
made according to the details of the software implementation, such as programming
language, logic, and styles. Test cases are derived from the program structure. White-box
testing is also called glass-box testing, logic-driven testing or design-based testing .
Unit testing
This involves testing of individual software components or modules. Typically done by the
programmer and not by testers, as it requires detailed knowledge of the internal program
design and code.
System testing
Entire system is tested as per the requirements. Black-box type testing that is based on overall
requirements specifications, covers all combined parts of a system.
End-to-end testing
Similar to system testing, involves testing of a complete application environment in a
situation that mimics real-world use, such as interacting with a database, using network
communications, or interacting with other hardware, applications, or systems if
appropriate.
Usability testing
User-friendliness check. Application flow is tested, Can new user understand the application
easily, Proper help documented whenever user stuck at any point. Basically system
navigation is checked in this testing.
Install/uninstall testing
Tested for full, partial, or upgrade install/uninstall processes on different operating
systems under different hardware, software environment.

35

Recovery testing
Testing how well a system recovers from crashes, hardware failures, or other catastrophic
problems.
Security testing
Can system be penetrated by any hacking way. Testing how well the system protects against
unauthorized internal or external access. Checked if system, database is safe from external
attacks.
Compatibility testing
Testing how well software performs in a particular hardware/software/operating
system/network environment and different combination s of above.
Comparison testing
Comparison of product strengths and weaknesses with previous versions or other
similar products.
Alpha testing
In house virtual user environment can be created for this type of testing. Testing is done at
the end of development. Still minor design changes may be made as a result of such testing.
Beta testing
Testing typically done by end-users or others. Final testing before releasing application for
commercial purpose.

36

7.1 BENEFITS
So if youre about to begin your own resume or even updating an existing one, take
a deep breath, dont stress and consider the benefits of using a online resume
Maker.

Save Time
Building your resume online saves you time better spent networking or getting the
training and education you need to succeed. Just add your personal information to
one of our industry-specific templates and build a great resume in minutes.

Free and Easy to Use

Theres no risk involved in using an online resume builder like ours because its
free. And its super-easy to use too, so theres no learning curve to stop you.

Peace of Mind
Using an online resume builder delivers a great confidence boost since you can
move forward knowing you have a professionally formatted resume that will
impress your future employer. Eliminating fear related to the task and beating
writers block allows you to get on with the business of landing your dream job.
This project has large scope as it has the following features which help in
making it easy to use understand and modify it:

Automation of Classroom attendance.

No Need to do lengthy paper work.
To save the environment by using paper free work.
Management of Student Data.

37

38

10.1 CONCLUSION

The significance project has provided the following benefits:

The significance is to automate the attendance system.

It ends the old paper pen work.
Making the college campus more updated.
Making students aware of their semester and till date performance.
Technical Savvy College Campus.

This project has the following features which help in making it easy to use
understand and modify it:

Automation of Classroom attendance.

No Need to do lengthy paper work.
To save the environment by using paper free work.
Management of Student Data.

The Main Points are:

Simplified Management of Students Performance

Real Time Notification.
Making Campus Tech-Savvy.
Student and Faculty Interaction.

39

11.1 REFERENCES

Tutorials Point : tutorialspoint.com

Wkipedia : www.wikipedia.com
W3School : www.w3schools.com
DotNet : www.aspdotnetsuresh.com
Android : www.androidtutorials.com

40