0% found this document useful (0 votes)
15 views64 pages

Android Based Student Attendance Management System

Uploaded by

Abdi Firdisa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views64 pages

Android Based Student Attendance Management System

Uploaded by

Abdi Firdisa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 64

COLLEGE OF ENGINERING AND TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY


Project title :Android Based Student Attendance management system
For Mettu University’s College of Engineering and Technology

In partial fulfillment of the Requirements for B.Sc. Degree in Information


technology Industrial Project I

Team Member Name


1 Gebreiyesus Negese
2. Gebretensay Melkamu
3.Melkame Muluneh
4.Yihenew Mezgebu
5. Birke Moges

Submit to:Department of information Technology


Submission date 12/07/2014E.c

Advisor: Mr.Begna Dejen

Mettu,Oromia,Ethiopia
Android based Student Attendance Management system for Mettu University College of
Engineering And Technology

Android Based Student Attendance management system


For Mettu University’s College of Engineering and Technology
INDUSTRIAL PROJECT I
SUBMITTED BY:
Team Member Name ID

1 Gebreiyesus Negese -----------------------------------WDU111284


2. Gebretsay Melkamu-----------------------------------WDU111285
3.Melkame Muluneh-----------------------------------WDU111326
4.Yihenew Mezgebu -----------------------------------WDU111396
5. Birke Moges ------------------------------------WDU103153
Project Advisor:
1._________________________________________________________
Advisor Name Signature Date
Project Examiner:
1._________________________________________________________
Examiner Name Signature Date
2._________________________________________________________
Examiner Name Signature Date

Fourth year IT section two group one students final project documentation. I
Android based Student Attendance Management system for Mettu University College of
Engineering And Technology

ACKNOWLEDGEMENT

Any accomplishment requires the blessing of the God. Next we would like to thank
our honorable main advisor Instructor Begna Dejen for his continuous comments in
every steps of the project that they forwards throughout these weeks. We also would
like to thanks all members of Mettu University Information Technology Department
Heads and members who give any information when we asked them. Finally, we want
to extend our thanks to our friend’s for their encouragement, motivation and support
throughout our study.
Finally we would like express our love, thanks, appreciation, and respect for their on
going support of our parents and family members, for their continues encouragement
and financial support.

Fourth year IT section two group one students final project documentation. II
Android based Student Attendance Management system for Mettu University College of
Engineering And Technology

Table of contents
ACKNOWLEDGEMENT...................................................................................... II
1. Introduction................................................................................................................ 1
1.1. Introduction To Android...................................................................................1
1.2. Background.......................................................................................................2
1.2.1. background of the Organization.................................................................... 2
1.2.2. Background The Project................................................................................ 2
1.3. The Existing System......................................................................................... 3
1.4. Related works................................................................................................... 4
1.5. Statement of the problem..................................................................................4
1.6. Objectives......................................................................................................... 5
1.7. Methodology.....................................................................................................5
1.8. Feasibility study................................................................................................9
1.8.2. Technical Feasibility....................................................................................10
1.8.3. Social and Operational Feasibility...............................................................10
1.8.4. Schedule feasibility......................................................................................10
1.9. Scope of the Project........................................................................................ 11
1.10. Limitation of The project..............................................................................12
1.11. Significance of the Study..............................................................................12
1.12. Work plan..................................................................................................... 12
1.13. Budget plan...................................................................................................13
2. Chapter Two Analysis....................................................................................... 14
2.1. Existing System.............................................................................................. 14
2.1.1. Limitations Of The Existing System........................................................... 14
2.2. Supplementary requirements.......................................................................... 15
2.2.1. constraints.................................................................................................... 15
2.3. NEW SYSTEM ............................................................................................. 16
2.3.3. Essential use case diagram...........................................................................19
2.3.4. System use-case diagram.............................................................................20
2.3.5. Key abstraction with CRC analysis............................................................. 29
2.3.6. Sequence diagram........................................................................................30
2.3.7. Activity diagram.......................................................................................... 38
2.3.8. Conceptual Class diagram........................................................................... 44
2.3.9. User Interface Prototyping...........................................................................45

Fourth year IT section two group one students final project documentation. III
Android based Student Attendance Management system for Mettu University College of
Engineering And Technology

3. Chapter Three Design................................................................................... 46


3.1. Purpose and Goal of the Design..................................................................... 46
3.1.1. Purpose of system designing....................................................................... 46
3.1.2. Design Goal................................................................................................. 46
3.2. Class Modeling Diagram................................................................................ 48
3.3. Current software architecture......................................................................... 49
3.4. Proposed software architecture.......................................................................49
3.5. Subsystem Decomposition..............................................................................50
3.6. Component Diagram.......................................................................................51
3.7. Deployment Diagram......................................................................................52
3.8. Persistence Modeling Diagram.......................................................................53
3.9. Access control and security............................................................................ 54
3.10. Exception Handling...................................................................................... 54
3.11. User Interface design.................................................................................... 55
References.................................................................................................................... 57

List of tables
Table 1 :software tools.............................................................................................6
Table 2 :work break down structure...................................................................... 12
Table 3 :Gantt chart for our work plan.................................................................. 13
Table 4 :budget plan.............................................................................................. 13
Table 5 :Use case descriptions for register............................................................ 21
Table 6 :Use case descriptions for login................................................................22
Table 7 :Use case descriptions for take course attendance....................................23
Table 8 :Use case descriptions for take exam attendance......................................24
Table 9 :Use case descriptions for take view attendance...................................... 25
Table 10 :Use case descriptions for manage account............................................ 26
Table 11 :Use case descriptions for assign instructor............................................27
Table 12 :Use case descriptions for approve student.............................................28
Table 13 :Access control and security ................................................................. 54

