Design and Implementation of Employee at

DESIGN AND IMPLEMENTATION
OF
EMPLOYEE ATTENDANCE RECORD MANAGEMENT SYSTEM
CASE STUDY
ERNEST BAI KOROMA UNIVERSITY OF SCIENCE & TECHNOLOGY.
BY
NAME: AMADU JALLOH
A DISSERTATION SUBMITTED TO THE

DEPARTMENT OF PHYSICS AND COMPUTER SCIENCE
SCHOOL OF TECHNOLOGY
NJALA UNIVERSITY
In partial fulfillment for the award of Bachelor of

Science with Honors in Computer Science
December, 2021
Acknowledgement
First, I will want to express my obedience and gratitude to our creator God for giving me
strength to complete this dissertation work properly then I will like to express my special
thanks to my parents and elder sister for their continuous support of mental, physical and
financial during my study at Njala University.
I would especially like to thank my supervisor, Mr. Yayah L. Kamara, Senior Lecturer at
the Department of Physics and Computer Science, Njala University for his continuous
support and valuable ideas, knowledge with excellent comments to carry out this Dissertation
work. His guidance and encouragement have provided me the proper knowledge and right
way to go through the work. I would also like to thank our fellow academician fighting for
excellent in Njala University for their cordial help and support during our Dissertation work.
Special thanks to Mrs. Binta Jalloh, , for her relentless support and effort towards my
success. And special thanks to my Parents Mrs. Haja Isatu Jalloh, Alhaji Juldeh Jalloh,
Classmates, Friends, relatives and loved ones.
Copyright2021 JALLOH, Amadu – Njala University, Department of Physics & Computer Science , SL
Certification
This is to certify that the work embodied in this project report entitled Employee Attendance
Record Management System is the original work of Amadu Jalloh(21358) has not been
presented for an award of Bachelor’s Degree in this university or any other university.
I ……………………………………………………………., certify that this project was under

my supervision and that this presentation is a true account of the result obtain by them.
Supervisor
Mr. Yayah L. Kamara
Sign:…………………..
Date:…………………..
Dedication
This work is dedicated to God Almighty for giving me the opportunity, direction, protection,
knowledge and strength to accomplish this innovative piece of work.
I also stand to dedicate this work to Osman Jalloh as a blueprint for him to follow
,Mr. Mohamed Sheriff Bah, Mrs. Timmie Jalloh, Kadiejatu Shour, Dr. Maurice Baimba Kargbo and
Prof. Edwin J.J. Momoh for their relentless support and effort towards my success. And special
thanks to my parents, Classmates, Friends, relatives and loved ones , let my God in heaven
pour his blessings upon them and lengthen their days of life with prosperity and peace.
This day I pray to God Almighty for his blessing, wisdom, provision, courage, prosperity,
peace and love to us all and a welcoming blessed and elevated New Year 2022.
ABSTRACT
Attendance is an elementary and most vital criteria needed in all the education system. Over
the years the manual attendance system has been carried across most of educational
institutions. To overcome the problem of manual attendance, , this study focuses on
developing a web based attendance management system, which will be implemented on any
computer using Ernest Bai Koroma University as a case study.
The main purpose of this project are to carry out a careful study of the existing system of
attendance management and design a computerized method that will help to minimize storage
space and keep all records in the computer for future references. As attendance is a key
indicator when evaluating performance of an employee punctuality and regularity are the
factors employers seek from an employee. Most often commitment of a staff are assessed and
judged using those factors.
Contents
Acknowledgement .................................................................................................................................. 1
Certification ............................................................................................................................................ 2
Dedication ............................................................................................................................................... 3
ABSTRACT............................................................................................................................................ 4
CHAPTER ONE: INTRODUCTION ..................................................................................................... 8
OVERVIEW ....................................................................................................................................... 8
TECHNOLOGY USED: ................................................................................................................. 9
UNIQUE AND SPECIAL FEATURES ......................................................................................... 9
ERNEST BAI KOROMA UNIVERSITY OF SCIENCE AND TECHNOLOGY ............................ 9
PROBLEM STATEMENT ............................................................................................................... 10
AIM AND OBJECTIVES OF STUDY ............................................................................................ 10
AIM:.............................................................................................................................................. 10
SPECIFIC OBJECTIVES: ................................................................................................................ 11
SCOPE AND LIMITATION OF THE STUDY ............................................................................... 11
SCOPE: ......................................................................................................................................... 11
LIMITATION: .............................................................................................................................. 11
TECHNOLOGY USED: ............................................................................................................... 12
SIGNIFICANCE OF STUDY: ......................................................................................................... 12
METHODOLOGY: .......................................................................................................................... 13
LIST OF ABBREVIATIONS: .......................................................................................................... 13
CHAPTER TWO: INTRODUCTION .................................................................................................. 14
LITERATURE REVIEW ................................................................................................................. 14
ATTENDANCE MANAGEMENT SYSTEM PROCESS ............................................................... 14
PROPOSED SYSTEM ..................................................................................................................... 14
Advantages of Proposed System ................................................................................................... 14
REVIEW OF RELATED WORKS .................................................................................................. 15
SUMMARY ...................................................................................................................................... 17
CHAPTER THREE: METHODOLOGY ............................................................................................. 18
INTRODUCTION ............................................................................................................................ 18
ADVANTAGE OF WATERFALL MODEL ............................................................................... 18
USER-CENTERED REQUIREMENTS .......................................................................................... 19
DATABASE DEVELOPMENT METHODOLOGY ....................................................................... 19
MODEL OF DATABASE DEVELOPMENT ................................................................................. 22
Requirements gathering ................................................................................................................ 22
Database Analysis ......................................................................................................................... 22
The conceptual data model ........................................................................................................... 23
DATABASE DESIGN...................................................................................................................... 23
USING RELATIONAL THEORY FOR FORMAL DESIGN ......................................................... 24
Indexes .............................................................................................................................................. 27
users .................................................................................................................................................. 27
SUMMARY OF STEPS FOR DATABASE DESIGN ..................................................................... 28
CHAPTER FOUR:SYSTEM ANALYSIS AND DESIGN .................................................................. 30
INTRODUCTION ............................................................................................................................ 30
DESCRIPTION OF THE CURRENT SYSTEM ............................................................................. 30
SOFTWARE DEVELOPMENT LIFE CYCLE MODEL ................................................................ 30
REQUIREMENT SPECIFICATION ............................................................................................... 31
ANALYSIS OF THE CURRENT SYSTEM.................................................................................... 31
DRAWBACKS OF THE CURRENT SYSTEM .............................................................................. 32
DESCRIPTION OF THE PROPOSED SYSTEM............................................................................ 33
GOALS OF PROPOSED SYSTEM: ............................................................................................ 33
Advantages of Proposed System ................................................................................................... 34
REQUIREMENT ENGINEERING .................................................................................................. 34
FUNCTIONAL REQUIREMENTS ............................................................................................. 34
NON-FUNCTIONAL REQUIREMENTS ................................................................................... 35
SYSTEM DESIGN ........................................................................................................................... 35
METHOD OF DATA COLLECTION ............................................................................................. 37
SYSTEM DESIGN ........................................................................................................................... 37
CONSTRAINTS OF A SYSTEM .................................................................................................... 37
PROPERTIES OF A SYSTEM ........................................................................................................ 38
ELEMENTS OF A SYSTEM: .......................................................................................................... 39
TYPES OF SYSTEMS ..................................................................................................................... 40
ANALYSIS OF SYSTEM DESIGN ................................................................................................ 41
EMPLOYEE ATTENDANCE UPDATE INPUT FORM:............................................................... 45
EMPLOYEE ACCOUNT INTERFACE FORM:............................................................................. 46
DATA INPUT METHODS .............................................................................................................. 47
INPUT INTEGRITY CONTROLS .................................................................................................. 48
OUTPUT DESIGN ........................................................................................................................... 48
OBJECTIVES OF OUTPUT DESIGN: ....................................................................................... 48
OUTPUT INTEGRITY CONTROLS: ......................................................................................... 49
FORMS DESIGN: ............................................................................................................................ 49
TYPES OF FORMS:..................................................................................................................... 50
INTERFACE DESIGN ......................................................................................................................... 51
CHAPTER FIVE: SYSTEM IMPLEMENTATION AND TESTING ................................................. 56
Introduction:...................................................................................................................................... 56
SYSTEM IMPLEMENTATION ...................................................................................................... 56
HARDWARE AND SOFTWARE REQUIREMENT .......................................................................... 57
Hardware requirement ...................................................................................................................... 57
Software requirement ........................................................................................................................ 57
INSTALLATION OF HARDWARE AND SOFTWARE: .......................................................... 57
TESTING TECHNIQUES: ................................................................................................................... 58
SYSTEM TESTING: ........................................................................................................................ 58
SOFTWARE QUALITY ASSURANCE: ........................................................................................ 60
SOFTWARE QUALITY ASSURANCE (SQA): ............................................................................. 61
PROCEDURES AND STANDARDS: ............................................................................................. 61
SOFTWARE QUALITY ASSURANCE ACTIVITIES:.................................................................. 62
TRAINING: ...................................................................................................................................... 62
SYSTEM IMPLEMENTATION: ......................................................................................................... 63
DIRECT IMPLEMENTATION: ...................................................................................................... 63
PARALLEL IMPLEMENTATION: ................................................................................................ 63
PHASED IMPLEMENTATION: ..................................................................................................... 63
SYSTEM SECURITY AND CONTROLS: ..................................................................................... 63
HARDWARE AND SOFTWARE SECURITY: .............................................................................. 64
BACK-UP PROCEDURES: ............................................................................................................. 65
CHAPTER SIX:REVIEW AND MAINTENANCE: ........................................................................... 66
INTRODUCTION: ........................................................................................................................... 66
Corrective Maintenance: ............................................................................................................... 66
Perfective maintenance ................................................................................................................. 67
Adaptive Maintenance .................................................................................................................. 67
CHAPTER SEVEN:CONCLUSION AND .......................................................................................... 68
Introduction ....................................................................................................................................... 68
Conclusion ............................................................................................................................................ 68
Project Constraints ............................................................................................................................ 68
Recommendations ................................................................................................................................. 70
Hardware and Software Security ...................................................................................................... 70
Back-up Procedures .......................................................................................................................... 71
REFERENCE........................................................................................................................................ 72
CHAPTER ONE: INTRODUCTION
OVERVIEW
Attendance is an elementary and most vital criteria needed in all the education system. Over
the years the manual attendance system has been carried across most of educational
institutions. To overcome the problem of manual attendance, , this study focuses on
developing a web based attendance management system, which will be implemented on any
computer using Ernest Bai Koroma University as a case study.
The main purpose of this project are to carry out a careful study of the existing system of
attendance management and design a computerized method that will help to minimize storage
space and keep all records in the computer for future references. As attendance is a key
indicator when evaluating performance of an employee punctuality and regularity are the
factors employers seek from an employee. Most often commitment of a staff are assessed and
judged using those factors.
This system will lessen the constraint of browsing for records through numbers of lines
across numbers of pages amongst numbers of books to keep track of employee’s attendance
record with the existing file system by generating automated report in a user friendly
interface. The system will be built on the core values of robustness, security, responsively,
interactivity and compatibility
This system is being developed to maintain easy access of information from the database.
The application makes use of MySQL database, Hypertext Mark-up Language(HTML),
Cascading Style Sheet and PHP Framework. It tracks all the details of a Staff attendance from
morning log time, lunch and off time. The conventional method of taking attendance by file
system signing is very time consuming, insecure and hence inefficient.
The system will automatically count the number of absents and the percentage of present for
all the staff and their time in and out of office. This system provides a tedious work in
maintaining attendance records besides saving time to analyze every attendance list and
assuring the calculation made was error-free.
TECHNOLOGY USED:
 Framework: PHP, MySQL

 System Requirement
 Minimum RAM: 1 GB
 Hard Disk: 120 GB
 Processor: Intel Core i3 or higher
 Operating System: Windows OS, Linux OS, UNIX OS and Mac OS.
