6CS020 PROJECT AND PROFESSIONALISM WITH

COMPUTER SCIENCE ARTEFACT

PROJECT PROPOSAL
STUDENT ATTENDANCE MANAGEMENT SYSTEM FOR
SCHOOL/COLLEGE

Student Id: 1930143

Student Name: Bishal Baba Maka
University Email Address: B.B.Maka@wlv.ac.uk
B.Sc. (Hons) Computer Science
Supervisor: Er. Lokesh Gupta
Submitted date: 14th December 2019

0|PAGE
ABSTRACT

Student attendance management system deals with the maintenance of the

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
staffs will be provided with the separate username & password to make the
student’s status.

The staffs handling the particular subjects responsible to make the attendance for
all students. Only if the student present on that particular period, the attendance
will be calculated. The student’s attendance reports based on weekly and
consolidate will be generated.
Project Title: Student Attendance Management System

Statement:

The Student Attendance Management system will provide the needed

solution. The system consists of application files for the teachers, which are
installed on their android devices. The Attendance app will be used to mark the
attendance of the students and will also be used to generate reports of all the
students and thus will enable the faculty members to keep track of student’s
record. Rather than signing on the attendance sheets, the teacher will mark the
attendance by just a single click on his device.

Academic Question:

What are the most appropriate techniques, tools and technologies for
implementing a project management system and what needs to be done to
make such a system to make it robust, secure and resilient?

Above mentioned is the academic question asked in reference to them Student

Attendance Management System. This question tries to cover the tools,
methodology and processes used to develop and build the better application.

The proposal below contains answers in reference to the academic question. The
research for this proposal is based on the same academic question.

Aims and Objectives

Aims:

The aim of this proposal is to allow us to demonstrate our academic

and research capabilities. The aims of this proposal are:

• To research on development of Student attendance

management system.
• To research and add suitable features to Student attendance
management system.
• To implement the analyzing and notifying technology in the
system.
• To keep the system stable, robust and resilient
 Objectives:

• Develop an android application

• Research on necessity and appropriate features for the app
• Implement the required and necessary features to the app
• Implement the analyzing and notifying technology to the app
• Ensure the quality of the mobile application

Artefact (proposed) to be developed:

Artifact 1:

Android Application for Student Attendance Management System.

Artifact 2:

Used to generate weekly or monthly reports based on student’s

attendance.

Artifact 3:

System uses data of attendance to automatically generate reports

of low absentee and notify the staff.

This app will have the analyzing and notifying system so that the staffs can easily
be notified when student have low attendance. All the data of student’s attendance
will be stored on the staff’s mobile (excel, forms, etc…) which can later be
transferred in the school’s server. This

mobile app will be used by the academic department and will replace the

traditional and time-consuming way of taking attendance.

Literature Review

PROBLEM DOMAIN IN DETAIL

Monitoring attendance is a very important process in nearly every institution and
organization. The current method involves using paper sheets or books to assist
students. This method could easily permit impersonation and may cause loss or
damage to the attendance sheet. By using this traditional approach, attendance is
therefore time-consuming and therefore an automated and reliable system is
needed. (Akshay A. Kumbhar, 2014)

MY PROJECT AS SOLUTION
The Attendance monitoring system will provide the needed solution. The system
consists of application files for the teachers, which are installed on their android
devices. The Attendance app will be used to mark the attendance of the students
and will also be used to generate reports of all the students and thus will enable
the faculty members to keep track of student’s record. Rather than signing on the
attendance sheets, the teacher will mark the attendance by just a single click on
his device.
(BACKGROUND RESEARCH)

The Android software stack as shown in figure 1 can be subdivided into five layers:
The kernel and low-level tools, native libraries, the Android Runtime, the
framework layer and on top of all the applications. (Bellosa, 2010)

Figure 1 Android Architecture

The kernel in use is a Linux 2.6 series kernel, modified for special needs in power
management, memory management and the runtime environment. Right above
the kernel run some Linux typical daemons like bluez for Bluetooth support and
wpa supplicant for WiFi encryption.

As Android is supposed to run on devices with little main memory and low powered
CPUs, the libraries for CPU and GPU intensive tasks are compiled to device
optimized native code. Basic libraries like the libc or libm were developed
especially for low memory consumption and because of licensing issues on
Android. In this layer the surface manager handles screen access for the window
manager from the framework layer. Opposing to other frameworks, the media
framework resides in this layer, as it includes audio and video codecs that have to
be heavily optimized. (Bellosa, 2010)

Frameworks in the Application Framework layer are written in Java and provide
abstractions of the underlying native libraries and Dalvik capabilities to
applications. Android applications run in their own sandboxed Dalvik VM and can
consist of multiple components: Activities, services, broadcast receivers and
content providers. Components can interact with other components of the same or
a different application via intents. (Bellosa, 2010)
LITERATURE REVIEW OF RESEARCH PAPER

Different methods and principles have been applied to effectively monitor the
attendance of the students. A system providing an improvised electronic card and
card reader serially interfaced to the digital computer system was proposed, which
is an embedded computer-based attendance management system (O. Shoewu O.
Shoewu, 2011).

A wireless attendance management system used the iris of the individual for
authentication (Seifedine Kadry, 2010). All processes like capturing the image of
iris recognition, extracting minutiae, storing and matching used an off-line iris
recognition management system.
WORK FLOW DIAGRAM OF SIMILAR SYSTEM

