WEB-BASED SIWES ALLOCATION AND SUPERVISION SYSTEM

A CASE STUDY OF FACULTY OF COMPUTING

BAYERO UNIVERSITY KANO

BY

MUHAMMAD SALIHU GIDADO

(CST/18/SWE/00215)

B.Sc. Software Engineering

June, 2023
WEB-BASED SIWES ALLOCATION AND SUPERVISION SYSTEM
A CASE STUDY OF FACULTY OF COMPUTING
BAYERO UNIVERSITY KANO

BY
MUHAMMAD SALIHU GIDADO
(CST/18/SWE/00215)

A Project Submitted to the Department of Software Engineering, Faculty of Computing,

Bayero University Kano, In Partial fulfillment of the Requirement for the Award of
Bachelor of Science (B.Sc.) Degree in Software Engineering.

SUPERVISED BY: DR. KABIR UMAR

June, 2023
 DECLARATION

I, SALIHU GIDADO MUHAMMAD declare that this thesis is an original report of my research,

has been written by me and has not been submitted for any previous degree. The work is almost

entirely my own work; the collaborative contributions have been indicated clearly and

acknowledged. Due references have been provided on all supporting literatures and resources.

_______________________________________

MUHAMMAD SALIHU GIDADO

(CST/18/SWE/00215)

i
 CERTIFICATION

This project work “Web-based SIWES Allocation and Supervision System” was carried out by

me under the supervision of Dr. Kabir Umar and has not been submitted in part or full to this

university or other institutions for the award of a degree.

Dr. Kabir Umar ________________________

Project Supervisor Signature and Date

Maryam Ibrahim Mukthar _______________________

Project Coordinator Signature and Date

Dr. Mohammed Hassan _______________________

Head of Department Signature and Date

________________________ _______________________
External Examiner Signature and Date

ii
 DEDICATION

I am dedicating this project to Allah SWA, from whom I draw my inspirations from, for his grace

and mercy to start and finish this work.

iii
 ACKNOWLEDGEMENT

I am greatly indebted to a number of people without whose assistance and input this project could
not be a success.
First of all, I acknowledge the power of Allah SWA, who has always been present to give me the
strength and inspiration to keep on working and complete this study.
My sincere gratitude and full recognition go to my parents Alh. Muhammad Gidado and Hajiya
Fatima (Goggo) Hassan who bore me, raised me, supported me, who’s love and support carried
me through the roughest times, who anxiously awaited the day I will call to tell them “I am done”
and I think when I did finish, they will more relieved than I was.! Many thanks to them for giving
me so much attention beyond my expectation and their blanket support kept me on my toes, I won’t
forget the attention and encouragement I enjoyed from my special brothers Musa (Dan’azumi),
Adam, Sulaiman, Tasiu, Sakina, Jafar, and Abdulrahman all are family Alh. Muhammad Gidado.
I want to specially thank my amiable supervisor, Dr. Kabir Umar - a man of wisdom and deep
thinking, for all his efforts and patience in making this project work a reality and also special thank
goes my kind level and project coordinator Malama Maryam Ibrahim Mukhtar for her
thoughtfulness and support that enthusiastically aided all the technicalities of this of the project. I
really appreciate you all.
Worthy of special recognition and appreciation are my lecturers who imparted in me both scholarly
and otherwise. Dr. Mohammed Hassan, head of this great department, whose efficient
administration and fatherly council has been of great help to me as an individual. Prof. Bashir
Shehu Galadanci, Malama Sanah Abdullahi Mu’az, Malama Saratu Yusuf Ilu, Dr. Salisu Musa
Barodo, Dr. Fagge have all helped and provided me with extensive professional guidance and
taught me more than I could ever imagined, since from the initial stage of my academic pursuit.
Also, I recognize the immense support I received from my special friends Nuuman Musa, Usman
Musa “Abe” Sunusi Hassan “Chila”, Abdulrashid Musa “A-Rasheed”, Barr. Alkasim Umar
“Gwani Susi” Muhammad Khamis “Ancestor” Muhammad Buhari Ilyas “Presidor”, Abubakar
Usman “Samandaji”, Hameed Alabi, Kabiru Yakubu Sani “Engineer” Aliyu Kabiru “Gwany”,
Rukaiya Muhammad Garba “Rukky” Nafi’u Khaleed “Iniesta”, Jamil A. Bala “Fabiano”, and all
those who have helped me in any way or the other that I cannot fully acknowledge herein I say a
big thank you.

iv
 TABLE OF CONTENTS

TABLE OF CONTENTS
DECLARATION ............................................................................................................................. i

CERTIFICATION .......................................................................................................................... ii

DEDICATION ............................................................................................................................... iii

ACKNOWLEDGEMENT ............................................................................................................. iv

ABSTRACT.................................................................................................................................... x

CHAPTER ONE ............................................................................................................................. 1

INTRODUCTION .......................................................................................................................... 1

1.1 Background of the study ....................................................................................................... 1

1.2 Problem Statements ............................................................................................................... 2

1.3 Aim and Objectives ............................................................................................................... 2

1.4 Scope of the study ................................................................................................................. 2

1.5 Significance of the study ....................................................................................................... 3

1.6 Definition of terms ................................................................................................................ 3

LITETATURE REVIEW................................................................................................................ 4

2.1 Introduction ........................................................................................................................... 4

2.2 Related Works ....................................................................................................................... 4

2.2.1 Table of summary............................................................................................................... 8

2.3 Summary ................................................................................................................................. 10

CHAPTER THREE ...................................................................................................................... 11

METHODOLOGY ....................................................................................................................... 11

3.1 Introduction ......................................................................................................................... 11

3.2 Project Workflow ................................................................................................................ 11

3.3 System Development Model ................................................................................................... 12

v
 3.4 Analysis of Existing and Proposed System ......................................................................... 13

3.4.1 Description of Existing System ........................................................................................ 14

3.4.2 Requirement Elicitation.................................................................................................... 14

3.4.3 Requirement Definition .................................................................................................... 15

3.4.4 Requirement Analysis ...................................................................................................... 17

3.5 System Design ..................................................................................................................... 18

3.5.1 Description of Proposed System ...................................................................................... 18

3.5.2 Architecture Design.......................................................................................................... 19

3.5.3 Database Design ............................................................................................................... 20

CHAPTER FOUR ......................................................................................................................... 21

IMPLEMENTATION AND TESTING ....................................................................................... 21

4.1 Introduction ......................................................................................................................... 21

4.2 Implementation.................................................................................................................... 21

4.2.1 Implementation Tools ................................................................................................. 21

4.2.2 Algorithm of major functionality ..................................................................................... 22

4.2.1 Description of System Operation (Using Sample Interfaces) .......................................... 24

4.3 Testing ................................................................................................................................. 28

4.3.1 Testing Strategy .......................................................................................................... 28

Unit Testing ............................................................................................................................... 28

4.3.3 Integration Testing ........................................................................................................... 32

4.3.4 System Testing ................................................................................................................. 35

4.3.5 Usability Testing .............................................................................................................. 36

Discussion ................................................................................................................................. 39

Summary ................................................................................................................................... 39

vi
CHAPTER FIVE .......................................................................................................................... 40

SUMMARY, CONCLUSION AND RECOMMENDATIONS ................................................... 40

5.1 Summary ............................................................................................................................. 40

5.2 Conclusion........................................................................................................................... 40

5.3 Limitation ............................................................................................................................ 41

5.4 Recommendations ............................................................................................................... 41

REFERENCES ............................................................................................................................. 42

APPENDIX A: .............................................................................................................................. 44

APEENDIX B: System Testing Evidence .................................................................................... 47

APPENDIX C: Codes of major functionality (align to 4.2.2) ...................................................... 51

vii
 LIST OF TABLES

Table 4.1 Hardware Specification………………………………………………….……… 21

Table 4.2 Software Specification…………………………………………………….……. 22

Table 4.1 Boundary Value Analysis …………………………….…………………..……. 36

