SCHOOL ATTENDANCE MANAGEMENT SYSTEM

SCHOOL ATTENDANCE MANAGEMENT

SYSTEM

FARAH SYAHIRAH BINTI ROSLI

BACHELOR OF COMPUTER SCIENCE

(INTERNET COMPUTING)

UNIVERSITI SULTAN ZAINAL ABIDIN

2018

SCHOOL ATTENDANCE MANAGEMENT SYSTEM (SAMS)

FARAH SYAHIRAH BINTI ROSLI

Bachelor of Computer Science (Internet Computing)

Faculty of Informatics and Computing

Universiti Sultan Zainal Abidin, Terengganu, Malaysia

August 2018

i

DECLARATION

I hereby declare that the work in this thesis is my own efforts and ideas with

helps getting information from resources that I have confessing, except for quotations

and summaries from the other’s work which have been appropriately acknowledge. I

also declare that it has not been submitted by any degree in Universiti Sultan Zainal

Abidin or other institutions.

________________________________

Name : Farah Syahirah binti Rosli

Date : ..................................................

ii

CONFIRMATION

I have confirmed that I have read this report and in my point of view, this project

fulfils a condition to be awarded a Bachelor of Computer Science (Internet

Computing).

.

________________________________

Name : Mat Atar bin Mat Amin

Date : ..................................................

iii

ACKNOWLEGMENT

In the Name of Allah, The Most Gracious and The Most Merciful, the School

Attendance Management System for subject CSB35102 which is final year project is

able to develop. I would like to express my profound gratitude and deep regards to

several important person that directly and indirectly involve with this process. Firstly,

I would like to thanks Encik Mat Atar bin Mat Amin as my supervisor for this project

for guidance, monitoring and constant encouragement throughout the course of this

final year project. I want to take this opportunity to thank my parent and also special

thanks to all lectures of Faculty Informatics and Computing for their attention,

guidance, and advice to help and support that encourages me to finish up my project.

May Allah S.W.T bless all the effort that has been taken to finish this project.

iv

ABSTRACT

Nowadays, manual class attendance still use and sometimes when teachers are

too busy they always forget to bring it. This system will develop to ease every teacher

to take their class attendance without using pen and paper. There have several

objective of this project. First of the objective is to design a management school

attendance system that can make via online. Second is to implement the mobile

computing in the system and the lastly is to develop the functional of the system in

helping the user to manage the class attendance.

For this project mobile computing is the one of technique that use in this

project to develop this system being mobile application. There has technical

challenges that mobile computing must surmount to achieve its potential are hardly

trivial. The issues to be dealt with stem from essential properties of mobile computing.

v

ABSTRAK

Pada masa kini, sistem kehadiran masih menggunakan secara manual dan

kadang kala guru terlalu sibuk lalu guru lupa untuk membawa buku kehadiran

tersebut. Oleh itu, sisem ini akan dibangunkan untuk memudahkan pengurusan

kehadiran bagi setiap guru kelas tanpa membuat secara manual lagi. Di samping itu,

projek ini mempunyai beberapa objektif untuk dicapaikan untuk membuat sistem ini

berjalan dengan baik. Antara objektifnya adalah untuk membentuk satu sistem

kehadiran sekolah yang boleh digunakan secara rangkaian internet. Seterusnya,

adalah untuk melaksanakan pengkomputeran mudah alih dalam sistem dan juga untuk

membangunkan fungsi yang berjaya dalam sistem untuk membantu pengguna

megurus kehadiran tersebut dengan mudah dan lancer.

Untuk pengkomputeran projek ini adalah salah satu teknik yang digunakan

dalam projek ini untuk membangunkan satu sistem yang menjadi aplikasi mudah alih.

Tambahan pula, terdapat cabaran teknikal yang membolehkan pengkomputeran

mudah alih untuk mencapai potensinya. Isu-isu ini perlu ditangani dengan ciri-ciri

penting pengkomputeran mudah alih.

vi

CONTENTS

PAGE

DECLARATION i

CONFIRMATION ii

ACKNOWLEGDEMENT iii

ABSTRACT iv

ABSTRAK v

CONTENTS vi

LIST OF TABLES ix

LIST OF FIGURES x

CHAPTER I INTRODUCTION

1.1 Project Background 1