UNIQUE AND SPECIAL FEATURES
 Concrete Functionality
 Efficiency and Accuracy
 Framework
 Web service
ERNEST BAI KOROMA UNIVERSITY OF SCIENCE AND TECHNOLOGY
On the 17th day of September 2014, this was signed into law; the Universities
(Amendment) Act 2014 establishing the Ernest Bai Koroma University of Science
and Technology, comprising;
The Secretariat of the Ernest Bai Koroma University of Science and Technology, in
the heart of the Tonkolili District, with campuses in the three northern-district-
headquarter towns of Makeni (in Bombali), Portloko (in Portloko) and Magburaka (in
Tonkolili).
The university does not have a long history but the constituent institutions do have thriving
history and purpose built campuses to leverage though with a huge need for rehabilitation and
up scaling. the former women’s college and later Portloko teachers college that now constitute
the Portloko campus, The now Makeni campus was first established as a catholic college, the
St. Augustine’s college, and later became the Makeni teacher’s college , which then morphed
into the Northern polytechnic. Here morality was the key for all graduates of the college.
The former Islamic college that now houses the secretariat, and the former government
technical institute, otherwise referred to as the trade center in Magburaka, now the institute of
technical and vocational education and training in the faculty of engineering were the pride for
Islamic and technical education in the northern region.
These were all established to provide a holistic education for corpus, anima et spirit (body,
mind, and spirit).
PROBLEM STATEMENT
Based on the observation, there is no available employee attendance system at Ernest Bai
Koroma University of Science & Technology, They are still practicing the manual way of
taking daily attendance records. . Employees write their names and time in and out daily
without enough supervision on the attendance books and sign one by one.
However, the attendance book can be lost easily and the whole attendance process is tending
to human mistake. Consequently, data loss may happen and the data in attendance list might
be inaccurate due to deception.
As attendance is a key indicator when evaluating performance of an employee punctuality

and regularity are the factors employers seek from an employee. Most often commitment of a
staff are assessed and judged using those factors.
This system will lessen the constraint of browsing for records through numbers of lines
across numbers of pages amongst numbers of books to keep track of employee’s attendance
record with the existing file system by generating automated report in a user friendly
interface. The system will be built on the core values of robustness, security, responsively,
interactivity and compatibility.
AIM AND OBJECTIVES OF STUDY

AIM:
The main aim of this project is to carry out a careful study of the existing system of
attendance management and design a computerized method that will help to minimize
storage space and keep all records in the computer for future references.
SPECIFIC OBJECTIVES:
The objectives of developing Employee Attendance Record Management System are listed
below:
 Employee Attendance Record Management System will helps to analyze all the
attendance data inserted and then verify either each of the employee is following the
university attendance policy.
 To ensure accuracy and consistency in attendance processing.
 To offer insight on staff time in, time off and visual rich report.
 To store, access and manage employee attendance data for every staff.
 To generate and save unique EBKUST pin
 To capture employee login time in real time
 To store employee daily lunch period in real time
 To capture and store employee time in after lunch in real time
 To record employee logout time in real time
 The System will be capable of creating, modify and deletion of employee details.
 The system will generate report on the daily (a)daily, (b)monthly and (c)annual
attendance records
SCOPE AND LIMITATION OF THE STUDY

SCOPE:
This Software is mainly focused and only accommodates the computerized

attendance exercise due to the time and resource constraint confine within the Ernest
Bai Koroma University of Science & Technology, Office of the Deputy Registrar,
Makeni University Campus.
LIMITATION:
This Software is limited to cover only all the manual procedure involved during the
attendance management.
Due to security reasons the system is a standalone and completely offline system
hosted only locally on virtual private server (VPS).
This study had a lot of challenges as the project researcher was faced with the problem of
doing their preliminary investigations as listed below:
Rainy Season –
After the completion of our final comprehensive exams in August, there were
often torrential down pour throughout the country so little efforts was made to start the
project
work quite earlier.
Inadequate Financial Help –

Knowing very well that we are poor students and not attached to
any substantive job it was difficult to procure finances for this project work especially when
we
had to pay huge amount of money on transportation fare from Njala to our various residential
locations in the country.
TECHNOLOGY USED:
 Framework: PHP, MySQL

 System Requirement
 Minimum RAM: 1 GB
 Hard Disk: 120 GB
 Processor: Intel Core i3 or higher
 Operating System: Windows OS, Linux OS, UNIX OS and Mac OS.
SIGNIFICANCE OF STUDY:
With the growth in information technology, this study offers numerous values to the
attendance management process in Ernest Bai Koroma University of Science & Technology.
All the records will be stored on the computer with the help of the database program.
METHODOLOGY:
This Software will be implemented using MySQL database, hypertext mark-up language,
Cascading Style Sheet and PHP Framework which is a functional script that serve as the
Graphical User Interface (GUI).
LIST OF ABBREVIATIONS:
SQL = “Structural Query Language”
PHP = “Personal Homepage”
GUI = “Graphical User Interface”
CSS = “Cascading Style Sheet”
EBKUST = “Ernest Bai Koroma University of Science & Technology”
GB = “Gigabyte”
TB = “Terabyte”
OS = “Operating system”
HTML = “Hypertext Mark-up Language”
VPS = “Virtual Private Server”
CHAPTER TWO: INTRODUCTION
LITERATURE REVIEW
This chapter contains an overview of the broad area and review of developmental
technologies and platforms that will be used as well as the review of related works
concerning the Computerized Employee Attendance Record Management System.
Nowadays many education system are using a manual attendance monitoring system and
most of the time they accidentally loss their attendance sheet so they cannot properly monitor
the attendance of their Employees.
In this study, the aim is to provide a better way of monitoring the employee attendance of
Ernest Bai Koroma University of Science and Technology. This system will provide
Administrators an easy way of handling, recording and monitoring the daily attendance of
employees.
The system will provide an efficient way of record keeping activity.
The theoretical framework is the combine idea of the stated system.
The study of this procedure is important because many educational system encounter the
same problem during their attendance monitoring. It may become stepping stone in a more
organize and productive system of procedures in the future. This study wants to help other
educational system to be innovated involving the use of computerization inside the campus
and also for future proponents that will be involve in this kind of study.
ATTENDANCE MANAGEMENT SYSTEM PROCESS

In the present system all work is done on paper. The whole attendance session is stored in
register and at the end of the session the reports are generated on paper.
PROPOSED SYSTEM
To overcome the drawbacks of the existing system, the proposed system has been evolved.
This project aims to reduce the paper work and saving time to generate accurate results from
the employee’s attendance. The system provides with the best user interface. The efficient
reports can be generated by using this proposed system.
Advantages of Proposed System
 It is trouble-free to use.
 It is a relatively fast approach to enter attendance
 Is highly reliable, approximate result from user
 Best user Interface
 Efficient reports
REVIEW OF RELATED WORKS
 Web Based Coaching Institute Management System Mayuri Kamble et al

2018, “Coaching Institute Management System” software developed for an
institute has been designed to achieve maximum efficiency and reduce the time
taken to handle the storing activity. It is designed to replace an existing manual
record system thereby reducing time taken for calculations and for storing data.
The system is strong enough to withstand regressive daily operations under
conditions where the database is maintained and cleared over a certain time of
span. The implementation of the system in the organization will considerably
reduce data entry, time and also provide readily calculated reports.
 Rakhi Joshi et al (2017)., have developed a smart learning and attendance system
by implementing a QR code-based access to a central server built with .Net and
visual studio technologies. An android based app is also created which allowed
students to access contents from anywhere and anytime. The system also provided
for attendance report generation both to parents and individuals as messages.
 Y. K. Saheed et al (2016)., have developed an attendance management system

using barcode which is to be printed on the student’s identity card. By scanning
their card in the device, the attendance of the student is updated, which results in
reducing effort on paper work and it saves the valuable time.
 Saraswat and Kumar (2010), proposed fingerprint verification technique in taking