Fourth year IT section two group one students final project documentation. IV
Android based Student Attendance Management system for Mettu University College of
Engineering And Technology

list of figures
Figure 1 :essential use case diagram......................................................................19
Figure 2 :system use case diagram........................................................................ 20
Figure 3 :class responsibility collaborator model..................................................29
Figure 4 :sequence diagram for register................................................................ 30
Figure 5 :sequence diagram for login.................................................................... 31
Figure 6 :sequence diagram for manage account.................................................. 32
Figure 7 :sequence diagram for take course attendance........................................ 33
Figure 8 :sequence diagram for take exam attendance..........................................34
Figure 9 :sequence diagram for view attendance.................................................. 35
Figure 10 :sequence diagram for assign instructor................................................ 36
Figure 11 :sequence diagram for approve student.................................................37
Figure 12 :Activity diagram for registration..........................................................38
Figure 13 :Activity diagram for login....................................................................39
Figure 14 :Activity diagram for manage account.................................................. 40
Figure 15 :Activity diagram for take course attendance........................................41
Figure 16 :Activity diagram for take exam attendance......................................... 42
Figure 17 :Activity diagram for view attendance.................................................. 43
Figure 18 : conceptual class diagram.....................................................................44
Figure 19 :User interface prototyping....................................................................45
Figure 20 :Class Modeling Diagram......................................................................48
Figure 21 :Proposed software architecture............................................................ 49
Figure 22 :Subsystem decomposition diagram......................................................50
Figure 23 :component diagram..............................................................................51
Figure 24 :Deployment diagram............................................................................52
Figure 25 :Persistence Modeling Diagram............................................................ 53
Figure 26 :user interface design.............................................................................56

Fourth year IT section two group one students final project documentation. V
Android based Student Attendance Management system for Mettu University College of
Engineering And Technology

Abbreviations

MeU……………………………………..Mettu university.
SRS …………………………………… System Requirement Specification.
OOSD……………………………………Object oriented System Design.
OOA……………………………………..Object Oriented Analysis.
UML …………………………………..Unified modeling language.
UI ………………………………………User Interface.
DB ……………………………………….Database.
XML……………………………………Extensible markup language.
CPU …………………………………….Central processing unit.
PC……………………………………… Personal computer.
HOD……………………………………head of department.
CRC…………………………………….class responsibility collaborator.

Fourth year IT section two group one students final project documentation. VI
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1. Introduction

These days, computer is one of many inventions that greatly affect our way of living.
In fact, it is noted as an essential tool in many areas including business, government,
industry, sciences, education, school, home, and in almost any company and
establishment that existed. It can perform process data rapidly, accurately and reliable
and by using these machines, spending a lot of time and effort in doing a certain task
is minimized.
Student attendance is a baseline factor in determining student success. The attendance
is important because students are more likely to succeed in academics when they
attend consistently. It’s difficult for the teacher and the class to build their expertise
and growth if a large number of students are often absent. In addition to falling behind
in academics, students who are not in school on a regular basis are more likely to get
into difficulty with the law and cause problems in their communities.This project is an
important role in maintain the attendance of all students.
The project Android Student Attendance Management System is developed so the
users can used to maintain daily student attendance in college. This is used to access
the attendance information of a particular student.The information is stored by the
operator which will be the provided by the teacher for a particular class.This system
will also help in evaluating attendance eligibility criteria of student.

1.1. Introduction To Android

Android is an operating system for mobile devices such as Smartphone’s and tablet
computers. It is developed by the Open Handset Alliance led by Google. It's is built
on a Linux foundation.Google purchased the initial developer of the software Android
Inc., in 2005.This alliance shares a common goal of fostering innovation on mobile
devices and giving consumers a far better user experience than much of what is
available on today's mobile platforms.Android is Linux based open source operating
system , Easy access to the android apps.Its supports all Google services.Android
phone can also function as a router to share internet.It’s free to customize.Can install a
modified ROM[2].

Fourth year IT section two group one students final project documentation.
1
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1.2. Background

1.2.1.background of the Organization

Mettu University, in its acronym (MeU), was established as a result of Ethiopian


government’s endeavor towards realizing the country’s renaissance through educating
the generation. It is one of the nine newly established public higher learning institutes.
The faculty of Engineering and Technology is one of the 5 faculties in Mettu
University. Currently, the faculty enrolling more than 1500 students. The College
teaches/traines postgraduate coursework in Mechanical Engineering, Civil
Engineering, Electrical Engineering, Construction Technology and management,
Information Technology and Computer Science.
Facility and services
Computer centers: three computer labs consisting of 60 PCs which are connected
through LAN networks enables the students to practice computer programs as well as
on Auto Cad and Matlab programs[4].Laboratories and workshops: there are about
four laboratories and workshops which are functional for eight hours daily.These
laboratories and workshops are very important to fulfill the demand of innovative,
highly skilled, practical-oriented, entrepreneurial, and ethical human resources in the
various fields of Engineering and Technology.

1.2.2.Background The Project

Nowadays, the students’ population is rapidly increasing and this is a big problem for
the college to have a manual transaction and operation.Monitoring is one of the great
responsibilities of a teacher. This includes teaching lessons to his/her students, writing
lesson plans, and recording the achievement of the students. Teachers have a lot of
things to do in their daily routine, due to this daily task, they consume much time in
doing paper works and preparing some devices as they are required to perform
because they operate these tasks manually. In order to give a solution to this problem,
developing a computerized and automated transaction is a great solution .