1.2 Problem statement 3

1.3 Objectives 3

1.4

1.5

Scopes

1.4.1 Admin

1.4.2 Teacher

1.4.3 Student

Limitation of work

4

4

4

4

5

1.6 Activities and milestones 6

CHAPTER II LITERATURE REVIEW

2.1

2.2

2.3

Introduction

Android system and Mobile computing

Category of system

8

8

9

2.4 Research / Analysis 9

2.5

2.6

Research Comparison

Summary

12

14

vii

CHAPTER III

METHODOLOGY

3.1 Introduction 15

3.2 Research paradigm and justification 15

3.3 System development Methodology 17

3.3.1 Analysis phase 17

3.3.2 Design phase

3.3.3 Implementation phase

3.3.4 Testing phase

3.3.5 Development phase

17

17

18

18

3.4

3.5

3.6

System framework

Context diagram

Data flow diagram

19

20

21

3.6.1 Data flow diagram level 0 21

3.6.2 Data flow diagram level 1 23

3.6.2.1 Admin 23

3.6.2.2 Teacher

3.6.2.2 Student

24

26

3.7 Entity relationship 26

3.8 Proof of concept 28

3.9 Software Requirement 28

3.10 Summary 29

CHAPTER IV IMPLEMENTATION

4.1 Introduction 30

4.2 Screenshot of interfaces 30

4.2.1 Admin site 32

viii

4.2.2 Teacher Site

4.2.3 Student Site

36

39

4.3 Test case 39

4.4 Summary 45

CHAPTER V CONCLUSION

5.1 Discussion 46

5.2 Result discussion 46

5.3 Project constraint 47

5.4

5.5

Future work

Conclusion

47

47

REFERENCES 49

ix

LIST OF TABLES

TABLE TITLE PAGE

1.1 Activities and milestone (FYP1) 6

1.2 Activities and milestone (FYP2) 7

2.1 Research Comparison 12

3.1

3.2

4.1

4.2

4.3

4.4

4.5

4.6

4.7

4.8

4.9

4.10

4.11

4.12

Software Requirement

Tools requirement

Test case success & fail login (Admin)

Test case success teacher login

Test case success student login

Test case of register teacher

Test case of add and delete student

Test case of add and edit class

Test case view teacher profile (Admin)

Test case view class (Teacher)

Test case of update profile teacher (Teacher)

Test case of attendance (Teacher)

Test case of report (Teacher)

Test case of class enrol (Student)

28

29

40

40

41

41

42

42

43

43

43

44

44

45

x

LIST OF FIGURES

FIGURE TITLE PAGE

3.1 Waterfall diagram 16

3.2 Framework diagram 19

3.3 Context diagram 20

3.4

3.5

3.6

3.7

3.8

3.9

3.10

3.11

3.12

3.13

4.1

4.2

4.3

4.4

4.5

4.6

4.7

4.8

4.9

4.10

4.11

4.12

4.13

Data flow diagram level 0

Data flow diagram level 1 (Teacher)

Data flow diagram level 1 (Class)

Data flow diagram level 1 (Report)

Data flow diagram level 1 (Teacher)

Data flow diagram level 1 (Student)

Data flow diagram level 1 (Attendance)

Data flow diagram level 1 (Report)

Data flow diagram level 1 (Enroll)

Entity relationship diagram

Login attendance

Register form

Homepage and welcome page

List of class (Admin)

Student login list

List of teacher (View)

List of teacher (Delete)

List of class (Teacher)

List student in each class (Attendance)

List of class before view each class

List of student absence of each class

Report

Class enroll

22

23

23

24

24

25

25

25

26

27

31

31

32

33

34

35

35

36

37

37

38

38

39

1

CHAPTER I

INTRODUCTION

1.1 Project Background

School attendance is a list of name in every class that use for all teachers to

take their student attendance in every days. This is to help teachers to enter the

attendance of student. However, in school now is lack of new technology by using in

online attendance system.

School Attendance Management System is a mobile computing system that can be

used in order to gain the data of student attendance in school. The system will be able

to store list of student name in systematic and collect the number of attendance for

each student. This new system will replace the old approach the attendance

management and increase efficiency of work done using an appropriate tools and

technique. This system must conduct all the basic function likes add name of student

and collect number of attendance.

2