Table 4.2 Test Case Scenario …………………………………………………………..…. 36

Table 4.3 Login Authentication Test Cases …………………………………..…..………. 37

Table 4.4 Upload Student Test Cases ………………………………………….……..…… 37

Table 4.5 SIWES Place Test Cases ……………..….……………………………..…...…. 38

Table 4.6 Allocate Supervisor Test Cases ………………..…………………………..….... 38

Table 4.7 Fill Logbook …….………………...…………..…………..………………….... 39

Table 4.8 Test Case of major functionalities …….……...……………………………..… 40

Table 4.9 Questionnaire Administered ……………………………………..………..…… 43

Table 4.11 System Usability Questionaire………………………………………………….. 36

viii
 LIST OF FIGURES

Fig. 3.1 Project Workflow ……………………….……….……….……………………. 20

Fig. 3.2 Object Oriented Approach ……………...…..………………..………………… 21

Fig. 3.3 Use Case Diagram ……………….…….………………………...………...…… 25

Fig. 3.4 System Admin Activity ……………….……………………………..………… 26

Fig. 3.5 SIWES Coordinator Activity ………….…………………………...……...…… 26

Fig. 3.6 Industry Supervisor Activity ..……….…………………………………………. 26

Fig. 3.7 Institution Supervisor Activity ……….……….…….……………………........... 26

Fig. 3.8 Student Activity ……………………..…………………………………...…….. 27

Fig. 3.9 Class Diagram …………………….……………………………………………. 27

Fig. 3.10 E-R Diagram …………………………………………………………..………... 28

Fig. 4.1 Admin Login Page …………………..……………………………………….… 32

Fig. 4.2 Student Login Page …………………………………..………………..………... 32

Fig. 4.3 Upload Student Page ………………………….………………………………... 33

Fig. 4.4 Allocate Student Page ………………………….………………………….......... 33

Fig. 4.5 Fill Application Page ……………………..…………………………………….. 34

Fig. 4.6 Fill Logbook Page ……………….……………………………………………… 34

Fig 4.7 Supervisor Comment Page ………………………………………………….…... 35

ix
 ABSTRACT

Students at their undergraduate studies in Nigeria are expected to undergo a program known as

the Student Industrial Work Experience Scheme (SIWES), the program is meant to expose students

to real world practical work. Despite all the technologies available, the proper method of

managing the students is still left behind. Accordingly, there is a need to put together an automated

system that will handle the SIWES management process from its beginning to the end. This project

focuses on studying the existing methods of managing SIWES students at the Faculty of

Computing; with the view of developing and implementing a web-based solution. The study,

however, reviewed related literature and performed system analysis and design of the new system.

The system was developed using Mysql framework with HTML, CSS, JavaScript and PHP as the

languages. The major problems covered are student to supervisor allocation, request letter

downloading, SIWES place submission, SIWES place approval/rejection, logbook management,

lodging complaint, grading student and notification alert to the system users. At the end of the

project, we found that more than 90% of the systems associated to the SIWES program are web

based and it is recommended for future studies to build mobile applications. Also, the data stored

can be used to allocate project supervisors using similarity in their skills. We further recommend

the utilisation of the system as it will bring efficiency and effectiveness in the management of

SIWES students in the faculty.

x
 CHAPTER ONE
INTRODUCTION

1.1 Background of the study

In 1973, the Industrial Training Fund (ITF) created the Students Industrial Work Experience
Scheme (SIWES) in response to a rising concern among industrialists that graduates of higher
education institutions lack enough practical background studies to prepare them for work in
industry (Sylvester et al., 2017).
The ITF withdrew from managing the scheme in 1979 due to organizational logistics issues
and increased financial burdens as a result of SIWES' rapid expansion, but this has since changed
as the scheme is now funded by the Federal Government of Nigeria (FGN) and managed by the
ITF (Yemisi, 2015). In 1985, the FGN reviewed the Scheme, and Decree No. 16 of August 1985
required that "all students enrolled in specialized engineering, technical, business, applied
sciences, and applied arts should have supervised industry attachment as part of their studies." It
also directed the ITF to resume full administration of the Scheme in collaboration with all the
institutions supervising agencies (NUC, NBTE and NCCE) (Adeyewa, 2015).
The Scheme's aims, which include bridging the gap between theory and practice among
engineering and technology students in Nigerian institutions of higher learning, have been actively
and effectively pursued. Though gratifying to note that Scheme is crucial and aimed at producing
skilled labour required by the Nigerian economy, it is constantly encountering array of challenges.
There are some visible challenges facing students’ industrial work experience scheme which hinder
the fulfillment of its objectives even in Faculty of Computing, Bayero University Kano (NUC,
NBTE and NCCE) (Adeyewa, 2015).
In a bid to identify these challenges, (Ogbuanya et al., 2018) carried out research which postulated
10 unique challenges faced by the scheme. These includes challenge of securing a place for
attachment, manual handling of SIWES activities, manual completion of logbook, few
supervisions visit due to distance among others.
This literature recommended solutions to these identified challenges. According to
(Adeyewa, 2015), the traditional way of operating the programme has been that of manual or
analogue method over the years, there is a need to modernize the operations for effectiveness and
efficiency of the scheme by developing a web-based application that will caters the SIWES

1
activities which would serve as a better alternative to the manual system that is currently being
used in Faculty of Computing, Bayero University Kano.

1.2 Problem Statements

The current process of allocating and supervising SIWES student in Faculty of Computing, and
other faculties in Bayero University Kano is handled manually, student is required to fill the
logbook daily and the student is also required to give it to the industry-based supervisor to sign
and comment weekly and then at the end of the industrial program, the student is to submit it back
to school. Each year, higher institutions spend a lot of money in order to print these logbooks,
money that could be put into better use if the logbook application is put into place. Supervisors in
most cases have to travel down to wherever each student is doing his/her Industrial training in
order to inspect and some of these distances could be quite far. In travelling, supervisors encounter
a lot of stress and also expose themselves to unforetold risks. Due to this, supervisors tend to visit
students just once leading to inadequate monitoring of students’ activities. Due to this, I suggest to
develop a web-based application for automating the manual process.

1.3 Aim and Objectives

The aim of this project is to develop a web-based application for management of SIWES allocation
and supervision. A case study of Faculty of Computing, Bayero University, Kano. The objectives
of this study are as follows:
1. To design a web application for management of SIWES allocation and supervision.
2. To implement the web application using HTML, CSS, Javascript, PHP and MySQL.
3. To evaluate the web application through usability testing.

1.4 Scope of the study

This project mainly focuses on a web-based SIWES allocation and supervision system that will
make SIWES management in the Faculty of Computing, Bayero University Kano more effective,
enjoyable, relaxed, simple from the comfort of offices, houses and etc.

2
1.5 Significance of the study

This study developed a secured student industrial work experience scheme (SIWES) allocation
and supervision system to take care of the manual process of the existing systems. This developed
system was able to achieve the automation of the current process. The present process involves
students and supervisors manually handle all activities involved in SIWES management. Despite
the fact there are no much existing systems that digitally caters for this component of the scheme,
the available existing systems are subjected to inappropriate management of the scheme.

1.6 Definition of terms

SIWES: Is a skills training program designed to expose and prepare students of

universities and other tertiary institutions for the industrial work situation
they are likely to meet after graduation.
SUPERVISOR: Refers to an individual who monitor and supervises a person or activity.
STUDENT: Refers toa person who formally engaged in leaning, especially one enrolled
in a school to learn something.
COMPUTER: This is an electronic machine that can accept, handle and manipulate data

by performing arithmetic and logic operations without human intervention

usually under the control of a program.

DATABASE: Is a collection of information that is related to a particular subject or

purpose.

INFORMATION: It is the data that have been processed interpreted and understood by the

recipient of the message or report.

SOFTWARE: This is a logically written program that hardware uses to perform its
operations.

SYSTEM: This is the collection of hardware, software, data, information, procedure

and people.

3
 CHAPTER TWO
LITETATURE REVIEW

2.1 Introduction