Fourth year IT section two group one students final project documentation.
2
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1.3. The Existing System

The existing system is a manual entry for the student’s attendance Here,
the attendance will be carried out in handwritten registers. It will be a tedious job to
maintain the record for the user. The system requires more human effort and
consumes more resources like paper,pen and so on.The retrieval of the information is
not easy because records are maintained in handwritten registers. This application
requires correct feed in the respective input field. Supposed there were wrong inputs
entered, the application resists requiring the user to input correct data.

Draw Backs of the existing system

Not User Friendly: The existing system is not user friendly because the retrieval of
data is very slow and data is not maintained efficiently.
Manual control: All calculations to generate report is done manually so there is
greater chance of errors.
Lots of paperwork: Existing system requires lot of paper work.Loss of even a single
register/record led to difficult situation because all the papers are needed to generate
the reports.
Time consuming: Every work is done manually so we cannot generate report in the
middle of the session or as per the requirement because it is very time consuming.

Fourth year IT section two group one students final project documentation.
3
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1.4. Related works

In early years punch card was used for data storage , it is also known as Hollerith
cards, through these cards companies were able to store and access via entering the
card into the computer system [1]. Now a day also it is used as one of the most
popular attendance system. Employees are using this card for in and out, they only
need to wave the punch card near a reader then it will ensure the presence of
employee .
Many desktop applications for Employee attendance has been developed there are
some examples:
1. Desktop application for attendance developed to take daily attendance of
employee’s. Then information is stored by the operators.Saurabh Kumar Jain, Uma
Joshi, and Bhumpesh Kumar Sharma developed the software. The technology which
they used for their application is Language:-VB.NET and Back end:-MS- Access.

1.5. Statement of the problem

In most educational institutions the attendance is taken manually. using manual paper
that contain attendance information could be lost and may raise a conflict between the
students and teachers.The paper it can be lost not available a lot for only few
days.And the attendance paper is unsafe means there is not a mechanism to protect.
It will be damaged or accessed by any other individual.when the instructor assigned
for many class he/she prepare the attendance sheet for all class separately so here
requires more effort and time.In addition to this difficult for teachers to keep track of
the large number of students because by using paper sheets a student can help the
other students or his/her friend to answer even the other student may be absent or
come late in class. To overcome these problems we will have develop a better system
which is android based; it will fully responsive where a user can use in mobile,
tablets.In this system records will kept safe,secure and the attendance information of
particular or all students of particular class will be accessed easily and without time
consuming.

Fourth year IT section two group one students final project documentation.
4
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1.6. Objectives

1.6.1. General Objectives

The main objective of our project is to develop android based student


attendance management system.

1.6.2. Specific objective

The specific objectives of this project are:


 To perform requirement analysis.
 To reviewing the existing system problems.
 To determining how to build the proposed system.
 To designing the system with appropriate methodologies and tools.
 To developing a database that will be used by the system.
 To secure the data and information.
 To implement and Test the system using a chosen programming language and
paradigm.

1.7. Methodology

1.7.1. Data Collection Methodology

Interview:The additional data will be gathered through the technique of interview,


through this technique we get different information’s from the current workers of the
organization and from peoples.
Observation: - This method important to know the actual event which will happen in
the existing system. In this method all team members have observed and note down
the events from that observation.
Document(literature review) :We will collect information from different references,
projects and web sites. By discussing and analyzing the problems with project team.

Fourth year IT section two group one students final project documentation.
5
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1.7.2. System Development tools

To develop the system different software, hardware tools and programming language
are very important.

1.7.2.1.Software tools and language

We use different software to develop the proposed system. This software is used to us
for preparing the documentation and drawing the diagrams and also to design the
system. Those are:To implementation (developing) this project we will use the
following soft-wares.

Table 1:software tools

Fourth year IT section two group one students final project documentation.
6
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1.7.2.2.Hardware tools
Different hardware used to develop our project.
 Computer
 Network cable
 USB Flash

1.7.3. System Analysis and Design Methodology


1.7.3.1.Rapid Application Development (RAD)

RAD is a software development methodology, which favors iterative


development and the rapid construction of prototypes instead of large amounts of
up-front planning. The rapid development process starts with the development of
preliminary data models and business process models using structured techniques. In
the next stage, requirements are verified using prototyping, eventually to refine the
data and process models. These stages are repeated iteratively; further development
results in a combined business requirements and technical design statement to be used
for constructing new systems[5].

1.7.3.2. Waterfall development methodology


The waterfall model is a traditional engineering approach applied to software
engineering. A strict waterfall approach discourages revisiting and revising any prior
phase once it is complete.This inflexibility in a pure waterfall model has been a
source of criticism by supporters of other more flexible models. It has been widely
blamed for several large-scale government projects running over budget, over time
and sometimes failing to deliver on requirements due to the Big Design Up
Front approach.Except when contractually required, the waterfall model has been
largely superseded by more flexible and versatile methodologies developed
specifically for software development[5].

Fourth year IT section two group one students final project documentation.
7
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1.7.3.3. Spiral development methodology

Spiral development model which combines some key aspect of the waterfall
model and rapid prototyping methodologies, in an effort to combine advantages
of top-down and bottom-up concepts. It provided emphasis in a key area many felt
had been neglected by other methodologies: deliberate iterative risk analysis,
particularly suited to large-scale complex systems[5].

1.7.3.4.Object Oriented System Development Methodology