Finally, the system provide high ability to store student name into database so

it will stored in a more organized manner. The system can be helpful to the teacher

using the keyboard without using the paper and pen to write the names of student

and it will help out the management in managing the work.

3

1.2 Problem Statement

Mostly management attendance is done manually, where all data is collected using

paper and it being kept in the register book. This approaches cause a lot of

problem to the teachers to handle the student data manually. Besides that, in a

manual system will be also take times for teacher to write back all name of student in

their register book. The data also been some duplicate when done manually.

In addition, teacher also have a problem by searching the data of the attendance

based on the specific such as searching the student name in specific date. This

approach is no effective and systematic in handling the process of manage record of

the attendance. This system will become more easily and systematically for teacher

using in technology.

1.3 Objectives

Generally, the objective to develop the new system is to replace the manually

management system for school attendance, which not efficient to be used in

today’s environment. For the main objectives of this project have been identified

as follows:

a) To design a management school attendance system that can make via online.

b) To implement the mobile computing in the system.

c) To develop the functional of the system in helping the user to manage the class

attendance.

4

1.4 Scopes

The scopes for this project are identified to make the system development

process easier. The scope is divided into two which are the system scope and user

scope.

1.1.1 Admin

Login module.

Register student.

Can manage create, retrieve, update and delete (CRUD) teacher and

data.

View report

1.1.2 User Scope

Teacher

Login module

Register

Able to check student attendance

Able to edit profile teacher

Manage report

Student

Login module

Able to enroll

5

1.5 Limitation of work

The limitation of this system is only for take an absence student attendance.

The report will view by the attendance that teacher click for absence only.

6

1.5 Activities and milestones

ACTIVITY (FYP 1)

WEEK

1 2 3 4 5 6 7 8 9 1

0

1

1

1

2

1

3

1

4

1

5

1

6

Topic Discussion and

Determination

Project Title Proposal

Introduction

Literature Review

Methodology

Draft of Report

Submit Draft of

Report

Presentation

Final Report

Table 1.1 Activities and Milestones (FYP 1)

7

ACTIVITY (FYP 2) WEEK

1 2 3 4 5 6 7 8

Project Meeting with

Supervisor

Project Development

Project Development

(Continues)

Project Testing

Project Testing

(Continues)

Submit Draft of

Report

Final Presentation

Final Report FYP2

Table 1.2 Activities and Milestones (FYP 2)

8

CHAPTER II

LITERATURE REVIEW

2.1 Introduction

Literature review is a part of a process of reading, analyzing, evaluating and

summarizing scholarly material about a specific topic. This is use as a guideline to

develop a new system. Therefore, the new system can provider better system and

more functional from other system. In addition, it also including the existing system

and comparison the current system with new system to overcome the weakness of the

system.

2.2 Android system and Mobile computing

Android is a software stack for mobile devices that includes an operating system,

middleware and key applications. Besides that, an android ships with a set of core

applications including an e-mail client, SMS program, calendar, maps, browser,

contacts, and other features. All applications are written using the Java programming

language. The application architecture is designed to simplify the reuse of

components, the capabilities of any application can be published and then be made use

of by any other application (subject to security constraints enforced by the

framework). This same mechanism allows components to be replaced by the user.

9

Mobile computing is one technique that this system will use. The technical


trivial. Some of the challenges in designing software for mobile computing systems

are quite different from those involved in the design of software for today's stationary

networked systems. The many issues to be dealt with stem from three essential

properties of mobile computing: communication, mobility, and portability. Of course,

special-purpose systems may avoid some design pressures by doing without certain

desirable properties. For instance portability would be less of a concern for mobile

computers installed in the dashboards of cars than with hand-held mobile computers.

2.3 Category of System

The category of this system is education. The increased use of technology in

today's schools has created new possibilities for teachers and their students. Rather

than limiting the use of technology based on student ability, it is now possible for

teachers to develop integrated multi-literacy lessons. Technology in the form of apps

for iPads, iPods, and desktop computers enable teachers to achieve this goal.

2.4 Research / Analysis

There are several research that related to the topic of the system that will be develop.

Some of them have the same purpose but there are use different technique.

First research is review by Saptorshi Bhattacharjee et al., 2016. The title of the

research is Attendance Management System an Android Application. The system is an