attendance. Their proposed system makes use of fingerprint verification by using
extraction of minutiae technique and system that automates the whole process of
taking attendance.
 Subpratatsavee et al. [6] (2015). Another project that consists of using NFC for
attendance is the Attendance System using NFC Technology and Embedded
Camera Device on Mobile Phone reported by Subpratatsavee et al. [6]. In their
study, they have increases the level of security of the previous research by making
use of the camera located on the back of every smartphone. To avoid students
passing around their NFC tag for attendance, the camera is used for verification that
whoever tags it must be the same person as in the photo, which of course would be
monitored by the lecturer or administrator. This project uses the concept of one
centralized server to store its data efficiently while all related mobile phones
connected to the server. Users can also import and export data effortlessly.
 Attendance Management System G.Gangagowri et al (2018)., this system is
used Way to SMS software. This software is used to send SMS easily to their
parent’s. This system can store their data about the students and those cares absent
student details. It is an efficient method to store the attendance in the Web Site
rather than wasting the paper. It also updates the student report directly on the server
reducing the faculty’s time on logging from the computer.
 Online Student Attendance System P. N. Garad et al (2017), in this project, we

gave access to three users i.e. Admin, Student, Others. This project is based on
client-server. Here, the serve is Tomcat and client is JSP. In this project teachers or
the admin will be filling attendance and sending message to the student who is
absent. They will have privilege to fill attendance form, update attendance form,
send message to the guardian’s account whose child is absent, also those attendance
is less than 75%, and they also have privilege to send message to the students whose
fees are pending. The staff can also view the message whenever they want and also
can modify the details of students. Parents have privilege to view attendance and to
view message sent by the teacher. Students also have their account with the
privilege to view message sent by the subject teacher and to view the attendance.
SUMMARY
In this paper I have analysed Seven (7) papers based attendance management system. Based
on the studied literature, I have found that there is still scope of improvement in the said
system. In terms of performance and efficiency, this project has provided a convenient
method of attendance marking compared to the traditional method of attendance system. By
using databases, the data is more organized. This system is also a user friendly system as data
manipulation and retrieval can be done via the interface, making it a universal attendance
system. Thus, it can be implemented in either an academic institution or in organizations.
CHAPTER THREE: METHODOLOGY
INTRODUCTION
In this chapter I will be giving a brief overview of the research methodology that I will be
using for this project.
Research methodology is the specific procedures or techniques used to identify, select,

process, and analyze information about a topic. In a research paper, the methodology section
allows the reader to critically evaluate a study’s overall validity and ability.
The research methodology section answers two main questions: How was the data collected
or generated.
There are various types of methodology like RAD (rapid Application Development),
Waterfall, Scrum, Agile to name but few. For this project I will be using the waterfall model.
Waterfall Model is a sequential model that divides software development into pre-defined
phases. Each phase must be completed before the next phase can begin with no overlap
between the phases. Each phase is designed for performing specific activity during the SDLC
phase. It was introduced in 1970 by Winston Royce.
The stages of waterfall project management generally follow this sequence:
 Requirements.
 Analysis.
 Design.
 Construction.
 Testing.
 Deployment and maintenance.
Progress flows in one direction, like a real waterfall.
ADVANTAGE OF WATERFALL MODEL

 Before the next phase of development, each phase must be completed.
 Suited for smaller projects where requirements are well defined.
 They should perform quality assurance test (Verification and Validation) before
completing each stage.
 Elaborate documentation is done at every phase of the software’s development
cycle.
 Any changes in software is made during the process of the development.
USER-CENTERED REQUIREMENTS
(Sutcliffe & Gulliksen, 2012)Requirements engineering (RE) is, as its name suggests, the
engineering discipline of establishing user requirements and specifying software systems.
There are many definitions of the term; however, they all share the idea that requirements
definition involves finding out what people want from a computer system and understanding
what their needs mean in terms of design. It is closely related to software engineering (SE),
which focuses more on the process of designing and developing the system that users want.
Perhaps the most concise summary comes from Boehm (1981), who believes that
requirements are designing the right thing, as opposed to SE's designing the thing right.
RE is closely related to user-centered design (UCD), where user requirements are seen as part
of the process of a design exploration, prototyping, and evaluation with the user, rather than
as the more linear “specify-design-implement” process favored in the SE community,
although these differences have become less marked with the growth in Agile development
methods (Beck, 1999) that advocate involving users with an approach based on scenarios (as
stories).
DATABASE DEVELOPMENT METHODOLOGY

Database development is just one part of the much wider field of software engineering, the
process of developing and maintaining software. A core aspect of software engineering is the
subdivision of the of development process into a series of phases, or steps, each of which
focuses on one aspect of the development. The collection of these steps is sometimes referred
to as a development life cycle. The software product moves through this life cycle
sometimes repeatedly as it is refined redeveloped) until it is finally retired from use. Ideally,
each phase in the life cycle can be checked for correctness before moving on to the next
phase. However, software engineering is a very rich discipline with many different methods
for the subdivision of the development process and a details exploration of the many different
ways in which development can be structured is beyond the scope of this course.
Here, I start with an overview of the waterfall model such as you will find in most software
engineering textbooks. (Do note that in this course I aim to present database development
principles and techniques that are common to many development methods, not just the
waterfall model) figure below illustrates a general waterfall model which could apply to any
computer system development. It shows the process as a strict sequence of steps where the
output of one step is the input to the next and all of one step has to be completed before
moving on to the next.
However, in reality there is usually some degree to refinement and feedback as the product
proceeds through the development stages (it would be real to find that each task is performed
perfectly and never needs revisiting - although that is pone possibility!).
Figure above shows a general Model of system development.
The waterfall model we can use figure as a means of identifying the tasks that are required,
together with the input and output for each activity. What is important is the scope of the
activities, which can be summarized as follows:
 Establishing requirements involves consultation with, and agreement among,

stakeholders as to what they want of a system, expressed as a statement of
requirements.
 Establishing
 Requirement
 Analysis
 Design
 Implementation
 Testing
 Maintenance
 Released system
 Initial system
 Statement of requirement
 System specification
 Design document
 Analysis start by considering the statement of requirements and finishes by producing

a system specification. The specification is a formal representation of what system
should do, expressed in terms that are independent of how it may be realized.
 Design begin with a system specification and produces documents and provides a
detailed description of how a system should be constructed.
 Implementation is the construction of a computer system according to a given design

document and taking account of the environment in which, the system will be
operating (for example specific hardware available for the development).
Implementation may be staged, usually with an initial system than can be validated
and tested before the final system release for use.
 Testing compares the implemented system against the design documents and
requirements specification and produces and acceptance report or , more usually, a list
of errors and box that require a review of the analysis, design and implementation
processes to correct (testing is usually the task that leads to the waterfall model
iterating through the life cycle).
 Maintenance involves dealing with changes in the requirements, or the

implementation environment, bug fixing or porting of the system to new
environments (for example migrating a system from a standalone PC to a UNIX
workstation or a networked environment). Since maintenance involves the analysis of
the changes required, design of a solution, implementation and testing of that solution
over the lifetime of a maintained software system, the waterfall life cycle will be
repeatedly revisited.
MODEL OF DATABASE DEVELOPMENT
Requirements gathering
Here we are concerned only with the requirements that relate specifically to the data.
Establishing requirements involves consultation with, and agreement among, all the users as
to what persistent data they want to store along with an agreement as to the meaning and
interpretation of the data elements.
The administrator plays a key role in this process as the overview the legal and ethical issues
with the University. The also determine the impact of the data requirements. The data
requirements document is used to agree requirements with users.
Database Analysis
Data analysis begins with the statement of fata requirements and then produces a conceptual
data model. The aim of analysis is to obtain a detailed description of the data that will suit
user requirements so that both high- and low-level properties of data and their use are dealt
with. These include properties such as the possible range of values that can be permitted for
attributes such as, in the Open University example for instance, staff Pin, staff name, and
staff department. The conceptual data model is focused on the data in a database, irrespective
of the eventual uses of that data in the user processor or implementation of the data in a
specific computer environment. Therefore, conceptual data model is concerned with the
meaning of structure of data, but not with the details affecting how they implemented.
The conceptual data model is a formal representation of what database should contain and
the constrains the data must satisfy. This should be expressed in terms that are independent of
how the model may be implemented. As a result, analysis focuses on ‘What is required?’ not
‘How is it achieved?’ Data analysis is a highly skilled task and the analysis has a specialized
role that is beyond the scope of this course where our focus is on design.
Consequently, I will not consider the analysis task in detail but I will assume that the
conceptual data model is the starting point for our database development.
ANALYZE THE DATA REQUIREMENTS, NOT THE IMPLEMENTATION

One of the hardest issues facing an analysis is to perform the analysis without prejudging
decisions about implementation. The analysis purely focused on the data requirements and
not about how those requirements are to be met, or the limitations that might be enforced by
the system chosen to host the database. Compromises and enforced limitations resulting from
an Attendance system or computer system should be dealt with during the implementation
phase. The requirements gathering and analysis tasks should be performed as if the
implementation environment will do everything that needs to be done to satisfy the
requirements being specified. Any compromises made at the analysis stage will affect the
usefulness of the system and may lead to it failing to meet the user requirement.
DATABASE DESIGN
Database design starts with a conceptual data model and produces a specification of a logical,
schema, this will usually determine the specific type of database system that is required, but
not the detailed implementation of that design. The relational representation is still
independent for any specific Attendance system; it is another conceptual data model.
We can use relational representation of the conceptual data model as input to the design
process. The output of the design stage is a detailed relational specification, the logical
schema, of all the tables and constraints needs to safety the description of the data in the
conceptual data model. It is during the design activity that choices are made as to which
tables are most appropriate for representing the data in a database. These choices must
consider various design critical including, for example, flexibility for change, control
of duplication and how best to represent the constrains. It is the tables defined by the logical
schema that determine what data are stored and how they may be manipulated in the system.
Database designers familiar with relational databases and SQL might be tempted to go
directly to implementations after they have produced a conceptual data model. However, such
a direct transformation of the relational representation to SQL tables does not necessarily
result in a database that has all the desirable properties: completeness, integrity, flexibility,
efficiency and usability.
USING RELATIONAL THEORY FOR FORMAL DESIGN

