1.

Introduction

1.1.Aim:
The purpose of this application is to make the student attendance management system
more sophisticated. It includes all the required fields to provide details of the student which
consists of students attendance, results and also assignments which are allocated to students by
the concerned faculty members. It means to provide a customized application especially for
students and faculty members which could thereby reduce the efforts of faculty in physically
updating the attendance on registers which will be convenient to users for large number of
students attendance details and also it enables students to view their attendance, enhances to
assign works to students using assignments. Users can check the results of all the semesters of
the student given a roll number of the student.

1.1.1. Objective:
The main objective of this project is to provide an application to the college management which
helps in upgrading the current modules in the college attendance management system and to
improve the current system of allocating assignments and in displaying results.
Our project aims in providing the given below features:

Attendance

Assignments

Results

1.2. Literature Survey

Attendance was always an important part of final grade of students from the early days of
schools existence. But what is the reason for taking attendance? Many researchers conducted
researches to find out the relation between students attendance and result. Yao and Chiang
conducted a research to find out the relationship between students class attendance and their
overall grades between students who participated in computer science classes. The analysis of
their data showed that students who has more class attendance, have higher grades. Also, they
indicated that there is a strong correlation between absence from the first day of class and overall
result. Broucek and Bass indicated that the GPA is significantly correlated with attendance.

Tracking and stimulation of academic attendance are key factors to promotestudentsperformance

(Durden& Ellis, 1995). Academic attendance is such a vital instrument inthe academic environment that it is
logically explicable why researchers put so muchemphasis on it and on the full use of its advantages. In
order to make full use of the advantages that attendance register provides is crucial to create an
effectivemechanism to produce quality attendance data.Through a vigorous mechanism enforcement, it
is hard to ensure that individuals takefull benefit of all the offered educational opportunities by the
institution; poor attendance or absenteeism reduce the student interaction with the academic
environment and his exposure to the knowledge leading to the disruption of thelearning process
(Hornback et al., 2006). When students do not attend school on aregular basis, they are less
likely to reach their full potential and frequently end upbehind with their work and poor performance.

Johnston (2000) underlines that the aim of applying measures to control academicattendance is
not to penalize or punish students but motivate them and bring all thenecessary attributes
together to achieve academic success.Other aspects such as motivation and eagerness to gain
knowledge as factors todetermine good academic performance; a lot of different factors which
student attendance itself might depend on, they are attitude and motivation of students andtheir
parents, conditions in the school, transportation, student health, even weather,but these issues are
out scope of the paper.The study focus on the CPUT IT department and on the attendance
problem inherent to it.The problems faced concerning the attendance tracking system in CPUT
ITdepartment are:

Few lecturers check attendance register regularly because its manual, and it simply ends up
archived.

There is not a standard format for the attendance register.

The process is time consuming.

Some lecturers forget to register attendance.

Sometimes lecturers find it inconvenient to track and analyze attendance register.

This paper deals with the maintenance of the students attendance details. It generates the
attendance of the students on basis of their presence in class. It is maintained on the daily basis
of their attendance. The staff will be provided with the separate username & password to make
the students status. The staff 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 report and consolidate will be
generated. It also deals with allocation of assignments and examination results.

Moodle:
Moodle is a highly flexible, free software, open source learning platform. With comprehensive,
customizable and secure learning management features, it can be used to create a private website
for dynamic online courses. Moodle (acronym for modular object-oriented dynamic
learningenvironment), (stylized in lower-case asmoodle) is a also known as a learning
management system, or virtual learning environment. The platform can be used for e-learning
projects in University, Corporate training, School and Other sectors.
Moodle was originally developed by Martin Dougiamas to help educators create online
courses with a focus on interaction and collaborative construction of content, and is in continual
evolution. The first version of Moodle was released on 20 August 2002.
Moodle as a learning platform can enhance existing learning environment . As an E-learning
tool, Moodle has a wide range of standard and innovative features such as calendar and
Gradebook. Moodle is a leading Virtual learning environment and can be used in many types of
environments such as education, training and development and in business settings.
3