android based application and the application is compatible with all Android

minimum version from 4.2 Jelly Bean. The language that use for developed using

10

Extensible Markup Language (XML) and Java. For the database connectivity they are

use SQLite database because it is capable of handling and managing various queries,

cursors and more.

Second research is review by Saurabh Kumar Jain et al., 2015. The title of the

research is Attendance Management System. The system is a software developed for

daily student attendance in the school. This system will also help in evaluating

attendance eligibility criteria of the student. This project is developed as a desktop

application.

Third research is review by Abdullah et al., 2015. The title of the research is

Student Attendance Management System deals with the maintenance of student's

attendance details. It generates the attendance of the student on basis of presence in

class. It is maintained on the daily basis of their attendance. The staff will be provided

with the separate username & password to prepare the student's status. The staff

handling the particular subject in responsible to mark the attendance for all students.

Only if the student is present on that particular period, then the attendance will be

calculated. The students attendance reports on weekly and consolidate basis will be

generated.

Fourth research is review by Masalha et al., 2014. The Title of the research is

A Student Attendance System Using QR Code. The system lies between online

learning and traditional learning as a facilitation for the attendance record-keeping

process, in a way that enriches the lecture time so that it can better be utilized in

giving useful materials rather than wasting the time taking attendance. The system

11

requires a simple login process by the class instructor through its Server Module to

generate an encrypted QR code with specific information. This can be done at any

time before the class.

Last research is review by Shaik Muhammad Zahir bin Mohamed Farook

(2011) of EDUEASY Attendance System. The objective of this system is to analyst

the student attendance pattern and will produce a statistical table base on their daily

attendance data. In addition, it also will automatically generate a warning letter to any

student that skip school if they reach a certain limit.

12

2.5 Research Comparison

Title Year Compare

Attendance Management

System an Android

Application

2016 The only requirement is an android

smartphone with minimum version 4.2

jelly Bean. There not have any features

like sending warning messages to the

student with low attendance.

Attendance Management

System

2016 This system is dev eloped as desktop

application only. It is basis of subject

and month. It also not user friendly

because the retrieval of the data is very

slow and the data is not maintained

efficiently.

Student Attendance

Management System

2015 The proposed system provides a

solution to lecture attendance problems

by developing a web-based student

absence database to facilitate managing

student's absence. By using this system,

absence of students can be entered by a

responsible person or lecturer remotely.

Every student can view his/her absence

information using a search page that is

Table 2.1 Research Comparison

13

provided in the site. Also useful reports

regarding absences can be generated.

A Student Attendance

System Using QR Code

2014 The attendance solutions are based on a

QR code, which is being displayed for

students during or at the beginning of

each lecture. The students will need to

scan the code in order to confirm their

attendance.

EDUEASY Attendance

System

2011 This system uses Waterfall Model as its

software development methodology.

This system are develop four class,

administration, teacher, student

management and co-curriculum’s and

attendance management. It just use in

web browser.

14

2.6 Summary

Based on all research above, the system is only specific only for android in

version jelly Bean and majority of the system can use in web-based only. Now,

technology widespread, not only can use in specific version and web-based. For this

project it will upgrade. This system can use for all version in mobile application not

based on specific version only. It easily and systematic can use using smart phone.

15

CHAPTER III

METHODOLOGY

3.1 Introduction

The use of methodology to solve the problem and ensure the project are

working well and complete within the given time. They are many type of

methodology such as Waterfall, Critical Chain, Agile, Rapid Application

Development (RAD) and others. This chapter must be choose methodology that it is

suitable for development of the system to guide the researcher to manage the given

task. Conceptual data modelling is the representation of available data in organization

and it will displays the overall of the available in the organization.

3.2 Research Paradigm and Justification.

The waterfall model is a software development process. It emphasize the logical

progression of steps be taken throughout the software development life cycle (SDLC).

The phases consist of analysis, basic design, implementation, testing and maintenance.

The reason this model is choose because it suitable for the time was given to complete

this project in this semesters.

16

Waterfall model has been choose based on the following:

i. Project Monitoring

- Each phase of the development is monitored by time to time for ensure that

module of the system is match in system requirement.

ii. Allows design changes

- Any changes in developing the system can be implement at every phases to

improve the system.

ANALYSIS

IMPLEMENTATION