The SIWES program was reviewed in 1985, mandating supervised industry attachment for
students enrolled in specialized fields. The scheme aims to bridge the gap between theory and
practice among engineering and technology students in Nigerian institutions of higher learning.
However, it faces various challenges, including financial constraints, difficulty in securing
placements, and lack of proper planning (Sylvester et al., 2017).

Research studies have identified challenges and recommended solutions for SIWES,
emphasizing the need for adequate placement opportunities and modernizing the program using
Information and Communication Technology (ICT). The use of web-based applications and
automation can enhance efficiency, promptness, and scalability while addressing security
concerns. (Ogbuanya et al., 2018).

Additionally, the positive impact of work experience programs, including SIWES, on early
career success has been highlighted. However, improvements are needed in practical training and
the involvement of stakeholders throughout the program. (Adeyewa, 2015).

Previous research efforts have proposed cloud-based systems, recommender systems for
placements, and frameworks for preventing false reporting. However, security considerations have
been limited in many implementations (Oluwatosin, 2018).

2.2 Related Works

In 1973, the Industrial Training Fund (ITF) created the Students Industrial Work Experience
Scheme (SIWES) in response to a rising concern among industrialists that graduates of higher
education institutions lack enough practical background studies to prepare them for work in
industry (Sylvester et al., 2017).
The ITF withdrew from managing the scheme in 1979 due to organizational logistics issues
and increased financial burdens as a result of SIWES' rapid expansion, but this has since changed
as the scheme is now funded by the Federal Government of Nigeria (FGN) and managed by the

4
ITF (Yemisi, 2015). In 1985, the FGN reviewed the Scheme, and Decree No. 16 of August 1985
required that "all students enrolled in specialized engineering, technical, business, applied
sciences, and applied arts should have supervised industry attachment as part of their studies." It
also directed the ITF to resume full administration of the Scheme in collaboration with all the
institutions supervising agencies (NUC, NBTE and NCCE) (Adeyewa, 2015).
The Scheme's aims, which include bridging the gap between theory and practice among
engineering and technology students in Nigerian institutions of higher learning, have been actively
and effectively pursued. Though gratifying to note that Scheme is crucial and aimed at producing
skilled labour required by the Nigerian economy, it is constantly encountering array of challenges.
There are some visible challenges facing student’s industrial work experience scheme which
hinder the fulfillment of its objectives even in Faculty of Computing, Bayero University Kano.
In a bid to identify these challenges, (Ogbuanya et al., 2018) carried out research which postulated
10 unique challenges faced by the scheme. These includes challenge of securing a place for
attachment, manual handling of SIWES activities, manual completion of logbook, few
supervisions visit due to distance among others.
This literature recommended solutions to these identified challenges. According to
(Adeyewa, 2015), the traditional way of operating the programme has been that of manual or
analogue method over the years, there is a need to modernize the operations for effectiveness and
efficiency of the scheme. Worthy of note is the lack of adequate placement for prospective students,
and from study undertaken by (Ogbuanya et al., 2018), this takes the second place on prevalent
challenges bedeviling the scheme aside inadequate or proper financing.
The article recommended provision of adequate places of industrial attachment. Going on
is an era of simplifying almost all complicated works using technology, (Bhamra et al., 2016).
According to (Adeyewa, 2015), the traditional way of operating the programme has been
that of manual or analogue method over the years, there is a need to modernize the operations for
effectiveness and efficiency of the scheme.
The internet is a popular medium for accessing and sharing information in today's
technological environment, as it is the simplest and fastest means to transmit and retrieve
information. It also provides an unlimited access to anyone, at any place and time. The intended
system of digitalization intends a user-friendly operation which possibly will resolve ambiguity
and achieve certainty based on a web application that pays attention to security. Security is another

5
concerned with the confidentiality, integrity, and availability of systems and data in general
(Adeyewa, 2015)
Confidentiality refers to the ability to keep data secret and protected against unlawful
disclosure to only authorized parties. Integrity echoes information accuracy and necessitates
technology and methods that prevent unauthorized parties from improperly altering data.
Availability on the other hand refers to the ability that guarantees that information is
available to end users on a timely basis in order to meet assigned requirements (Fredj et al., 2021),
(Gaikwad & Bhatt, 2016), (Li, 2020). Security in the context of a Web application simply means
safeguarding the confidentiality, integrity, and availability of Web assets (Web pages and
databases). Understanding the vulnerabilities being faced by existing web applications will help
the underlining study in knowing how to go about building a secure web application.
The Open Web Application Security Project (OWASP) is a nonprofit foundation dedicated
to enhancing and providing a source for securing the web application (Kirk, 2017), the de factor
standard for categorizing web application vulnerabilities prioritizes the top 10 according to their
prevalence, exploitability, detectability and impact which greatly reduces the confidentiality,
integrity and availability of web applications. Using this guild provides a means to developing
secure web application software that minimizes vulnerabilities (Kirk, 2017)
Adding to previous research that suggests that undergraduate work experience in general,
and the SIWES program in particular, has a positive impact on a student's early career success,
(Oladimeji et al., 2017) found that those who work in government establishments, including the
organized private sector, are exposed to better opportunities for developing employability skills
than those who work in the private sector (Ogbuanya et al., 2018) carried out a study to evaluate
the effectiveness of SIWES programme using an entire population of about 130 respondents,
lecturers and industry supervisors inclusive and based on the findings of the study, 10 challenges
of SIWES in developing the required skill in the industry and 15 approaches that can be assumed
in evaluating the effectiveness of SIWES in Nigeria were also agreed (Ogbuanya et al., 2018).
Moreover, in an early attempt to obtain feedback on the Students’ Industrial Work
Experience Scheme from students who are the major beneficiaries of the scheme, (Ibegbulam et
al., 2017) carried out research and in its findings posited that the industrial training as it is presently
organized is not sufficiently meeting the practical needs of students.

6
 Stakeholders involved should be involved in the programme from placement to the actual
training (Adeyewa, 2015) stresses the numerous benefits of modernizing the SIWES programme
through the use of ICT which includes efficiency, promptness, cost effectiveness, scalability,
mobility and the satisfaction of stakeholders.
Through the powerful combination of technology and people, the pitfalls of the past can be
avoided to create a better tomorrow. By leveraging on the enormous potential of IT and our
dynamic youth, the SIWES programme can become an interesting and a very successful venture.
In addition, (Adeyewa, 2015) stresses that placement of students could be automated from the
robust database in the enrolment system. The enrolment database essentially becomes a shopping
center for organizations or any stakeholder to pick candidates. It must therefore be a searchable
database. Students who are placed either directly by companies or through the students by own
efforts are flagged and documented appropriately in terms of name of company, location.
After discovering that the current system of student management during the SIWES period
is ineffective, as it frequently involves supervisors physically visiting students, incurring some
operating costs, and that, in addition to monitoring, mentoring is another important role of the
supervisor (Babalola et al., 2015), leveraging-on-web-based technology to solve these problems.
Student’s registration and payment processes for the scheme being semi-manual lead (Sylvester et
al., 2017) to design a system web based in order to automate these processes enabling the SIWES
unit to be able to manage the large amount of data inflow during the SIWES period.
Furthermore, (Zachariah & Yabuwat, 2016) made a research to develop a cloud based that
would allow for near real-time collaborative supervision of students’ experience during SIWES
and recommendations were made that would allow for proper management of the processes by the
Institutions, Industries, and Industrial Training Fund (ITF), students being able to report their daily
activities and also upload picture of themselves in such sessions; and both the ITF, Industrial, and
Institution-based supervisors can monitor and make recommendations to the students. The system
was executed using PHP, JavaScript, CSS, Ajax technologies, MySQL database and hosted on
Google Cloud Infrastructure.
The online software could not be reviewed properly as servers were down. Considering the
difficulties encountered in securing placements for SIWES and how its negatively impacts the final
grades of some undergraduate students, (Ogunde & Idialu, 2019) proposed a recommender system