There will be occasions when it is necessary to prove formally that a system satisfies given
requirements. Using relational theory can allow a relational represent of a conceptual data
model to be analyzed rigorously. This stage, which is usually omitted in all but the most
exacting development environments (such as safety – critical system), involves using the
formal properties of the relational theory to mathematically prove properties of the
conceptual data model that would then be released in the database design.
Figure below summarizes the iterative (repeated) steps involved in database design, based on
the overview given. Its main purpose is distinguishing the general issue of what tables should
be used from the detailed definition of the constituent parts of each table – these tables are
considered one at a time, although they are not independent of each other. Each iteration that
involves a revision of the tables would lead to a new design; collectively they are usually
referred to as second – cut designs, even if the process iterates for more than a single loop
Links Media
Column Type Null Default Comments
to type
id (Primary) int(11) No
employee_id int(20) No
1 = AM IN,2 = AM
log_type tinyint(1) No out, 3= PM IN,
4= PM out
datetime_log datetime No current_timestamp()
date_updated datetime No current_timestamp()
Indexes
Uniqu Packe Colum Cardinalit Collatio Nul Comme

Keyname Type
e d n y n l nt
PRIMAR BTRE
Yes No id 27 A No
Y E
employee
Links Media
Column Type Null Default Comments
to type
id (Primary) int(20) No
employee_no varchar(100) No
firstname varchar(50) No
middlename varchar(20) No
lastname varchar(50) No
department varchar(100) No
position varchar(100) No
Indexes
Keyname Type
e d n y n l nt
PRIMAR BTRE
Yes No id 4 A No
Y E
users
Media
Column Type Null Default Links to Comments
type
id
int(20) No
(Primary)
username varchar(30) No
password varchar(100) No
firstname varchar(100) No
lastname varchar(100) No
11/14/21, 5:10 PM Print view - phpMyAdmin 5.1.1

localhost/phpmyadmin/index.php?route=/database/data-
dictionary&db=attendance&goto=index.php%3Froute%3D%2Fdatabase%2Fstructure 2/2
Indexes

Keyname Type
e d n y n l nt
PRIMAR BTRE
Yes No id 3 A No
Y E
SUPPORTING USERS AND USER PROCESS

Use of a database involves user processes (either application programmers or database tools)
which must develop outside of the database development. In terms of the three – schema
architecture we now need to address the development of the external schema. This will define
the data accessible to each user process or group of user processes. In reality, most DBMSs,
and SQL itself, do not have many facilities to support explicit definition of the external
schema. However, by using built – in queries and procedures, and with appropriate security
management, it is possible to ensure access to data by user process limited to a tailored subset
of entire database content.
In addition to ensuring that appropriate data access for each user process is achieve, the
database developer needs to address other user- related issues. Examples of each issues
include reporting of error conditions, constraint enforcement, automated processing using
triggers grouping of activities into transaction, defining database procedures and functions
and data security (in addition to the general database and user process access control).
SUMMARY OF STEPS FOR DATABASE DESIGN

Before we turn to consider implementation, you should note three general points that form
the basis of our design approach.
First, for a given conceptual data model it is not necessary that all the users requirements it
represents have to be satisfied by a single database. There can be various reasons for the
development of more than one database. However, if the collection of databases contains
duplicated data and users needed to access data in more than one database, then there are of
course further issues related to data replication and distribution.
Second, remember that one of the assumptions about our database development is that we can
separate the developments of a database from the development of user processors that make
use of it. This is based on the expectation that, once a database has been implemented, all
data required by currently identified user processes have been refined and can be accessed;
but we also require flexibility to allow us to meet future requirements changes. In developing
a database for some applications, it may be possible to predict the common requests that will
be presented to the database and so we can optimize our design for the most common
requests.
Third, at a detailed level, many aspects of database design and implementation depend on the
system being used. If the choice of system is fixed or made prior to the design task, that
choice can be used to determine design criteria rather than waiting until implementation.
That is, it is possible to incorporate design decisions for a specific system rather than produce
a generic design and then tailor it to the system during implication.
At the end of the design stage the logical schema will be specified by SQL data definition
language (DDL) statements, which is describe by the database that needs to implement to
meet the user requirements.
CHAPTER FOUR: SYSTEM ANALYSIS AND DESIGN
INTRODUCTION
Analysis can be defined as breaking up of any whole so as to find out their nature, function
etc. It defines design as to make preliminary sketches of; to sketch a pattern or outline for
plan. To plan and carry out especially by artistic arrangement or in a skillful wall. System
analysis and design can be characterized as a set of techniques and processes, a community of
interests, a culture and an intellectual orientation.
This chapter will provide the detail analysis of the current manual system of attendance
management system and problem of the current system. It also aimed to determine how the
new system will be achieved and fact finding technique used in the development of the
automated system of attendance management system.
DESCRIPTION OF THE CURRENT SYSTEM

The Existing system is a manual entry for the employees. Here the attendance will be carried
out in the hand written registers. 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. This application requires correct feed on input
into the respective field. Suppose the wrong inputs are entered, a line is drawn on the wrong
input which makes the hand writing ledger messy. So the employees find it difficult to use
the system.
SOFTWARE DEVELOPMENT LIFE CYCLE MODEL

The system development life cycle (SDLC) is a conceptual model used in project management
that describes the stages involved in an information development project, from the feasibility
study through maintenance of the completed software application.
For this project the Waterfall Development Model will be used.
Figure above shows a general Model of system development.
REQUIREMENT SPECIFICATION
It is the studying the current system and documenting its features for further analysis.
It is at the heart of system analysis where analyst documenting and describing system features
using fact finding techniques, prototyping and computer assisted tools.
ANALYSIS OF THE CURRENT SYSTEM

This is the problem-solving technique that decomposes a system into its component pieces
for the purpose of study how those components part will work and interacts to accomplish
their purpose.
System analysis is a detailed study of the various operations performed by the system and
their relationship within and outside of the system.
DRAWBACKS OF THE CURRENT SYSTEM
 Unreliable: This system (the existing system) can be manipulated since human beings
are directly involved in the process of recording and handling attendance record.
Human can be unreliable, deceived and show favoritism but in the proposed automated
system these are not possible
 Lack of immediate retrievals: the current system lacks the capacity of searching and
retrieving employee attendance records quickly from the flat paper file. The person who
is authorized with attendance management always move from one page to another to
find employees records and there is no guarantee that some of the records are recovered
quite quickly.
 Increase paper expenditure and work- It increases paper expenditure and work since
it is not an electronic system. The paper expenditure and work of the manual system is
far greater than the paper expenditure and work of the automated system.
 Lack of immediate information storage: There is still speculations that the attendance
office lacks backup storage systems that will retain employee’s records permanently or
when there is accidental loss of employee information on the spreadsheet platform and
how it will be recovered without this kind of storage device available.
 Lack of privacy: Privacy is not considered in the manual system, important and private
information may be made open during the process of recording attendance, as many
people (more than two persons) are involved
 Error prone: Human are likely to fail or make error. One of the most significant
downsides of a manual data entry is human error. When you rely on a person to
correctly transfer data from one place to another, mistakes are to be expected. Eye
fatigue, inattentiveness and hard to read information make it a recipe for error.
DESCRIPTION OF THE PROPOSED SYSTEM
GOALS OF PROPOSED SYSTEM:

To overcome the drawbacks of the existing system, the proposed system has been evolved.
This project aims to reduce the paper work and saving time to generate accurate results from
the employee’s attendance. The system provides with the best user interface. The efficient
reports can be generated by using this proposed system.
 Accuracy: the level of accuracy in the proposed system will be higher. All operation
would be done correctly and it ensures that whatever information is coming from the
system is accurate and valid.
 Reliability: The reliability of the proposed system will be high due to the above stated
reasons. The reason for the increased reliability of the system is, information is received
from employee to attendance office directly without waste of time.
 No redundancy: In the proposed system utmost care would be that no information is

repeated anywhere, in storage or otherwise. This would assure economic use of storage
space and consistency in data stored.
 Immediate retrieval of information: The main objective of proposed system is to

provide for a quick and effective retrieval of information from storage. Employees
record would be available from Employee Attendance records as required by the user.
 Mass storage: The computers adopted in this department will have the capability of
storing massive amount of records, hence the storage space is measured in Tera Bytes.
Meaning the system can support documentations for a prolong length of time.
 User Friendly Software: - the system would have a user-friendly interface and allow
Admins to easily interact with the command buttons to execute instructions as needed.
 Dedicated to Registry: This solution that would be implemented will exceptionally be

operated in the registry office by whom authorities and permissions are given. Meaning
the software is confined only to this department.
Advantages of Proposed System
 It is trouble-free to use.
 It is a relatively fast approach to enter attendance
 Is highly reliable
 Generates report on a daily, weekly, and monthly basis
 Best user Interface
 Efficient reports
REQUIREMENT ENGINEERING
(Sutcliffe & Gulliksen, 2012)This is also known as Requirement Analysis; it is the process of
determining user expectations for a new or modified system. This is divided into Functional
and Non-Functional Requirements.
FUNCTIONAL REQUIREMENTS
This defines the function of a system or its component. It deals with what the system should
do or provide for users. Functional requirements for this software includes:
 The Super Admin Shall be able to Login into the System using the unique username
and password.
 The Super Admin shall be able to add another Admin by creating another account
with a unique username and password.
 The Super Admin shall be able to create an account for every employee with a unique
Pin. The system generates pin for employee automatically so there is no duplicate Pin
in the system.
 The Admin shall be able to authenticate Employee Pin in the morning hours, lunch