TESTING

DESIGN

MAINTENANCE

Figure 3.1 Waterfall Diagram

17

iii. Testing is made easy

- Test scenarios are already detailed in the functional specification of the

requirements phase, which makes the testing process easier and more

transparent.

3.3 System Development Methodology

This methodology is adaptable to time given for complete the task. Every

phase must fulfil requirement specification.

3.3.1 Analysis Phase

The title of has been agreed to proceed is School Attendance Management

System. It has been decided this project with supervisor. In addition, this system will

develop for admin and teacher to do an online school attendance.

3.3.2 Design Phase

This design phases will contains Context Diagram, Data Flow Diagram

(DFD) Level 0 and Level 1, and sketching of the interface an Entity Relationship

Diagrams (ERD). All of the phase is the guide for user to understand how the system

will be functioning and the database of the system also will develop at this phase.

3.3.3 Implementation Phase

This system will be develop using PHP programming and MYSQL to

running the database of the system. The implementation of XAMPP is used for local

host server.

18

3.3.4 Testing Phase

This part is tested by using testing to test the single module of the system.

Besides, the system testing will detect and report issues within the application that

need to be resolved. It is not uncommon for this phase to cause a necessary repeat of

the previous coding phase, in order for revealed bugs to be properly squashed.

3.3.5 Maintenance Phase

This is a final phase, so the system is ready to release and user can use the

system. After the system is in steady state, it will achieve all the goals, requirement

and the objective for this project.

19

3.4 System Framework

TEACHER

INTERFACE SCHOOL ATTENDANCE MANAGEMENT SYSTEM

LOGIN

MANAGE ATTENDANCE

MANAGE REPORT

CRUD

INTERFACE SCHOOL ATTENDANCE MANAGEMENT SYSTEM

ADMIN LOGIN

MANAGE CLASS

EDIT PROFILE

VIEW REPORT

VIEW TOTAL ATTENDANCE

TOTAL ATTENDANCE

STUDENT

ENROLL CLASS

MANAGE TEACHER

MANAGE STUDENT

Figure 3.2 System Framework

20

Based on figure 3.2 show that the framework of the developed system. The entity for

the teacher that involve have to register into the system. Teacher will manage the

detail of the student and also the attendance. Besides that, teacher also can generate

the report for the end of the attendance.

3.5 Context Diagram

Context diagram is a diagram that defines the boundary between the system and

showing the entities that interact with it. This diagram is an overview of the system

process and functioning. The context diagram for School Attendance Management

System

Figure 3.3 Context Diagram

21

3.6 Data Flow Diagram

3.6.1 Data flow diagram level 0

Data flow diagram is a graphical representation of the flow and the process

data through an information system. It is how the system environment entities,

processes and the data interconnected to the stored in the database. In addition, it show

what kind of information will be input and output from the system and where the data

will come and stored.

22

Figure 3.4 Data Flow Diagram Level 0

23

3.6.2 Data flow diagram level 1

3.6.2.1 Admin

Diagrams 3.5, 3.6 and 3.7 show the DFD level 1 of admin. In DFD level 1, the

process in manage teacher (3.0) is divided into two sub process, which is view teacher

(3.2) and delete teacher (3.3). In addition, the process in manage class (5.0), and also

manage report (8.0) only has one process which is add class (5.1), and view report

(8.2).

Figure 3.5.Data Flow Diagram Level 1 (Teacher)

Figure 3.6 Data Flow Diagram Level 1 (Class)

24

3.6.2.1 Teacher

Diagrams 3.8, 3.8, 3.10 and 3.11 show the DFD level 1 of teacher. In DFD

level 1, the process in manage teacher (3.0) is divided into two sub process, which is

edit profile (3.1) and view profile (3.2). In addition, the process in manage student

(4.0) has two process, there are delete student (4.2) and view student (4.3). Besides

that, the process in manage attendance (6.0) and also manage report (8.0) only has 2

sub process. For manage attendance, there are edit attendance (6.1) and view

attendance (6.2) and manage report are edit report (8.1) and view report (8.2).

Figure 3.7 Data Flow Diagram Level 1 (Report)

Figure 3.8 Data Flow Diagram Level 1 (Teacher)

25

Figure 3.9 Data Flow Diagram Level 1 (Student)