7
to solve this challenge. Using past SIWES data, the developed system can recommend suitable
place of placements for students based on classification approach.
The researchers collected data through questionnaires only in the 20 local government
areas of Lagos state Nigeria, and basing its scope on software development and networking
company. Though security of the system was not mentioned, it was observed that many companies
are aware of this essential program of the government and are doing their best to comply. It is
worthy of note that most of these researches had no mention of security in its implementation,
except for (Oluwatosin, 2018) who developed a framework that uses time and location in
preventing false reporting of logbook. Using the Google API, students can have access to the
system only when they are at their place of primary assignment. Though implemented, the system
had access control issues.
This research, having identified the challenge of security vulnerability and threats associated with
online and automated SIWES system, developed a new system with adequate security architectures
in the kernel and application layers. The system was evaluated against vulnerabilities and found
working with the architectures. (Oluwatosin, 2018).

2.2.1 Table of summary

S/No Author/Year Title Problem Proposed Results
Address Solution
(Sylvester et Industrial Concern among SIWES funded Effective
1 al., 2017) Training Fund industrialists that by the Federal pursuit of
(ITF) and graduates lack Government of aims, bridging
Students practical Nigeria (FGN) the gap
Industrial background and managed by between
Work studies for work the ITF theory and
Experience in industry practice
Scheme
(SIWES)
2 (Yemisi, Students Organizational FGN funds Improved
2015) Industrial logistics issues SIWES, ITF management
Work and increased manages the and
Experience financial burdens scheme administration
Scheme of SIWES
(SIWES)
(Adeyewa, Students Challenges in Provision of Recommended
3 2015) Industrial SIWES program, adequate solutions to
Work lack of proper financing, challenges
Experience planning, proper planning

8
 Scheme inadequate of SIWES
(SIWES) finance, program, and
difficulties in orientation
securing
placement
(Ogbuanya Challenges Challenges in Financial Identified
4 et al., 2018) Faced by SIWES program, support for challenges and
Students finance burden, students and recommended
Industrial securing supervisors, solutions
Work placement, lack proper planning
Experience of planning of SIWES
Scheme program
(SIWES)
5 (Oladimeji et Challenges in Challenges in Provision of Identified
al., 2017) Students SIWES program, adequate challenges and
Industrial inadequate finance, recommended
Work finance, improved solutions
Experience difficulties in placement
Scheme securing process, proper
(SIWES) placement, lack orientation
of orientation
(Bhamra et Modernization Traditional Use of web- Improved
6 al., 2016) of Students manual/analogue based efficiency,
Industrial operations of application, effectiveness,
Work SIWES digitalization, and security of
Experience attention to SIWES
Scheme security program
(SIWES)
through
technology
(Fredj et al., Security in Concerns about Implementation Safeguarding
7 2021), Web confidentiality, of security of web assets
(Gaikwad & Applications integrity, and measures, and data
Bhatt, 2016), availability of protection
(Li, 2020) web applications against
unauthorized
access and data
alteration
8 (Kirk, 2017) Open Web Categorization of Prioritization of Minimization
Application web application top 10 of web
Security vulnerabilities vulnerabilities, application
Project development of vulnerabilities
(OWASP) secure web
application
software

9
 (Ibegbulam Evaluation of Insufficient Involvement of Improvement
9 et al., 2017)Students practical needs of stakeholders of practical
Industrial students in from placement training for
Work SIWES program to training students
Experience
Scheme
(SIWES)
(Zachariah & Cloud-Based Inefficiency of Cloud-based Enhanced
10 Yabuwat, Supervision of physical system for real- supervision
2016) Students' supervision, high time and
Experience in operating costs collaborative management
SIWES supervision, of SIWES
reporting of program
activities
(Babalola et Web-Based Ineffectiveness of Web-based Improved data
11 al., 2015) Automation of student system for management
SIWES management automating and efficiency
Processes during SIWES registration and of SIWES
period payment program
processes
(Oluwatosin, Preventing False reporting of Framework Prevention of
12 2018) False logbook in using time and false reporting,
Reporting of SIWES location data, access control
Logbook in Google API improvements
SIWES

2.3 Summary

This research developed a secured student industrial work experience scheme (SIWES)
allocation and supervision system to take care of the manual process of the existing systems.
This developed system was able to achieve the automation of the current process. The present
process involves students and supervisors manually handle all activities involved in SIWES
management.
Despite the fact there are no much existing systems that digitally caters for this component of
the scheme, the available existing systems are subjected to inappropriate management of the
scheme.
Therefore, leveraging on secure web application technologies using Unified Modelling
Languages for design, HTML, CSS, JavaScript, PHP for its implementation and this project
developed a secure solution to this pertinent challenge.

10
 CHAPTER THREE
METHODOLOGY

3.1 Introduction
The methodology used in developing this project work include obtaining information on
manual system of placement systems. The methods also include: analytical and critical study of
the existing systems, observation and obtaining information from staff and students. The design
was then carried out using UML Use Case Diagram, Sequence Diagram and Entity Relation
Diagram (ERD). HTML, CSS, JavaScript and PHP programming language was used for the
implementation.

Using the backend programming language, PHP model was utilized in creating roles for
different classes of users for various job functions, and permissions to perform certain operations
tied to their specific roles.

Lastly, the iterative waterfall model, where the entire system was broken into several
subsystems and each subsystem was further sub-divided into different modules in other to achieve
a secure system at unit levels. It is simple to use as it allows for parallel development and a
feedback path.

3.2 Project Workflow

Project workflow refers to the series of steps or activities that are followed in a project
from initiation to completion. It outlines the sequence of tasks, the dependencies between them,
and the overall flow of work. A project workflow provides a structured framework for managing
and executing project activities in an organized and efficient manner.

Figure 3.1: Project Workflow

11
3.3 System Development Model

A Modified Waterfall model was used in this work. Instead of the six major phases of the waterfall
model, it was reduced into 5 different phases. This is because all requirements were known
beforehand and the objective of our software development is the computerization/automation of
an already existing manual working system.

Use Case •Design System

•Testing
•Literature •Analysis •Implementation
Review

Report Activity, class Final System

Figure 3.2: Object Oriented Approach

The object-oriented approach is a software development methodology that focuses on designing

and implementing software systems using the concept of objects.

There are several reasons why I selected object-oriented approach for my software development.
Here are some of the reasons:

1. Iterative Development: While the waterfall approach follows a sequential and rigid
development process, the object-oriented approach can be used in combination with
iterative development methodologies like agile.

This allows for incremental development, frequent feedback, and faster delivery of working
software, while still benefiting from the advantages of object-oriented design and coding practices.

2. Modularity and Reusability: The object-oriented approach promotes modularity and

encapsulation. By encapsulating data and behavior within objects, it allows for modular
design and development.

12
This modularity enables code reuse, as objects can be easily reused in different parts of the system
or in other projects, leading to more efficient and maintainable code.

3. Modeling Real-World Entities: The object-oriented approach aligns well with modeling
real-world entities and relationships. By representing software components as objects that
mimic real-world entities, it becomes easier to understand, design, and communicate
about the system. This approach often results in more intuitive and maintainable code.

3.4 Analysis of Existing and Proposed System

The analysis of the existing system involves manual means of supervisor allocation by the
SIWES coordinator which is time consuming in doing so. It is tiresome to be assigning students to
supervisors individually, though there are much constraints to be considered when allocating the
supervisor. Students is required to go to department in order to collect documents that they are to
fill during the course of their industrial training. One of such documents is the Logbook.

Student is required to fill the logbook daily and the student is also required to give it to the
industry-based supervisor to sign and comment weekly and then at the end of the industrial
program, the student is to submit it back to school. Each year, higher institutions spend a lot of
money in order to print these logbooks, money that could be put into better use if the logbook
application is put into place.

The work of marking these logbooks by the lecturers is also made difficult, as for them to
mark the logbooks they would have to wait until all students have finished their industrial training,
be it 6 months or 3 months and this can be very cumbersome on the lecturers and would also take
a lot of time. Supervisors in most cases have to travel down to wherever each student is doing
his/her SIWES in order to inspect and some of these distances could be quite far. In travelling,
supervisors encounter a lot of stress and also expose themselves to unforetold risks.