The aim of the object oriented approach is to make the system elements more modular.
In addition an object oriented approach data and processes into single entities that we
are calling to object. Objects usually corresponding to the real world things a system
deal with such as customers, workers and other. As a result the system will be an easy
and simple to understand for the application owner and for the system developer thus
improving the system quality and the efficient of system analyses and design. The
systems are easier to adapt to changing requirements, easier to maintain, more robust,
and promote greater design and code reuse[5].
In this project we will be following an object oriented system development
methodology .
The team chooses OOSAD over other approaches because
 To simplify the design and implementation of complex program.

 To make it easier for teams of designers and programmers to work in a single


software project.
 To enable a high degree of re-usability of designs and software codes.
 Increased consistency among analysis, design and programming activities.
 Object-oriented development allows us to create modules of functionality.

Fourth year IT section two group one students final project documentation.
8
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1.8. Feasibility study

The feasibility study is intended to be a preliminary review of the facts to see if it is


worthy of proceed to the analysis phase. From the systems analyst perspective, the
feasibility analysis is the primary tool for recommending whether to proceed to the
next phase or to discontinue the project.

1.8.1. Economic Feasibility

The Attendance Management System will be developed economic with respect to the
college’s point of view. It is cost effective in the sense that it will eliminate the
paperwork completely. According to economic feasibility there are two types of
benefits which are money consideration and which are not money consideration.
These are tangible benefits and intangible benefits.

Tangible benefits: A tangible benefit of the proposed system includes:-


 It will cost effective in the sense that it will eliminate the paperwork
completely.
 The system will also time effective because the calculations are automated.
 It will decrease work overload.
Intangible benefits: it is moral satisfaction for the system user.
Those benefits are intangible benefits of the new system.
 It will be improving information accuracy.
 Work flow will be efficient.
 It will be reduce error.

Fourth year IT section two group one students final project documentation.
9
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1.8.2. Technical Feasibility

Our project will technically feasible. Because the technology that will use to develop
this system is widely available and it will easy for the user and also our system will
practically applicable within the current technology (i.e. the current equipment and
existing software and hardware) and customers will use our system without any worry
and it will not require extra knowledge to operate the system, so users will use the
system efficaciously and effectively and the system will be highly user friendly
interface that will allow the user of the system to perform the action they want
without confuse.

1.8.3. Social and Operational Feasibility

Our proposed system will be operationally feasible because the proposed system
will easily maintainable without requiring high experts or technical supports, and it
will reliable and suitable for user because the system will be installed in adaptable
technology’s and it will be platform independent (it will execute in any operating
system).
The system will be performs all operations to achieve the specified objective, and it
will not have any difficulty or procedures to perform the operation of the system. So,
the project is operational feasible.

1.8.4. Schedule feasibility

This determines how long the system will take to develop. Despite the complexity of
the project all the team members will try to come to an end to the project in the time
stated without considering any delay or any of the members being absent, sick or late.
But if such things happen we will provide the things we have so far and come with
some compensation mechanism. However, the team is so determined to finish this
project according to the schedule. Therefore, the project is feasible in terms of time
schedule. The reason is that the team is well organized and knows its duties and
responsibility.

Fourth year IT section two group one students final project documentation.
10
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1.9. Scope of the Project

The scope of the project is the system on which the software is installed, i.e. the
project is developed as a mobile phone(android) application, and it will work for a
particular institute. The scope of the project is limited to several process:
 Open the first page of the application.
 User login and register page.
 The college officer manage user account.
 The HOD register the course and assign for the instructor .
 The instructor take student attendance and give privilege to the class
representative.
 The student view their attendance status and the class representative will take the
attendance of instructor.
 The android student attendance management system designed in such a way that
makes it possible to access through any android platform.

Fourth year IT section two group one students final project documentation.
11
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

1.10. Limitation of The project

 Our project is not include the attendance of employee’s of the organization.

1.11. Significance of the Study

After the successful completion of our project the system will provide the following
service.

 The removal of paper work.


 The personal details of students registered.
 It assists the instructor to mark attendance to the students for their subject.
 It helps to allot the subject to the particular instructor.
 It provides the facility to have a user name and password to the instructor in order
to security purpose.

1.12. Work plan

Team organization
The project team member is structured with 5 members, one group leader, one vice
leader, one secretary, and 2 other members’ Problem solving takes place in group.
Decision making on problem solving process are made by group member’s agreement,
which is much better than individual decision making.

Responsible person

Gebreiyesus and yihenew

Table 2:work break down structure

Fourth year IT section two group one students final project documentation.
12
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Work Plan

Project work plan in 2014E.c


Jan03/1
Jan25- Feb15- Mar25- May20- June10-
-
Feb15 Mar25 May20 June10 June25
Jan25

Table 3:Gantt chart for our work plan

1.13. Budget plan

Table 4:budget plan

Fourth year IT section two group one students final project documentation.
13
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

2. Chapter Two Analysis

2.1. Existing System

Existing system is a manual entry for the students' Attendance. Here the attendance
have to be carry out in the hand written registers.First the instructor prepare the
attendance sheets by writing the student details and the date he/she attend the
class.During this the instructor may have assigned to many course for different class
at that time the instructor should prepare the attendance sheet for all class may take
much more time and more effort. So It will be a tedious job to maintain the record for
the user. The human effort is more here. The retrieval of the information is not as easy
as the records are maintained in the hand written registers.The instructor should report
the students who are not regularly attend the class to the department head by going
physically to the office this may another tired task. In order to simplify tasks we try to
investigate the new system to solve such problems.

2.1.1. Limitations Of The Existing System

The current attendance system of MeU is Manual.All work is doing on paper by


registering the student detail with their attendance status.The whole session
attendance is register on the paper.The retrieval of the information is not as easy as
the records are maintained in the hand written registers and the attendance paper may
be totally lost or damage.
Draw backs of the existing system
 Not User Friendly:
The existing system is not user friendly because the retrieval of data
is very slow and data is not maintained efficiently.
 Difficulty in report generating:
We require more calculations to generate the report so it is generated at the end of the
semester. And the student doesn’t get a single chance to improve their Attendance.
 Manual control:
All calculations to generate report are done manually so there is greater
chance of errors.

Fourth year IT section two group one students final project documentation.
14
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

 Lots of paperwork:
Existing system requires lot of paper work. Loss of even a single register/record led to
difficult situation because all the papers are needed to generate the reports.
 Time consuming:
Every work is done manually so we cannot generate report in the end of the semester
or as per the requirement because it is very time consuming.

2.2. Supplementary requirements

User Requirements
Since the current system cannot support authentication, so that data can be accessed
by an unauthorized user.also files are stored in paper, so that it may be lost, burnt or
damaged by fire and natural disaster.The User requirements for the new system are to
make the system fast, flexible, less prone to errors and reduce expenses and save time.
A system that can automate the checking of answers which are per-stored so that
results can be generated as soon as the Student gives the reason. The New system will
be more secure in managing Student attendance records and reliable enough to be
used in any condition. Finally, it will be prove cost effective as compared to the
current system.

2.2.1. constraints

The main business rules or principles of the system are


BR1: the students must attend the class regularly.
BR2:The instructor must take the student attendance and report the students to the
department who are not attend the class regularly.
BR3:The HOD should take appropriate justification to those students who are not
attend the class regularly.
BR4: The students who are not attend the class regularly with out any convincing
reason.The HOD should prevent them form take the final exam.

Fourth year IT section two group one students final project documentation.
15
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

2.3. NEW SYSTEM

The team proposed the new system to overcome the drawbacks in the existing
system.This project aims to reduce the paper work and allows only the registered
users perform their private activities.After register the user should login and will do
their task based on their access level. The college officer will manage the user
accounts and the HOD will assign the instructor for the particular course and approve
the students to their department and view the attendance status. The instructor will
take the course or exam attendance of students and give privilege to the class
representative.The student will view their attendance status.It require the necessary
details of the student and attendance details.To increase efficiency of managing
student Attendance Records is improved which results in proper resource
management of Attendance Management System data.User only need a Smartphone
or tablet which has Android OS to the work.The system will provides with the best
user interface. It will trouble-free to use. It will be relatively fast approach to enter
attendance status and it will be highly reliable, approximate result from user best user
Interface.

2.3.1. Functional requirement

Functional requirements that define specific behavior or functions of a system or its


component and describe what the system should do. In other words, they describe the
services provided for the users and describe the relations between the user and the
system.The new system should provide the following functional requirements.
The system enables college officer,HOD, instructors and students to register to the
system. The system enables the college officer to manage the HOD, instructors and
students.The HOD can register courses,assign the instructor for the particular subject
and approve the students for their departments and view the attendance status.The
system enables the instructor to record/take whether the course attendance or the
exam attendance of students and view the attendance.And give privilege to the class
representative to take attendance of the instructor and the student can view their
attendance status.

Fourth year IT section two group one students final project documentation.
16
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

2.3.2. Non-functional requirements

A non-functional requirement is a requirement that specifies criteria that can be used


to judge the operation of a system, rather than specific behaviors. It defines how a
system is supposed to be. Non-functional requirements are often called qualities of a
system. In order to give satisfaction to the clients, all the operations of existing system
should be interactive and easy way with fast response time and maximum through put.
Generally, the following are some of the non-functional requirements of the system: .
User Interface
The application will have a user interface which is simple to use and negotiable
through each page. The user interface of the application will be easy to use by each
user of the application with little training.Our interface will contains different buttons
which guide the users what to click and fill to enter their page to do what they
want.So the user interface will be easy to use.We will also use different text fields,
icons,buttons,to make attractive interface.
Portability
The application will be work in different platforms,for there could be platforms
shifting in the future and the work to have the acceptance of different institutions
having different platforms.

Usability
Since the system will be easily usable, it will easy to use and understand for the user.
Fault Tolerance
Our system will have good ability to operate under erroneous condition and display
the proper error message to correct the errors.The system will be able to give
response(error) message when the user enter incorrect input. If users enter incorrect
data like user name,password and invalid fields the system displays an error message
which informs the user to enter the correct information.

Fourth year IT section two group one students final project documentation.
17
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Operability
Every operation of the system will be as simple as possible for the user to operate
simply. This system achieves by providing simple user interface.
Security
The system database will be secured from unauthorized person by making the login to
the system only restricted to legal persons. We will be use password so it does not
accessed by illegal person.
Storage capability
The system will have an ability to store the required information of the users in the
database.

Fourth year IT section two group one students final project documentation.
18
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

2.3.3. Essential use case diagram

Essential use case is well-defined from the point of view of users in some roles in
relation to a system and describes the interaction between the user and the system at a
high level of abstraction.The actor’s are system college officer,head of department,
instructor, and student.

Figure 1:essential use case diagram.

Fourth year IT section two group one students final project documentation.
19
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

2.3.4. System use-case diagram

Figure 2:system use case diagram

Fourth year IT section two group one students final project documentation.
20
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

2.3.4.1.Use-case documentation

The user documentation is intended to help the users of the system. We described
each use case and actors in the use case diagram. It includes the name of all use case,
description about the use case, the name of all actor who act on the use case, what
precondition before the actor acts on the system, post condition after the actor acts on
the system and basic course of action which describes the interaction between the
actor and the system when the actor acts on the system and alternative course of
action.