Moodle has continued to evolve since 1999 (since 2001 with the current architecture).
Major improvements in accessibility and display flexibility were developed in 1.5. The current
version can be seen at the top of the table of releases, below. It has been translated into 82
different languages and is accessible in many countries worldwide.
Not having to pay license fees or to limit growth, an institution can add as many Moodle
servers as needed. The Open University of the UK currently uses a Moodle installation for their
200,000 users while the UK government uses a Moodle installation for their Civil Service
Learning platform serving half a million employees.
It is often known for individual departments of institutions to use the unlimited feature,
such as the maths department of the University of York.
The development of Moodle continues as a free software project supported by a team of
programmers and an international user community, drawing upon contributions posted to the
online Moodle Community website that encourages debate and invites criticism.
Users can freely distribute and modify the software under the terms of the GNU General
Public License version 3 or any later version

1.3. Feasibility Study

Feasibility analysis begins once the goals are defined. It starts by generating broad
possible solutions, which are possible to give an indication of what the new system should look
like. This is where creativity and imagination are used. Analysts must think up new ways of
doing things, generate new ideas. There is no need to go into the detailed system operation yet.
The solution should provide enough information to make reasonable estimates about project cost
and give users an indication of how the new system will fit into the organization. It is important
not to exert considerable effort at this stage only to find out that the project is not worthwhile or
that there is a need significantly change the original goal. Feasibility of a new system means
ensuring that the new system, which we are going to implement, is efficient and affordable.
There are various types of feasibility to be determined. They are,

1.3.1.

Economical Feasibility:
Development of this application is highly economically feasible. The only thing to be

done is making an environment with an effective supervision. It is cost effective in the sense that
has eliminated the paper work completely. The system is also time effective because the
calculations are automated which are made at the end of the month or as per the user
requirement.
1.3.2. Technical feasibility:
The technical requirement for the system is economic and it does not use any other
additional Hardware and software. Technical evaluation must also assess whether the existing
systems can be upgraded to use the new technology and whether the organization has the
expertise to use it. Install all upgrades framework into the .Net package supported widows based
application. This application depends on Microsoft office and intranet service ,database. Enter
their attendance and generate report .
1.3.3.

Operational Feasibility:
The system working is quite easy to use and learn due to its simple but attractive

interface. User requires no special training for operating the system. Technical performance
include issues such as determining whether the system can provide the right information for the
Department personnel student details, and whether the system can be organized so that it always
delivers this information at the right place and on time using intranet services.

2. Software Requirements Specification

2.1 Problem statement:

This system developed will reduce the manual work and avoid redundant data. By
maintaining the attendance manually, then efficient reports cannot 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.

2.2 Project scope and objectives:

Our project aims in providing the given below features

Attendance

Assignments

Results

2.3 Product perspective:

It is an independent application which resembles moodle software that enables our
application to be more flexible and many of the features are dynamic in nature which helps to
work in a very user friendly mode.
2.4Existing system and proposed system:
Existing system:
The existing system is only associated for managing student attendance which will be
entered by the faculty members for their respective classes where, only the faculty and head of
the department can view the attendance. Student can check the marks only by selecting the year
and the semester which he/she wants to view along with the roll number and assignments are
being given manually to all the students with same questions.
6

Proposed system:
Here, we provide a facility to overcome the above mentioned problems.

Students can check the consolidated attendance at the end of every month. By providing
an additional feature for the student to check the attendance , makes him to be aware of
his attendance.

Allocation of assignments on a daily basis or in a periodic basis will be addressed to the

students with the help of this facility where the allocated assignments can be viewed by
the students along with the questions which they were to answer and date of assignment
when it was allocated will also be mentioned.

Students can check their results of all the semesters without specifying any year and
semester details which they want to retrieve.

2.5.Requirements:
Functional requirements:
The system can generate efficient weekly,consolidate report based on the attendance. As the
attendance is maintained in registers it has been a tough task for admin and staff to maintain for
long time. The system provides more sophisticated application for the college management
which helps in upgrading the current modules in the college attendance management system like
students viewing their attendance and to improve the current system of allocating assignments
and in displaying results.
The various modules present in our project are
1. Admin module
2. Faculty module
3. Student module
4. HOD module
5. Results module