hours, After lunch and off time.
 The Admin shall be able to check attendance record, generate report of employee
attendance status and manage attendances records.
 The attendee shall provide all the necessary registration details.
NON-FUNCTIONAL REQUIREMENTS
Non-Functional requirements are requirements that specifies criteria that can be used to judge
the operation of a system, rather than specific behaviors. Non-Functional requirements for
this software includes:
 The System Should be easy to use by the Admin, and employees. And should be
Organized in a way that user errors are minimized.
 The System Should Be Secure from Unauthorized Usage and Access.
SYSTEM DESIGN
(Nym, 2021)System design is the process of defining the architecture, components, modules,
interface, and data for a system to satisfy specified requirement. this could also be seeing as
the application of the knowledge of System Analysis and Design to product development.
System design is said to be the descriptive in nature of what the system is and what it does and
shows how the expected program is to be operated.
System
EMPLOYEE ADMIN/REGISTRY LOGIN

+FirstName: Varchar
+Name: Varchar +Username: Varchar
+MiddleName: Varchar
+LastName: Varchar +Password: Varchar +Password: Varchar

+Department: Varchar +Email
+Address: Varchar
+Login ()
+Gender: Varchar
+Email: Varchar +Register ()

+Add Employee ()
+Register ()
+Check Attendance ()
+PRINT Report ()
+Delete Employee ()
+Add Subject, Class &
Exams ()
Copyright2021 JALLOH, Amadu – Njala+Login () Department of Physics & Computer Science , SL
University,
Fig 1. ERD Diagram
METHOD OF DATA COLLECTION
(BAH, 2019) A thorough investigation of the current system was carried out in order to
obtain detailed information about the application area to be designed. In the course of our
findings, several
effective methods of information gathering or data collection were employed which include:
interviewing the attendance officers; HR; discussion with pertinent stakeholders of the
system such
as the HODs and lecturers; evaluation and inspection of relevant documents.
SYSTEM DESIGN
It is a process of planning a new business system or replacing an existing system by defining
its components or modules to satisfy the specific requirements. Before planning, you need to
understand the old system thoroughly and determine how computers can best be used in order
to operate efficiently.
System Design focuses on how to accomplish the objective of the system.
System Analysis and Design (SAD) mainly focuses on -
 Systems
 Processes
 Technology
The word System is derived from Greek word System which means an organized relationship
between any set of components to achieve some common cause or objective.
A system is “an orderly grouping of interdependent components linked together according to
a plan to achieve a specific goal.”
CONSTRAINTS OF A SYSTEM
A system must have three basic constraints -
 A system must have some structure and behaviour which is designed to achieve a
predefined objective.
 Interconnectivity and interdependence must exist among the system components.
 The objectives of the organization have a higher priority than the objectives of its
subsystems.
For attendance, traffic management system, payroll system, automatic library system, human
resources information system.
PROPERTIES OF A SYSTEM
A system has the following properties -
a. Organization
Organization implies structure and order. It is the arrangement of components that helps to
achieve predetermined objectives.
b. Interaction
It is defined by the manner in which the components operate with each other.
For attendance, in an organization, Registry department must interact with Lecturers, HODs,
Deans, Finance department, Exam department, ICT department and General Duties
department.
c. Interdependence
Interdependence means how the components of a system depend on one another. For proper
functioning, the components are coordinated and linked together according to a specified
plan. The output of one subsystem is the required by other subsystem as input.
d. Integration
Integration is concerned with how a system component are connected together. It means that
the parts of the system work together within the system even if each part performs a unique
function.
e. Central Objective
The objective of system must be central. It may be real or stated. It is not uncommon for an
organization to state an objective and operate to achieve another.
The users must know the main objective of a computer application early in the analysis for a
successful design and conversion
ELEMENTS OF A SYSTEM:
The following diagram shows the elements of a system –
A. Outputs and Inputs
The main aim of a system is to produce an output which is useful for its user.
 Inputs are the information that enters into the system for processing.
 Output is the outcome of processing
B. Processor(s)
 The processor is the element of a system that involves the actual transformation
input into output.
 It is the operational component of a system. Processors may modify the input

either totally or partially, depending on the output specification.
 As the output specifications change, so does the processing. In some cases,

input is also modified to enable the processor for handling the transformation.
C. Control
 The control element guide the system.
 It is the decision–making subsystem that controls the pattern of activities

governing input, processing and output.
 The behaviour of a computer System is controlled by the Operating System

and software.
In order to keep system in balance, what and how much input is needed is determined by
Output Specifications.
D. Feedback
 Feedback provides the control in a dynamic system.
 Positive feedback is routine in nature that encourages the performance of the

system.
 Negative feedback is informational in nature that provides the controller with

information for action.
E. Environment
 The environment is the “super system” within which an organization operates.
 It is the source of external elements that strike on the system.
 It determines how a system must function. For eg, vendors and competitors of
organization’s environment, may provide constraints that affect the actual
performance of the business.
F. Boundaries and interface
 A system should be defined by its boundaries. Boundaries are the limits that
identify its components, processes, and interrelationship when it interfaces with
another system
 Each system has boundaries that determine its sphere of influence and control.
 The knowledge of the boundaries of a given system is crucial in determining

the nature of its interface with other systems for successful design.
TYPES OF SYSTEMS
The systems can be divided into the following types -
Physical or Abstract Systems
 Physical systems are tangible entities. We can touch and feel them.
 Physical System may be static or dynamic in nature. For eg, desks and chairs are the
physical parts of computer center which are static. A programmed computer is a
dynamic system in which programs, data, and applications can change according to the
user's needs.
 Abstract systems are non-physical entities or conceptual that may be formulas,
representation or model of a real system. Open or close systems.
 An open system must interact with its environment. It receives inputs from and
delivers outputs to the outside of the system. For eg, an information system which must
adapt to the changing environmental condition.
 A close system does not interact with its environment. It is isolated from environmental
influence. A complete closed system is rare in reality.
The scope of this chapter is to examine and layout of the critical elements of the design of the
new system, the sequence in which they will be carried out and investigate the abstract
represented representation of data flows, input and outputs of the system in relation to actual
inputs and output processes of the new system.
ANALYSIS OF SYSTEM DESIGN

System analysis contains details that are necessary for the implementation of the system. It
focuses on changing the performance requirement into design specification. This aspect is
concerned with how to approach the process of designing. System design is the most crucial
phase in the development of a system and it involves two parts.
 The logical design, which is arrived at as a result of systems analysis and;

 The physical desgn, which is derived from the logical design.
System also called synthesis is a complementary problem-solving technique that reassembles

a system’s component part back into complete system. Also, system design is a specification
or construction of a technical based solution for business requirements identified in systems
analysis.
System design is defined as those tasks that focus on the detail specification of the computer-
based solution. Normally the design proceeds into two stages, namely;
 Preliminary Design: here the features of the new system are specified. The cost of
implementing these features and benefits to be derived are estimated. In the case the
web or online hospital Management system I have deployed on the cloud. It is of course
cost effective to use the cloud platform for this solution because of many benefits. It is
Easy to adapt to the use of cloud anywhere anytime as long as internet is available. the
gap of isolation will be between staff, patient is close. One body is mindful about
electricity to run your resources and less burden on the maintenance of the computers
and servers on the cloud.
 Structural Design: here the computer-based work begins in full swing; designers come
up with a structured design in the form of a blue print of a computer system solution to
the specific problem taking into consideration user requirements. At this point, the
researcher can clearly see a mapping out process of inputs, outputs, databases object
forms and commence with codification scheme and process specification being drawn
up in details.
 Logical Design: This is the process of taking the user requirement that are gathered in
the system analysis phase and mapping to their respective business entities and then
processes.
Logical model shows what a system does, the logical systems specify users’ needs at a level
of detail that virtually determines the information flow into and out of the system, and require
data sources. Logical design can also be related to the abstract representation of the data flow.
There are three major steps involved in the creation of the login design;
1. Evaluate alternatives
2. Prepare design specifications
3. Prepare reports
Physical Design:
The physical design as the name s implies has to do with the production working system
by defining specifications that tells the programmer what to do the physical design
relates to the actual input and output processes of the system. The physical dictates and
laid down terms of how the data is entered into the database through an existing
interface. It posits that when users intend to access the data, some authorization and
authentical issues need to be resolved order wise the privilege granted to access the
database will be denied. There should also be techniques that would help display the
output from this solution.
This the physical portion of the design generally is apportioned into three phases;
1. User interface design
2. Data design
Process design
 USER INTERFACE DESIGN

User interface design is concerned with how users add information to the system and
how the system presents information back to them. The general strategy used in the
design of the program includes the manner in which the user interface is landscaped
and when using it to manipulate the device.
 Data design is about discovering and completing defining your application’s
data characteristics and processes. Data design is a process of gradual
refinement, from the coarse from where you decipher what data the application
requires to the precise data structures and processes that provide it. With a good
data design, your application’s data access is fast, easily maintain and can
gracefully accept future data enhancement.
The process of data design includes identifying the data, defining specific data
types and storage mechanisms and ensuring data integrity by using business
rules and other run time enforcement mechanisms. In data design, the researcher
will consider the following:
 Data identification: this describes the process of discover how your application
will use the data.
 Data definition: explains the general process of defining tables, rows, columns,
data types, keys and relationships.
 Data integrity: discusses some important ways to provide data integrity,

including normalization, business rules. Referential integrity, and data
validation.
 Data design cautions: presents some real-world conflicts that influence data
design decisions.
Program Design:
A program is a set of instructions which permits the computer hardware to manipulated and
execute instruction sets that is invoked on the input data to produce a desired output
(information) in the forms of textual mode, sound, graphics, numeric, satellite maps and
multimedia or video context. The definition of Design in software concept goes far beyond
the normal understanding in English dictionary, and are place into the following categories;
a. Input Design,
b. Output Design
c. File Design and Interface design.
Each of these categories will be discuss
1) Input Design
In an information system, input is the raw data that is processed to produce output. During the
input design, the developers must consider the input devices such as PC, MICR, OMR, etc.
Therefore, the quality of system input determines the quality of system output. Well-designed
input forms and screens have following properties –
 It should serve specific purpose effectively such as storing, recording, and retrieving