Figure 3.10 Data Flow Diagram Level 1 (Attendance)

Figure 3.11 Data Flow Diagram Level 1 (Report)

26

3.6.2.1 Student

Diagram 3.12 show the DFD level 1 of student. In DFD level 1, the process in

manage student (4.0), student can enroll themselves for add them to the list of student,

which is enroll student (4.1).

3.7 Entity Relationship Diagram

Entity relationship diagram is a data diagram that show the how the data is

connected each other. It is to generate the relationship between the entity and the

attributes.

Figure 3.12 Data Flow Diagram Level 1 (Enroll)

27

Figure 3.13 Entity Relationship Diagram

28

3.7 Proof of concept

Mobile computing is one technique that this system will use. The technical


trivial. Some of the challenges in designing software for mobile computing systems

are quite different from those involved in the design of software for today's stationary

networked systems. The many issues to be dealt with stem from three essential

properties of mobile computing: communication, mobility, and portability. Of course,

special-purpose systems may avoid some design pressures by doing without certain

desirable properties. For instance portability would be less of a concern for mobile

computers installed in the dashboards of cars than with hand-held mobile computers.

3.8 Software Requirement

Below are the software and tools use throughout the software development

process.

No. Software Purpose

1. Notepad C++ Used to make the code program

2. XAMPP Server A local host to run and test applications

3. MySQL (Phpmyadmin) As database for the system

4. Google Chrome A browser to open the application and run the

local host

6. Microsoft Word 2010 Used to prepare documentation of the report

7. Snipping Tool Used to captured and screen shot the images

Table 3.1 Software requirement for system development

29

3.9 Summary

Methodology is important to development in the system to make sure the system

is in correct path during development. The methodology is used for guide to the next

step what the used should do. The most suitable methodology for this system is

Waterfall Model. Every phases act as a guide to make sure the objectives of this

system can be achieved. In this phase, the modules involve being describe as the data

flow is from one module to another module.

In addition, the modelling of the system has been diagrammatically

portrayed; the focus is on DFD, ERD and architecture as well as database

specification. Precisely, DFD and ERD are specifically done with data flow and data

to data relationship, while architecture and database specifications are more on the

components of the system such that tables in database are used to manage and store

data.

No. Hardware Description

1. Laptop LENOVO

2. Processor Intel(R) Core(TM) i3 CPU M380@ 2.53GHz

3. Memory 4.00 GB RAM

5. Operating System MS Windows 2010

6. System type 64-bit Operating System

Table 3.2 Tools requirement for system development

30

CHAPTER IV

IMPLEMENTATION

4.1 Introduction

In this chapter, coding is illustrate in the interface captured. The user guide is

provided to enable user make use of the system. All the interfaces of different user is

shown in this chapter.

4.2 Screenshot of interfaces

Interfaces is the point of interaction between human and system. The design of

an interface should be user friendly. Below are interfaces for School Attendance

Management System.

Figure 4.1 shows the interface of login form of School Attendance

Management System. The admin, teacher and student need to fill their Id and

Password to access the system. For student, admin will set the Id and password to

login but for teacher, teacher must register first in the register form in figure 4.2

before login. If the Id or password are wrong popup will display where the Id or

password is not valid.

31

Figure 4.1 Login Attendance

Figure 4.2 Register form

32

Figure 4.3 shows the interface of School Attendance Management System

(SAMS) homepage and welcome page. In this homepage, user can click for login or

teacher register and after login the first page will out is welcome page.

4.2.1 Admin site

Figure 4.4 show the interface for admin to add the class that have in the school

and admin also can edit the class if each class will change for the class teacher every

year.

Figure 4.3 Homepage and Welcome page

33

Figure 4.5 show the interface of student list where admin can add student Id

and password for student login before enroll the class. In addition, admin also can

delete the list of student if the student change the school or end school and the data of

the student will automatically delete from the database.

Figure 4.4 List of Class

34

Last figure for admin site is figure 4.6 and figure 4.7. This figure show list of

teacher where admin can also view delete the teacher profile same like list of student

interface.

Figure 4.5 List of Student

35

Figure 4.6 List of Teacher (View)

Figure 4.7 List of Teacher (Delete)

36

4.2.2 Teacher site

Figure 4.8 show the interface for teacher to choose which class to check the