Non-functional requirements:
Front end: c#
Development tool: Visual studio 2010
Back end: Microsoft sql server2008

3.Design
3.1. Architecture

Admin

Adds and modifies all details

HOD

request for reports

Students Attendence Management System

enter students attendenceand allocates assignments and view results

receive assignments

request for reports

Students

Faculty

Fig 3.1: Architecture

The above architecture shows the translation flow of the students attendance management
system. Admin provides login to the faculty, HOD and students. He can adds new faculty or
students to the system. He can modify existing records. HOD requests for various reports to the
system. Faculty updates students attendance and allocates assignments to the students. Students
receives assignments from the respective faculty. Students can view his/her attendance and
results.

3.2 . Uml Diagrams:

3.2.1. Usecase Diagrams

login

manages student records

<<include>>

Admin

<<include>>
creates students records

<<include>>

modify student records

delete student records

add subject

add faculty
view students attendance records

Faculty

updates students attendance

HOD

allocates assignments

view students results

student
view assignments

Fig 3.2.1.1Usecase diagram for whole system

10

Fig 3.2.1.2: Usecase diagram for Faculty module

11

Login

Student

Assignment

Attendance

Fig 3.2.1.3: Usecase diagram for Student module

12

Admin

Login

Head Of
Department(HOD)

Month Records

Attendance

Fig 3.2.1.4:Usecase diagram for HOD module

13

Admin

student

student results

admin
faculty
semister wise results

HOD

Fig 3.2.1.5: Usecase diagram for results module

14

3.2.2. Class Diagrams

Admin
Faculty

+id: char
+name: char
+password: char

+id: char
+name: char
+password: char
+phno: integer

adds

+login()
+addNewFaculty()
+modifyFaculty()
+addNewStudent()
+modifyStudent()
+addNewSubject()
+modifySubject()
+handlesResults()

allocates

Assignmets
+id: char
+name: char

+viewStudentsAttendance()
+updatesAttendance()
+allocatesAssignments()
+viewResults()

updates attendance and view records

adds
handles
view

Subjects

Students

+id: char
+name: char
+classId: char
+displaySubjects()

+id: char
+name: char
+password: char

Results
+stuId: char
+stuName: char
+sem: char

view

+viewResults()
+viewAssignments()

view

+displayResults()

Fig 3.2.2.1 Class diagram for Whole System

15

HOD
view records

+id: char
+name: char
+password: char
+viewAttendance()
+viewResults()

Fig 3.2.2.2: Class diagram for Faculty module

16

Fig 3.2.2.3: Class diagram for student module

HOD Login
username : String
password : String
addHod()
getUsername()
getPassword()

Monthly Records
month : String

AttendancePercentage
studentrollnum : Integer

getMonthRecords()

getPercentage()

Fig 3.2.2.4: Class diagram for HOD module

17

StudentResults
+roll num: int
+getDetails()

StudentDetails

GetResults

+roll num: int

+name: varchar

+roll num: int

+marks: int

+getStudentInfo()

+getData()

Semister1

semister2

semister3

+roll num: int

+roll num: int

+roll num: int

+sem1Marks()

+sem2Marks()

+sem3Marks()

Fig 3.2.2.5: Class diagram for results module

18

3.2.3 Sequence Diagrams

Admin

Database

Faculty

students

HOD

results

1 : stores uname and passwords()

2 : updates attendance()

3 : allocates assignments()
4 : checks assignments()

5 : checksAtendance()
7 : enterResults()

6 : checks attendance()

9 : view results()

Fig 3.2.3.1: Sequence diagram for whole system

19

8 : view results()

Fig 3.2.3.2: Sequence diagram for Faculty module

20

Login

: Student

Assignment

Attendance

Database

login
Verifying sudent login details
verified

view assignment

check for assignment

return assignment details

view attendance

search student attendance