the information.
 It ensures proper completion with accuracy.
 It should be easy to fill and straightforward.
 It should focus on user’s attention, consistency, and simplicity.
All these objectives are obtained using the knowledge of basic design principles regarding –
 What are the input needed for the system?

 How end users respond to different elements of forms and screens.
EMPLOYEE ATTENDANCE UPDATE INPUT FORM:

This is the form where admins can update employee attendance in to the system by using the
employee’s Pin provided by the system, so that the updated employee record can take effect
in the attendance database.
Figure 2: Employee Attendance Update Input Form
EMPLOYEE ACCOUNT INTERFACE FORM:
This is the form where admins enter employee’s attendance record in to the system and
automatically generate Login in Pin for employee. The Pin generated will be unique for each
employee which would be used to authenticate the attendance of employees.
Figure 3: Employee Account Interface Form
DATA INPUT METHODS

(Ogbonna, 2019)It is important to design appropriate data input methods to prevent errors
while entering data. These methods depend on whether the data is entered by employee in
forms manually and later entered by admins in to the system, or data is directly entered by
employee in to the system.
A system should prevent user from making mistakes by –
 Clear form design by leaving enough space for writing legibly.

 Clear instructions to fill form.
 Clear form design.
 Reducing key strokes
 Immediate error feedback.
Some of the popular data input methods are –
 Batch input method (offline data input method).

 Online data input method.
 Computer readable forms.
 Interactive data input.
INPUT INTEGRITY CONTROLS
Input integrity controls include a number of methods to eliminate common input errors by
end users. They also include checks on the value of individual fields; both for format and the
completeness of all inputs.
Audit trails for data entry and other system operations are created using transaction logs
which gives a record of all changes introduced in the database to provide security and means
of recovery in case of any failure
OUTPUT DESIGN
The design of output is the most important task of any system. During output design,
developers identify the type of outputs needed, and consider the necessary output controls
and prototype report layouts.
OBJECTIVES OF OUTPUT DESIGN:

The objectives of input design are –
 To develop output that serves the intended purpose and eliminates the production of
unwanted output.
 To develop the output design than meets the end users’ requirements.
 To deliver the appropriate quality of output.
 To form the output in appropriate format and direct it to the right person.
 To make the output valuable on time for making good decisions.
Let us now go through various types of outputs –
 EXTERNAL OUTPITS:
Manufacturers create and design ewxternal output for printers. External outputs enable
the system to leave the trigger action on the part of their recipients or confirm action to
their recipients.
Some of the external output are designed as turnaround outputs, which are implemented
as a form and re-enter the system as an input.
 INTERNAL OUTPUT:
Internal outputs are present inside the system, and used by end-users and managers.
They support the management in decision making and reporting.
There are three types of reports produced by management information.
 Detailed Reports - They contain present information which has almost no filtering or
restriction generated to assist management planning and control.
 Summary Report – They contain trends and potential problems which are categorized
and summarized that are generated for managers who do not want details.
 Exceptional Report – They contain exceptions, filtered data to some condition or
standards before presenting it to the manager, as information.
OUTPUT INTEGRITY CONTROLS:

Output integrity controls include routing codes to identify the receiving system, and
verification messages to confirm successful receipt of messages that are handled by network
protocol. Printed or screen-format reports should include a date/time for report printing and
the data. Multipage reports contain report title or description, and pagination. Pre-printed
forms usually include a version number and effective date.
FORMS DESIGN:
Both forms and reports are the product of input and output design and are business document
consisting of specified data. The main difference is that forms provide fields for data input
but reports are purely used for reading. For example, order forms, employment and credit
application, etc.
During form designing, the designers should know –
 Who will use them?

 Where would they be delivered?
 The purpose of the form or report.
 During design, automated design tools enhance the developer’s ability to prototype
forms and reports and present them to end-users for evaluation.
A good form design is necessary to ensure the following:
 To keep the screen simple by giving proper sequence, information, and clear captions
 To meet the intended purpose by using appropriate forms.
 To ensure the completion of form with accuracy
 To keep the form attractive by using icons, inverse video, or blinking cursors etc.
 To facilitate navigation
TYPES OF FORMS:
I. Flat Forms
 It is a single copy form prepared manually or by a machine and printed on a
paper. For additional copies of the original, carbon papers are inserted between
copies.
 It is a simplest and inexpensive form to design, print, and reproduce, which
uses less volume.
II. Unit Set/Snap out Forms
 These are papers with one-time carbons interleaved into unit sets for either
handwritten or machine use.
 Carbons may be either blue or black, standard attendance log medium intensity.
Generally, blue carbons are best for handwritten forms while black carbons are best
for machine use.
III. Continuous strips Fan/fold
 These are multiple unit forms joined in a continuous strip with
perforations between each pair of forms
 It is a less expensive method for large volume use.
IV. No Carbon Required (NCR) Paper
 They use carbonless papers which have two chemical coatings (capsules), one
on the face and the other on the back of a sheet of paper.
 When pressure is applied, the two capsules interact and create an image.
INTERFACE DESIGN
Figure: User login form

User Profile: Used to authorize permission to the user to their specified
Admin Profile: Used to authorize permission to the Attendance Officer who has access to all
pages.
Password: a secret code used to authenticate permission to the users
CHAPTER FIVE: SYSTEM IMPLEMENTATION AND TESTING
INTRODUCTION:
The system implementation simply means putting the new system into action within the
institution.
The entire implementation process therefore involves the conversion of the manual system
being used to a computerized system and thereby helps to ascertain user’s participation.
Implementation is a process of ensuring that the system is operational. It involves
 Constructing a new system from scratch.

 Constructing a new system from the existing system
SYSTEM IMPLEMENTATION
It is the process of:
1. Defining how the information system should be built (i.e. physical system design)
2. Ensuring that the information system is operational and use.
3. Ensuring that the information meet quality standard (i.e. quality assurance)
SYSTEM IMPLEMENTATION
Implementation
planning
Develop and test Prepare site; install Select and train

software program and test hardware personnel
Complete Test system

documentation
Conversion
HARDWARE AND SOFTWARE REQUIREMENT
Hardware requirement
 Processor: Minimum Intel core 2 or higher (1.6GHZ); AMD Athlon 64 x2
Recommended 2Ghz or more
 Hard Drive: Minimum 200GB or higher recommended.
 Memory (RAM): Minimum 2GB or more recommended
Software requirement
 Operating System: Windows 10
 Browser: Chrome, Firefox or Microsoft Edge.
 Server: XAMPP
INSTALLATION OF HARDWARE AND SOFTWARE:

The installation of hardware and software will be done by the system analyst with the help of
the Administration as well as some of the potential users as this will make them feel as part of
the system.
There are some factors to be considered after the installation of the software and hardware in
order to have a successful implementation. These factors are as follows:
1. Location of terminal:
The system should be in the right condition so as to meet performance criteria, condition
such as dust free room or air condition room and room less susceptible to fire and
natural disaster.
2. Power supply:
The system should have a table power and enough power sockets so that accident such
as tripping over power cord can be avoided, stable power supply will prevent
distribution in processing and cause damage to the system by fluctuation of power
supply. This can be further ensure by the use of uninterrupted power supply (UPS).
3. Test Plan:
This is very essential. It is carefully planned to take into considerations various
scenarios that may occur in real life. Otherwise, there would be damage that the new
system will go with faults that might prove difficult or costly to correct.
4. Trying to Outwait the System:
This is done by passing wrong data and observing how the system will respond.
TESTING TECHNIQUES:
 White Box Testing: this is carried out by programmer as he or she has access to the
source code, to check whether the structure is effective or whether there are logical
errors.
 Black Box Testing: this is usually not done by the programmer and there is no access
to source code. The person will test the system using the user interface, testing the
functionality of the system against it specifications.
SYSTEM TESTING:
Black box testing is use in this system. It involves testing the system as a whole under
realistic condition, to ensure that the system works.
It was conceive that system testing, is also referred to as system test is the processing in
which a quality assurance (QA) team evaluates how the various components and modules of
an application or system interact together in the full, integrated application or system.to
evaluate the system compliance with its specified requirements.
The purpose of the test is to detect any inconsistency, between the assemblage requirements.
There are various stages in system testing.
a. Performance Testing:
Performance testing is a software testing process used for testing the speed, response
time, stability, reliability, scalability and resource usage of a software application under
particular workload.
Testing the system at peak load means putting the system under stress and trying to find
out whether it will work properly or fail.
b. Usable Testing:
Compare the developed system with user’s expectation and needs.
Usability test focuses on measuring a human made product’s to meet intended
purpose/s.
c. Time on Test:
How long does it take Admin to complete basic tasks?
d. Accuracy:
System accuracy tests are perform to ensure the accuracy of the system and recording
instrument in each module. How many mistakes did users made and were they fatal or
recover with the right information?
e. Recall:
Does users (staff) remember their Pin afterward?
f. Emotional response:
How does the users feel about the task completed, confident or stressed?
g. User Acceptance Testing (UAT):
The focus is to detect and fix major bugs, i.e. bugs that will cause the system not to run
at all or those that will cause the system to run and abnormally end. If the software runs
well under simulated testing environment, then it will also run well when using it on
real life scenarios.
h. When all parties are satisfied that the new system meets the required standards, the
system is formally accepted for installation.
SOFTWARE QUALITY ASSURANCE:
The quality of an application is determined by the following factors:
 Reliability
 Stability
 Portability
 Maintainability
 Efficiency
 Accuracy
 Error tolerance
 Testability
 Access control and audit.
a. Reliability:
Reliability is the probability that a system performs correctly during a specific time
duration. During this correct operation:
 No repair is required or performed
 The system adequately follows the defined performance specifications.
