Chapter-1

Introduction

1.1 Introduction

This system entitled ” Attendance Portal System ” is used to create a tool that maintains
students attendance on daily basis. The attendance portal system has three user modules ,
Adminstrator, Staff and Student. Maintaining attendance log has become a tedious task for
the staff and more tedious task for students to maintain proper attendance. This system
bring solution to such tiring work by bringing everything under a single roof.
Here Adminstrator is a person with good computer knowledge representing corresponding
schools or colleges that make us of this system. Initially the administrator creates
Classroom by creating standards and multiple divisions for each standards. And also
assigns a staff to each standard. Adminstrator maintains all the data of the staff and
provides login credentials to each and every staff . Adminstrator can also view the staff
reports , feedbacks and complains reports. Staffs assign the number of students per each
classroom. And inserts the student details along with their photograph. Staff can insert
attendance for these students on daily basis by marking attendance by choosing any one of
these option “ Absent “ , “Present”, ”Leave”. Staff can view the student report . Also
respond to complaints made by the student and also Approve or Reject the leave
application from their class students. Students can view their attendance , Present count ,
no.of complaints made and replies from their respective staffs and can also view the status
of their leave application.

1
1.2 System specification

1.2.1 Hardware configuration

Processor : PIV

Ram : 1 GB

Hard Disk : 500 GB Space

Monitor : VGA Color (256)

1.2.2 Software configuration

Operating System : Windows 2000 or Higher

Service Pack : 2+

Platform : Visual Studio 2012

Scripting : ASP.NET

Backend : SQL server 2014

Web Server : IIS

2
 Chapter-2

System Study

2.1 Purpose

To create a Tool that helps schools and colleges maintain student attendance on daily
basis and monthly basis by providing access to corresponding staff by allotting
classrooms for them and students of those classes under the guidance of those
corresponding teachers.

2.2 Study of the Existing System

 The Existing system is a manual entry of student attendance , Sometimes the attendance
will be carried out in the hand written registers.
 It will be a tedious job to maintain the record for the respective staff.
 The retrieval of the information is not as easy as the records are maintained in the
hand written registers.
 The manual entry of attendance requires correct feed on input into the respective field.
 Suppose the wrong inputs are entered, it requires more rectification which leads to more
work ,hence the user find it difficult to use.
 There is possibility for tampering and damage of records

2.3 Proposed System

To overcome the drawbacks of the existing system, the proposed system has been evolved.
This application aims to reduce the paper work and saves 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.

3
 It is trouble-free to use.
 It is a relatively fast approach to enter attendance
 Is highly reliable, approximate result from user.
 Students can apply leave in advance , file complains and suggestions.
 Staff can approve or deny the leave applications.

4
 Chapter-3

System Design

Design is the first step in the development phase for any engineered product or system. The
designer’s goal is to produce a model or representation of an entity that will later be built. Design
is the place where quality is fostered in software development. Design provides us with
representations of software that can assess for quality. Design is the only way that we can
accurately translate a customer‟s view into a finished software product or system. Software
design serves as a foundation for all the software engineering steps that follow. Without a strong
design we risk building an unstable system – one that will be difficult to test, one whose quality
cannot be assessed until the last stage.

3.1 System Modules

1. Login:

This feature allows only authorized users to use the application i.e., Adminstrator , Staff
and Students. The application comes with a default administrator account. The
Adminstrator account has a user id “Admin” and password “123” by default. Staff can
login using the credentials provided by the administrator. Students can also login using the
credentials created by their staff . These users can also change his/her password whenever
necessary.

2. Add Classes :
It allows the Admin to add standards and division for each respective standards. Later
the staff who is assigned to each standard will assign the number of seats for each
division .

5
3. Add Staff :

The College or School Adminstrator creates accounts for the staff and assigning
classroom for them. Adminstrator gathers staff details along with their picture and
qualification details.

4. Add Students :

Each standard has a staff assigned under those staff certain number of students are
assigned . These staff add these students to their respective classes. Staff inserts all the
student data and provide them the login credentials.

5. Insert Attendance:

Staff of each class can insert attendance to each student date wise by selecting the
option one of these option “Absent”, ‘Present”, “Leave” from the drop down menu .
They can also view the Attendance Report later.

6. Apply Leave :

Students can apply for leave in advance by mentioning in the reason and the number of
days . Students can also view the status of the leave application i.e whether the leave
application has been “Approved” or “ Rejected”.

6
3.2 Data Flow Diagram

A data flow diagram is a graphical view of how data is processed in a system in terms of input and