Due to this, supervisors tend to visit students just once leading to inadequate monitoring of
students’ activities. When students resume after their SIWES, they submit their IT logbook in
hardcopy which can be prone to theft and also destruction by natural disasters.

The proposed system illustrates how the system operates and function. This system can allow
students update their logbook at any time via a paperless, environmentally-friendly method as well

13
as submit their logbook and final report online. Supervisors can also access the student’s logbook
at any time; therefore, they can evaluate and grade the student at their own pace.

The SIWES coordinator may also access the system and assigned upload students, assigned
supervisor, grades students at any time to monitor the progress of the industrial training process.

3.4.1 Description of Existing System

At present, the operations of the SIWES in Faculty of Computing, Bayero University Kano
are predominantly manual. In order to fully leverage on the advancement in technology to improve
the process, I embarked on this research.
In addition to this, it has been observed that SIWES students are often visited once or twice
throughout the programme. However, ensuring that student acquire relevant experience requires a
regular assessment of their daily activities and this can only be feasible if students are required to
report back to the supervisor on regular basis, and the supervisor can thereafter provide timely
advice and mentoring to the students.
Students on the SIWES programme are given log book to fill-in their daily activities to be
submitted at the end of the programme and over the years, it was observed that at the end of the
programme, supervisors still fault some student’s reports. Some of the challenges the students are
faced with are not being posted to where they can really acquire technical know-how in the
organization they are attached to.
This is a regular occurrence due to lack of visitation and proper mentoring during the course
of the programme. In order to avoid these problems, it is imperative that the institution-based
SIWES coordinator ensures that the supervisors assigned to supervise these students visit them as
scheduled since proper supervision will help to detect problems the students encounter in their
respective duty posts and all these will also help to identify students that did not take part in the
exercise. Hence, the need for means of solving the above problems.

3.4.2 Requirement Elicitation

The study used both primary and secondary data collection methods to obtain information
for the proposed system's development from different stakeholders, including the institutional-
based, SIWES coordinators, SIWES supervisors and students who have been in the scheme for
years.

14
 Through a thorough observation of the existing system mostly as it operates within the
Bayero University Kano, so as to know ways to improve on what is obtainable. This process
helped obtained vital information that helped in the design of the system.

3.4.3 Requirement Definition

1. Functional Requirements:
Functional requirements describe what the software must do to validate the system. They are
called product features:
1. System Admin Functionalities
i. Admin shall login to the system.
ii. Admin shall manage faculty, department and SIWES supervisor.
iii. Admin shall manage the system.
2. SIWES Coordinator Functionalities
i. SIWES coordinator can login to the system.
ii. SIWES coordinator can upload student’s records.
iii. SIWES coordinator can approved or reject application.
iv. SIWES coordinator can post notification
v. SIWES coordinator can view complaint.
vi. SIWES coordinator can view students list.
vii. SIWES coordinator can change password.
3. Student Functionalities
i. Student can login to the system.
ii. Student can submit approval letter.
iii. Student can fill logbook.
iv. Student can view supervisor’s comment
v. Student can lodge complain.
vi. Student can change password.
4. Institutional Supervisor Functionalities
i. Institution supervisor can login to the system.
ii. Institution supervisor can view assigned students.
iii. Institution supervisor can comment on student’s logbook.

15
 iv. Institution supervisor can grade students.
5. Industry Based Supervisor Functionalities
i. Industry based supervisor can login to the system.
ii. Industry based supervisor can comment on student’s logbook.
iii. Industry based supervisor can grade students.
2. Non-Functional Requirements:
Non-Functional Requirements: The non-functional requirements are restrictions, quality based
on the solutions that will meet the functional requirements. In essence, it is concerned with how
well the system performs.
The security, usability, accessibility, reliability and accuracy, flexibility and also how user-
friendly. A non-functional requirement also deals with both hardware and software specifications
of the system.
i. User friendly: The system shall be easy to use and understand.
ii. Performance: The system shall respond quickly to user requests.
iii. Reusability: The system will provide a means to reuse some of its features like the
diagrams and codes.
iv. Maintainability: The system will be easy to maintain as changes can be
implemented easily.

16
3.4.4 Requirement Analysis

The diagram shows the functionality of the system to be developed, together with the associated
user that can perform that particular role. The system user involves the student, supervisor, SIWES
coordinator and the system itself. It is given in Figure 3.3 Use case diagram below:

Figure 3.3: Use Case Diagram

17
 3.5 System Design

3.5.1 Description of Proposed System

I choose activity diagram to describe my system. Activity diagrams are graphical

representations of work flow of stepwise activities and actions with supports for choice, interaction
and concurrency.

In the unified modeling language, activity diagrams can be used to describe the business and
operational step-by step workflows of components in a system. An activity diagram shows the
overall flow of control.

In this study, I have a separate activity diagram for the system admin, SIWES coordinator,
institutional supervisor, student and industry-based supervisor.

Figure 3.5: SIWES Coordinator Activity

Figure 3.4: System Admin Activity

Figure 3.6 Industry Supervisor Activity Figure 3.7: Institution Supervisor Activity
18
 Figure. 3.8: Student Activity

3.5.2 Architecture Design

Figure 3.9: Class Diagram

19
3.5.3 Database Design

The general theme for a database is to handle information as an integrated whole. Database is
a collection of interrelated data stored with minimum redundancy to serve many users quickly and
efficiently. Its objective is to make information access easy, quick inexpensive and flexible for the
user.

Database design is the creation of a conceptual model of a database that caters for the present
as well as future information storage need of an organization; its aim is to improve the existing
situation.

The new system is developed by taking input from existing system and supplied to the
proposed system.

Figure 3.10: E-R Diagram

20
 CHAPTER FOUR
IMPLEMENTATION AND TESTING

4.1 Introduction

This chapter describes the installation of the new system, the software and the hardware that would
be needed to be installed for proper implementation.

4.2 Implementation

The current implementation of SIWES portal is built for three stakeholders: SIWES Students,
Supervisory unit (which include the supervisor, industry-based supervisor, SIWES coordinator)
and System Admin. Users in the system can communicate with each other and access member
information based on their classification.
The implementation deals with the collection of interdependent physical devices, together
with their programming, which provides functionality and performance for which the system was
design.
The implementation of this online SIWES system software is made concise to make it friendly
to user in terms of accessibility and availability.

4.2.1 Implementation Tools

The project was developed using PHP, HTML, CSS, JavaScript and MySQL Database. This
section describes the tools used in the development of the system, in terms of hardware and
software.

1. Hardware Specifications
The system was developed on a Dell laptop computer with the below hardware specifications:
Table 4.1 Hardware Specification
Category Hardware Used
Memory 12G
Hard Drive 1TB
Processor Corei3 3.0GHz

21
 2. Software Specifications
The table below gives the list of software used during the development of the system
together with their specifications:
Table 4.2 Software Specification
Category Software Used
Operating System Windows 10
Integrated Development Environment (IDEs) Visual Studio Code
Programming Language HTML, CSS, Javascript and PHP
Database MySQL
Web browser Chrome, Firefox, Microsoft Edge etc.

4.2.2 Algorithm of major functionality

Below are the six major algorithm for my system functionalities:

1. Login Pseudo Algorithm

Step 1: login user’s details

Step 2: if login authentication failed
repeat step 1 with correct details
Else:

Step 3: terminate

2. Upload Students Pseudo Algorithm

Step 1: after coordinator login

Step 2: if student’s records exist

Step 3: fetch student’s CSV file

Step 3: upload a CSV file of the student

Else:

Step 4: terminate

22
3. Fill SWIES Place Pseudo Algorithm

Step 1: after student login

Step 2: click on submit approval letter
Step 3: fill the place of your attachment information
Step 4: upload acceptance letter
Step 5: submit application
Step 4: terminate
4. Allocate Supervisor/Approved or Reject Application Pseudo Algorithm