It is to be proven that the system is reliable at all times and even when left for a period of
time, it can be relied upon to perform the same task constantly with the same outputs.
b. Stability:
A system is said to be stable, if its output is under control. Otherwise it is said to be
unstable. A stable system produces a bounded output for a given bounded input. The
system also provides information and more importantly the Admin knows where
exactly to go in order to access specific record.
c. Portability:
The attendance report will be saved on digital video diskette (DVD) and flash drive,
after it has been compressed, and transferred, to any other machine. It will run on
Compaq, IBM, Dell. HP, and Toshiba etc.
d. Maintainability:
Maintainability is the probability of performing a successful repair action within a given
time.
Maintenance measure the ease and speed with which the system can restore operational
status after a failure occur.
e. Efficiency:
In this system, the computer resources used are minimum. It takes up to
2GB of storage space. Records can be retrieved very quickly; function can be performed
within a few seconds whilst waiting for result.
f. Accuracy:
The performance of the system is very accurate and also all data produce by
The system is accurate.
g. Error tolerance:
This is to ensure that nothing is overloaded, each common button/link is individually
checked, identify errors and the result of clicking is detected.
h. Testability:
This is to eliminate program error of bugs to ensure that the system performs it
functions. The ability to edit, delete and repeat.
SOFTWARE QUALITY ASSURANCE (SQA):

Is a planned and the systematics approach to:
 The evaluation of the quality of software product standards, processes and procedures
 The adherence to the software product standards, processes and procedures
(Kuna, n.d.)Software quality assurance seeks to guarantee that standards and procedures are
established and followed throughout the system development lifecycle, complying with
agreed – upon standards and procedures are evaluated through processing, monitoring,
product evaluation and audits.
PROCEDURES AND STANDARDS:

Standards are the established criteria to which the software products are compared. They are
documentation, standards, design standards and code standards.
Procedures are the established criteria against which development and control processes are
compared. They are explicit steps to be followed in carrying out the process.
SOFTWARE QUALITY ASSURANCE ACTIVITIES:
 Product evaluation: this is the activity that assures that software products reflect the
requirement of the applicable standards.
 Process monitoring: this ensures that appropriate step to carry out the process being
followed.
 Audit: this is a look at a process or product and compare them with established
procedure and standard.
The problem of identifying quality software could be tackled by the institution by using
software quality techniques and by improving the quality of their data.
TRAINING:
The system Admin involve in the implementation has to be adequately and toughly trained in
order to benefit from the new system.
Effective training must include orientation to new policies and operations as well as the
hardware and software skills needed to be used in the system. The training meant to make
system Admin efficient in using the equipment and the software with particular reference, to
the application that has been developed.
Training should be planed and scheduled to occur just after the user acceptance test and more
efficiently on the job. This should be done in line with the system analyst who design the
problem.
Training can be taken in the following forms:
 Lecturers and seminars

 Discussions and meetings following a formal lecture
 Disk base tutorial
 Training provided by third party installation
 User manuals and other standardize documentation
 Direct hands on experience by staff to familiarize with the system.
SYSTEM IMPLEMENTATION:
This involves basically the conversion of the current manual file to a logical file required by
the new system. It is an important stage in the system implementation process.
It is difficult and time-consuming process and extreme care should be taken to avoid
inputting wrong data into the system. This can be accomplished using either of the following:
DIRECT IMPLEMENTATION:
With direct conversion, the old system cases to abruptly and is replaced by the new one. This
method is dangerous and potentially the most expensive. The disadvantage of this system is
lacking current result from the old system to compare with those from the new system once
conversion has occurred in order to identify shortcoming.
PARALLEL IMPLEMENTATION:
With this method, the old system and the new system are operated simultaneously for a while
until enough confidence is built in the new system. Both are compared for similarities and
discrepancies. If there are discrepancies the old system continues to work until things are
rectified. The advantage of this method provides securities against failure of the system, but
the negative side of this system is costly in terms of staff time and resources.
PHASED IMPLEMENTATION:
This method is suited to systems that are built by modules or are to be installed at several
systems within the university. It is like pilot implementation except that at the start of the new
system it is introduced incorrectly in stages.
SYSTEM SECURITY AND CONTROLS:

System security could be defined as the protection of hardware and software from accident or
deliberate threats, which might cause unauthorized modification, disclosure or destruction of
data.
Therefore, every system must provide built in features for security and integrity of data.
System security: this take into cognizance the security and safety of the activities and
resource by protecting it from accident or unforeseen damage.
Unforeseen damage is cause by environmental disasters and political or civilian confusion

such as fire, storm, heavy wind, war, riot, heat and smoke etc.
Preventive measures most put in place and detectors should be installed around the computer
room as well as fire extinguishers in case there is fire breakout.
This system should also be protected against viruses.
(Jr, n.d.)A virus is a deviant program which causes the computer to deviate from it normal
action. They attach themselves to executable program file with the intention to corrupt the
files. They can corrupt the system by destroying the data and automatically crash the entire
computer system.
To protect the new system from viruses, antivirus software should be install on the system
and it must be regularly updated as and when demanded.
Every external storage medium must be properly scanned for viruses before installing into the
system.
HARDWARE AND SOFTWARE SECURITY:

These are the security measure that will be put in place to protect both the hardware and
software from damage.
The computer room should be air-conditioned or properly ventilated because computer

generate a lot of heat and needs a cool environment to work accurately and to avoid break
down in the event of power failure, the computers must be connected to uninterrupted power
supply (UPS) which will be a temporary source of power in case there is a power cut whilst
the system would be saving data and after that should be shut down systematically.
 Data Security:
Data security means the process of protecting data from unauthorized access and data
corruption through its lifecycle. Data security includes data encryption, hashing,
tokenization and key management practices that protect data across all applications and
platforms.
 Data Integrity:
Data integrity guarantees and secure the searchability and traceability of your data to
its original source. Data performance and stability also increases when you ensure
effective data accuracy and data protection. Maintaining the integrity of data and
ensuring the completeness of data is essential.
 System Security:
This is the proper functioning of hardware and software. The users of this system must
make sure that the operations of the system should always conform to its design
specification, and that should not change or made to act incorrectly.
 Confidentiality:
Privacy is required in the system. In this case user Pin were created for each user login
(staff) and Admin creates the user Pin.
 Physical control:
Physical security control, to include deterrent, detective, and preventive measures, are
the means to put in place to mitigate physical security issues. Deterrent aim to
discourage those who might violate the security, detective measures alert us to or allow
us to detect when there is a potential intrusion, and preventive controls actually prevent
intrusions from taking place. In isolation, none of these controls is a complete solution,
but together, they can put us on a much stronger footing for physical security control.
BACK-UP PROCEDURES:
Back-up procedures should not be neglected in a computerized information system. It is wise
and important to have multiple copies of the database and forms of the system. This should
be kept in another location or area different from the database in case of any unforeseen
disaster that might occur.
CHAPTER SIX: REVIEW AND MAINTENANCE:
INTRODUCTION:
Upon implementing the new system, review and maintenance of the system should be
carrying out in order for the system to operate efficiently.
The review stages are useful which means to eliminate faults and errors. There will also be
changes to some activities and procedures as well as system functions, and also procedures
may need to be modified accordingly.
(Publication, n.d.)Regardless of how well the system is designed, constructed and tested the
system or application may have errors or bugs which will inevitable occur. Some Bugs will
be cause by miscommunication of requirement. Design flaws will cause otherwise. Others
will be caused by unanticipated misuse of the programs. In all these situation, corrective
measures should be taken.
These corrective measures are called system or program maintenance.
The fundamental objectives of system maintenance are listed below:
 To make predictable changes to existing programs to correct errors that were made
 During system design and implementation. Therefore, we exclude enhancement and
new requirements from these activities.
 To preserve those aspects of the system or program that are correct. In order to
achieve these objectives, you should understand the programs you are fixing and the
applications in which those programs participate.
There are three types of maintenance intruded in this system:
 Corrective maintenance
 Perfective maintenance
 Adaptive maintenance
Corrective Maintenance:
This is concern with the immediate action in response to a problem. A fault may arise which
will prevent the system software from running. The process of corrective maintenance will
solve the problem. This is done to see that the system is ok.
Perfective maintenance
This attempt to make the software operate more effectively by improving the software
efficiency and enhance its performance. Much perfective maintenance result from users
request as the user will start to use the system. The need for some of these types of
maintenance may be reduced, by better system analysis and design.
Adaptive Maintenance
Here the maintenance of the new system needs to be developed. It is carried out to take
account of anticipated problem s or changes in the processing environment. For example,
changes in the employee number require a complete change in the employee registration
record.
Therefore, I perform the above three maintenance activities to consider the system to operate
well and adequately.
CHAPTER SEVEN: CONCLUSION AND RECOMMENDATION
INTRODUCTION
This chapter summarizes the experience of writing this project, and will attempt to spell out
the challenges faced, and how these challenges were solved or converted to become
opportunities.
Some recommendations will be made with regards implementation of the project, and
possibly towards enhancement of the project.
CONCLUSION
To have start this project in the first instance seems like some task that will not be easily
achievable; however, it has become a reality though it has not come through very easily with
respect to capturing requirements from users, doing extensive research, and most especially
the task of designing computerize system that will synchronize with the objectives and
deliverables of the project proposal.
However, a software or system development project that involves the computerization of an