output. The Data flow diagram (DFD) contains some symbol for drawing the data flow diagram.

Process Data Flow

Source or Destination of data Data Store

LEVEL 0:

7
DFD –ADMIN

8
DFD – STAFF

DFD-STUDENT

9
3.3 Activity Diagram

The activity diagram used to describe flow of activity through a series of actions. Activity
diagram is a important diagram to describe the system. An activity diagram shows the overall
flow of control.

Basic notation in Activity Diagram:

Initial node : The filled in circle is the starting point of the diagram.

Activity Final node: The filled circle with a border is the ending point. An activity diagram
can have zero or more activity final nodes.

Activity: The rounded rectangle represents activities that occur.

Flow/Edge: The arrow on the diagram.

Fork: A black bar with one flow going into it and several leaving it. This denotes the
beginning of parallel activity.

Join: A black bar with several flows entering it and one leaving it. All flows going into the
join must reach it before processing may continue. This denotes the end of parallel
processing.

Decision: A diamond with one flow entering and several leaving.

10
ACTIVITY DIAGRAM – ADMIN

11
ACTIVITY DIAGRAM – STAFF

12
ACTIVITY DIAGRAM – STUDENT

13
3.4 USE CASE DIAGRAM

The use case diagram are usually referred to as behavior diagram used to describe the actions of
all user in a system. All user describe in use case are actors and the functionality as action of
system.The Use case diagram is a collection of diagram and text together that make action on
goal of a process.

14
3.5 TABLE DESIGN

STAFF TABLE

Primary key : SID

ATTENDANCE TABLE

Primary key : AID

15
STUDENT TABLE

Primary key : SID

LEAVE TABLE

Primary key : LID

16
STANDARD TABLE

Primary key : SID

DIVISON TABLE

Primary key : DID

FEEDBACK TABLE

Primary key : FID

17
3.6 INPUT DESIGN

In an information system, input is the raw data that is processed to produce output. It is
important to design appropriate data input methods to prevent errors while entering data. These
methods depend on whether the data is entered by customers in forms manually and later entered
by data entry operators, or data is directly entered by users on the PCs.

The objectives of input design are ,

 To design data entry and input procedures

 To reduce input volume
 To design source documents for data capture or devise other data capture methods
 To design input data records, data entry screens, user interface screens, etc.
 To use validation checks and develop effective input controls.

ADD STAFF

18
ADD NEW STUDENT

19
3.7 OUTPUT DESIGN

The design of output is the most important task of any system. During output design,
developers identify the type of outputs needed, and consider the necessary output controls
and prototype report layouts.

Objectives of Output Design

The objectives of input design are −

 To develop output design that serves the intended purpose and eliminates the
production of unwanted output.

 To develop the output design that meets the end users requirements.

 To deliver the appropriate quantity of output.

 To form the output in appropriate format and direct it to the right person.

 To make the output available on time for making good decisions.

20
ADD STAFF REPORT

ADD STUDENT REPORT

21
 CHAPTER-4

TESTING

Definition

The process or method of finding error/s in a software application or program so that the
application functions according to the end user's requirement is called software testing. Software
testing is the process of verifying a system with the purpose of identifying any errors, gaps or
missing requirement versus the actual requirement. Software testing is broadly categorized into
types functional testing and non-functional testing . Testing should be started as early as possible
to reduce the cost and time to rework and produce software that is bug-free so that it can be
delivered to the client. However, in Software Development Life Cycle (SDLC), testing can be
started from the Requirements Gathering phase and continued till the software is out there in
productions. It also depends on the development model that is being used.

Testing Objective

The main objective of testing is to uncover a host of errors, systematically and with minimum
effort and time. Stating formally, we can say,

• Testing is a process of executing a program with the intent of finding an error.

• A successful test is one that uncovers an as yet undiscovered error.

• A good test case is one that has a high probability of finding error, if itexists.

• The tests are inadequate to detect possibly present errors.

• The software more or less confirms to the quality and reliable standards.

22
4.1 Unit Testing

Unit Testing is a level of software testing where individual units/ components of a software are
tested. The purpose is to validate that each unit of the software performs as designed. A unit is
the smallest testable part of any software. It usually has one or a few inputs and usually a single
output. In procedural programming, a unit may be an individual program, function, procedure,
etc. In object-oriented programming, the smallest unit is a method, which may belong to a base/
super class, abstract class or derived/ child class. (Some treat a module of an application as a
unit. This is to be discouraged as there will probably be many individual units within that
module.) Unit testing frameworks, drivers, stubs, and mock/ fake objects are used to assist in unit
testing.