attendance. The teacher not only can check for their own class but also for the other

class.

Figure 4.9 show that the interface for teacher to take the attendance of the

class. This list of attendance will came out based on student enroll by themselves.

Figure 4.8 List of Class

37

Figure 4.10 and figure 4.11 show that the interface for list of the absence for

each class.

Figure 4.9 List Student in each Class (Attendance)

Figure 4.10 List of Class before View Each Class

38

Figure 4.12 show that the interface for report attendance. For all student and

date. This report admin also can see the report.

Figure 4.11 List of Student Absence of each class

Figure 4.12 Report

39

4.2.1 Student site

Figure 4.13 show that the interface for student choose the class that student in.

Then, the popup will came out to tell that student already enroll that class and the

student cannot enroll for other class.

4.3 Test case

A test case is a set of conditions or variables under which a tester will

determine whether a system under test satisfies requirements or works correctly. The

process of developing test can also help find problems in the requirement or design of

an application. The test case below shows several process of the (SAMS) that have

been tested.

Figure 4.13 Class Enroll

40

4.3.1 Authentication for Admin, Teacher and Student

Step Procedure Expected Result Pass/Fail

1 Go to login page Preview page loaded Pass

2

Enter incorrect invalid Id or

password and login

Page will show an error

message

Pass

3

Enter correct details or valid and

login

Login successful

class list page display

Pass



2


password and login


message

Pass

3


login

Login successful

Class page display

Pass

Table 4.1 Test Case Success and Fail Admin Login

Table 4.2 Test Case Success Teacher Login

41



2


password and login


message

Pass

3


login

Login successful

class enroll page display

Pass

4.3.2 Register Teacher


1 Go to register page. Preview page loaded. Pass

2 Not enter any details in the form.


message to fill all the form.

Pass

3 Enter the details and submit.

Register successful

Log in page display.

Pass

Table 4.3 Test Case Success Student Login

Table 4.4 Test Case of Register Teacher

42

4.3.3 Add and Delete Student (Admin)


1 Click Student on menu.

Table of student and form will

show.

Pass

2

Enter the form of Id and password for

student and click ADD.

Page will successful added

details of the student and

retrieve in the table below the

form.

Pass

3 Click DELETE button of each details.

The details will delete from

the table.

Pass

4.3.4 Add and Edit Class (Admin)


1 Click Class on menu. Table and form will show. Pass

2

Enter the form of Class teacher and

choose class for class list and click

Add.

Page will successful added

details of the class and retrieve

in the table below the form.

Pass

3

Click EDIT to edit the details or

DELETE for delete the details

The details will retrieve in

form and successful edit or

delete.

Pass

Table 4.5 Test Case of Add and Delete Student

Table 4.6 Test Case of Add and Edit Class

43

4.3.5 View Teacher Profile (Admin)

4.3.5 View Class (Teacher)

4.3.6 Update Profile Teacher (Teacher)


1 Click Teacher on menu. Table of teacher list show. Pass

2

Click VIEW for each one teacher

profile.

Page will successful view the

details of a teacher

Pass


1 Click Class on menu. Table of class show. Pass

2 Click OPEN for each class

Page will successful view

class attendance details that

student enroll.

Pass


1 Click Profile on menu. Table of profile show. Pass

2

Click VIEW of own profile and click

UPDATE to update the profile.

Page will successful view and

profile successful update.

Pass

Table 4.7 Test Case View Teacher Profile (Admin)

Table 4.8 Test Case View Class (Teacher)

Table 4.9 Test Case of Update Profile Teacher (Teacher)

44

4.3.7 View (Teacher and Admin) and Add Attendance (Teacher)

4.3.7 View and Generate Report (Teacher)


1 Click Student List on menu. Attendance list show. Pass

2

Click checkbox of every name that

absent and click submit button

(Teacher)

Page will successful view to

another page based on the

name that click, attendance

successful view.

Pass

3 Can view attendance only Page will successful view Pass


1 Click Report on menu. Report show. Pass

2 View report and click submit

Page will successful view and

generate to PDF

Pass

Table 4.10 Test Case of Attendance

Table 4.11 Test Case of Report

45

4.3.7 View and Generate Report (Teacher)

4.4 Summary

As the conclusion of this chapter, the developer testing the system which many