return student attendance

Fig 3.2.3.3: Sequence diagram for Student module

21

: Admin

Login

Month Records

Attendence
percentage

: Head Of
Department(HOD)
login

verification
Verified

getMonthRecords
Check Records

Retrived Data

getAttendance

checkPercentage

retrived Percentage

Fig 3.2.3.4: Sequence diagram for HOD module

22

Database

: Admin

user

student details

data base

admin

1 : enters student results()

2 : enter student roll num()

3 : retrieve results()

4 : getData()
5 : provides data()
6 : displays results semister wise()

Fig 3.2.3.5: Sequence diagram for results module

23

3.2.4. Activity Diagrams

Admin

Database

Faculty

Student

HOD

updateAttendance
Login

Login

faculty

manages data
Data

addsubject

true

viewResults

viewAttendance
allocateAssignment
addfaculty

false
login

manageStudentRecors

invalidLogin
logout

Student

false

true

viewAttendece

viewResults

login
false

true

logout

viewAttendance

HOD

logout

Fig 3.2.4.1: Activity diagram for whole system

24

viewResults

Fig 3.2.4.2: Activity diagram for Faculty module

25

Fig 3.2.4.3: Activity diagram for Student module

26

Fig 3.2.4.4: Activity diagram for HOD module

27

user

student details

database

admin

student results

enter student id
invalid id

if valid id

retrieveStudentsData
enters students results

getResultsData

displays semister wise results

Fig 3.2.4.5: Activity diagram for results module

28

3.2.5. Component Diagrams

Admin

Database

Student
student
Faculty

Fig 3.2.5.1 Component diagram for Whole System

Fig 3.2.5.2 Component diagram for Faculty module

29

Fig 3.2.5.3 Component diagram for Student module

Fig 3.2.5.4 Component diagram for HOD module

30

admin

database

user

Fig 3.2.5.5 Component diagram for results module

31

3.2.6. Deployment Diagrams

Database

Admin

student

HOD

faculty

Fig 3.2.6.1 Deployment diagram for Whole System

Fig 3.2.6.2 Deployment diagram for Faculty module

32

Fig 3.2.6.3 Deployment diagram for Student module

Fig 3.2.6.4 Deployment diagram for HOD module

33

administrator

database

users

Fig 3.2.6.5 Deployment diagram for results module

34

4. Implementation

4.1 Modules:
The application has following modules
1. Admin module
2. Faculty module
3. Student module
4. HOD module
5. Results module

4.2 Modules Description

4.2.1 Admin module:

Admin has rights for creating any new entry and modifying faculty and student
details.
Admin allots the subject to particular staff.
provides user name and password to the staffs, students and HOD.
Responsible for maintaining and handling results.

//sample code
using System;
usingSystem.Collections.Generic;
usingSystem.ComponentModel;
usingSystem.Data;
usingSystem.Drawing;
usingSystem.Linq;
usingSystem.Text;
usingSystem.Windows.Forms;
35

usingSystem.Data.SqlClient;
usingSystem.Configuration;