Table 5:Use case descriptions for register


Actor College_officer, HOD ,Instructor and student.

Use case name Register


Use case no UC 1

Description User should be register for access private activities in the


system.
Precondition The user should open the application.

Post-condition The user register successfully to the system.


User action Application response
Basic course of
action
1. The user opens the 2. The system displays the
application login and register page.
4. The system displays a form
2. The user clicks on which is used to register user’s
register button. detail.
6. If the user fills the form
5. The user fills the form correctly the system displays
and clicks on submit successfully registered
button. message else fill the form
correctly message displayed.
7 End use case.

Alternative course If the user fills the form incorrectly, the system tells the user
of action to fill the form correctly.

Fourth year IT section two group one students final project documentation.
21
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Table 6:Use case descriptions for login


Actor College_officer/, HOD ,Instructor and student.
Use case name Login
Use case no UC2
Description Checking either the user is authorized or not to access tasks in
the system.
Precondition The user must have valid user name and password.
Post-condition For valid login the system must allow the user to do what he/she
wants in the system.
Basic course of User action Application response
action
1. User accesses the start 2. System displays the
login page.
button
4. The system checks the
3. The user enters user name
username and password.
and password. 5.system acknowledges
6. The user request to login the user to login
9 End use case. 7. System checks the
account.
8.The system opens the
needed page

Alternative If user entered incorrect user name/password, the system displays


course of action enter the correct user name or password. Then system allows the
user to click the login button and to enter the correct password
and user name. Through these alternatives for the correct
username and password system opens.

Fourth year IT section two group one students final project documentation.
22
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Table 7:Use case descriptions for take course attendance.


Actor Instructor

Use case name Take course attendance

Use case no UC 3

Description The Instructor record the student attendance based on his/her


assigned subject.
The Instructor must have user name and password open and login to
Precondition the application.

Post-condition The Instructor takes the registered student’s attendance information.

User action Application response


Basic course of
action 1. The Instructor open the 2. The application
application. displays login page.
3. The Instructor clicks on 4. The system displays
Take course attendance list of students.
button. 6 The system display’s a
5. The Instructor clicks on check box
the student name Alternate present or
7 End use case. absent
Alternative If user entered incorrect user name/password, the system displays
course of action enter the correct user name or password. Then system allows the user
to click the login button and to enter the correct password and user
name.

Fourth year IT section two group one students final project documentation.
23
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Table 8:Use case descriptions for take exam attendance.


Actor Instructor

Use case name Take exam attendance

Use case no UC 4

Description The Instructor record the student attendance based on his/her


assigned subject.
The Instructor must have user name and password open and login
Precondition to the application.

Post-condition The Instructor takes the registered student’s attendance information.

User action Application response


Basic course of
action 1. The Instructor open the 2. The application
application. displays login page.
3. The Instructor clicks on 4. The system displays
Take exam attendance list of students.
button. 6 The system display’s a
5. The Instructor clicks on check box
the student name Alternate present or
7 End use case. absent
Alternative If user entered incorrect user name/password, the system displays
course of action enter the correct user name or password. Then system allows the
user to click the login button and to enter the correct password and
user name.

Fourth year IT section two group one students final project documentation.
24
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Table 9:Use case descriptions for take view attendance.


Actor Instructor,Student,HOD

Use case name View attendance

Use case no UC 5

Description The Instructor after record the student attendance the student and
HOD can view the attendance status.
The Instructor,Student,HOD must have user name and password
Precondition open and login to the application

Post-condition The Instructor,Student,HOD can view the attendance status.

User action Application response


Basic course of
action 1. The Instructor,Student, 2. The application
HOD open the application. displays login page.
3.The Instructor,Student, 4. The system displays
HOD clicks on view the attendance status.
attendance button.
5. The Instructor,Student,
HOD can view the
attendance status.
6.End use case.
Alternative If Instructor,Student, HOD entered incorrect user name/password,
course of action the system displays enter the correct user name or password. Then
system allows the user to click the login button and to enter the
correct password and user name.

Fourth year IT section two group one students final project documentation.
25
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Table 10:Use case descriptions for manage account.


Actor College_officer

Use case name Manage account

Use case no UC 6

Description The College_officer should manage the account of the


student,instructor and the HOD.
The College_officer should have user name and password open and
Precondition login to the application.

Post-condition The College_officer would mange account.

User action Application response


Basic course of
action 1.The College_officer open 2. The application
the application. displays login page.
3. The College_officer enter 4. The system displays
his/her username and the manage account of
password and click login the users.
button. 6.The system displays
5.The College_officer click delete account and
on manage account button. activate account button.
7.The College_officer select
and click on Delete or
activate button.
8.End use case.
Alternative If The College_officer entered incorrect user name/password, the
course of action system displays enter the correct user name or password. .

Fourth year IT section two group one students final project documentation.
26
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Table 11:Use case descriptions for assign instructor.


Actor HOD

Use case name Assign Instructor

Use case no UC 7

Description The HOD should assign instructor for the particular course.

The HOD should have user name and password open and login to
Precondition the application.

Post-condition The HOD would assign instructor.

User action Application response


Basic course of
action 1.The HOD open the 2. The application
application. displays login page.
3. The HOD enter his/her 4. The system displays
username and password and assign instructor button.
click login button. 6.The system displays
5.The HOD click on assign course list and assign
instructor button. button.
7.The HOD click on assign
button.
8.End use case.
Alternative If The HOD entered incorrect user name/password, the system
course of action displays enter the correct user name or password. .

Fourth year IT section two group one students final project documentation.
27
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Table 12:Use case descriptions for approve student.