Step 1: after coordinator login

Step 2: review sent application
Step 3: view approval letter
Step 4: if place of attachment is relevant
Step 5: assign supervisor and approved application
Else:

Step 6: reject application

Step 7: terminate

5. Fill Logbook Pseudo Algorithm

Step 1: after student login

Step 2: add comment
Step 3: select week number
Step 4: write description of the work done.
Step 5: if sketched diagram is available
Step 6: upload sketched diagram
Else:

Step 7: select date

Step 8: submit comment

Step 9: terminate

23
 6. Comment on Logbook Pseudo Algorithm

Step 1: after supervisor login

Step 2: click no student to comment
Step 3: comment on logbook
Step 4: if sketch diagram is available
Step 6: view diagram
Else:
Step 7: terminate

4.2.1 Description of System Operation (Using Sample Interfaces)

The implementation of this web-based SIWES allocation and supervising system software is
made concise to make it friendly to user in terms of accessibility and availability.

Figure. 4.1: Admins Login

Page
As shown in figure 4.1 this page is meant for the login of all the users except student, the system
can detect the role of the user by his/her login credentials. Upon authentication of the user, he/she
will then be redirected to the appropriate page.

24
 Figure 4.2: Student Login
As shown in figure 4.2 this page Page
is meant for the student login, the system can detect its login
credentials. Upon authentication of the student will then be redirected to the appropriate page.

Figure 4.3: Upload Students

As shown in figure 4.3 this is the page
Pagewhere coordinator can upload a CSV file for a list of SIWES
students.

25
 Figure 4.4: Allocate Supervisor Page

In this page as shown in figure 4.4 SIWES coordinator can view student application, if the industry
is relevant to his/her course of study, then supervisor will be allocated to him and the application
will be approved.

Figure 4.5: Fill Application Page

As shown in figure 4.5 this is the page where student can access and fill the organization
information and upload approval letter for approval.

26
 Figure 4.6: Fill Logbook Page
As shown in figure 4.6 this page gives the field for filling the work-done during the day, which
can be accessed by the student's supervisor.

Fig. 4.7: Supervisor Comment Page

As shown in figure 4.7 this page gives the field for commenting the work-done by the student's
institutional supervisor.

27
4.3 Testing

Testing in software development refers to the process of evaluating a software application or

system to identify defects, bugs, or errors that could impact the quality or functionality of the

software. Testing involves executing software components or entire systems and comparing the

expected results with actual results to determine if the software works as intended.

Testing is an important part of the software development life cycle as it helps to ensure that

the software is reliable, effective, and meets the requirements of end-users.

4.3.1 Testing Strategy

Here, the boundary value analysis was used for the strategic test, to test for all the test cases

presented in the partitions. The testing strategy is based on Supervisor Allocation.

The boundary value analysis test cases for supervisor allocation may have a minimum number

of 2 students and maximum number of 15 students respectively.

Table 4.3 Boundary Value Analysis

BOUNDARY VALUE ANALYSIS
Invalid Valid Invalid
0 and 1 2, 3, 8, 14, 15 16 and above
Partition 1 Partition 2 Partition 3

Unit Testing

Unit testing involves testing each individual component of the system in isolation. In the context
of the SIWES allocation and supervising system, unit testing would involve testing individual
modules such as the login, uploading SIWES students, supervisor allocation, approving or
rejecting place of attachment, filling logbook, commenting on logbook, grading student modules
and other major system functionalities.

28
 Table 4.4 Login Authentication Test Case

TEST TEST PRECONDITION TEST EXPECTED ACTUAL STATUS

CASE DESCRIPTION INPUT RESULT RESULT
ID

Verify the field in Login screen must All field are Warning The warning
the log-in screen exit blank and message (No message
(username & log-in username or pop-up
TC-01 password) button is password) Pass
clicked

Verify the field in Login screen must Username Warning The warning
the log-in screen exit entered, message message
(username & password (Incorrect pop-up
TC-02 password) field is username or Pass
blank password)

Verify the field in Login screen must Password Warning The warning
the log-in screen exit entered, message message
(username & username (Incorrect pop-up
TC-03 password) field is username or Pass
blank password)

Verify the field in Login screen must Both Successfully Login

the log-in screen exit username log-in successfully
(username & and
TC-04 password) password Pass
are entered

29
 Table 4.5 Upload Student Test Cases

TEST TEST PRECONDITION TEST STEPS EXPECTED ACTUAL STATUS

CASE DESCRIPTION INPUT RESULT RESULT
ID
Verify file File upload field Student Click on Warning The
upload field must exist record upload message warning
TC-05 (file upload not student (No file message Pass
field) uploaded button choosen) pop-up as
expected

Verify file File upload field Student Click on File File

upload field must exist record upload uploaded uploaded
TC-06 (file upload uploaded student successfully successfully Pass
field) button

Table 4.6 SIWES Place Test Cases

TEST TEST PRECONDITION TEST STEPS EXPECTED ACTUAL STATUS

CASE DESCRIPTION INPUT RESULT RESULT
ID
Verify the field Student Application Click on Warning The
of student application form form field submit message warning
TC-07 application field must exist is empty application (Please message
(student filled out pop-up as
application this field) expected Pass
form field)

Verify the field Student Application Click on Application Application

of student application form form field submit has been has been
TC-08 application field must exist with application submitted submitted
(student industry successfully successfully Pass
application details
form field)

30
 Table 4.7 Allocate Supervisor Test Cases

TEST TEST PRECONDITION TEST STEPS EXPECTED ACTUAL STATUS

CASE DESCRIPTION INPUT RESULT RESULT
ID
Review and Supervisors drop Supervisor Click on Warning The
verify student’s down menus not approve message warning
TC-09 application for must exist selected now (Please message
approval and button select pop-up as
assign supervisor) expected Pass
supervisor

Review and Supervisors drop Supervisor Click on Application Application

verify student’s down menus selected approve approved approved
TC-10 application for must exist now successfully successfully
approval and button
assign Pass
supervisor

Table 4.8 Fill Logbook Test Cases

TEST TEST PRECONDITION TEST STEPS EXPECTED ACTUAL STATUS

CASE DESCRIPTION INPUT RESULT RESULT
ID
Verify the field Student Student Click on Warning The
of student description of description submit message warning
description of work done form of work comment (Please message
work done field must exist done form filled out pop-up as
(student field is this field) expected
TC-11
description of empty Pass
work done
form field)

31
 Verify the field Student Student Click on Your Your
of student description of description submit comment comment
description of work done form of work comment has been has been
work done field must exist done form successfully successfully Pass
(student field with submitted submitted
description of comment
TC-12
work done
form field)

Table 4.9 Logbook Comment Test Cases

TEST TEST PRECONDITION TEST STEPS EXPECTED ACTUAL STATUS

CASE DESCRIPTION INPUT RESULT RESULT
ID
Verify the field Supervisor Supervisor Click on Warning The
of supervisor comment form comment submit message warning
comment field must exist form field comment (Please message
(supervisor is empty filled out pop-up as
TC-13 comment form this field) expected Pass
field)

Verify the field Supervisor Supervisor Click on Comment Comment

of supervisor comment form comment submit submitted submitted
comment field must exist form field comment successfully successfully
(supervisor is fill with
TC-14 comment form comment Pass
field)

4.3.3 Integration Testing

The integration testing for my system “SIWES allocation and supervising system” focuses
on verifying the correct integration and interaction of various components within the system.

The goal is to ensure that the system functions properly as a unified whole, with all the
modules working together seamlessly.

32
 Table 4.10 Test Cases of major functionality

TEST TEST PRECONDITION TEST STEPS EXPECTED ACTUAL STATUS

CASE DESCRIPTION INPUT RESULT RESULT
ID
Verify the field Login screen must All field are Click sign Warning The warning
exit blank and in button message (No message
TC-01 in the log-in log-in username or pop-up
button is password)
clicked Pass
screen