Advantages

 Unit testing increases confidence in changing/ maintaining code. If good unit tests are
written and if they are run every time any code is changed, we will be able to promptly
catch any defects introduced due to the change.

 Codes are more reusable. In order to make unit testing possible, codes need to be
modular. This means that codes are easier to reuse.

 The cost of fixing a defect detected during unit testing is lesser in comparison to that of
defects detected at higher levels.

 Debugging is easy. When a test fails, only the latest changes need to be debugged.

23
24
 CHAPTER-5

CONCLUSION

5.1 Conclusion

The main objective of the project has been satisfied , the project is developed by making the best
use of the software and hardware tools mentioned above. Thus the system is very handy in
nature, easily accessible and time efficient. There is no tampering of data because maintaining
attendance reports have become quite easy. The system has passed the test cases and is properly
functioned. The unique feature in this project is that it encourages and accepts suggestion and
complains from the students which is very important to improve the quality of education and
increase the standards.

25
5.2 Scope for future aspects

A number of directions can be followed as an extension of this research. Some challenges and
open questions still to be explored in the research work are as follows:

 Developing a Android based application for students and staff to access anytime.
 Identifying new sources of implicit knowledge
 New methods for student and staff interaction.
 New module to share knowledge and Discussion rooms.
 New methods to improve the management maintenance of educational institutions.

26
 CHAPTER-6

APPENDICES

6.1 Web References

 www.DOT NETcom

 www.ASP Tutorial.com

 www.draw.io

 www.stackoverflow.com

 www.w3schools.com

6.2 Books Referred

1. Alex Homer ,”Professional ASP.NET 1.1”, 2004 Edition , Wrox Publication

2. Steven Holzner , “Visual Studio. NET Black Bok”, 2003 Edition, Dreamtech Publication

3. Roger S Pressman , “Software Engineering”, 2000 Edition, Dreamtech Publications

4. Karli Watson, Richard Anderson, “Professional.NET 1.1” 2004 Edition, Dreamtech

Publications.

27
 CHAPTER-7

SAMPLE SOURCE CODE & SCREENSHOTS

7.1 Sample Coding

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title><link rel="stylesheet" type="text/css"
href="engine1/style.css" media="screen" />
<style type="text/css">a#vlb{display:none}</style>
<script type="text/javascript" src="engine1/jquery.js"></script>
<link href="Style.css" rel="stylesheet" type="text/css" />
<style type="text/css">
.style1
{
width: 100px;
}
.style2
{
width: 4px;
}
.style3
{
width: 100%;
}
.style4
{
width: 75px;
}

28
.style5
{
font-family: "Arial Rounded MT Bold";
font-size: x-small;
color: #006666;
}
</style>
</head>
<body>
<form id="form1" runat="server">
<div id="header">

<asp:Image ID="Image3" runat="server" ImageUrl="~/img/logo1.png" />

</div>
<div id="menu">
<table class="style1">
<tr>
<td>
<asp:Button ID="Button1" runat="server" CssClass="btnmenu" Text="Home"
PostBackUrl="~/Home.aspx" />
</td>
<td class="style2">
<asp:Button ID="Button4" runat="server" CssClass="btnmenu" Text="Standard"
PostBackUrl="~/Branch.aspx" />
</td>
<td>
<asp:Button ID="Button3" runat="server" CssClass="btnmenu" Text="Staff"
PostBackUrl="~/Staff.aspx" />
</td>
<td>
<asp:Button ID="Button2" runat="server" CssClass="btnmenu" Text="FeedBack"
PostBackUrl="~/Feedback.aspx" />
</td>
<td>
<asp:Button ID="Button5" runat="server" CssClass="btnmenu" Text="Admin Panel"
PostBackUrl="~/Admin/Home.aspx" />
</td>
<td>
<asp:Button ID="Button6" runat="server" CssClass="btnmenu" Text="Contact Us"
PostBackUrl="~/ContactUs.aspx" />
</td>
</tr>
</table>
</div>
<div id="mainn">
<div id="left">
<div id="studentlogin">
<table class="style3">
<tr>
<td class="logintitle" colspan="2">
Student Login</td>
</tr>
<tr>
<td class="lbl">
Login Name :</td>
<td>