Actor HOD

Use case name Approve student

Use case no UC 8

Description The HOD should approve the students for their department.

The HOD should have user name and password open and login to
Precondition the application.

Post-condition The HOD would approve the students.

User action Application response


Basic course of
action 1.The HOD open the 2. The application
application. displays login page.
3. The HOD enter his/her 4. The system displays
username and password and approve student button.
click login button. 6.The system displays
5.The HOD click on approve student list and approve
student button. button.
7.The HOD click on approve
button.
8.End use case.
Alternative If The Faculty entered incorrect user name/password, the system
course of action displays enter the correct user name or password. .

Fourth year IT section two group one students final project documentation.
28
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

2.3.5. Key abstraction with CRC analysis


A class responsibility collaborator model is a collection of standard index cards that
have been divided into three sections, those are a class represents a collection of
similar objects, a responsibility is something that a class knows or does, and a
collaborator is another class that a class interacts with to fulfill its responsibilities. The
layout of a CRC card looks like below

Fname Fname
Lname Lname
Address Address
HOD Email Instructor
Email
Password Instructor Password Student
Manage account Student
Register () () Register ()
Manage account () Assign Instructor ()
Register course()
View Attendance ()

Fname Fname
Lname Lname
Address Address
Email Email
Password Password Instructor
Student
Registered () Registered ()
Take attendance () Take_inst_Attendance()
View Attendance ()
View Attendance ()

Figure 3:class responsibility collaborator model.

Fourth year IT section two group one students final project documentation.
29
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

2.3.6. Sequence diagram

A Sequence diagram is used to define event sequences between objects for a certain
outcome and Shows the sequence of interactions among objects and used to model the
flow of messages, events and actions between the objects or components of a system.
In a sequence diagram, object interaction occurs through messages on the vertical and
horizontal dimensions and designated by horizontal arrows and message names.

Figure 4:sequence diagram for register.

Fourth year IT section two group one students final project documentation.
30
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 5:sequence diagram for login

Fourth year IT section two group one students final project documentation.
31
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 6:sequence diagram for manage account.

Fourth year IT section two group one students final project documentation.
32
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 7:sequence diagram for take course attendance.

Fourth year IT section two group one students final project documentation.
33
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 8:sequence diagram for take exam attendance.

Fourth year IT section two group one students final project documentation.
34
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 9:sequence diagram for view attendance.

Fourth year IT section two group one students final project documentation.
35
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 10:sequence diagram for assign instructor.

Fourth year IT section two group one students final project documentation.
36
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 11:sequence diagram for approve student.

Fourth year IT section two group one students final project documentation.
37
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

2.3.7. Activity diagram

Activity diagram is basically a flow chart to represent the flow from one activity to
another activity. So the control flow is drawn from one operation to another.
An activity diagram is represented by shapes that are connected by arrows run from
start activity to completion activity and represent the sequential order of performed
activities.

Figure 12:Activity diagram for registration.

Fourth year IT section two group one students final project documentation.
38
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 13:Activity diagram for login.

Fourth year IT section two group one students final project documentation.
39
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 14:Activity diagram for manage account.

Fourth year IT section two group one students final project documentation.
40
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 15:Activity diagram for take course attendance.

Fourth year IT section two group one students final project documentation.
41
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 16:Activity diagram for take exam attendance.

Fourth year IT section two group one students final project documentation.
42
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Figure 17:Activity diagram for view attendance.

Fourth year IT section two group one students final project documentation.
43
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

2.3.8. Conceptual Class diagram

A class diagram describes the structure of a system by showing the system's classes,
their attributes, operations (or methods), and the relationships among objects. And
Class diagram provides an overview of the target system by describing the objects and
classes inside the system and the relationships between them.

Student_Id:int()
Dep’t:varchar(15)
Year:int()

Figure 18: conceptual class diagram

Fourth year IT section two group one students final project documentation.
44
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

2.3.9. User Interface Prototyping

User interface prototyping describes the function of each actor in the system with
their access level and privilege. The functions of each Actor in our system are
described as follows:

Activate
Acount

Figure 19:User interface prototyping

Fourth year IT section two group one students final project documentation.
45
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

3. Chapter Three Design

3.1. Purpose and Goal of the Design

3.1.1. Purpose of system designing

The purpose of system designing is to show the direction how the system is built and
to obtain clear and enough information needed to drive the actual implementation of
the system. The purpose of the proposed system design part is very important so as to
make the implementation of the proposed system very easy.The different types of the
system modeling techniques that are used to make easy the implementation of the
system such as deployment diagram and component modelling will show in detail.

3.1.2. Design Goal

The design goals are to describe the structure of the system including any sub
programs to be used along with packaging of the system.
Design goals describe the qualities of the system that developers should achieve.Such
goals are normally derived from the nonfunctional requirements of the system
described earlier.
User interface
The user interface of the application should be easy to use by each user of the
application with little training.Our interface will contains different buttons which
guide the users what to click and fill to enter their page to do what they want.so the
user interface will be easy to use.We will also use different text fields,
icons,buttons,to make attractive interface.
Security
The system will be built with the security methods. The user has to enter a user name
and password to access the system. Therefore the system will be secures that any
unauthorized user is not allowed to access the system.

Fourth year IT section two group one students final project documentation.
46
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Portability
The application will be work in different platforms,for there could be platforms
shifting in the future and the work to have the acceptance of different institutions
having different platforms.