(username &

password)

Verify the field Login screen must Username Click sign Warning The warning
in the log-in exit entered, in button message message
TC-02 screen password (Incorrect pop-up
(username & field is username or Pass
password) blank password)

Verify the field Login screen Password Click sign Warning The
in the log-in must exit entered, in button message warning
TC-03 screen username (Incorrect message
(username & field is username or pop-up Pass
password) blank password)

Verify the field Login screen Both Click sign Successfully Login
in the log-in must exit username in button log-in successfully
TC-04 screen and
(username & password Pass
password) are entered

Verify file File upload field Student Click on Warning The

upload field must exist record not upload message warning
TC-05 (file upload uploaded student (No file message Pass
field) button choosen) pop-up as
expected

Verify file File upload field Student Click on File File

upload field must exist record upload uploaded uploaded
TC-06 (file upload uploaded student successfully successfully Pass
field) button

33
 Verify the field Student Application Click on Warning The
of student application form form field submit message warning
TC-07 application field must exist is empty application (Please message
(student filled out pop-up as
application this field) expected Pass
form field)

Verify the field Student Application Click on Application Application

of student application form form field submit has been has been
TC-08 application field must exist with application submitted submitted
(student industry successfully successfully Pass
application details
form field)

Review and Supervisors drop Supervisor Click on Warning The

verify student’s down menus not approve message warning
TC-09 application for must exist selected now (Please message
approval and button select pop-up as
assign supervisor) expected Pass
supervisor

Review and Supervisors drop Supervisor Click on Application Application

verify student’s down menus selected approve approved approved
TC-10 application for must exist now successfully successfully
approval and button Pass
assign
supervisor

Verify the field Student Student Click on Warning The

of student description of description submit message warning
description of work done form of work comment (Please message
work done field must exist done form filled out pop-up as
(student field is this field) expected Pass
TC-11
description of empty
work done
form field)

Verify the field Student Student Click on Your Your

of student description of description submit comment comment
description of work done form of work comment has been has been
work done field must exist done form successfully successfully
(student field with submitted submitted
TC-12
description of comment
work done Pass
form field)

34
 Verify the field Supervisor Supervisor Click on Warning The
of supervisor comment form comment submit message warning
comment field must exist form field comment (Please message
(supervisor is empty filled out pop-up as
TC-13 comment form this field) expected Pass
field)

Verify the field Supervisor Supervisor Click on Comment Comment

of supervisor comment form comment submit submitted submitted
comment field must exist form field comment successfully successfully
(supervisor is fill with
TC-14 comment form comment Pass
field)

4.3.4 System Testing

This ensures that application programs written and tested in isolation work properly when

they are integrated into the total system, after all the module has been integrated as single unit

system the application is then tested to see whether it meet the user need.

Firstly, the application was loaded via localhost showing interface such as home page, we

then first upload students record to test all the necessary assumption case that can go wrong i.e.

testing the strength of the user login details, which comes clean, then proceed down to the SIWES

coordinator dashboard which contains some features like upload students, SIWES applications,

view complaint, drop information, report, settings and logout, with each containing a certain

features for performing a specific task like: uploading of students record, approving/rejecting place

of SIWES, assigning supervisor, dropping notification, viewing complaint etc.

Student dashboard has some list of features that allow student to download request letter,

fill place of SIWES, upload acceptance letter, fill logbook, lodge complain, etc.

35
 Institution supervisor dashboard contains a list of features among are view assigned

students, view logbook, comment on logbook, view complaint, grade student etc.

System Admin dashboard contains features like adding SIWES coordinator, adding

department, upgrading the system etc. And for industry-based supervisor dashboard it has some

features like viewing student’s logbook, commenting on logbook, grade students etc.

The whole tests cases of the system came out clean after it has undergone a series of testing

stages by the developer and the system users.

4.3.5 Usability Testing

Here are the usability test questions for the developed system that give out to the system

users to see whether the system meets the requirement: And descriptive analysis was used to

generate the result of the questionnaire.

USABILITY TEST QUESTIONNAIRE

Good day, my name is SALIHU GIDADO MUHAMMAD with registration number

CST/18/SWE/00215 conducting a final year undergraduate project title “Design and
implementation of SIWES Allocation & Supervising System” a case study of Faculty of
Computing, Bayero University Kano. This is a usability test questions that you help me rate the
overall working of the system from scale 1 to 5 after operating and testing the system vigorously.

Table 4.11 Usability Questionnaire Table

1 2 3 4 5
No. Question (Strongly (Disagree) (Neutral) (Agree) (Strongly
Disagree) Agree)
How easy was it
1 to navigate
through the
system?

36
 How intuitive
2 was the process
of applying for a
placement within
the system?
Did you find it
3 straightforward
to submit your
SIWES
placement
preferences?
How would you
4 rate the clarity of
the instructions
provided within
the system?
Did the system
5 provide clear
feedback on the
status of your
placement
application?
How user-
6 friendly was the
interface for
submitting
progress reports?
How well did the
7 system allow you
to communicate
with your
assigned
supervisor?
How likely are
8 you to
recommend this
SIWES
allocation and
supervising
system to others?
How useful were
the system's
9 notifications?

37
Below, the data collected was analyzed and questionnaire administered were scrutinized and

presented in tabular forms. A total number of 12 questionnaires were distributed system users but

I was able to collect back 10 questionnaires.

Table 4.10 Questionnaire Administered

Questionnaire Administered Frequency Percentage

Total number of 10 70

questionnaires return

Total number of 2 30

questionnaires not returned

Total number of administered 12 100

Figure 4.8: System Usability Test Table

38
Discussion
The system usability test was conducted as shown in figure 4.8 above to evaluate the overall
usability and performance of the system. The test aimed to assess how effectively users can interact
with the system and accomplish their tasks, considering factors such as ease of use, efficiency, and
user satisfaction.
During the testing process, a sample group of users interacted with the system, performing various
tasks and providing feedback on their experience. The tasks assigned to the users covered a range
of functionalities and scenarios to ensure comprehensive testing.
The results of the system usability test indicated that the system achieved an impressive accuracy
rate of 94%. This suggests that the system is functioning correctly for the majority of the tested
tasks, meeting the expected performance standards.

Summary
This chapter summaries the basics implementation of the system, such as the preliminary tools
use in building the system and rigorous testing stages it undergone in the software environment
for ensuring the safety of the system.

39
 CHAPTER FIVE
SUMMARY, CONCLUSION AND RECOMMENDATIONS

5.1 Summary

The major focus of this research was to develop cloud-based SIWES App that will facilitate

collaborative management and supervision of students on SIWES and other SIWES related

activities. The system was designed, developed and implemented on Google Cloud which

demonstrated the realization of the objective of the research. Having implemented the system on

cloud, the system can easily be modified for scalability and incorporation of more functionalities.

The system if adopted, shall reduce the challenges of coordination and supervision of students on

SIWES which usually require concerned supervisors to travel long distances. Therefore, we

encourage the adoption of the system and that more research could be done to check other areas

the researchers may not have considered for better achievement of the overall objective.

5.2 Conclusion

The study was meant to simplify the process of SIWES management. To do so, we started by

reviewing some literature and observing related systems. The study was mainly focused on the

student SIWES place selection, supervisor allocation and logbook management. Nevertheless, to

meet these requirements, we had to implement more functionalities, enabling the primary ones to

work. In conclusion, a web-based application was developed for the Faculty Computing. The

problems of SIWES Place selection, supervisor allocation, data collection and logbook

management have now been simplified. Also, losing a logbook is now a talk of the past. It is

believed that the system when fully utilized, will alleviate the pain associated with the SIWES

process and also improve the efficiency and effectiveness of programme on the students in the

40
faculty. Not only in terms of what they have learnt, but also believing in doing more, knowing that

this system was also built by once a SIWES student from their faculty.

5.3 Limitation

As a result of the various stages involved in SIWES management, this work focuses only

on uploading SIWES student, printing request letter, uploading approval letter, approving or