namespace College
{
public partial class faculty_login : Form
{
publicfaculty_login()
{
InitializeComponent();
}

private void btn_login_Click(object sender, EventArgs e)

{
stringuid = textBox1.Text;
stringpwd = textBox2.Text;
SqlCommandcmd = new SqlCommand(string.Format("select *from faculty where
userid='{0}' and password='{1}'",uid,pwd),con);
SqlDataReaderdr = cmd.ExecuteReader();

if (dr.Read())
{
if (textBox1.Text == "faculty1"&& textBox2.Text == "faculty1")
{

36

faculty_homefh = new faculty_home();

fh.Show();
this.Hide();
}
else if (textBox1.Text == "faculty2"&& textBox2.Text == "faculty2")
{
faculty2_homefh = new faculty2_home();
fh.Show();
this.Hide();
}
else if (textBox1.Text == "faculty3"&& textBox2.Text == "faculty3")
{
faculty3_homefh = new faculty3_home();
fh.Show();
this.Hide();
}
}
else
{
MessageBox.Show("Invalid userid and Password");
}
}

private void btn_cancel_Click(object sender, EventArgs e)

{
37

textBox1.Text = string.Empty;
textBox2.Text = string.Empty;
}
}
}

4.2.2

Faculty module:

Faculty can update the student attendance daily, where the updating privilege is only been
given to the faculty. And once the details of the students are updated for the day, it cant
be changed.
Faculty can also retrieve all the students attendance details for the day.
This module also includes a facility to retrieve attendance of all the students at the end of
each months attendance.
A final record for the entire semester can be viewed by retrieving all the attendance
information from the starting of the semester.
In this module, faculty can also assign work to students, by allocating the assignment
number for a particular student for a specified date.
//sample code
namespace College
{
public partial class faculty_home : Form
{
publicfaculty_home()
{
InitializeComponent();
}

private void label2_Click(object sender, EventArgs e)

38

private void button5_Click(object sender, EventArgs e)

{
CLASS1_UPDATE ur = new CLASS1_UPDATE();
ur.Show();
this.Hide();
}

private void button2_Click(object sender, EventArgs e)

{
get_day_records gr = new get_day_records();
gr.Show();
this.Hide();
}

private void button1_Click(object sender, EventArgs e)

{
get_student_recordsgs = new get_student_records();
gs.Show();
this.Hide();
}

39

private void button3_Click(object sender, EventArgs e)

{
get_month_recordsgm = new get_month_records();
gm.Show();
this.Hide();
}

private void button6_Click(object sender, EventArgs e)

{
assigmnments a =new assigmnments();
a.Show();
this.Hide();
}

private void pictureBox2_Click(object sender, EventArgs e)

{
Form1 f1 = new Form1();
f1.Show();
this.Hide();
}

private void pictureBox1_Click(object sender, EventArgs e)

{

Form1 f1 = new Form1();

40

f1.Show();
this.Hide();
}

private void button4_Click(object sender, EventArgs e)

{
finalrecords f = new finalrecords();
f.Show();
this.Hide();
}
}

4.2.3

Student Module:

In this module, student can check the details of the assignment which will be assigned by
their respective faculty members.
Student can check the attendance details of his/her alone. Where a daily updated
attendance by the faculty can be viewed and also at the end of the month, percentage of
all the classes present can also be viewed.
//sample code
using System;
usingSystem.Collections.Generic;
usingSystem.ComponentModel;
usingSystem.Data;
usingSystem.Drawing;
usingSystem.Linq;
usingSystem.Text;
usingSystem.Windows.Forms;
41

usingSystem.Data.SqlClient;
usingSystem.Configuration;

namespace College
{
public partial class std_home : Form
{
publicstd_home(string name)
{
InitializeComponent();
label2.Text = name;
}

private void std_home_Load(object sender, EventArgs e)

{
string name = label2.Text;
// MessageBox.Show(date);
SqlConnection
con=newSqlConnection(ConfigurationManager.ConnectionStrings["con"].ToString());
con.Open();
SqlCommandcmd = new SqlCommand(string.Format("select sid,assignment,date from
assignment where sname='{0}'",name), con);
SqlDataReaderdr = cmd.ExecuteReader();
DataTabledt = new DataTable();
dt.Load(dr);
dataGridView1.DataSource = dt;
42

private void button2_Click(object sender, EventArgs e)

{
Form1 f1 = new Form1();
f1.Show();
this.Hide();
}

private void linkLabel1_LinkClicked(object sender, LinkLabelLinkClickedEventArgs e)

{
getassign g = new getassign();
g.Show();
this.Hide();
}
}
}

4.2.4

Head Of The Department Module:

Head of the department can get a consolidated attendance records of all the students of
the branch at the end of each month, where details of the students is also mentioned.
HOD can also check the total number of classes which were attended by the students
along with the total percentage of the attendance which student has got, for the end of
each semester.
//sample code
namespace College
43

{
public partial class hodhome : Form
{
publichodhome()
{
InitializeComponent();
}

private void button4_Click(object sender, EventArgs e)

{
Form1 f1 = new Form1();
f1.Show();
this.Hide();
}

private void button3_Click(object sender, EventArgs e)

{
hod_monthly h = new hod_monthly();
h.Show();
this.Hide();
}

private void button2_Click(object sender, EventArgs e)

{
attendencepercentagehod a = new attendencepercentagehod();
44

a.Show();
this.Hide();
}
.
4.2.5

Students result module

This modules provides the students to check their results given the roll number of the
student, where all the previous semester marks along with the recently completed
semester will be provided in a chronological order.
//sample code
private void grid2()
{
intrno = int.Parse(textBox1.Text);
SqlConnection
con=new
SqlConnection(ConfigurationManager.ConnectionStrings["con"].ToString());
SqlDataAdapter da = new SqlDataAdapter(string.Format("select sub1internal as
WSInternal,sub1external as WSExternal,sub2internal as ASNInternal,sub2external as
ASNExternal,sub3internal as
MSInternal,sub3external
as
MSExternal,sub1internal+sub2internal+sub3internal+sub1external+sub2external+sub3ex
ternal as Total from marks2 where studid={0} and semister='semister2'", rno), con);
DataSet ds = new DataSet();
da.Fill(ds);
dataGridView2.DataSource = ds.Tables[0];

}
private void getdata()
{
intrno = int.Parse(textBox1.Text);

45

SqlConnectioncon=new
SqlConnection(ConfigurationManager.ConnectionStrings["con"].ToString());
SqlDataAdapter da = new SqlDataAdapter(string.Format("select *from marks where
studid={0}", rno), con);
DataSet ds = new DataSet();
da.Fill(ds);
textBox2.Text = ds.Tables[0].Rows[0][1].ToString();
textBox3.Text = ds.Tables[0].Rows[0][0].ToString();

46

5.Testing

5.1 Purpose
The purpose of testing is to assess product quality. It helps to strengthen and stabilize the architecture
early in the development cycle. We can verify through testing, the various interactions , integration of
components and the requirements which were implemented. It provides timely feedback to resolve the
quality issues, in a timely and cost effective manner.

5.2 Test Cases

For HOD Login

Test

Input

Expected
Behaviour/Result

Actual Behaviour

Result

Valid login

User id, password

Login success

Login success

Test passed!

Invalid login

Incorrect
username and
password

Login failed

Login failed

Test passed!
Invalid user id
and password

Fig 5.2.1: Test Case Table For HOD Login

47

Fig 5.2.2: HOD Login Successful

48

Fig 5.2.3: HOD Login failed because of invalid user id and password

49

For Faculty Login

Test

Input

Expected
Behaviour/Result

Actual Behaviour

Result

Valid login

User id, password

Login success

Login success

Test passed!

Invalid login

Incorrect
username and
password

Login failed

Login failed

Test passed!
Invalid user id
and password

Fig 5.2.4: Test Case for faculty login page

50

Fig 5.2.5: faculty login successful

51

Fig 5.2.6: faculty login failed

52

For Student Login

Test

Input

Expected
Behaviour/Result

Actual Behaviour

Result

Valid login

User id, password

Login success

Login success

Test passed!

Invalid login

Incorrect
username and
password

Login failed

Login failed

Test passed!
Invalid user id
and password

Fig 5.2.7: test case for student login page

53

Fig 5.2.8: Student login successful

54

Fig 5.2.9: student login failed

55

For Update Records

Test

Input

Expected Result

Actual Behaviour

Result

Updating Record
successfully

Roll number

Displaying name
and attendance of
the student
correctly

Displaying name
and attendance of
the student
correctly

Record updated
successfully

Updating Record

No Roll
number/invalid
roll number

Doesnt display
anything/ invalid
roll number

Doesnt display
anything/invalid
roll number

Did not update

any record

Failed

Fig5.2.10: test case for update students records

56

Fig 5.2.11: record updated successfully

57

Fig 5.2.12: failed record up dation

58

Fig 5.2.13: record already updated

59

For Students Attendance Percentage

Test

Input

Expected Result

Actual Behaviour

Result

To get students
attendance
percentage

Roll number

Displaying the
total working
classes and total
present classes
along with the
attendance
percentage

Displaying the
total working
classes and total
present classes
along with the
attendance
percentage

Displays
attendance
percentage of the
students

To get students
attendance
percentage

No Roll
number/invalid
roll number

Displaying zero
number of total
working classes
and zero number
of total present
classes along with
NaN attendance
percentage

Displaying zero
number of total
working classes
and zero number
of total present
classes along with
NaN attendance
percentage

Doesnt display
any percentage

Fig5.2.11: test case for students attendance percentage

60

Fig 5.2.14:attendance percentage

61

Fig 5.2.15:attendance percentage when an invalid roll number is given.

62

5.3.Outputs

Fig 5.3.1: home page of the application

63

Fig 5.3.2: login page for the head of the department

64

Fig 5.3.3: HOD login page with correct username and password

65

Fig 5.3.4: HOD home page

66

Fig 5.3.5: Monthly records of class 1 page

67

Fig 5.3.6: list of students monthly details of class1

68

Fig 5.3.7: list of students monthly details of class

69

Fig 5.3.8: attendance details of all students of all the classes

70

Fig 5.3.9: login page of the faculty

71

Fig 5.3.10: login details of the faculty login page

72

Fig 5.3.11: list of classes taken for different years by faculty1

73

Fig 5.3.12: faculty home page

74

Fig 5.3.13: page to get the details of all the students attendance records for the day.

75

Fig 5.3.14: Get Students Records page with fields of roll number and date to be entered

76

Fig 5.3.15: details of the student for the GET Students Record page

77

Fig 5.3.16: Get Day Records page for class1

78

Fig 5.3.17: list of students attendance for the day of class1

79

Fig 5.3.18: Get Monthly Records page

80

Fig 5.3.19: Students total attendance percentage of all the classes present

81

Fig 5.3.20: given a roll number, we get the student attendance percentage of all the classes.

82

Fig 5.3.21: update class1 records page

83

Fig 5.3. 22: update class1 records page with the details of the student status to be updated

84

Fig 5.3.23: records when successfully updated

85

Fig 5.3.24: assignment allocation page by faculty

86

Fig 5.3.25: list of students roll numbers to whom assignment is to be allocated

87

Fig 5.3.26: list of assignments to be allocated for different students

88

Fig 5.3.27: page with successfully allocation of assignments

89

Fig 5.3.28: page with list of assignments

90

Fig 5.3.29: examination results page

91

Fig5.3.30 : examination results page with the details of the students marks

92

Fig 5.3.31: student login page

93

Fig 5.3.32: student login page with student details

94

Fig 5.3.33: student home page

95

Fig 5.3.34: list of assignments where the student can view

96

Fig 5.3.35: student viewing his attendance

97

Moodle screenshots:

98

99

100

Fig 5.3.36: moodle pictures

101

Conclusion
This project is successfully implemented with all major features mentioned in the Software
Requirement Specification. The application was tested and found to execute successfully.
This application helps the college management system to work in more flexible and efficient way
by maintaining and updating attendance, allocating assignments to students without manually
giving them, and assignments which allocated are distinct to each and every student. Viewing
results of the student module has been improved in the system.

102

Future Enhancements
Discontinue of particular student eliminate potential attendance.
Bar code Reader based attendance system.
Individual Attendance system with photo using Student login.
Integrating this application with moodle.

103

References
Books References
[1] Introducing Microsoft .NET, Second Edition author David S. Platt.
[2] Joe Mayo, Microsoft Visual Studio 2010: A Beginner's Guide, Tata McGraw Hill, 2010.
[3] Alex Mackey, Introducing .NET 4.0: With Visual Studio 2010, Press, USA, 2010.

Websites
1. http://www.w3schools.com/asp.net/
2. http://www.cramerz.com/aspdotnet
3. http://www.dotnetspider.net/
4. http://www.stackoverflow.com
5. .http://www.moodle.org

104