Performance
The system will be respond in a very minimal duration of response time. This mean
our system gives response to the users in short period of time according to their input.
Fault Tolerance
The system should be able to give response(error) message when the user enter
incorrect input. If users enter incorrect data like user name,password and invalid
fields the system displays an error message which informs the user to enter the correct
information.
Usability
Everyone who has a little knowledge of a computer can access our system easily
because our system doesn’t require more knowledge.

Fourth year IT section two group one students final project documentation.
47
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

3.2.Class Modeling Diagram

Class diagrams are the most common diagram found in modeling object-oriented
systems. A class diagram shows a set of classes, interfaces, collaborations and their
relationships. We use class diagrams to model the static design view of a system.

Figure 20:Class Modeling Diagram

Fourth year IT section two group one students final project documentation.
48
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

3.3. Current software architecture

The existing system is manual system and hence there is no current software
architecture that will be considered. As a result, we only describe the software
architecture of the newly proposed system.

3.4. Proposed software architecture

The proposed system will be expected to replace the existing system.the proposed
system will use three tier architectures to design our system.Because 3-tier
Architecture increases performance ,flexibility,maintainability,usability,and
portability while hiding the complexity of the distributed processing from the
users/clients.
Three-tier architectures consists of three components distributed in 3 layers:
Client(requester of the service).
Business logic(data handler).
Server(provider of the service).

Figure 21:Proposed software architecture

Fourth year IT section two group one students final project documentation.
49
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

3.5. Subsystem Decomposition

Subsystem decomposition is needed to make the system clear and understandable by


dividing the whole system in to subsystems and components. Subsystem diagram
shows the service it provides or it accepts from other subsystems, and the coupling
and the coherence between them.In the subsystem decomposition we try to show the
relationship between each component.

Figure 22:Subsystem decomposition diagram

Fourth year IT section two group one students final project documentation.
50
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

3.6. Component Diagram

The component diagram illustrates the software components to build the system.
Components are modeled as rectangles with two smaller rectangles jutting out from
the left hand side. Components have dependencies on the interface of other
components. Component diagrams can show how various components are structurally
related to one another in a given system.

Figure 23:component diagram

Fourth year IT section two group one students final project documentation.
51
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

3.7.Deployment Diagram

Deployment diagram depicts a static view of the run-time configuration of processing


nodes and the components that run on those nodes. In other words, deployment
diagrams show the hardware for our system, the software that is installed on that
hardware, and the middleware used to connect the disparate machines to one another
as well as how the nodes communicate with each other and with devices.
In other words, it shows which component of the software will install on which
machine and how they communicate with each other if they are on different machines.

Figure 24:Deployment diagram

Fourth year IT section two group one students final project documentation.
52
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

3.8.Persistence Modeling Diagram

Persistence models also called data model or Entity relationship (ER) models, are
used to communicate the design of a database, usually a relational database, to both
users and other developers. Persistence are used the schema of database. The strength
of persistence models is that data entities are conceptually the same as the table of
relation data base and that attributes are the same as table columns.

Figure 25:Persistence Modeling Diagram

Fourth year IT section two group one students final project documentation.
53
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

3.9. Access control and security

Access control deals with the access of different actors with their functionality or
activity.It helps us to control the access of our system the individual actor may
perform several tasks as well a single action may also perform by several
actors.Access control realizes which actor performs which activity in the case of our
system.
Actor Class Operation
College officer Register Register()
Manage user account Manage_ account()
Department head Register Register()
Assign instructor Assign_instructor()
Register course Register_course()
Approve student Approve_student()
View attendance View_attendance()
Instructor Register Register()
Take course Attendance Take_course_Attendance()
Take Exam Attendance Take_Exam_Attendance()
View attendance View _attendance()

Student Register Register()


Take Instructor attendance() Take_course_Attendance()
View attendance View _attendance()

Table 13:Access control and security

3.10. Exception Handling

The system will display messages if it is tried to access using wrong/invalid account
by checking against the account table.The system will provide alert when user insert
invalid data.The system will display messages if it is tried to access using invalid data
by checking against the system table data.The system will display messages if the
user try to enter wrong input.

Fourth year IT section two group one students final project documentation.
54
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

3.11.User Interface design

In the proposed system user Interface design is the process that focuses on how
information is provided and accepts from users. Thus the user interface design is a
technique which is designed in our new system for defining the manner in which users
and system exchange information easily. A good user friendly interface provides a
user to perform the activities of the system easily and effectively.
The application start page

Fourth year IT section two group one students final project documentation.
55
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

Login page Student Registration page

Figure 26:user interface design

Fourth year IT section two group one students final project documentation.
56
Android based Student Attendance Management system for Mettu University’s College of
Engineering And Technology

References

1) Tabusca, Silvia Maria - "The Internet Access as a Fundamental Right"; published in


“Journal of Information Systems and Operations Management”, Vol.4. No.2 ,viewed 21
Dec 2021,<www.freeprojectz.com>.
2) MR.Chanda Singh,Mr.Ankita Tiwari,Mr.Chandani Yadav,2017-18,”Introduction To
Android”,Prof.ArvindVishwakarma,viewed22Dec2021,<http://developer.android.com>.
3) Raegen T. Miller, Richard J. Murnane and John B. Willett – “Do Teacher Absences
Impact Student Achievement?”; published in: Educational Evaluation and Policy
Analysis,Vol.30,No.2,viewed at 28 Dec2021;<http://www.jstor.org/stable/30128059.>

4) “Mettu university faculty of engineering and technology”.tzadmission.net,


14/05/2020,https://tzadmission.net/Metu-university-historical-background/
5) “Soft ware development methodologies”,synopsis,28/03/2017,https://www.synopsis.com
/blogs/software-security/.

Fourth year IT section two group one students final project documentation.
57

You might also like