rejecting place of attachment, assigning supervisors to students, filling logbook, commenting on

logbook, lodge complaint, view complaint, grade student etc.

5.4 Recommendations

I am writing to provide recommendations for improving the SIWES allocation and

supervising system, focusing on addressing the current limitations and enhancing the overall
effectiveness of the system. Through a thorough assessment of the system, I have identified several
areas that require attention and improvement. I believe implementing the following suggestions
will lead to a more robust and efficient SIWES program:

1. SIWES Place Search Page: Adding a SIWES place search page will enables the students
to search for a specific SIWES place by name, address and skill. It will directly link the
place name to the place detail described in Place of the SIWES information Page.
2. Chart Page: Adding a chat page that will be used for communication and sharing of files
between the lecturer and the student or even between the coordinator and all the users.

3. Integration with ITF Team: Incorporate the ITF team into the SIWES allocation and
supervising system by establishing an interface or portal that allows seamless
communication and collaboration.
4. Bank Information Management: Include a module within the SIWES allocation and
supervising system to securely manage bank information of SIWES students. This module
should allow students to input their bank details, ensuring accurate and efficient
disbursement of stipends.

41
 REFERENCES

Adetiba, E., Matthews, V., Egunjobi, V., & Olajide, A., 'Development of e-SIWES Portal: A Web
based Platform for Student Industrial Work Experience Scheme (SIWES) Management'.
International Journal of Applied Information Systems, Vol. 8, Issue 3, 2012, 10–17.

Adeyewa, Z. D., 'Modernising the Operations of the SIWES Programme : The Role of ITU and
other Stakeholders', 2015, April, 1–6.

Babalola, G., Adeyemo, O., & Adewole, L., 'Leveraging on Web-based Technology for the
Management of Students on SIWES programme in Higer Educational Institutions (HEIs):
A case study of Afe Babalola University', International Journal of Advance Research,
IJOAR .Org ISSN 2320-9194, 3, 2015, 1–13.

Bhamra, H. K., Malhotra, K. S., & Chaudhary, K., 'Campus Placement Automation', International
Journal of Engineering Development and Research, Vol. 2, Issue 4, 2016, 64–70.

Fredj, O. Ben, Cheikhrouhou, O., Krichen, M., Hamam, H., & Derhab, A., 'An OWASP Top Ten
Driven Survey on Web Application Protection Methods, In Lecture Notes in Computer
Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in
Bioinformatics)', Vol. 12528, LNCS (Issue March), 2021. Springer International
Publishing. https://doi.org/10.1007/978-3-030-68887-5_14

Gaikwad, P. P., & Bhatt, P., 'Web Development and Cryptography', International Journal of
Computer Science and Information Technologies, Vol. 5, Issue 7, 2016, pp 2240-2244.

Ibegbulam, I. J., Ejikeme, A. N., & Enem, F. N., 'Students ’ Industrial Work Experience Scheme
(SIWES) in Nigerian Universities: Perceptions of undergraduate Library and Information
Science (LIS) students. Journal of Applied Information Science and Technology, Vol. 3,
Issue 10, 2017, pp 56–66.

Kirk, J., 'Introduction to the OWASP Top Ten. OWASP Project', 2017 1–33.
https://www.owasp.org/images/a/ae/OWASP_10_Most_Common_Backdoors.pdf Li, J.
(2020)., 'Vulnerabilities mapping based on OWASP-SANS: A survey for static application

42
 security testing (SAST)', Annals of Emerging Technologies in Computing, Vol. 3, Issue4,
pp 1–8. https://doi.org/10.33166/AETiC.2020.03.001

Ogbuanya, T. C., Njoku, C. A., Kemi, P. O., & Ogunkelu, M. O., ' Evaluating the effectiveness of
Students Industrial Work Experience Scheme (SIWES) programme to ensure quality of
technical, vocational education and training in technical colleges in Lagos State. Vocational
and Technical Education, Vol. 7, Issue 10, 2018, pp 61–69.
https://doi.org/10.5897/IJVTE2018.0256

Ogunde, A. O., & Idialu, J. O., 'A recommender system for selecting potential industrial training
organizations', Engineering Reports, Vol. 3, Issue 1, 2019, pp 1–15.
https://doi.org/10.1002/eng2.12046

Oladimeji, A. O., Lawson, O. S., Olajide, O. G., & Akinfiresoye, W. A., 'Students ’ Industrial Work
Experience Scheme ( SIWES ), Rufus Giwa Polytechnic Experience , Prospescts ,
Challenges And Improvement', Journal of Multidisciplinary Engineering Science Studies
(JMESS), Vol. 4, Issue 3, 2017, pp 2458–2925. www.jmess.org

Oluwatosin, I. G., 'Secure Student Industrial Work Experience Scheme Management System',
2018 Michael, O., & Kolawole B. O., 'Mobile-based SIWES Placement Recommendation
System (A Case Study of Nigerian Universities)', International Journal of Computer
Applications, Vol. 9, Issue 152, 2016, pp 1–6. https://doi.org/10.5120/ijca2016911103

Sylvester, E., Alani, A. O., & Do, E., 'Computerization of the Students’ Industrial Work
Experience Scheme (SIWES) Registration and Payment System (SIWES-RPS) in Nigeria',
Scholars Journal of Engineering and Technology, Vol. SJET, Issue 5, 2017, pp 104–116.
https://doi.org/10.21276/sjet.2017.5.3.6

Winograd, T., Tracy, M., & Jansen, W., 'Guidelines on Securing Public Web Servers
Recommendations of the National Institute of Standards and Technology. Vol. 1, Issue 2,
2017, pp 1–142.

43
 APPENDIX A: Elicitation Evidences

INTERVIEW QUESTIONS ON DEVELOPING SIWES ALLOCATION

AND SUPERVISION SYSTEM:
Interview with the system users:

1. How is the allocation of SIWES placements determined for students?

2. Can you explain the process of supervising students during their SIWES placement?
3. What criteria are considered when approving students to specific organizations for their
SIWES program?
4. How often are students required to meet with their supervisors, and what is the nature of
these meetings?
5. What measures are in place to ensure students receive adequate support and guidance from
their supervisors during the SIWES program?
6. What steps are taken to address any challenges or issues that may arise between students
and their supervisors during the SIWES program?
7. Are there any mechanisms in place to ensure that students are placed in organizations
relevant to their field of study or career goals?
8. How would you describe the level of support and guidance you received from your
supervisor during your SIWES placement?
9. Can you describe the communication and interaction between you and the SIWES
coordinator regarding your placement? Did you have the opportunity to provide input or
express your preferences?
10. Did you have regular meetings or interactions with your supervisor? If yes, how often did
these meetings occur and what was discussed?
11. Did you have regular meetings with your supervisor to discuss your progress, challenges,
or any specific learning objectives? How did these meetings contribute to your overall
experience?
12. Were there any challenges or issues you faced with your supervisor during the SIWES
program? How were these challenges addressed or resolved?

44
45
46
 APEENDIX B: System Testing Evidence

Student Login Page

Admins Login Page

47
Upload Student Page

Allocate Supervisor Page

48
Fill Application Page

Fill Logbook Page

49
Comment on Logbook Page

50
 APPENDIX C: Codes of major functionality (align to 4.2.2)

Login Codes

Upload Student Codes

51
Fill SIWES Place Codes

Allocate Supervisor Codes

52
Fill Logbook Codes

Comment on Logbook Codes

53
 APPENDIX D: Full List of all Test Cases
S/NO TEST CASES

01 Login Authentication

02 Manage SIWES Coordinator

03 Manage Faculty

04 Manage Department

05 Manage Supervisors

06 Upload Students

07 Approved/Reject Place of SIWES

08 Assign Supervisor

09 View Complaint

10 View SIWES Applications

11 Drop Notification

12 View Student’s List

13 Change Password

14 View Assigned Students

15 View Logbook

16 Comment on Logbook

17 Grade Students

18 Submit Approval Letter

19 Fill Logbook

20 Lodge Complain

54