29
<asp:TextBox ID="txtstuuname" runat="server" CssClass="txt"></asp:TextBox>
</td>
</tr>
<tr>
<td class="lbl">
Password :
</td>
<td>
<asp:TextBox ID="txtstupass" runat="server" CssClass="txt"
TextMode="Password"></asp:TextBox>
</td>
</tr>
<tr>
<td>
&nbsp;</td>
<td>
<asp:Button ID="btnstudenlogin" runat="server" CssClass="btn" Text="Login"
onclick="btnstudenlogin_Click" />
</td>
</tr>
<tr>
<td>
&nbsp;</td>
<td>
<asp:LinkButton ID="LinkButton1" runat="server" ForeColor="#339966"
Visible="False">Forgot Password</asp:LinkButton>
</td>
</tr>
<tr>
<td>
&nbsp;</td>
<td>
<asp:Label ID="lblstuerror" runat="server"></asp:Label>
</td>
</tr>
<tr>
<td colspan="2"
style="border-top-style: solid; border-top-width: thin; border-top-color:
#808080">
<table class="style3">
<tr>
<td class="style4">
<asp:Image ID="Image1" runat="server" Height="65px"
ImageUrl="~/img/student.png" Width="70px" />
</td>
<td>
Student login with username and password and view reports..</td>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div id="stafflogin">
<table class="style3">
<tr>
<td class="logintitle" colspan="2">

30
Staff Login</td>
</tr>
<tr>
<td class="lbl">
Login Name :</td>
<td>
<asp:TextBox ID="txtstaffuname" runat="server" CssClass="txt"></asp:TextBox>
</td>
</tr>
<tr>
<td class="lbl">
Password :
</td>
<td>
<asp:TextBox ID="txtstaffpass" runat="server" CssClass="txt"
TextMode="Password"></asp:TextBox>
</td>
</tr>
<tr>
<td>
&nbsp;</td>
<td>
<asp:Button ID="btnstafflogin" runat="server" CssClass="btn" Text="Login"
onclick="btnstafflogin_Click" />
</td>
</tr>
<tr>
<td>
&nbsp;</td>
<td>
<asp:LinkButton ID="LinkButton2" runat="server" ForeColor="#339966"
Visible="False">Forgot Password</asp:LinkButton>
</td>
</tr>
<tr>
<td>
&nbsp;</td>
<td>
<asp:Label ID="lblstafferror" runat="server"></asp:Label>
</td>
</tr>
<tr>
<td colspan="2"
style="border-top-style: solid; border-top-width: thin; border-top-color:
#808080">
<table class="style3">
<tr>
<td class="style4">
<asp:Image ID="Image2" runat="server" Height="65px"
ImageUrl="~/img/teacher.png" Width="70px" />
</td>
<td>
Staff can make attendance of student and generate reports afte login to
system.</td>
</tr>
</table>
</td>

31
</tr>
</table>
</div>
</div>
<div id="right"> <div id="wowslider-container1">
<div class="ws_images">
<a href="#"><img src="data1/images/479706089.jpg" alt="" title=""
id="wows0"/></a>
<a href="#"><img src="data1/images/blogimagehandraise2_1.jpg" alt="" title=""
id="wows1"/></a>
<a href="#"><img src="data1/images/phreassignmentsfaq.jpg" alt="" title=""
id="wows2"/></a>
</div>
<div class="ws_bullets"><div>
<a href="#wows0" title=""><img src="data1/tooltips/479706089.jpg"
alt=""/>1</a>
<a href="#wows1" title=""><img src="data1/tooltips/blogimagehandraise2_1.jpg"
alt=""/>2</a>
<a href="#wows2" title=""><img src="data1/tooltips/phreassignmentsfaq.jpg"
alt=""/>3</a>
</div></div>
<a style="display:none" href="http://wowslider.com">Script Image Slider by
WOWSlider.com v1.7</a>
</div>
<script type="text/javascript" src="engine1/script.js"></script>
<table class="style3">
<tr>
<td class="style5">
<asp:Image ID="Image4" runat="server" ImageUrl="~/img/mm.jpg" />
</td>
</tr>
</table>
</div>
</div> <div id="footer">© 2018 Student Attandance System. All Rights
Reserved.</div>
</form>
</body>
</html>

32
33
7.2 Screenshots

HOME PAGE

ADMIN LOGIN

34
ADD STANDARD

ADD STAFF

35
STAFF REPORT

STAFF :

36
ADD STUDENT

ADD STUDENT REPORT

37
INSERT ATTENDANCE

COMPLAIN MODULE

38
VIEW LEAVE APPLICATION

STUDENT

39
APPLY LEAVE

40
LODGE COMPLAIN

41
COMPLAIN: STAFF RESPONSE

42
LEAVE APPLICATION : RESPONSE

43
 CHAPTER-8

MYKLASSROOM TIMESHEET

44
 CHAPTER-9

PLAGIARISM REPORT

45