error is identify and fixed to improve the functionality of the system. Every unit of the

system is running the testing phase so can correct the error immediately. The system

will be integrated and at this place integrated testing is done.


1 Click Class on menu. Table of class show. Pass

2 Click ENROLL button.

Page will show popup

message that the student

successful enroll and student

cannot enroll another class.

Pass

Table 4.12 Test Case of Class Enroll (Student)

46

CHAPTER V

RESULT AND CONCLUSION

5.1 Discussion

In this chapter, coding is illustrate in the interface captured. The user guide is

provided to enable user make use of the system. All the interfaces of different user is

shown in this chapter.

5.2 Result Discussion

This School Attendance Management System (SAMS) has been carried out and

follow all the objective that have been stated in Chapter 1. All the functional in this

project is successful develop such as CRUD in the system. It easily use for user to

manage the attendance. This system also have been implement as mobile application

by using cordova software to being the mobile computing. Therefore, the objective of

this project are successful follow.

47

5.3 Project Constraint

This School Attendance Management System (SAMS) have several problem.

The problems are:

i. The name of the student in attendance list will be redundant in the same date.

If teacher have wrong click on checkbox and it was at the same name, the

same student name will be save to the database.

ii. The report of the attendance cannot be generate to pdf directly. It only can

generate when it in web system on in application system.

5.4 Future Work

Although SAMS system is good for teacher based on their criteria preferences,

future work can be consider to enhance the system even more. The future work based

on below:

i. Report can be download directly through smart phone.

ii. Calculation of the total student based on each class in specific date.

iii. More accurate criteria taken based on attendance and suitable for

attendance system.

5.5 Conclusion

The conclusion of this project is this school attendance system is already

successful done by using application. The teacher will not use in manually anymore.

Besides that, this application is more easily use for collecting data and more

systematic compare to manually. The teacher also will not waste their time to rework

all the student data, student just register themselves for each class for their attendance.

48

This because technology nowadays is extremely widespread regardless of age limits.

Therefore, this system is not have any problem for students and teacher by using

technology.

49

REFERENCES

[1] Abdullah, H. A., Mohson, I. A., & Ali, E. S. M. (2015). Student Attendance

Management System. i-Manager's Journal on Information Technology, 4(2), 7.

[2] Bhattacharjee, S., Kundu, D., Raychaudhuri, S., & Chakraborty, P. (2016).

Attendance Management System an Android Application.

[3] Corkett, J., & Benevidesa, T. (2013). Apps for All: Education App

Integration. Procedia-Social and Behavioral Sciences, 84, 61-65.

[4] Forman, G. H., & Zahorjan, J. (1994). The challenges of mobile

computing. Computer, 27(4), 38-47.

[5] Minaei-Bidgoli, B., Kashy, D. A., Kortemeyer, G., & Punch, W. F. (2003,

November). Predicting student performance: an application of data mining

methods with an educational web-based system. In Frontiers in education,

2003. FIE 2003 33rd annual (Vol. 1, pp. T2A-13). IEEE.

[6] Masalha, F., & Hirzallah, N. (2014). A students attendance system using QR

code. International Journal of Advanced Computer Science and

Applications, 5(3), 75-79.

[7] Noor, S. A. M., Zaini, N., Latip, M. F. A., & Hamzah, N. (2015, December).

Android-based attendance management system. In Systems, Process and

Control (ICSPC), 2015 IEEE Conference on (pp. 118-122). IEEE.

[8] Patel, U. A., & Priya, S. (2014). Development of a student attendance

management system using rfid and face recognition: A review. International

Journal of Advance Research in Computer Science and Management Studies,

2(8), 109-119.

50

[9] Rogers, R., Lombardo, J., Mednieks, Z., & Meike, B. (2009). Android

application development: Programming with the Google SDK. O'Reilly

Media, Inc..

[10] Shaik Muhammad Zahir Bin Mohamed Farook (2011). Development

EDUEASY Attendance System in Web Browser.

[11] Von Konsky, B. R., Ivins, J., & Gribble, S. J. (2009). Lecture attendance and

web based lecture technologies: A comparison of student perceptions and

usage patterns. Australasian journal of educational technology, 25(4).

Documents

SCHOOL ATTENDANCE MANAGEMENT SYSTEM