Figure 2 Work flow diagram of similar system

STUDENT ATTENDANCE MANAGEMENT SYSTEM WORKING PROCESS
DIAGRAM

Figure 3 Flow diagram of Attendance Management App

ANALYSIS TO LITERATURE REVIEW

Ours is a simplified and cost-effective model of embedded android based manual

attendance system that allows lecturers to mobile monitor student attendance and
verify if each student made the required percentage to sit for an examination using
an improvised algorithm. The proposed app does not only speed up the process
of taking attendance but allows for less error and faster verification process of
authenticating student lecture attendance policy required for writing examination
in a college environment.
Development

METHODOLOGY
Spiral Methodology

It is a waterfall model and iterative model combined method. Each phase starts
with a design goal in the spiral model and ends with a review of progress. The
development here begins with a small set of requirements and goes through each
phase of development for those set of requirements. In every-increasing spirals,
the functionality is added to meet additional requirements until the application is
ready for the production phase. (Guru99, 2019)

Why use Spiral Methodology

i. Risk Handling: Projects with many unknown risks occurring as the
development proceeds, in this case, Spiral Model is the best development
model to follow due to risk analysis and risk handling at each stage.

ii. Good for large projects: It is recommended to use the Spiral Model in large
and complex projects.

iii. Flexibility in Requirements: Change requests in the Requirements at later

phase can be incorporated accurately by using this model.

iv. Customer Satisfaction: Customers can see the product development at the
early stage of software development and have thus become accustomed to
the system by using it before the overall product is completed. (Pal, 2019)
Phases of Spiral Methodology

Figure 4 Spiral model diagram

i. Determine Objectives
It includes estimating the cost, schedule and resources for the iteration
along with acknowledging the system requirements.

ii. Identify and resolve Risk

The potential risk is identified while risk mitigation strategy is planned and
finalized.

iii. Development and Testing

This phase includes testing, coding and deploying software to the customer.

iv. Plan the next iteration

 The software is evaluated by the customer in this phase. It also includes
identifying and monitoring risks such as schedule slippage and cost
overrun. (Guru99, 2019)

TOOLS AND TECHNOLOGIES TO BE USED

Software Required
a) Operating System (Windows)
It manages the computer memory and processes as well as its
software and hardware.

b) Database (MySQL)
It is the world’s most popular open database which boosts the
performance, scalability and reliability.

c) Programming Language (Java)

Java applications are typically complied to bytecode that can run on
any Java virtual machine(JVM) regardless of computer architecture.

d) Android Studio
It is used to accelerate the development and helps in building the
highest quality apps.

e) MS Word
It is used for the documentation process of the project.

Hardware Required
a) Laptop

A laptop with 8GB RAM is required.

b) Android device (Mobile phones)

Mobile phones powered by android is used for testing.

c) Hard Disk

A hard disk with 1TB memory space can be used for backups.
Project Plan

WORK BREAK DOWN

Figure 5 Work breakdown structure

GANTT CHART

/
Probable issues during the project

RISK FACTORS

The efficiency and effectiveness of the project could be affected by numerous risk
factors. Some of them are included below:

i. Resource negligence and time management may result in project delivery

failure.

ii. There are high chances of hardware crashing leading to project failure.

iii. The efficiency of the project could be hampered due to lack of genuine
paper.

iv. The implementation phase could not go as planned on the proposal.

v. There could be a possible lack of human resources.

FALLBACK PLAN

The points listed below could be used as a solution to address the possible risk
factors:

i. The management of resources and time should be monitored time and

again.

ii. To prevent impacts from sudden hardware crash and failures, backup plans
should be made and followed.

iii. If there is lack of genuine paper, hosting questionnaire and taking

suggestions from the supervisor frequently.
iv. While implementing the project, proper planning should be done and should
be carried out simultaneously.

v. Human resources should be prepared backhand for possible risky

situations.

SOME SOCIAL, LEGAL AND ETHICAL ISSUES THAT MIGHT ARISE DURING
OR AFTER THE PROJECT
i) Some clients might not be content with this type of method.
ii) Damage or tampering can be done to the system.
iii) Legal issues regarding the claiming the rights of the application could
arise.
iv) Law suit charges may be filed in terms where there is lack of proof for
presenting proof of work. (Bourgeois, 2019)

SOLUTION FOR SOCIAL, LEGAL AND ETHICAL ISSUES

i) Students should adapt while also taking constructive feedback to
improve the application.
ii) Proper security measures should be adopted to secure the system
from external interference.
iii) Royalties should be paid to the developer and mutual terms should be
met.
iv) A proper documentation of proof of the work should be kept to tackle
law suits.
Conclusion and Recommendation
Conclusion

As per the necessity for the necessity to complete the Final year project (FYP), a
research proposal was to be made on the given topic of our FYP. Research,
background study, history of the project and its related system were scoured
through the internet. Due to the lack of related system apps and no guarantee of
their credibility, research papers regarding the topic were scoured and put into
perspective with the project’s own vision of the application.

Recommendation

For the future, this application can be further developed with new and exciting
features such as rating each class studied per day. The application can also be
developed into a brother-system for the attendance management for the teachers
with minor or major changes given the usability requirements gathered after the
research and survey of the application.