information systems management needs to executed using a systematic approach and a stage
by stage methodology. (Nym, 2021)The model assume for this process was that which is
embedded in the systems database development methodology were employed which gives the
opportunity to develop and analyses, testing and implementation of the project deliverables.
In context of undergoing the task of attempting to carry out this project for Ernest Bai
Koroma University of Science and Technology, it can be stated that it has been a huge
learning experience for me, and also a very challenging one. Despite the fact that I had a
good collaborative experience, interaction with
some personnel and key stakeholders at some the Registry Office was very challenging, and I
was faced with quite a number of constraints that are considered to be major challenges that
presented themselves and directly affected the entire process of report writing and
applications development.
It would be nothing but fulfilling to throw light on some of such constraints, if not all.
Project Constraints
A constraint is naturally something that imposes a limit of some sort, or a restriction, or
regulation that prevents something from happening. A typical example of a constraint is the
fact that there are only so many hours in a day to accomplish quite a huge number of daily
tasks.
Software development projects can have an immense pool of constraints that normally exert a
negative pull on the progress, result, or quality of outcome of the project. Projects generally
fail because one or more of the key project variables are not managed effectively. It is highly
possible that the relationship between the variables are poorly understood and not managed at
all.
(BAH, 2019)Realistically, it is not the projects that fail; rather people do because they fail to
effectively manage the project(s). In most cases, software or systems development project
constraints revolve around the following elements:
Scope: the level of penetration of the problem statement, which determines the total of those
tasks to be performed in the course of the projects to deliver a product;
Time: required elapsed calendar time, usually defines by the project schedule or target ship
or go live date;
Resources: these are allocated to and consumed by the project. Human resource, finance, raw
materials, tools and office supplies, development effort are all examples of resources.
Resources are reflected in a project budget either in cash funds or direct man-hour.
Quality: degree of correctness of the entire system; thus, how well it meets defined user’s
requirements. It is also natural that if systems developers are running short on one of the
above elements, adequate and appropriate adjustments will have to be made on the others in
order to apply the necessary compensation required to attempt stabilizing the development
equation. Should there be an excess of one element, a reduction in pressure on the others can
equally do the job as in the case of running-short. This is however not a guarantee of success,
nor a mathematically-precise model of reality, but it’s a good reminder that work requires a
combination of factors and that someone is responsible for finishing the work with a given
amount of resources that may require a specific amount of time. This will surely also have
measurable levels of quality.
During the entire process of carrying out this project, major constraints that the Project that I
faced were;
Rainy Season – After the completion of our final comprehensive exams, there were often
torrential down pour throughout the country so little efforts was made to start the
project work quite earlier.
Inadequate Financial Help – Knowing very well that I am a poor students and not attached
to any substantive job it was difficult to procure finances for this project work especially
when I had to pay huge amount of money on transportation fare from Njala to our various
residential locations in the country.
RECOMMENDATIONS
Recommendations can be viewed as an advisable course of action regarding future work that
can be carried out on the Employee Attendance Management System in order to broaden its
scope of operations and hence increase the level of dependence on it. This will then serve as a
model that can be implemented by other Universities and Organizations around the country.
I hereby subscribe the following recommendations:
Hardware and Software Security
These are the security measure that will be put in place to protect both the hardware and
software from damage.
The computer room should be air-conditioned or properly ventilated because computer
generate a lot of heat and needs a cool environment to work accurately and to avoid break
down in the event of power failure, the computers must be connected to uninterrupted power
supply (UPS) which would be a temporary source of power in case there is a power cut whilst
the system would be saving data and after that should be shut down systematically.
Data Security: in simple terms would mean the protection of data from loss, disclosure,
modification and destruction.
Data Integrity: must always be preserved to ensure that computerized data of the meter
application processing until is always resemble those in source documents and that it was
not accidentally altered, destroyed or disclosed.
System Security: this is proper functioning of hardware and software. The users of this
application must make sure that the operations of the system should always conform to its
design specification, and that should not change or made to act incorrectly.
Confidentiality: privacy is required in the system. In this case password were created for
each user login (staff) and Admin creates the user pin.
Physical Control: is one of the main issues of physical security. This is achieved by
preventing intruders
Back-up Procedures
Back-up procedures should not be neglected in a computerized information system. It is wise
and important to have multiple copies of the database and forms of the system. This should
be kept in another location or area different from the database in case of any unforeseen
disaster that might occur.
Skilled Personnel
All system users must be proficient in the use of standard computer application software;
most especially with word processing and spread sheet software suits. A little more
knowledge in the area of database management and programming would be of an added
advantage.
REFERENCE
BAH, M. S. (2019). (99+) (PDF) DESIGN AND IMPLEMENTATION OF STUDENT
PROGRESS MANAGEMENT SYSTEM | MOHAMED S H E R I F F BAH -
Academia.edu [ACADEMIA]. 1148365,924032.
https://www.academia.edu/41728072/DESIGN_AND_IMPLEMENTATION_OF_ST
UDENT_PROGRESS_MANAGEMENT_SYSTEM
Jr, E. O. M. (n.d.). Faculty Attendance Monitoring Using RFID With Overload Computation
And Email Notification for City College of Calamba. Retrieved October 31, 2021,
from
https://www.academia.edu/37054229/Faculty_Attendance_Monitoring_Using_RFID_
With_Overload_Computation_And_Email_Notification_for_City_College_of_Calam
ba
Kuna, T. (n.d.). FINALTHESIS-. Retrieved October 31, 2021, from
https://www.academia.edu/25528992/FINALTHESIS_
Nym. (2021, September 8). Employee Attendance Management System Project Report
(PDF). Itsourcecode.Com. https://itsourcecode.com/fyp/employee-attendance-
management-system-project-report-pdf/
Ogbonna, R. (2019, October 14). STUDENTS ATTENDANCE MANAGEMENT SYSTEM.
Modish Project. https://www.modishproject.com/students-attendance-management-
system/
Publication, I. R. (n.d.). EMPLOYEE ATTENDANCE RECORD SYSTEM USING
MICROCONTROLLER. IJCIRAS. Retrieved October 31, 2021, from
https://www.academia.edu/43474157/EMPLOYEE_ATTENDANCE_RECORD_SY
STEM_USING_MICROCONTROLLER
Sutcliffe, A., & Gulliksen, J. (2012). User-Centered Requirements Definition. Usablity in
Government Systems User Experience Design for Citizens and Public Servants, 285–
300. https://doi.org/10.1016/B978-0-12-391063-9.00050-X
Ghatge, M. S. T., & Bhoite, S. D. (2016). Improving College Working Efficiency Through
Design and Development of A Computerized Information System (CIS). International
Journal of
Scientific Research, 4(7), 521-524.
Nikam, S., & Jadhav, B. T. (2011). Design and Development of Result Tool for University
and College Exam and it's Performance Study. International Journal on Computer Science
and
Engineering, 3(11), 3518-3524.
EBKUST University official Website (http://ebkustsl.edu.sl) –University Background and

History

Design and Implementation of Employee at

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Design and Implementation of Employee at

Uploaded by

Copyright:

Available Formats

DESIGN AND IMPLEMENTATION

NAME: AMADU JALLOH

A DISSERTATION SUBMITTED TO THE

In partial fulfillment for the award of Bachelor of

I ……………………………………………………………., certify that this project was under

 Framework: PHP, MySQL

UNIQUE AND SPECIAL FEATURES

ERNEST BAI KOROMA UNIVERSITY OF SCIENCE AND TECHNOLOGY

As attendance is a key indicator when evaluating performance of an employee punctuality

AIM AND OBJECTIVES OF STUDY

SCOPE AND LIMITATION OF THE STUDY

This Software is mainly focused and only accommodates the computerized

Inadequate Financial Help –

 Framework: PHP, MySQL

SQL = “Structural Query Language”

PHP = “Personal Homepage”

GUI = “Graphical User Interface”

CSS = “Cascading Style Sheet”

EBKUST = “Ernest Bai Koroma University of Science & Technology”

HTML = “Hypertext Mark-up Language”

VPS = “Virtual Private Server”

ATTENDANCE MANAGEMENT SYSTEM PROCESS

Advantages of Proposed System

REVIEW OF RELATED WORKS

 Web Based Coaching Institute Management System Mayuri Kamble et al

 Y. K. Saheed et al (2016)., have developed an attendance management system

 Saraswat and Kumar (2010), proposed fingerprint verification technique in taking

 Online Student Attendance System P. N. Garad et al (2017), in this project, we

Research methodology is the specific procedures or techniques used to identify, select,

The stages of waterfall project management generally follow this sequence:

Progress flows in one direction, like a real waterfall.

ADVANTAGE OF WATERFALL MODEL

DATABASE DEVELOPMENT METHODOLOGY

 Establishing requirements involves consultation with, and agreement among,

 Analysis start by considering the statement of requirements and finishes by producing

 Implementation is the construction of a computer system according to a given design

 Maintenance involves dealing with changes in the requirements, or the

MODEL OF DATABASE DEVELOPMENT

ANALYZE THE DATA REQUIREMENTS, NOT THE IMPLEMENTATION

USING RELATIONAL THEORY FOR FORMAL DESIGN

datetime_log datetime No current_timestamp()

date_updated datetime No current_timestamp()

Uniqu Packe Colum Cardinalit Collatio Nul Comme

11/14/21, 5:10 PM Print view - phpMyAdmin 5.1.1

Uniqu Packe Colum Cardinalit Collatio Nul Comme

SUPPORTING USERS AND USER PROCESS

SUMMARY OF STEPS FOR DATABASE DESIGN

DESCRIPTION OF THE CURRENT SYSTEM

SOFTWARE DEVELOPMENT LIFE CYCLE MODEL

For this project the Waterfall Development Model will be used.

ANALYSIS OF THE CURRENT SYSTEM

DRAWBACKS OF THE CURRENT SYSTEM

GOALS OF PROPOSED SYSTEM:

 No redundancy: In the proposed system utmost care would be that no information is

 Immediate retrieval of information: The main objective of proposed system is to

 Dedicated to Registry: This solution that would be implemented will exceptionally be

EMPLOYEE ADMIN/REGISTRY LOGIN

+LastName: Varchar +Password: Varchar +Password: Varchar

+Email: Varchar +Register ()

 Interconnectivity and interdependence must exist among the system components.

A. Outputs and Inputs

 It is the operational component of a system. Processors may modify the input

 As the output specifications change, so does the processing. In some cases,