0% found this document useful (0 votes)

27 views

Eye Me

Uploaded by

erickryan2

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

27 views

Eye Me

Uploaded by

erickryan2

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 136

REPUBLIC OF CAMEROON REPUBLIQUE DU CAMEROON

Peace-work-fatherland Paix-travail- patrie

AFRICAN INSTITUTE OF COMPUTER MOBILE INFORMATION TECHNOLOGIES

SCIENCES - CAMEROON OFFICE AND TELECOMMUNICATION
PAUL BIYA TECHNOLOGICAL CENTER OF
EXCELLENCE B.P. 6722-YAOUNDE CAMEROUN
P.O. Box: 13719 Yaoundé www.mit2online.com [email protected]
Tel: +237.242.729.957 Fax: 22729958 Contact: (+237) 698742341 / 678414712

E-mail:[email protected] N° RCCM:RC/YAE/2018/B/2177-N° C:M071812715553X

Web site: www.iaicameroun.com

INTERNSHIP REPORT

FINGERPRINT-ASSISTED ONLINE STUDENT FOLLOW-

UP PLATFORM: case study AICS-Cameroon.

Internship carried out from 1st June to 30th September 2022

In view of obtaining a Higher Technician Diploma (HTD) in Computer Sciences
Option: Software Engineering
Written by:
ASANE DERICK ENOW

Level II Software Engineering students

Academic Supervisor: Supervision: Professional Supervisor:

Mrs. TCHINGA ALICE Mrs. KONGNI AMANDINE
Lecturer at AICS-Cameroon Computer Science Engineer at MIT²

0
FINGERPRINT-ASSISTED ONLINE STUDENT FOLLOW-UP
PLATFORM: Case study AICS-Cameroon

DEDICATION

THIS WORK IS DEDICATED TO MY FAMILY. FOR THEIR LOVE,

SUPPORT AND ENCOURAGEMENT TOWORDS MY ACADEMIC
SUCCESS.

DERICK-ASANE ASANE DERICK ENOW i

African Institute of Computer Sciences (AICS) Cameroon
Paul Biya Technological Center of Excellence
nd
2 Year Option for Software Engineering 2021/2022 Academic Year.
FINGERPRINT-ASSISTED ONLINE STUDENT FOLLOW-UP
PLATFORM: Case study AICS-Cameroon

ACKNOWLEDGEMENT

Drafting this document would have not been possible without the contribution of some
people who took upon themselves to see this work being accomplished. Our gratitude goes
to the following people:
➢ The Resident Representative of IAI-Cameroon, Mr. Abanda ARMAND Claude, for
his support, words of encouragement and the different advices on how to approach
situations.
➢ The chief executive officer of MIT², Mr. FOTSA SEGNING Lucien and his staffs for
trusting us by given us the opportunity to serve as interns in their prestigious enterprise.
➢ Our professional supervisor, Mrs. KONGNI AMANDINE Prisca for her moral
support, advice and professional expertise she shared with us.
➢ Our academic supervisor Mrs. TCHINGA ALICE for her moral support, effort and
advices throughout the academic year.
➢ To our academic teachers Mr. AGBOR ANDERSON, Mr. JIONGANG THIBAUT
AND Mr. NDENGE for their advices and assistance in realizing this document.
➢ To all my teachers of AICS CAMEROON for the knowledge they impacted me with
for me to be where I am today.
➢ For my brothers and sister for their love and support (ASANE LUCIA, ASANE
HOPE, EDET DESTINY, EDET JONES, EDET MARVELOUS AND EDET
RAPHA).
➢ The countless contributors of open-source programming community, for their great
help in learning basic skills and detecting and solving bugs.
➢ To my benches’ (bench mates) ZEUGANG WILSON AND MOBOU CASY ROSE
for their advices and cooperative support.
➢ To Mr. & Mrs. VUSHUGAH for their moral and material support.
➢ To all my classmates for their collaborative work throughout the academic year.

DERICK-ASANE ASANE DERICK ENOW ii

SUMMARY

DEDICATION ............................................................................................................................ i
ACKNOWLEDGEMENT .........................................................................................................ii
SUMMARY ............................................................................................................................. iii
LIST OF FIGURES ................................................................................................................... v
LIST OF TABLES ...................................................................................................................vii
GLOSSARY .......................................................................................................................... viii
ABSTRACT.............................................................................................................................. ix
RESUME ................................................................................................................................... x
GENERAL INTRODUCTION .................................................................................................. 1
PART ONE: INSERTION PHASE ........................................................................................... 2
INTRODUCTION ................................................................................................................. 4
WELCOME AND INTEGRATION...................................................................................... 5
GENERAL PRESENTATION OF MIT² .............................................................................. 6
ORGANIZATION OF MIT² ............................................................................................... 11
HARDWARE AND SOFTWARE RESOURCES OF MIT² .............................................. 14
BRIEF PRESENTATION OF THE PROJECT THEME .................................................... 16
CONCLUSION .................................................................................................................... 17
PART TWO: SPECIFICATION BOOK ................................................................................. 18
INTRODUCTION ............................................................................................................... 20
I. CONTEXT AND JUSTIFICATION ........................................................................... 21
II. OBJECTIVES OF THE PROJECT ............................................................................. 22
III. EXPRESSION OF NEEDS ..................................................................................... 22
IV. ESTIMATED COST OF THE PROJECT ............................................................... 24
CONCLUSION .................................................................................................................... 30
PART THREE: ANALYSIS PHASE ...................................................................................... 31
INTRODUCTION ............................................................................................................... 33
I. DESCRIPTION OF THE EXISTING SYSTEM ........................................................ 34
II. PRESENTATION OF THE ANALYSIS METHOD .................................................. 36
III. JUSTIFICATION OF THE ANALYSIS METHOD ............................................... 43
IV. MODELING OF THE SYSTM ............................................................................... 44

DERICK-ASANE ASANE DERICK ENOW iii

CONCLUSION .................................................................................................................... 62
PART FOUR: CONCEPTION PHASE .................................................................................. 63
INTRODUCTION ............................................................................................................... 65
I. TECHNICAL BRANCH ............................................................................................. 66
II. IMPLEMENTATION BRANCH ................................................................................ 69
PRELIMINARY DESIGN................................................................................................... 69
CONCLUSION .................................................................................................................... 95
PART FIVE: REALISATION PHASE ................................................................................... 96
INTRODUCTION ............................................................................................................... 98
I ENTITY RELATIONSHIP DIAGRAM ..................................................................... 99
II PRESENTATION OF DEVELOPMENT TOOLS ................................................... 100
CONCLUSION .................................................................................................................. 102
PART SIX: USER GUIDE .................................................................................................... 103
INTRODUCTION ............................................................................................................. 105
GENERAL CONCLUSION .................................................................................................. 117
ANNEXE ............................................................................................................................... 118
BIBLIOGRAPHY ....................................................................................................................xii
WEBOGRAPHY ................................................................................................................... xiii
TABLE OF CONTENT ........................................................................................................... xv

DERICK-ASANE ASANE DERICK ENOW iv

LIST OF FIGURES

Figure 1:Geolocation of MIT² Office (Source: MIT² Documentation) ................................... 10

Figure 2:Organisational chart of mit2 (Source: MIT2 Documentation) .................................. 13
Figure 3:Project Gannt Chart ................................................................................................... 28
Figure 4: UML 2.5 diagrams overview (source: https://creately.com/blog/diagrams/uml-
diagram-types-examples/) ........................................................................................................ 38
Figure 5: 2TUP diagram (Source: https://www.mysciencework.com/omniscience/pervasive-
mobile-healthcare-system-based-on-cloud-computing) .......................................................... 41
Figure 6: Use Case diagram formalism ................................................................................... 44
Figure 7:General Use Case Diagram ....................................................................................... 48
Figure 8:Student management use case diagram ..................................................................... 49
Figure 9: Attendance management Use case diagram ............................................................. 50
Figure 10:Activity Diagram Formalism................................................................................... 53
Figure 11:Attendance Recording Activity Diagram ................................................................ 56
Figure 12: Registration Activity Diagram ............................................................................... 58
Figure 13:Formalism of a state machine diagram.................................................................... 59
Figure 14:fingerprint State Machine Diagram ......................................................................... 61
Figure 15:Attendance State machine Diagram ........................................................................ 61
Figure 16:Hardware Diagram .................................................................................................. 66
Figure 17:High Level Architecture Diagram ........................................................................... 66
Figure 18: n-tier Architecture (Source: https://www.pinterest.es/pin/752241943987565648/)
.................................................................................................................................................. 67
Figure 19: The MVC architecture (Source: https://www.freecodecamp.org/news/the-model-
view-controller-pattern-mvc-architecture-and-frameworks-explained/) ................................. 68
Figure 20:Formalism of a component diagram (Source:
https://www.pinterest.com/pin/551128073157994549/) ......................................................... 69
Figure 21:Package Diagram Formalism .................................................................................. 72
Figure 22:Package Diagram Components ............................................................................... 73
Figure 23:EYE-ME mobile package diagram.......................................................................... 74
Figure 24:EYE-ME web package diagram .............................................................................. 75
Figure 25:Deployment Diagram Formalism ............................................................................ 76
Figure 26:Deployment Diagram components .......................................................................... 77
Figure 27:EYE-ME Deployment Diagram .............................................................................. 78
Figure 28:Interaction Overview Diagram Formalism.............................................................. 78
Figure 29:Communication Diagram Formalism ...................................................................... 83
Figure 30:Authentication Communication Diagram ............................................................... 85
Figure 31:Identification Communication Diagram .................................................................. 86
Figure 32:Timing Diagram Formalism .................................................................................... 87
Figure 33:Login Timing Diagram ............................................................................................ 88
Figure 34:Class Diagram Formalism ....................................................................................... 89
Figure 35:EYE-ME Class Diagram ......................................................................................... 91

DERICK-ASANE ASANE DERICK ENOW v

Figure 36:Object Diagram Formalism ..................................................................................... 93

Figure 37:EYE-ME Object Diagram ....................................................................................... 94
Figure 38:Entity Relationship Diagram ................................................................................... 99
Figure 39:Mongodb logo ....................................................................................................... 106
Figure 40:Downloading MongoDB community version ....................................................... 106
Figure 41:Lauching the installatin wizard. ............................................................................ 107
Figure 42:Clicking next ......................................................................................................... 107
Figure 43:Agreement license ................................................................................................. 108
Figure 44:Select complete setup ............................................................................................ 108
Figure 45:Run service network server user ........................................................................... 109
Figure 46:unselecting MongoDB Compass and click Next ................................................... 109
Figure 47:Click Install to start installation............................................................................. 110
Figure 48:Clicking on finish to complete installation............................................................ 110
Figure 49:EYE-ME login page .............................................................................................. 111
Figure 50:Attendance service Notification interphase ........................................................... 112
Figure 51:List of student interphase ...................................................................................... 113
Figure 52:Attendance Service Dashboard ............................................................................. 114
Figure 53:View daily attendance interphase. ......................................................................... 115
Figure 54:Parent Notification Interphase. .............................................................................. 116

DERICK-ASANE ASANE DERICK ENOW vi

LIST OF TABLES

Table 1:MIT2 partners and customers (Source MIT2 Document) ............................................ 8

Table 2:Hardware resources of MIT² (source: MIT²) .............................................................. 14
Table 3:Software resources of MIT² (Source: MIT²) .............................................................. 15
Table 4:Hardware Resource (Source:
https://www.scribd.com/document/561202966/mercuriale-2022) .......................................... 24
Table 5:Software Resources .................................................................................................... 25
Table 6:Human Resource (Source: https://www.paylab.com/) ............................................... 26
Table 7:Total Project Estimate Cost ........................................................................................ 26
Table 8:Chronogram of activities ............................................................................................ 27
Table 9:Limitation, consequence and proposed solutions ....................................................... 35
Table 10:Use case diagram component ................................................................................... 45
Table 11:Actors of our system. ................................................................................................ 46
Table 12:Authenticate Textual Description ............................................................................. 51
Table 13:Student Identification Textual Description ............................................................... 52
Table 14:components of an Activity Diagram ......................................................................... 54
Table 15:Identification Activity Diagram ................................................................................ 57
Table 16 State Machine Diagram Components: ...................................................................... 60
Table 17:Elements of a component diagram ........................................................................... 70
Table 18:EYE-ME component diagram .................................................................................. 71
Table 19:Sequence Diagram Components ............................................................................... 80
Table 20:EYE-ME Authentication Sequence Diagram ........................................................... 81
Table 21:EYE-ME Identification Sequence Diagram: ............................................................ 82
Table 22:Communication Diagram Components .................................................................... 84
Table 23:Timing Diagram Components .................................................................................. 88
Table 24:Class Diagram Components ..................................................................................... 90
Table 25:object diagram components ...................................................................................... 93
Table 26:Material Resource (https://www.mantratec.com/products/Fingerprint-
Sensors/Optical-Fingerprint-Scanner-MFS100-V2) .............................................................. 100
Table 27: Development environment..................................................................................... 101
Table 28:Framework and programming language ................................................................. 101

DERICK-ASANE ASANE DERICK ENOW vii

GLOSSARY

➢ 2TUP: Two Track Unified Process.

➢ AICS: African Institute of Computer Sciences.
➢ APK: Android Package Kit.
➢ ERD: Entity Relational Diagram.
➢ IPA: iOS App Store Package.
➢ MFS: Mantra Fingerprint Sensor
➢ MVC: Model View Controller.
➢ UML: Unified Modelling Language.

DERICK-ASANE ASANE DERICK ENOW viii

ABSTRACT

Follow-up is a word which is formed by combing two words that’s, follow and
up in other to form an idea, follow-up simply means trying to get more information about
the status or progress of something or somebody over a period of time. This project is aim
in developing an online platform in which both parent and the school administration can
better follow-up students during their academic journey. When parents send their children
to school, most of them don’t have an idea if they are effectively attending classes or not
and most at times, they just discover at the end of the academic year that their children were
not effectively schooling, after they have spent hundreds of thousands in other to secure
their education. after seeing into this problem, we decided to develop an application call
EYE-ME. with the help of EYE-ME, parents will have the ability to view their child’s
attendance status on daily basis at real-time and other vital information like the timetable,
school fees status, notifications from the school administration just to name the few.
Whereas the school administration will be able to record attendance with the help of a
fingerprint sensor and manage attendance, identify each student accurately like in the case
of exams where many students come without their badges, and it will also help to straighten
the relationship between parents and the school administration. In order to accomplish this
project, we used UML (Unified Modelling Language) as our modelling language coupled
with 2TUP (2 Track Unified Process) in order to form a Method.

Key word:
❖ Fingerprint sensor
❖ Follow-up
❖ EYE-ME

DERICK-ASANE ASANE DERICK ENOW ix

RESUME
Le suivi est défini simplement comme essayer d’obtenir plus d’informations sur
l’état ou le progrés de quelque chose ou de quelqu’un sur une periode de temps. Ce projet
vise à developer une plateforme en ligne dans laquelle les parents et l’administration de
l’école peuvent mieux suivre les étudiants pandant leur parcours academique. Lorsque les
parents envoient leurs enfants à l’école, la plupart d’entre eux ne savent pas s’ils assistent
effectivement aux cours ou non et la plupart du temps, ils decouvrent juste à la fin de
l’année academique que leurs enfants n’étaient pas effectivement scolarisés, après avoir
dépensé des centaines de milliers pour assurer leur education. Après avoir vu ce problème,
nous avons décidé de développer une application appelée EYE-ME, les parents auront la
possibilité de consulter quotidiennement l’état de frequentation de leur enfant en temps réel
et d’autres informations vitale telles que l’horaire, l’état des frais de scolarité, les
notifications de l’administration de l’école, pour n’en nommer que quelques unes. La
direction de l’ecole pourra enregistrer l’assiduité à l’aide d’un capture d’empreintes
digitales et gérer l’assiduité, identifier chaque étudiant comme dans le cas des examens ou
de nombreux étudiants se présentent sans leur badge, et cela contribuera également à
resserrer les liens entre parents et la direction de l’école.

Mot-Clé:
❖ Capteur d’empreintes digitales
❖ Suivi
❖ EYE-ME

DERICK-ASANE ASANE DERICK ENOW x

GENERAL INTRODUCTION
Nowadays, mobile devices are part and parcel of our lives, which are used for
different purposes, including educational objectives. African institute of computer sciences
which is our case study is an institute which trains thousands of software engineer each
year, it is widely known due to it level of discipline. Each year AICS-Cameroon put in
place a period of four months for level 2 students to carry out an academic internship, this
will enable students to familiarize themselves with the professional milieu, how it functions
and to know what is required of them once they transit from educational to the professional
milieu. We did our internship at “Mobile Information Technologies and
Telecommunications” (MIT2), which is a young company whose mission is to develop
mostly mobile applications for both individuals and companies. At MIT2 we worked on the
theme “FINGERPRINT ASSISTED ONLINE STUDENT FOLLOW-UP
PLATFORM” which will enable parents to view their child’s attendance status at real-
time and which will also help the school administration to record attendance in a more
appropriate way, with the help of a fingerprint sensor. To obtain these objectives, we used
6 main sections or phases which are;

The insertion phase, here we present the company in which we did our internship, and the
integration of the interns into the company;
The specification book, which identifies the need of the future system users and points out
different constraints of the project;
Analysis phase, here we choose our analysis method and the presentation of all the diagram
use for the analysis of the project;
The conception Phase, which presents the generic and detailed conception of the project
to bring out real world constituents;
The realization phase, which presents the choice of technologies and the technics
necessary for the implementation of our solution;
The user guide, which will present a user friendly and graphical description of each
functionality of the application.

DERICK-ASANE ASANE DERICK ENOW 1

PART ONE: INSERTION PHASE

DERICK-ASANE ASANE DERICK ENOW 2

Preamble

This section of our report will cover details of how we were welcomed in the host
company, the company presentation and organization, and a brief introduction to our
project.

Content overview

INTRODUCTION
I. WELCOME AND INTEGRATION
II. GENERAL PRESENTATION OF MIT²
III. ORGANISATION OF MIT²
IV. HARDWARE AND SOFTWARE
RESOURCES
V. BRIEF PRESENTATION OF THE
PROJECT

CONCLUSION

DERICK-ASANE ASANE DERICK ENOW 3

INTRODUCTION
The insertion phase is a period in which the different interns got to know more about
their host company. we got to know about the staffs, the different hardware and software
used, the different department which constitute the company and we were introduced to our
workspace, how the company functions both internally (that’s, how the different task is
schedule, the rules and regulations, working periods and so on) and externally (that’s, how
they interact with customers and delivers their products). We also had a time to discuss
amongst us interns on topics like what we love doing most, what we dislike, our believes,
our best meals, sports, songs, our temperaments, our inborn talents and those we learn as
we grow up. We shared about our different realizations and failures in life.

DERICK-ASANE ASANE DERICK ENOW 4

WELCOME AND INTEGRATION

We arrived at Mobile Information Technologies and Telecommunication (MIT²)
on Wednesday 01st June 2022, at 7:30am. We were received by the marketing agent, Mrs.
KONGNI Prisca Amandine, who introduced us to our workspace and presented all the
departments which constitute the company and their functioning. Later run, she gave us the
task to do some findings on the possible internship themes that we can work on.
After some few hours, the chief executive officer (CEO) of the company came to
our workspace, he presented himself and we did same too, he gave us a light speech on
how MIT² came into existence and the different challenges they faced. He gave us some
words of encouragement putting emphasis on integrity, faithfulness and punctuality. After
he left us, the marketing agent led emphasis on punctuality one more time and she read the
rules and regulations governing the company in an audibly manner.

DERICK-ASANE ASANE DERICK ENOW 5

GENERAL PRESENTATION OF MIT²

A. History
MIT² stands for Mobile Information Technologies and Telecommunications. MIT²
was officially created in July 2018. As its name suggest, MIT² was born to realize a lot of
ambitions such as to reduce the technological gap between Africa and the western countries
through innovation and sustainable mobile solution, to improve and normalize resource-
sharing all over the world through telecommunication and information technologies, just
to name a few. Despite the fact that it is a young company in its domain, MIT² can count
on great experience of its founders, who has realized a good number of professional
projects.

B. Missions
The mission of MIT² mainly relate to the empowerment and the perpetuation of humankind.
These missions include:
Design and realize mobile-oriented software for companies and individuals;
Assist new born companies for quick growth using computer sciences;
Provide training and certifications to improve qualified human resources in many fields of
study;
Take an active part in the sustainable development of the world through innovative
solutions and virtual reality.

C. Activities
The activities of MIT² range from computer sciences, engineering, training and selling of
computing equipment to technological innovation. We can outline the following:
• Conception realization, and hosting of websites;
• Software development and maintenance;
• Training and certification in java, oracle, cisco and other platforms;
• Conception and realization of multimedia;
• Sales of computing and technological tools
• Counselling and innovation.

DERICK-ASANE ASANE DERICK ENOW 6

DERICK-ASANE ASANE DERICK ENOW 7

D. Key Realizations of MIT²

Products:
MIT² Hotel (hotel management software);
MIT² Resto (restaurant management software);
MIT² Shop (commercial management software);
MIT² school (school management software);
MIT² Care (hospital management software);
C Network manager (managing Canal + Distribution network);
C mobile (mobile application for Renewal of Canal + bundle);

E. Company partners and customers

Table 1:MIT2 partners and customers (Source MIT2 Document)

Partners/customers logo
CANAL +

CAMPOST

Ministry of public health

AGRO service

DERICK-ASANE ASANE DERICK ENOW 8

AICS-Cameroon

VEO

CODECIS

UN women

Prodigies Hotel

DERICK-ASANE ASANE DERICK ENOW 9

F. GEOGRAPHICAL LOCATION
Mobile Information Technologies and Telecommunication is located along the Yaounde-
Mfou road, precisely the entrance to Carriere, the first four story building at your left.

Figure 1:Geolocation of MIT² Office (Source: MIT² Documentation)

DERICK-ASANE ASANE DERICK ENOW 10

ORGANIZATION OF MIT²
A. Administrative Organization of MIT²
MIT² is administratively organized as follows:

a. The General Management

This is the highest decision level of the company and it ensures the following:
✓ A good functioning of all the departments;
✓ Defines project strategies;
✓ Motivates the employees of all services;
✓ Evaluate the company activities and gives orientations etc.

b. Communication department
This department is in charge of:
✓ Multimedia communication and marketing;
✓ Management of cultural affairs;

c. Human Resource Department

This department is responsible for:
✓ Management of personnel;
✓ Recruitments;

d. Software Engineering Department

This is the department in which all the interns were assigned to. This department
is in charge of the following:
✓ Conception and Realization of programming services;
✓ Evaluation and Realization of projects.

e. Executive Secretary
This section is in charge of:
✓ Assist in general management in the achievement of its tasks;
✓ Manage internal and external mails as well as general affairs;

f. Department of Financial Affairs

This department is in charge of:
✓ Financial accounting and Taxation;
✓ Management of the company patrimony.

DERICK-ASANE ASANE DERICK ENOW 11

g. Training and Certification Department

This department is in charge of:
✓ Elaboration of training programs and projects;
✓ Training and issuing certificates after training;

h. Technical Department
This department is in charge of:
✓ Innovation;
✓ Maintenance;
✓ Telecommunication;
✓ Visual and Augmented reality;

DERICK-ASANE ASANE DERICK ENOW 12

B. Functional organization of mit²

The functional branch of MIT² is organized as follows,

General
Management
General
management

Executive
Secretary
Assist general
management

Human Marketing and Training and Sofware Network and

Financial Affairs Commercial
Resources Communication Certification Engineering Telecommunication
departement Department Department
departement Department Department Department
Accounting and Marketing Sales Training Development Maintenance
taxation Recruitment

Figure 2:Organisational chart of mit2 (Source: MIT2 Documentation)

DERICK-ASANE ASANE DERICK ENOW 13

HARDWARE AND SOFTWARE RESOURCES OF

MIT²
A. Hardware Resources

Table 2:Hardware resources of MIT² (source: MIT²)

N° Designation Quantity Characteristics Observation

1 Virtual private cloud (VPC) on 1 / Excellent

line (Amazon AWS)

2 Local server 1 HP Good

3 MacBook Pro 1 APPLE Excellent

4 Smart TV 1 Samsung Good

5 Video projector 1 EPSON Good

6 Training equipment and office / / /

furniture.

7 Mobile Modem 2 CAMTEL Excellent

DERICK-ASANE ASANE DERICK ENOW 14

B. Software Resources
Table 3:Software resources of MIT² (Source: MIT²)

OPERATING SYSTEMS APPLICATIONS ANTIVIRUS

Windows, Linux, Mac NetBeans, Eclipse, Android AVAST
Studio, Oracle, PostgreSQL,
Visual paradigm, Adobe
Master collection, 3D Max,
Sketchup, Mozilla Firefox,
Google chrome, Visual Studio
Code, Sublime Text, Jasper
Soft Studio, MySQL

DERICK-ASANE ASANE DERICK ENOW 15

BRIEF PRESENTATION OF THE PROJECT

THEME
During our insertion phase into MIT², we were asked to look for themes which solves a
specific problem and something innovative in which we did, our professional supervisor
took some time to look into what we had as themes and she also proposed some themes.
Finally, we had to go for “FINGERPRINT-ASSISTED ONLINE STUDENT
FOLLOW-UP PLATFORM”. This platform will help the school to identify students
during exams (since some students forget their badges at home and the invigilator can allow
them to write without any proper verification, and many seize the opportunity to carryout
exam malpractices) and to get in touch with parents at real-time, and it will help parents to
follow-up their children from far away distances (for them to be accountable to them
whenever they absent from classes) and also get notified on current activities of the school.
All this will help to create consciousness in students and increase productivity.

DERICK-ASANE ASANE DERICK ENOW 16

CONCLUSION
The insertion phase was a very educative one, we got to know more about the history of
the company, how it all started till the level it is right now, how it is structured and one of
its main realizations as a young company is C mobile: which is an application which helps
canal + subscribers to renew their bundle from home and use a digital remote for their
decoders, then we discovered that it’s a very serious and goal oriented company. We got to
Know the staff and other interns, in fact we felt at home. Finally, we decided to work on
the theme “FINGERPRINT ASSISTED ONLINE STUDENT FOLLOW-UP
PLATFORM”. Now that we have chosen the theme we will work on; we can move on to
the specification book of our report where we will identify the objectives and requirements
for our project.

DERICK-ASANE ASANE DERICK ENOW 17

PART TWO: SPECIFICATION BOOK

DERICK-ASANE ASANE DERICK ENOW 18

Preamble

The specification book outlines the goals to be achieved through this project and
the responsibilities of the different parties involved in the project. It specifies and describes
the subject and the needs of the users, as well the conditions necessary to realize the project.
Content Overview

INTRODUCTION
I. CONTEXT AND JUSTIFICATION
II. OBJECTIVES OF THE PROJECT
III. EXPRESSION OF NEEDS
IV. ESTIMATED COST OF THE PROJECT
V. PROJECT PLANNING
VI. LIST OF PARTICIPANTS

CONCLUSION

DERICK-ASANE ASANE DERICK ENOW 19

INTRODUCTION
The specification book of our reports helps us provide details about our theme, to
improve our understanding of it and increase the likelihood of it succeeding. To delimitate
the scope of our project, we will specify the context of our theme. From the context, we
will list the problems we have identified in our context and that we have decided to address
throughout the project. After presenting our solution, we will talk about the objective we
have set for ourselves for the project. Also, we will explore the needs to which our system
will respond both at the functional and non-functional level. We will then look at the
estimated financial requirements for our project, and establish a plan we will follow to
complete our project on time. From here we will discuss what is expected of us by the end
of the project under the project deliverables.

DERICK-ASANE ASANE DERICK ENOW 20

I. CONTEXT AND JUSTIFICATION

AICS-Cameroon which is our case study, in today’s society, education is
considered as a vital part of being accepted by the people around us, it’s something no one
can take away from you and it greatly defines your milieu of influence. An educated society
is crucial for economic growth, NELSON MANDELA once said, “education is the most
powerful weapon we can use to change the world” and we strongly believe that, one of the
key factors which plays a great role in achieving a good education is discipline.
Last, year in AICS-Cameroon, there was a student called john, who spend his whole
academic year dogging away from classes in other hangout with friends, while his parents
at home or at their job site have the impression, he is effectively school and attending
classes, he went fort tricking his parents by demanding a lot of monies in pretext that it is
requested by the school administration.
During exams John will solicit his friends to write for him since he was unable to do that
by himself due to the innumerable accumulation of absences, his parents were summoned
for the disciplinary cancel but John brought a random person to stand as his parents.
After seeing his performance at the end of the academic year, his parents were filled with
shame and disgrace, I personally felt so bad. But he is not the only one, after carrying out
some research, statistics showed that, among the students enrolled in AICS-Cameroon,
21% do not effectively school and attend classes after their guardians have spent hundreds
of thousands earned most at times from unskilled jobs in order to secure their education.

➢ How can we avoid the act of students staying back at home or elsewhere during
school periods?
➢ How can we avoid the act of students tricking their parents by extracting monies
from them?
➢ How can parents view their child’s attendance status on a daily basis?
➢ How can we ensure that students write exams by themselves?
➢ How can we replace the presence list since we need to go through several list in
order to filled or store attendance in a computer?

DERICK-ASANE ASANE DERICK ENOW 21

II. OBJECTIVES OF THE PROJECT

A. General Objective
This project as a whole has as main objective to provide parents or guardians with
ability to have access to information related to their child remotely at real-time.

B. Specific Objectives
Specifically, it will consist of:
➢ Guardians will have the ability to inspect if their child attended a class or not;
➢ The administration will have the capability to send notifications and alerts to
guardians;
➢ The administration will have the capability to identify students in the exam hall, to
ensure no student writes for another and for other occasions;
➢ Change the system of talking attendance from manually to digitally.

III. EXPRESSION OF NEEDS

A. Functional needs
Functional needs describe what the users can do on the system. There are listed
below as follows:
❖ Alert and notifications;
❖ Managements of user’s accounts;
❖ Monitoring conduct;
The above functionalities are explained below:
• Alert and notifications: permit guardians to receives information from the administration
concerning the wellbeing of their child.
• Management of user’s accounts: The admin will be able to add, delete, modify the
different accounts.
• Monitoring conduct: parents or guardians will be able to view the conduct of their child
like number of absences.

DERICK-ASANE ASANE DERICK ENOW 22

B. Non-functional Needs
i. Hardware requirements
Portability and ease of installation: the hardware should be light-weight and easily
transportable; it should require little or no skill to install and setup guide.
Reusability and Reliability: fingerprint sensors should be reusable
Compatibility: The fingerprint sensor should be compactible from one mobile device to
and other without any issues.

ii. Software requirements

Security: since our system manages student information, a good mechanism should be
implemented to give access to the system just to authorized users.
Performance: the software should provide a user-friendly interface. It should easily and
readily connect to the hardware. Students’ identification should be done in little frame time
with a worst case 12 seconds and a best case 2of 0.25 seconds.
Parents or guardians should easily login and logout from their account without any
constraint.

1
Worst case: represents the poorest outcome we can obtain for a particular situation
2
Best case: represents the optimum performance of a particular system or thing.

DERICK-ASANE ASANE DERICK ENOW 23

IV. ESTIMATED COST OF THE PROJECT

A. Hardware Resources

Table 4:Hardware Resource (Source: https://www.scribd.com/document/561202966/mercuriale-2022)

RESOURCE HARDWARE USAGE QUANTITY UNIT

S COST(FCFA)
COMPUTER DELL main resource for 1 368000
Windows 10 pro 64 bits, the
Latitude E6520, 8GB RAM, accomplishment of
500GB hard disk; intel core this project; report
i5. writing, designs,
analysis, coding
Fingerprint Mfs-100-mantra Captures and 1 85230
sensor transmit fingerprint
biometrics into the
application.
Mobile phone AQUOS Testing of 2 80000
4 GB RAM, 64 GB hard disk functionalities.

Removable 8GB USB key For file transfer 1 6325

disk from one computer
to another.
CD CD-ROM 3 3000

MODEM 4g LTE-advanced mobile Used to share 1 23000

Wi- internet access
Fi hotspot mq531 150mps amongst devices
Total 3 559862

DERICK-ASANE ASANE DERICK ENOW 24

B. Software Resources
Table 5:Software Resources(https://www.g2.com/categories/pricing)

RESOURCES HARDWARE USAGE QUANTITY UNIT COST(FCFA)

Development tool Visual studio code Code editing 1 Open source

Project planner Gantt project Project 1 Free software

planning tool

Operating system Microsoft windows Computer 1 103000

10 pro operating
system

Text Editor Microsoft office For typing and 1 161000

word 2019 formatting of
report

Presentation Microsoft office For making 1 84230

PowerPoint 2019 presentations

Modelling tool Visual-paradigm Modelling the 1 3350

Modeler version system in uml

Geo-location plan Microsoft Visio To draw 1 Free version

designing tool 2007 location plan

Web browser Google chrome For running and 1 Free version

testing
application

Database PostgreSQL Communing 1 Open source

management with the
system database

Total 2 351580

DERICK-ASANE ASANE DERICK ENOW 25

C. Human Resources

Table 6:Human Resource (Source: https://www.paylab.com/)

RESOURCES NUMBER COST PER DAY NUMBER OF COST (FCFA)

DAYS

Project manager 1 250000 60 15000000

Analyst 1 150000 30 4500000

Designer 1 130000 25 3250000

Programmer 1 100000 32 3200000

TOTAL 3 4 25950000

D. Total Project Estimated Cost

Table 7:Total Project Estimate Cost

Total 1(FCFA) Total 2(FCFA) Total 3(FCFA) Overall total (FCFA)

559862 351580 25950000 26861442

Margin of error = 10% of Overall total

=2686144.2 FCFA
Final Total = Overall Total + margin of Error
=29547586.2 FCFA

DERICK-ASANE ASANE DERICK ENOW 26

I. PROJECT PLANING
a. Chronogram of activities
Table 8:Chronogram of activities

PHASE OBJECTIVE OUTPUT DURATION PERIOD

Insertion Welcome and Insertion 2weeks 01st to 14th June 2022

installation into report
the into the
company, and the
attribution of
themes
Specification Assessment of Specification 1week 6days 15th to 28th June 2022
functional needs book

Analysis Analysis of the Analysis book 3weeks 29th June to 19th July
system 2022

Conception Hardware and Conception 2weeks 20th July to 09th august

software book 2022
conception

Realization Realization of the Realization 4weeks 2days 10th august to 09th

system document September

Deployment Deployment of the Testing of the 1week 2days 12th to 20th September
system software and
debugging

Writing user guide Instructions on User guide 1week 3days 21st to 30th September
how to use the
software and
hardware

DERICK-ASANE ASANE DERICK ENOW 27

b. GANTT CHART

Figure 3:Project Gannt Chart

DERICK-ASANE ASANE DERICK ENOW 28

E. LIST OF PARTICIPANTS AND DELIVERABLES

a. List of participants

NAME TITLE ROLE

Mrs. TCHINGA ALICE Lecturer at AICS-Cameroon Academic supervisor

Mrs. KONGNI AMANDINE Computer science engineer Professional supervisor

at MIT2
ASANE DERICK ENOW software engineering Analyst and developer
student at AICS-Cameroon

b. Deliverables
we are supposed to submit a report at the end of this project that includes;
➢ A user guides.
➢ We are also expected to submit CD ROM containing the mobile application
IPA3 and APK4

3
IPA (iOS APPLICATION SOFTWARE PACKAGE) An .ipa file is an iOS application archive file which
stores an iOS app.
4
APK (ANDRIOD APPLICATION PACKAGE) It is a file format used by android operating system for the
distribution and installation of mobile applications.

DERICK-ASANE ASANE DERICK ENOW 29

CONCLUSION
The specification book helps us to site the different needs we need in order to
implement our application for student follow-up, we saw list of participants and
deliverables for our project. In time allocated for this section, we were able to accomplish
the different task, we will move directly to the next phase which is the analysis phase. In
the analysis phase we will study the existing system in detail and model our system with a
modelling language and process.

DERICK-ASANE ASANE DERICK ENOW 30

PART THREE: ANALYSIS PHASE

DERICK-ASANE ASANE DERICK ENOW 31

Preamble
After specification book, we have the Analysis phase which permits us to represent
a detailed analysis of the limitations identified in our context, and our solution, through a
software development process and modelling language.

Content Overview

INTRODUCTION

I. DESCRIPTION OF THE EXISTING SYSTEM.

II. PRESENTATION OF THE ANALYSIS
METHOD
III. JUSTIFICATION OF THE ANALYSIS
METHOD
IV. MODELING OF THE SYSTEM

CONCLUSION

DERICK-ASANE ASANE DERICK ENOW 32

INTRODUCTION
The analysis book permits us to examine in an explicit way the existing system,
it’s limitations and how we can remedy them. We will also describe in details the modeling
language known as UML (Unified Modeling Language) which is coupled with Two Tract
Unified Process (2TUP) to form a method and its justification why we decided to use it in
preference of another. then we will dive directly into the modeling of the proposed solution
consisting of diagrams that meets the requirements of the functional needs.

DERICK-ASANE ASANE DERICK ENOW 33

I. DESCRIPTION OF THE EXISTING SYSTEM

Each week a class list is deposited in each class in order for the class delegate to
carry out the roll call in order to record the attendance for that day, and most at times the
class delegate will favor his friends who are not in class by recording them present thinking
he is helping them, and when these lists are collected at the end of each week, it being
manage by an excel document and it makes at least a month before attendance statistics is
pasted in each class room for justifications. During exams the invigilator will check each
student writing, by looking his/her name on the badge if it corresponds to the name writing
on the answer sheet. When the administration schedules a date for the disciplinary cancel,
most at times students are the once to inform their parents about it. Parents see their Child’s
attendance status only at the end of academic year and they have no idea, if their child went
to school effectively or not and they also have no idea if their child actually paid their
school fee or not. This study helps us to detect some limitations and their consequences,
and after closely reviewing everything, we proposed some solutions which can be applied
to this system.

DERICK-ASANE ASANE DERICK ENOW 34

Table 9:Limitation, consequence and proposed solutions

LIMITATION CONSEQUENCE PROPOSED SOLUTION

Attendance is done manually The class delegate might favor EYE-ME which will enable the
with the use of a class list and his friends by marking them recording of attendance with an
it takes a month before the present while they not actually automatic generation of attendance
attendance statistics is in class, and somethings those statistics which will permit students
pasted for justification. who are in class are marked to see their attendance status at real
absent by mistake too. time.
During exams many Most at times students who EYE-ME has an interphase that will
students forget their badges forget their badges at home are permit the invigilators to check each
at home and the invigilator those students who have the student writing the exams with the
might allow them to take the intention to carryout help of a fingerprint sensor. So that,
exams. examination malpractices, no student writes for another
they will write for their friends student, since a fingerprint is unique
with the impression they are to every student.
helping them.
Parents see their child’s During the academic year a EYE-ME will permit parents to
conduct status just at the end student might stay back at have information concerning their
of the academic year. home especially those renting child’s status at real-time and which
around the school campus, and will permit each student to be
their parents will have no idea accountable to their parents in case
if they were in school. they are not in school.
Students are the once to Most at time when students EYE-ME will enable parents to
inform their parents commit crimes or when they receive instant notifications and
concerning any issue of the don’t want their parents to alert. Concerning the current
school like informing his know what they actually do activities of the school
parents on the different while in school, they will look administration.
schedules for the for a random person to stand as
disciplinary cancel. their parents, while their
parents have no idea on what is
happening.

DERICK-ASANE ASANE DERICK ENOW 35

II. PRESENTATION OF THE ANALYSIS METHOD

We have studied in details some analysis methods by looking at its objectives,
its structuring, its pros and cons, so as to choose an analysis method which is reliable and
adaptive to our project, below are some analysis methods we studied and a brief explanation
in order for you to understand why we made our choice;

1. MERISE: it is an information system design and development widely used in

France. It was first early introduced in 1980s.
2. Agile: this methodology is growing in popularity, thanks to highly competitive
business environment and increased innovation. In general, agile methodologies
prioritized shorter, interactive cycle and flexibility.
3. Scrum: this is the most popular agile development framework because it is
relatively simple to implement. It also solves so many problems that software
developers struggle with in the past, convoluted development cycles, project plan,
and shifting production schedules. This methodology allows for rapid development
and testing, especially with small teams.
4. APF: which stands for ADAPTIVE PROJECT FRAMEWORK, it grows from the
difficulty in managing most IT projects using traditional project management
methods due to uncertain and changing requirement. APF begins with a requirement
breakdown structure (RBS) to define strategic goals based on productive
requirements, functions, sub-function and features. The project proceeds in iterative
stages, and at the end of each step, teams evaluate previous results to improve
performance and practices.
5. XP: which stands for Extreme Programming is a software development
methodology that advocate frequent releases in short development cycles, which is
intended to include checkpoints for the adoption of new customer requirements and
improve productivity. This methodology takes its name from the idea that the
traditional software engineering practices are taken to extreme levels.

DERICK-ASANE ASANE DERICK ENOW 36

A. MODELING WITH UML 2.5

The unified modeling language (UML) is a general purpose, developmental modeling
language in the field of software engineering that is intended to provide a standard way to
visualize the design of a system.
The Unified Modeling Language (UML) was standardized in January 1997 by the
Object Management Group (OMG) which is an American association created in 1989 and
aims to promote and standardize the object model in all it forms. In 2005, UML was also
published by the international organization for standardization (ISO) as an approved ISO
standard. Uml since 2015 is in its version 2.5. This version consists of fourteen diagrams
classified into structural and behavioral diagrams

a. Structural Diagrams:
Structural diagrams represent the static components of a system; they emphasize
on what should be in the system we are modeling. They include:
✓ Class diagram;
✓ Object diagram;
✓ Package diagram;
✓ Composite structural;
✓ Deployment diagram;
✓ Component diagram;
✓ Profile diagram.

DERICK-ASANE ASANE DERICK ENOW 37

b. Behavioral Diagrams:
The behavioral diagrams capture the dynamic state of a system; they emphasize on what
should happen in the system we are modeling. They are:
✓ Use case diagram;
✓ Activity diagram;
✓ State machine diagram;
✓ Sequence diagram;
✓ Communication diagram;
✓ Interaction overview diagram;
✓ Timing diagram.

c. UML 2.5 diagrams overview

Figure 4: UML 2.5 diagrams overview (source: https://creately.com/blog/diagrams/uml-diagram-types-examples/)

It is important to note that uml is a modeling language and not a method or procedure.
Hence, to give it an approach, we need to associate UML to a Unified process (UP) in order
to give our conception a methodology to follow. A unified process is a generic method for

DERICK-ASANE ASANE DERICK ENOW 38

developing software. This implies it is necessary to adapt the UP to the context of the
project, team domain and or the organization. We will use the Two Tracks Unified Process
(2TUP) throughout our project to implement our solution.

DERICK-ASANE ASANE DERICK ENOW 39

B. The Process of Development of a Software

A process can be defined as a partially sequence of steps that permits us to obtain
software systems or evolution of an existing one. The main objective of software
development is the production of quality software that response to the needs of the users
during a particular time and at a particular cost.

a. A Unified Process
A unified Process is a process of development of software constructed on UML; it is
iterative, incremental, centered on architecture, driven by use cases and requirements.
Iteration is distinct sequence of activities with a basic plan and evaluation criterion that
produces an internal or external output. Either the content of an iteration is improved or the
evolution of the system is evaluated by users.
An increment is the difference between two released products at the end of two iterations.
Each iteration that the group is capable of integrating the technical environment in order to
develop a final product and give users the possibility of having tangible results.
Centered on architecture the different models derived during the establishment of system
must be reliable and coherent.
Driven by use case and requirements enables the clear definition of a users’ needs and
priorities respectively thereby minimizing the risk of project failure.

b. The Two Track Unified Process (2TUP)

2TUP is a unified process which is belt on UML and has as objective to bring
solution to constraints of functional and technical changes imposed on information systems
by strengthening controls on development capacities. It proposes a Y-sharped development
life cycle that separates the functional aspect from the technical aspects, and the merging
of these two forms the implementation aspect. 2TUP distinguishes therefore two branches:
the functional and technical branches, the combination of the result of these two branches
forms the third: the realization branch – where we realize our system. The diagram bellow
illustrates the branches of 2TUP.

DERICK-ASANE ASANE DERICK ENOW 40

Figure 5: 2TUP diagram (Source: https://www.mysciencework.com/omniscience/pervasive-mobile-healthcare-system-based-

on-cloud-computing)

a. The left branch (functional branch)

It captures the functional needs of a system. This ensures the production of software
that meets the needs/requirements of the user. The analysis here consists of studying
precisely the functional specification in order to obtain an idea of what the system is going
to realize and its result does not depend on any technology.
b. The right branch (Technical branch)
The technical branch enumerates the technical needs and proposes a generic design
validated by a prototype. The technical needs include constraints and choices related to the
conception of the system, the tools and equipment as well as the integration constraint with
the existing system condition. The different diagrams are shown in the table below.
c. The middle branch (Realization or implementation branch)
In this branch, we study the preliminary conception, detailed conception, and
documentation of the system. The realization branch supports the following:
Preliminary conception: This is the most sensitive step of 2TUP as it is the confluence of
the functional and technical branch. It is completed when the deployment model, the

DERICK-ASANE ASANE DERICK ENOW 41

operating model, the logical model, interphases and the software configuration model are
defined.
Detailed conception: This is the detailed design of each feature of the system.
Coding and testing: This are the phase where we program the designed features and test
the coded features.
The recipe: Also known as the deliverables is the validation phase of the functions of the
developed system.

DERICK-ASANE ASANE DERICK ENOW 42

III. JUSTIFICATION OF THE ANALYSIS

METHOD

The reason why we chose UML modelling language and the software development process
2TUP instead of many others that exist, include:
UML is the current standard for programming in an object-oriented language. For
this reason, it is widely understood and well known making it easy for a new programmer
to join the project and be productive from the very first day.
UML diagrams allow teams to virtualize how a project is or will be working, and
they can be used in any field, not just software engineering. The diagrams will allow teams
to virtualize together how a system or a process will work or did work. It can provide new
ideas for how teams have to collaborate to achieve the goal of the workflow process.
2TUP is centered around the creation and maintenance of a model, rather than the
production of mountain documents.
2TUP is user oriented as it permits the development of software that responds to the
needs of the users through the study of the user needs.
2TUP is iterative and incremental, hence it enables the project team to produce
refined amelioration if necessary and easily integrate it in the already existing system.
2TUP by permitting the project team identify and test the key functionalities of the
system limits the risk related to building the system.

DERICK-ASANE ASANE DERICK ENOW 43

IV. MODELING OF THE SYSTM

A. Capture of Functional Needs
The first step of the left (functional) branch of Two Track Unified Process (2TUP) is the
capture of the functional needs. At this step, we capture the intended behavior of the system
that maybe express as services, tasks or functions the system is required to perform.

1. Use Case Diagram

a) Definition
A use case diagram shows the functionalities of a system, their interdependencies
and how they relate with actors of the system. A use case is a specification of behaviour.
The main objectives of the use case diagram are:
• Provide a high-level view of the system;
• Identify the functions of the system.
Use case diagrams are completed with a textual description of each use case that is intended
to define the use case in greater details.
b) Formalism

Figure 6: Use Case diagram formalism

DERICK-ASANE ASANE DERICK ENOW 44

Table 10:Use case diagram component

Elements Notation Description

Actors Represents an entity that
directly interacts with the
system. The actor is what
performs the different possible
actions of the system.
Use case A use case represents a
Use Case functionality of the system. It is
1
an action that can be performed
by an actor.
Association it indicates that an actor takes
part in a use Case.

Include An inclusion denotes that an

included action must be
performed before the including
action can be performed.

Extend An extension denotes that an

extending action may be
performed while an extended
action is being performed.
Generalization This shows that an actor or a use
case is a kind of another abstract
or concrete actors can be
defined and later specialized
using generalization
relationship.

DERICK-ASANE ASANE DERICK ENOW 45

Elements Notation Description

System It is a container of use cases
which interact with external
actors

c) The Actor of our System

After the study of the current system in AICS-Cameroon, in other to implement
our proposed solution, we identified the actors listed in the table below.

Table 11:Actors of our system.

Actor Role

Parents Their responsibility is to follow-up dear

children at real-time. They can view
attendance, school fee status, and other vital
information.
Class Delegate He is in charge of recording attendance of
students, on daily basis.

Identification Service He can identify a random student at the

campus, during exams or on special occasions.

Administrator The administrator is in charge of the general

functioning of the system. .

Attendance Service They play the major role in the system, such as
manage students, attendance, etc

DERICK-ASANE ASANE DERICK ENOW 46

Fingerprint Sensor Its role is to register each student uniquely and

to identify a random student.

SMS API Is used send a unique code to parents during the

registration of a particular student

Geolocation API Is is used get the position class delegate during

the recording of attendance.

DERICK-ASANE ASANE DERICK ENOW 47

d) General Use Case Diagram

Figure 7:General Use Case Diagram

DERICK-ASANE ASANE DERICK ENOW 48

e) Student management Use Case diagram

Figure 8:Student management use case diagram

DERICK-ASANE ASANE DERICK ENOW 49

f) Attendance management Use case Diagram

Figure 9: Attendance management Use case diagram

DERICK-ASANE ASANE DERICK ENOW 50

g) Textual description of use cases

Table 12:Authenticate Textual Description

Actors Student delegate, identification service,

parents, Administrator
Goal in context: Permit client to access the system,

Pre-condition(s) 1. The actor already has an account;

2. The app is launched;

Nominal scenario 1. The actor clicks on the login button;

2. The system opens the login page;
3. The actor fills and submit the form;
4. The system verifies the credentials;
5. System opens the accounts home page.
Alternative scenario At step (4) of the nominal scenario, if the user’s
credentials are incorrect, the system sends an error
message and takes the user back to step (2) of the
nominal scenario.
Post-condition: User logs in successfully.

Failed closing condition: User not granted access.

DERICK-ASANE ASANE DERICK ENOW 51

Table 13:Student Identification Textual Description

Actors identification service, Administrator

Goal in context: Permits the school administration to easily identify each

student uniquely.
Pre-condition(s) Users should have login to the account.

Nominal scenario 1. User clicks on the identification button;

2. The system displays the identification page;
3. The user enters a particular name;
4. The system verifies the input;
5. The system displays the student information;
Alternative scenario 1. If the system does not find record with that name, it
displays an error message and it moves back to step (2)
in the Nominal scenario.
Post-condition: Student found.

Failed closing condition: Student not found

DERICK-ASANE ASANE DERICK ENOW 52

2. ACTIVITY DIAGRAM
a) Definition
An activity diagram is a graphical representation of workflows that show the steps needed
in the realization of a process; showing the details from a start point to an end point through
all decisions and actions that can possible be performed. Activity diagrams are intended to
model both the computational and organizational process. They flow can be sequential,
branched or concurrent. Below is an activity diagram formalism.
b) Formalism:

Figure 10:Activity Diagram Formalism

DERICK-ASANE ASANE DERICK ENOW 53

Table 14:components of an Activity Diagram

Elements Diagrammatic Representation Description

Activity Use to represent a set of

actions.

Action Represent a task to be

performed.

Activity edge A directed connection between

two activity nodes through
which tokens may flow.
Initial node Shows the beginning of an
activity or set of actions.

Final node Stops all controls and object

flows in an activity.

Object node Represents an object

connected to a series of object
flows.
Decision node Represents a test condition
that slits an incoming activity
edge into opposite outgoing
activity edges.
Merge node Reunite different decision
paths created using a decision
node.
Fork node Slits behaviour into parallel or
concurrent flows of activities
(or actions)

DERICK-ASANE ASANE DERICK ENOW 54

Join node Unites a set of parallel or

concurrent flows of activities
or actions.

Swimlane and partition A way of grouping activities

performed by the same actor in
an activity diagram or to group
actions in the same thread.

DERICK-ASANE ASANE DERICK ENOW 55

c) Attendance Recording Activity Diagram

Figure 11:Attendance Recording Activity Diagram

DERICK-ASANE ASANE DERICK ENOW 56

d) Identification Activity Diagram

Table 15:Identification Activity Diagram

DERICK-ASANE ASANE DERICK ENOW 57

e) Student Registration Activity Diagram

Figure 12: Student Registration Activity Diagram

DERICK-ASANE ASANE DERICK ENOW 58

3. State Machine Diagram

a. Definition
A state machine diagram describes the behaviour of a single object in response to a
series of events in a system. Also known as the state machine diagram, it models the
dynamic flow of control from the state of a particular object within a system.
b. Formalism

Figure 13:Formalism of a state machine diagram

DERICK-ASANE ASANE DERICK ENOW 59

Table 16 State Machine Diagram Components:

Element Diagram Relationship Description

State Models a situation during

which a certain invariant
condition holds.

First (Initial) State It represents a default vertex,

that is, a source for a single
transaction to the default or
composite state.
Final State A state specifying that the
enclosing region is complete.

Transition A direction relation between a

source and a target vertex.

Choice pseudo State A diamond symbol that

indicates a dynamic condition
with branched potential results

Terminate Implies that the execution of a

state by means of it context is
terminated.
Diagram Overview A placeholder for the linked
states in a state machine
diagram.

DERICK-ASANE ASANE DERICK ENOW 60

c. Fingerprint State Machine Diagram

Figure 14:fingerprint State Machine Diagram

d. Student State Machine Diagram

Figure 15:Attendance State machine Diagram

DERICK-ASANE ASANE DERICK ENOW 61

CONCLUSION
In the analysis phase, we chose a software development process and modelling
language, after which we presented the existing system, its limitation and our proposed
solutions. We went forth explaining the functional need of our system, we saw the use case
diagram which shows the relationship between the actors and use case (the action the actor
can perform on the system), we saw the activity diagram which shows the workflow of our
system, and lastly the State machine diagram which shows the behaviour of a single object
in response to an event. We will now move to the conception phase in which we will present
the other two branches of the 2TUP which are the Technical and the realization branch of
our system.

DERICK-ASANE ASANE DERICK ENOW 62

PART FOUR: CONCEPTION PHASE

DERICK-ASANE ASANE DERICK ENOW 63

Preamble
The conception phase will permit us to present in an orderly manner the components
necessary for the good functioning of our software and also the architecture used for the
proposed solution. It bridges the gap between the analysis phase and the realization phase.
Content Overview

INTRODUCTION
I. TECHNICAL BRANCH
A. Generic Design
II. IMPLIMENTATION BRANCH
B. Preliminary Design
C. Detailed Design
CONCLUSION

DERICK-ASANE ASANE DERICK ENOW 64

INTRODUCTION
The conceptual phase will describe in details the necessary specifications, features and
operations that will satisfy the functioning requirements of the proposed system as
modelled in the analysis phase. This phase is meant to identify and consider essential
components (hardware /or software), structure (network capabilities), processes and
procedures for the system to accomplish it objectives. We will look at some diagrams such
as the component diagram, package diagram, communication diagram, class diagram and
the object diagram.

DERICK-ASANE ASANE DERICK ENOW 65

I. TECHNICAL BRANCH
A. GENERIC DESIGN
a. Hardware diagram of the system
The hardware diagram simply shows how the system components of our system are
deployed; it shows the positioning of each device into it right proportion.

Figure 16:Hardware Diagram

b. High Level Architectural Diagram of the Software

The high-level architecture diagram provides an overview of the entire system, identifying
the main components that would be developed for the product and their interfaces. The
high-level architecture diagram below illustrates this.

Figure 17:High Level Architecture Diagram

DERICK-ASANE ASANE DERICK ENOW 66

B. CAPTURES TECHNICAL NEEDS

a. Physical architecture
The design of the DBMS depends on its architecture. An n-tier architecture partitions on
the whole system into related but separated n modules, which can be independently
modified, altered, changed or replace. A large amount of data on web servers, personal
computers (pc) and others are link with networks with the help of basic client or server
architecture.
Within the scope of our project, we made use of the multi-tier architecture This
architecture separate it tiers from each other based upon the user and the manipulated data
in the database. It is important to note that with the multi-tier architecture, only neighboring
layers can communicate. Each layer has a well-defined communication interface and the
evolution of the layer is independent of the other. The multi-tier of our system is made up
of:
❖ The hardware tier, which represents our fingerprint sensor and it is connected directly
to our mobile phone using a wired connection.
❖ The client tier, which is also known as our presentation interphase.
❖ Application Tier, which represents our webserver.
❖ The data tier, which represents our DBMS server

Figure 18: n-tier Architecture (Source: https://www.pinterest.es/pin/752241943987565648/)

DERICK-ASANE ASANE DERICK ENOW 67

c. Logical architecture
Model View controller or MVC as it is popularly called, is a software design patten for
developing application. A model view controller patten is made up of the following three
parts.
✓ Model: The lowest level of the patten which is responsible for maintaining data.
✓ View: This is responsible for displaying all or a portion of data to the user.
✓ Controller: It handles software codes that controls the interactions between the model
and the view.
MVC is popular as it isolates the application logic from the user interface and
supports separation of concerns. Here the controller receives all requests for the application
then works with the model to prepare data needed by the view. The view then uses the data
prepared by the controller to produce a final response. The MVC can be represented as
follows.

Figure 19: The MVC architecture (Source: https://www.freecodecamp.org/news/the-model-view-controller-pattern-mvc-

architecture-and-frameworks-explained/)

DERICK-ASANE ASANE DERICK ENOW 68

II. IMPLEMENTATION BRANCH

Here we will see the preliminary conception, detailed conception and
documentation of the system.

PRELIMINARY DESIGN
1. Component diagram
a. Definition
Component diagrams are used to model the physical aspect of a system. Now the question
is what are this physical aspect? They are elements such as Executables, libraries, files,
document etc. which resides in a node. The component diagram does not describe the
functionality of the system but it describes the components used to make those
functionalities.

b. Formalism

Figure 20:Formalism of a component diagram (Source: https://www.pinterest.com/pin/551128073157994549/)

DERICK-ASANE ASANE DERICK ENOW 69

Table 17:Elements of a component diagram

NAME REPRESENTATION DESCRIPTION

A component A component is an abstract logical

unit block of a system.it is
represented as a rectangle with
smaller rectangle in the upper right
corner which saves as it icon for
recognition.

Dependency Dependency is a directed

relationship which is used to show
that some components are
dependent on others for their
correct functioning.
interface An interface is a circle or a semi-
circle attached to a stick which
looks like a lollipop. It describes
groups of operations provided or
required by components.
port A port (represented by a small
square at the end of a required or
provided interface) is used when
the components delegate the
interfaces to an internal class.

DERICK-ASANE ASANE DERICK ENOW 70

c. System component diagram

Table 18:EYE-ME component diagram

DERICK-ASANE ASANE DERICK ENOW 71

2. Package Diagram
a. Definition
This is a structural diagram used to show the organization and arrangement of various
model elements in the form of packages. A package diagram is the grouping of related uml
elements such as classes, diagrams or eve other packages.

b. Formalism

Figure 21:Package Diagram Formalism

DERICK-ASANE ASANE DERICK ENOW 72

Figure 22:Package Diagram Components

NAME Representation Description

Package A package is a namespace

use to group related
elements; it is a mechanism
used to group elements into
a better structure in a
system.
Package import A relationship Indicate that,
functionality has been
imported from one package
to another.

Package access A relationship Indicates that

one package requires
assistance from the function
of another package.

Package merge It is a relationship which

shows that, the functionality
of two packages are
combines to a single
function.

DERICK-ASANE ASANE DERICK ENOW 73

c. Mobile package Diagram

Figure 23:EYE-ME mobile package diagram

DERICK-ASANE ASANE DERICK ENOW 74

d. Web Package Diagram

Figure 24:EYE-ME web package diagram

DERICK-ASANE ASANE DERICK ENOW 75

3. Deployment Diagram
a. Definition
Deployment diagram is a structural diagram used to visualize the topology of the physical
components of a system, where the software is deployed. They consist of nodes and their
relationship. It is related to the component diagram because the components are deployed
using the deployment diagram. A deployment diagram consists of nodes. Nodes are nothing
but physical hardware used to deploy the application.
b. Formalism

Figure 25:Deployment Diagram Formalism

DERICK-ASANE ASANE DERICK ENOW 76

Figure 26:Deployment Diagram components

Element Representation Description

Node It is a hardware used to
deploy the application

Artifact An artifact is a major

product, which is
produced or used during
the development of a
software. E.g diagrams,
data models, setup scripts
Component It represents a modular
part of a system that
encapsulates its content
and whose manifestation
is replaceable within it
environment.
Association An association helps to
connect two nodes
together which permits
them to communicate
together

DERICK-ASANE ASANE DERICK ENOW 77

c. System Deployment Diagram

Figure 27:EYE-ME Deployment Diagram

Figure 28:Interaction Overview Diagram Formalism

DERICK-ASANE ASANE DERICK ENOW 78

A. DETAILED DESIGN

4. Sequence Diagram

a. Definition
A sequence diagram is an interaction diagram which represents the flow of message
between elements in a system, it is termed as an event diagram. It portrays the
communication between any two lifelines as a time-ordered sequence of events.
b. Formalism

DERICK-ASANE ASANE DERICK ENOW 79

Table 19:Sequence Diagram Components

Element Representation Description

Lifeline An individual participant in a

sequence diagram, it is
position at the top of the
diagram.

Combined fragment It represents a choice of

behavior in which at most one
operand will be chosen.

Messages These are arrows which shows

the direction of message flow.
We have the synchronous, the
asynchronous and the self-
messages.

Activation It describes the time period in

which an operation is
performed by an element.

DERICK-ASANE ASANE DERICK ENOW 80

c. Authentication Sequence Diagram

Table 20:EYE-ME Authentication Sequence Diagram

DERICK-ASANE ASANE DERICK ENOW 81

d. Identification Sequence Diagram

Table 21:EYE-ME Identification Sequence Diagram:

DERICK-ASANE ASANE DERICK ENOW 82

5. Communication Diagram

a. Definition
It is a diagram which is used to show the relationship between the actors of a system, both
the sequence and the communication diagrams represent the same information but
differently. Instead of showing the flow of message. It depicts the architecture of the object
residing in the system as it is based on object-oriented programming.

b. Formalism

Figure 29:Communication Diagram Formalism

DERICK-ASANE ASANE DERICK ENOW 83

Table 22:Communication Diagram Components

Element Representation Description

Object An actor represents an

individual participant in the
interaction conversation.
link It initiates an association it
connects two objects
together for them to
communicate.
Actor A role play by an entity that
interacts with the subjects.

message Defines a particular

communication between
lifelines in an interaction.

DERICK-ASANE ASANE DERICK ENOW 84

c. Authentication Communication Diagram

Figure 30:Authentication Communication Diagram

DERICK-ASANE ASANE DERICK ENOW 85

d. Identification Communication Diagram

Figure 31:Identification Communication Diagram

DERICK-ASANE ASANE DERICK ENOW 86

6. Timing Diagram

a. Definition
Timing is used to show the interactions when a primary purpose of a diagram is to be reason
about time; it focuses on conditions changing within and among lifelines along a linear
time axis. Timing diagram is a special form of a sequence diagram. The most notable
graphical difference between timing and sequence diagram is that, time dimension in timing
diagram is horizontal and the time is increasing from left to right and the lifeline are shown.
In separate compartments arranged vertically. The timing diagram is available since UML
version 2.0 and includes elements such as message lifeline, timeline and object or role.
b. Formalism

Figure 32:Timing Diagram Formalism

DERICK-ASANE ASANE DERICK ENOW 87

Table 23:Timing Diagram Components

Element Description

Lifeline One of the participants involved in the interaction.

State line Shows the state of a participant at a given time.

State This is the state of a participant (classifier or attribute) during a

particular time interval.
Time constraint This is a specific moment in the execution of a process.

Duration The duration constraint is the time interval between two specific
constraint moments.

c. Login Timing Diagram

Figure 33:Login Timing Diagram

DERICK-ASANE ASANE DERICK ENOW 88

7. Class Diagram

a. Definition
A class diagram is a static diagram. It represents the static view of an application. class
diagram is not only used for visualizing, describing and documenting different aspect of
the system but also for constructing executable code of the software application. Class
diagram describes the attribute and operation of a class and also constraints imposed on the
system. It purpose is to model the static view of an application.
b. Formalism

multiplicity
private (accessible
only within the class class name 0..1
scope)
- Attribute : int

0..*

public Classe_2
(accessible out
of the class
scope)

Figure 34:Class Diagram Formalism

DERICK-ASANE ASANE DERICK ENOW 89

Table 24:Class Diagram Components

Element Representation Description

class A class is an element that

defines the attributes and
behaviors that an object is able
to generate
Composition If a parent of a composite is
deleted, usually, all of its parts
are deleted with it.

Aggregation If the parent of the aggregate is

deleted, usually the children
are not deleted.

Dependency It existed between two classes,

if one changes it may cause the
change in the order, but the
other way around.
Generalization it a relationship between a
whole thing (called
superclass) and a more
specific thing (called subclass)

Association It is a general type of

relationship between
elements, it may include
cardinality, roles etc.

DERICK-ASANE ASANE DERICK ENOW 90

c. EYE-ME Class Diagram

Figure 35:EYE-ME Class Diagram

DERICK-ASANE ASANE DERICK ENOW 91

d. Relationships between classes

R1: An identification personnel can identify zero or many students, and a student can be
identified by zero or many identification personnels
R2: A discipline-master can create zero or many students, and a student can be created one
discipline-master.
R3: A discipline-master can send zero or many notifications, and a notification can be sent
by one and only one discipline master.
R4: A student has one or many fees, and a fee is own by one student.
R5: A student has one timetable, and a timetable is used by one or many students.
R6: An administrator can add zero or many discipline-masters, and a discipline-master can
be added by one administrator
R7: A student has zero or many attendance statuses, and attendance status belongs to one
and only one student
R8: A timetable contains many times and, a time is found in many timetables

DERICK-ASANE ASANE DERICK ENOW 92

8. Object Diagram

a. Definition
Object diagram represent an instance of a class diagram. It represents the static view of a
system but this static view is a snapshot of the system at a particular moment. They are
used to render a set of objects and their relationship as an instance
b. formalism

Figure 36:Object Diagram Formalism

Table 25:object diagram components

Element Representation Description

Object An object is an
instance of a class.

Link It is an instance of
an association.

DERICK-ASANE ASANE DERICK ENOW 93

c. EYE-ME Object Diagram

Figure 37:EYE-ME Object Diagram

DERICK-ASANE ASANE DERICK ENOW 94

CONCLUSION
In the conception phase, we set as objective to plane the different aspect of our
system by showing how it will be structure and deployed within existing technical
architectures. We began by taking into account the technical constraints for our system,
after which we proceeded to identify the components of our system, how they are grouped
together and how they should be deployed on appropriate deployment targets. We finished
this phase by looking at interactions between the various aspects and actors of our system.
The next phase of our report is the realization phase where we will look at aspects
concerning the implementation of our system.

DERICK-ASANE ASANE DERICK ENOW 95

PART FIVE: REALISATION PHASE

DERICK-ASANE ASANE DERICK ENOW 96

Preamble
In this phase we will to straight forward in the implementation of our solution, we will base
ourselves on the analysis and conception phases.
Content

INTRODUCTION
I THE ENTITY RELATIONAL DIAGRAM
II PRESENTATION OF DEVELOPMENT TOOLS
CONCLUSION

DERICK-ASANE ASANE DERICK ENOW 97

INTRODUCTION
Here in the realization phase, we will concentrate on building or implementing
our solution, based on the different analysis and conception that we had carried out, which
will help to facilitate our work, this phase is as critical as the previous phases. We are going
to look at the relationship that exist between the entities of the entity relational diagram.
Furthermore, we will see the choices of technologies used for the implementation of our
system.

DERICK-ASANE ASANE DERICK ENOW 98

I ENTITY RELATIONSHIP DIAGRAM

Figure 38:Entity Relationship Diagram

DERICK-ASANE ASANE DERICK ENOW 99

II PRESENTATION OF DEVELOPMENT
TOOLS
A development tool is a hardware or a software that supports the rapid implementation of
software application. That’s used to create, debug, maintain, or otherwise support other
programs and applications.

A MATERIAL RESOURCES

Table 26:Material Resource (https://www.mantratec.com/products/Fingerprint-Sensors/Optical-Fingerprint-Scanner-

MFS100-V2)

Resource Parameters Specification Quantity

Spatial Resolution Optical Scratch-free
Sensor
Platen Size 16.4 mm * 20.0 mm
Image Size 296 * 354 Pixels
Light Source RED LED
Fingerprint sensor 1
Capture mode Auto capture with built-in quality
check
Approx Weight 0.141 kg (Module: 0.025 kg)

Sensing Area 296 * 354 Pixels

DERICK-ASANE ASANE DERICK ENOW 100

B TECHNOLOGICAL STACK

Table 27: Development environment

Resource Version License Owner Function

Microsoft Visual 1.60 Microsoft Text editing and

Studio Code Corporation coding

Table 28:Framework and programming language

Framework / Programming Version License Owner Function

language
React js 18.2.0 Facebook Web application

Node js/ express js 16.15.1 Ryan Dahl Web/mobile

application
React native 0.69.0 Facebook Mobile application

DERICK-ASANE ASANE DERICK ENOW 101

CONCLUSION
In our realization phase, we implemented our application. In other to accomplish this
phase, we made used of our analysis and conception phase. The Entity-Relational diagram.
helped us to establish our database. We then presented the development tools we used for the
development or realization of our system, we had material resource (visual studio code) and
technology stack (React js, react-native js, Node js/express js). We will move to the user guide
phase where we shall elaborate on how to install and use EYE-ME.

DERICK-ASANE ASANE DERICK ENOW 102

PART SIX: USER GUIDE

DERICK-ASANE ASANE DERICK ENOW 103

Preamble
The purpose of the user guide is to provide users of our platform with step-by-step
instructions on how to install and use the system.
Content Overview

INTRODUCTION
I INSTALLATION OF THE APPLICATION
II SHOW CASE
CONCLUSION

DERICK-ASANE ASANE DERICK ENOW 104

INTRODUCTION
This is the final phase of our report. In this phase we will walk through the
requirements for our system, the necessary installation process, accessing our system and
it futures, all this in a step by step manner to facilitate the setting up of the platform for the
first time users. The steps of different processes will be accompanied by images. After we
will showcase our application by viewing the different screens and some brief explanation.

DERICK-ASANE ASANE DERICK ENOW 105

I INSTALLATION OF THE APPLICATION

A. WEB APPLICATION INSTALLATION
To deploy a software, we need to install it database server, in our case in MongoDB will
be installed in our system which is windows.

Figure 39:Mongodb logo

i. Installing the Database Server

STEP 1: Downloading the MongoDB MSI installer Package

We go to https://www.mongodb.com/try/download/community in other to download
MongoDB an note that we are downloading the community version since it is free and open
source.

Figure 40:Downloading MongoDB community version

DERICK-ASANE ASANE DERICK ENOW 106

STEP 2: Install MongoDB with the installation Wizard

A. Make sure you logged in as a user with admin privileges. Then navigate to your
downloads folder and double click on the .msi package you just downloaded. This will
launch the installation wizard.

Figure 41:Lauching the installatin wizard.

B Click to the next installation.

Figure 42:Clicking next

DERICK-ASANE ASANE DERICK ENOW 107

C Accept the license agreement then click Next

Figure 43:Agreement license

D Select the Complete setup.

Figure 44:Select complete setup

DERICK-ASANE ASANE DERICK ENOW 108

E Select “Run service as Network Service user” and make a note of the data directory,
we’ll need this later.

Figure 45:Run service network server user

F We won’t need Mongo Compass, so unselect it and click Next.

Figure 46:unselecting MongoDB Compass and click Next

DERICK-ASANE ASANE DERICK ENOW 109

G Click Install to begin installation.

Figure 47:Click Install to start installation

H Click finish to complete installation.

Figure 48:Clicking on finish to complete installation

DERICK-ASANE ASANE DERICK ENOW 110

B Mobile Application Installation

To be able to use EYE-ME mobile application, we need to download the APK file or IPA file
and install it. After installing it, run the application.

II SHOWCASES

a. Here we have the login page of EYE-ME.

Figure 49:EYE-ME login page

DERICK-ASANE ASANE DERICK ENOW 111

b. This is the attendance service interphase to send notifications to parents

Figure 50:Attendance service Notification interphase

DERICK-ASANE ASANE DERICK ENOW 112

c. This is an interphase which shows the list of students with an add button to add a new
student into the application.

Figure 51:List of student interphase

DERICK-ASANE ASANE DERICK ENOW 113

d. Attendance service dashboard.

Figure 52:Attendance Service Dashboard

DERICK-ASANE ASANE DERICK ENOW 114

e. The interphase which enables parents view their child’s attendance status at real-time.

Figure 53:View daily attendance interphase.

DERICK-ASANE ASANE DERICK ENOW 115

f. Parents interphase to view notification

Figure 54:Parent Notification Interphase.

DERICK-ASANE ASANE DERICK ENOW 116

GENERAL CONCLUSION
Having coming to an end of our project and the end of our internship at MIT2, we have
achieved a lot from our internship period, it was very challenging and demanding, we had
to manage stress, failures and successes. Our stay in MIT2 was a very profitable, we learned
how to adapt to the professional milieu and to also work in team. For our project we worked
on the theme “FINGERPRINT ASSISTED ONLINE STUDENT FOLLOW-UP
FLATFORM”, our greatest desire is to help parents to be able to follow-up dear child
while at home, in other for their child to acquire good and consistent Knowledge, be without
follow-up student develop the habit of absenteeism. We began by identifying user needs
and project constraints and requirements in the specification book, then we went forth to
analyze our system (EYE-ME) using UML-2TUP methodology. We made use of visual
paradigm, a modelling software used to draw our various diagrams. In other to realize
project, we used react-native for mobile front-end, React js for the front-end, NodeJS for
the backend and MongoDB as our database. And EYE-ME is assisted by a fingerprint
sensor (mantra 100 mfs). Our system EYE-ME will enable parents to view their child
attendance status at real time, received alerts and notifications, and other vital information
from the school administration. To make EYE_ME a game changer, we won’t end here,
we continue to acquire knowledge in other to better EYE-me.

DERICK-ASANE ASANE DERICK ENOW 117

ANNEXE

DERICK-ASANE ASANE DERICK ENOW 118

BIBLIOGRAPHY

➢ Mr. JIONGANG Thibaut UML course AICS-Cameroon 2021-2022

➢ OMG, OMG Unified Modelling Language 2.5, Object Management Group, March
2015, 794 pages.
➢ React-native course (from basics to advanced) from UDEMY 2022.
➢ Nodejs course from
➢ Mongo dB course from mongo DB website 2022.
➢ Association For the Defense of Student’s Rights IN Cameroon 2022.
➢ Mr. Ndenge JavaScript course (introduction into JavaScript) AICS-Cameroon 2021-
2022.

DERICK-ASANE ASANE DERICK ENOW xii

WEBOGRAPHY
➢ https://www.codecademy.com/learn/learn-nodejs?g_network=g&g_device=c&g_adid June
10th 2022 03:35AM, UDEMY NodeJS course
➢ https://en.wikipedia.org/wiki/Bibliography/ what is Bibliography? September 15th 2022 8:07
PM.
➢ https://www.omg.org/spec/UML/2.5.1/About-UML/ Object Management Group UML 2.5
documentation. July 15th 2022 5:02 AM.
➢ https://www.merriam-webster.com/dictionary/follow-up what is follow-up?
➢ https://www.mantratec.com/products/Fingerprint-Sensors/MFS100-Fingerprint-Scanner
Biometric Fingerprint Scanner MFS100, June 28th 2022 11:48 PM.
➢ https://fr.wikipedia.org/wiki/Two_Tracks_Unified_Process Two Track Unified Process. July
02nd 2022 6:11 PM.
➢ https://www.tutorialspoint.com/mvc_framework/mvc_framework_introduction.htm Model
View Controller (MVC). June 20th 2022.
➢ https://www.makeuseof.com/tag/what-is-apk-file/ what is APK? August 21st 2022 10:13.
➢ https://drg.global/what-we-do/methods/street-interviews/ More information on street
interview. August 10th 2022 04:01 AM.
➢ https://reactnative.dev/search?q=native+scratch+course React native documentation. August
05th 2022 1:32 PM.
➢ https://docs.expo.dev/get-started/installation/ Expo documentation August 07th 2022 8:35PM.
➢ https://console.twilio.com/?frameUrl=/console SMS API information. August 07th 2022
5:30PM.
➢ https://formik.org/docs/guides/validation FORMIK documentation. August 09th 2022 7:27PM.
➢ https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-
OOP# Object Oriented programming July 01th 2022 8:35PM.
➢ https://www.appmysite.com/blog/what-is-an-ipa-file-and-how-can-you-open-one/ what is
IPA?
➢ https://www.lifewire.com/understanding-finger-scanners-4150464 How does fingerprint
scanner works. July 25th 2022 12:00 AM.
➢ https://blog.kms-solutions.asia/mobile-app-development-lifecycle Mobile Development life
cycle. June, 21st 2022. 09:10 AM.

DERICK-ASANE ASANE DERICK ENOW xiii

➢ https://advice.writing.utoronto.ca/planning/intros-and-conclusions How to write a good

introduction and conclusion. September, 6th 2022. 07:20 AM.
➢ https://www.osbay.com/en/pros-and-cons-of-mobile-app-development-2/ The cons and pros
of mobile development.

DERICK-ASANE ASANE DERICK ENOW xiv

TABLE OF CONTENT

DEDICATION ............................................................................................................................ i
ACKNOWLEDGEMENT .........................................................................................................ii
SUMMARY ............................................................................................................................. iii
LIST OF FIGURES ................................................................................................................... v
LIST OF TABLES ...................................................................................................................vii
GLOSSARY .......................................................................................................................... viii
ABSTRACT.............................................................................................................................. ix
RESUME ................................................................................................................................... x
GENERAL INTRODUCTION .................................................................................................. 1
PART ONE: INSERTION PHASE ........................................................................................... 2
INTRODUCTION ................................................................................................................. 4
WELCOME AND INTEGRATION...................................................................................... 5
GENERAL PRESENTATION OF MIT² .............................................................................. 6
A. History........................................................................................................................ 6
B. Missions ..................................................................................................................... 6
C. Activities .................................................................................................................... 6
D. Key Realizations of MIT² .......................................................................................... 8
E. Company partners and customers .............................................................................. 8
F. GEOGRAPHICAL LOCATION ............................................................................. 10
ORGANIZATION OF MIT² ............................................................................................... 11
A. Administrative Organization of MIT² ...................................................................... 11
a. The General Management .................................................................................. 11
b. Communication department ............................................................................... 11
c. Human Resource Department ............................................................................ 11
d. Software Engineering Department ..................................................................... 11
e. Executive Secretary ........................................................................................... 11
f. Department of Financial Affairs ............................................................................ 11
g. Training and Certification Department .............................................................. 12
h. Technical Department ........................................................................................ 12
B. Functional organization of mit²................................................................................ 13

DERICK-ASANE ASANE DERICK ENOW xv

HARDWARE AND SOFTWARE RESOURCES OF MIT² .............................................. 14

A. Hardware Resources ................................................................................................ 14
B. Software Resources .................................................................................................. 15
BRIEF PRESENTATION OF THE PROJECT THEME .................................................... 16
CONCLUSION .................................................................................................................... 17
PART TWO: SPECIFICATION BOOK ................................................................................. 18
INTRODUCTION ............................................................................................................... 20
I. CONTEXT AND JUSTIFICATION ........................................................................... 21
II. OBJECTIVES OF THE PROJECT ............................................................................. 22
A. General Objective .................................................................................................... 22
B. Specific Objectives .................................................................................................. 22
III. EXPRESSION OF NEEDS ..................................................................................... 22
A. Functional needs ...................................................................................................... 22
B. Non-functional Needs .............................................................................................. 23
i. Hardware requirements.......................................................................................... 23
ii. Software requirements ............................................................................................. 23
IV. ESTIMATED COST OF THE PROJECT ............................................................... 24
A. Hardware Resources ................................................................................................ 24
B. Software Resources .................................................................................................. 25
C. Human Resources .................................................................................................... 26
D. Total Project Estimated Cost ................................................................................... 26
E. LIST OF PARTICIPANTS AND DELIVERABLES ............................................. 29
a. List of participants ............................................................................................. 29
b. Deliverables ....................................................................................................... 29
CONCLUSION .................................................................................................................... 30
PART THREE: ANALYSIS PHASE ...................................................................................... 31
INTRODUCTION ............................................................................................................... 33
I. DESCRIPTION OF THE EXISTING SYSTEM ........................................................ 34
II. PRESENTATION OF THE ANALYSIS METHOD .................................................. 36
A. MODELING WITH UML 2.5 ................................................................................. 37
a. Structural Diagrams: .......................................................................................... 37
b. Behavioral Diagrams: ........................................................................................ 38
c. UML 2.5 diagrams overview ............................................................................. 38
B. The Process of Development of a Software ............................................................. 40

DERICK-ASANE ASANE DERICK ENOW xvi

a. A Unified Process .............................................................................................. 40

b. The Two Track Unified Process (2TUP) ........................................................... 40
III. JUSTIFICATION OF THE ANALYSIS METHOD ............................................... 43
IV. MODELING OF THE SYSTM ............................................................................... 44
A. Capture of Functional Needs ................................................................................... 44
1. Use Case Diagram.............................................................................................. 44
2. ACTIVITY DIAGRAM..................................................................................... 53
3. State Machine Diagram...................................................................................... 59
CONCLUSION .................................................................................................................... 62
PART FOUR: CONCEPTION PHASE .................................................................................. 63
INTRODUCTION ............................................................................................................... 65
I. TECHNICAL BRANCH ............................................................................................. 66
A. GENERIC DESIGN................................................................................................. 66
a. Hardware diagram of the system ....................................................................... 66
b. High Level Architectural Diagram of the Software ........................................... 66
B. CAPTURES TECHNICAL NEEDS ....................................................................... 67
a. Physical architecture .......................................................................................... 67
c. Logical architecture ........................................................................................... 68
II. IMPLEMENTATION BRANCH ................................................................................ 69
PRELIMINARY DESIGN................................................................................................... 69
1. Component diagram ........................................................................................... 69
2. Package Diagram ............................................................................................... 72
3. Deployment Diagram ......................................................................................... 76
A. DETAILED DESIGN .............................................................................................. 79
4. Sequence Diagram ............................................................................................. 79
5. Communication Diagram ................................................................................... 83
6. Timing Diagram ................................................................................................. 87
7. Class Diagram .................................................................................................... 89
8. Object Diagram .................................................................................................. 93
CONCLUSION .................................................................................................................... 95
PART FIVE: REALISATION PHASE ................................................................................... 96
INTRODUCTION ............................................................................................................... 98
I ENTITY RELATIONSHIP DIAGRAM ..................................................................... 99
II PRESENTATION OF DEVELOPMENT TOOLS ................................................... 100

DERICK-ASANE ASANE DERICK ENOW xvii

A MATERIAL RESOURCES ................................................................................... 100

B TECHNOLOGICAL STACK ................................................................................ 101
CONCLUSION .................................................................................................................. 102
PART SIX: USER GUIDE .................................................................................................... 103
INTRODUCTION ............................................................................................................. 105
I INSTALLATION OF THE APPLICATION ........................................................ 106
A. WEB APPLICATION INSTALLATION ....................................................... 106
B Mobile Application Installation ....................................................................... 111
II SHOWCASES ....................................................................................................... 111
GENERAL CONCLUSION .................................................................................................. 117
ANNEXE ............................................................................................................................... 118
BIBLIOGRAPHY ....................................................................................................................xii
WEBOGRAPHY ................................................................................................................... xiii
TABLE OF CONTENT ........................................................................................................... xv

DERICK-ASANE ASANE DERICK ENOW xviii

African Institute of Computer Sciences (AICS) Cameroon
Paul Biya Technological Center of Excellence
nd
2 Year Option for Software Engineering 2021/2022 Academic Year.

Stock Price Prediction Srs Report
No ratings yet
Stock Price Prediction Srs Report
27 pages
0 - Project 7 - Tic-Tac-Toe Game Project
50% (6)
0 - Project 7 - Tic-Tac-Toe Game Project
30 pages
6030 Project
100% (5)
6030 Project
29 pages
Heinemann Software Design and Development
86% (7)
Heinemann Software Design and Development
320 pages
CSCU Exam Info and Test Objective
100% (2)
CSCU Exam Info and Test Objective
7 pages
Compulsory Redemption FAQs
No ratings yet
Compulsory Redemption FAQs
6 pages
Airline Reservation System (Informatics Practices Project Class XII)
No ratings yet
Airline Reservation System (Informatics Practices Project Class XII)
32 pages
Project 3 - Random Number Guess Project
75% (16)
Project 3 - Random Number Guess Project
23 pages
ONLINE CONSULTING Final
No ratings yet
ONLINE CONSULTING Final
156 pages
Computer Science Project Topics and Materials For Final Year Students
No ratings yet
Computer Science Project Topics and Materials For Final Year Students
9 pages
Godwin Massawe
No ratings yet
Godwin Massawe
20 pages
csharppblFINAL1.dox
No ratings yet
csharppblFINAL1.dox
33 pages
Shoe Billing Project
No ratings yet
Shoe Billing Project
26 pages
CS Project
No ratings yet
CS Project
41 pages
Final Project
No ratings yet
Final Project
86 pages
1618 IT Fundamental & Procedural Programming
No ratings yet
1618 IT Fundamental & Procedural Programming
29 pages
CS PRO 2024
No ratings yet
CS PRO 2024
48 pages
ICT-PSS-07 24-1 Object Oriented Programming 1 OOP1
No ratings yet
ICT-PSS-07 24-1 Object Oriented Programming 1 OOP1
7 pages
A Project Report On " ": It Team Work Place
No ratings yet
A Project Report On " ": It Team Work Place
52 pages
Pirate Engineer Template
No ratings yet
Pirate Engineer Template
2 pages
CS_PRO_2024[1]
No ratings yet
CS_PRO_2024[1]
48 pages
Kelvin Report_065751
No ratings yet
Kelvin Report_065751
18 pages
Computer Science Project Topics and Materials in Nigeria
50% (2)
Computer Science Project Topics and Materials in Nigeria
13 pages
MAD LAB RECORD - FINAL
No ratings yet
MAD LAB RECORD - FINAL
80 pages
bank mgmt
No ratings yet
bank mgmt
34 pages
191it52a-Mad Lab
No ratings yet
191it52a-Mad Lab
80 pages
Bank MGMT
No ratings yet
Bank MGMT
30 pages
FINAL REPORT MIRIAM DUNAMIS 2024 2025
No ratings yet
FINAL REPORT MIRIAM DUNAMIS 2024 2025
63 pages
Resturent Management
No ratings yet
Resturent Management
29 pages
191CS52A-MAD LAB with mini project
No ratings yet
191CS52A-MAD LAB with mini project
90 pages
Shoe Billing Project - Naiem
No ratings yet
Shoe Billing Project - Naiem
26 pages
Library Management System File W
No ratings yet
Library Management System File W
27 pages
P10 computer sales and service system
No ratings yet
P10 computer sales and service system
34 pages
Report
No ratings yet
Report
15 pages
Project - 3 - Shoe Store Billing System
No ratings yet
Project - 3 - Shoe Store Billing System
31 pages
Cloth Store Billing System (Informatics Practices Project Class XII)
No ratings yet
Cloth Store Billing System (Informatics Practices Project Class XII)
38 pages
Computer Science & Engineering: Project Report
No ratings yet
Computer Science & Engineering: Project Report
8 pages
Bca - V Minor Project Report
No ratings yet
Bca - V Minor Project Report
37 pages
Cs Project
No ratings yet
Cs Project
47 pages
Godson Public School: Academic Session: 2021-2022 Project Report Topic
No ratings yet
Godson Public School: Academic Session: 2021-2022 Project Report Topic
33 pages
Project 3 - Random Number Guess Project-1
No ratings yet
Project 3 - Random Number Guess Project-1
23 pages
Shoe Billing Project
No ratings yet
Shoe Billing Project
25 pages
Template For Capstone Proposal
100% (1)
Template For Capstone Proposal
15 pages
Shoe Management Class 12
No ratings yet
Shoe Management Class 12
29 pages
Shoe Billing Project
0% (1)
Shoe Billing Project
27 pages
Tushar (Project)
No ratings yet
Tushar (Project)
30 pages
Project Report Model - IP (3)
No ratings yet
Project Report Model - IP (3)
38 pages
Computer Programming
No ratings yet
Computer Programming
11 pages
Project - 6 - Book Shop Management System-1
No ratings yet
Project - 6 - Book Shop Management System-1
28 pages
Shoe Billing Project
No ratings yet
Shoe Billing Project
27 pages
Commonwealth Shared Scholarship Application Preview
100% (1)
Commonwealth Shared Scholarship Application Preview
12 pages
Final Report
No ratings yet
Final Report
27 pages
Format 2
No ratings yet
Format 2
14 pages
Bus Ticket System
No ratings yet
Bus Ticket System
15 pages
Book Stall Management
No ratings yet
Book Stall Management
26 pages
Coding Technology Co. LTD Profile
No ratings yet
Coding Technology Co. LTD Profile
40 pages
1 Updated 20044570016
No ratings yet
1 Updated 20044570016
9 pages
Master of Computer Applications: Rishikesh Pawan U 1NH18MCA34
No ratings yet
Master of Computer Applications: Rishikesh Pawan U 1NH18MCA34
35 pages
Library Management System
No ratings yet
Library Management System
75 pages
Cit 351
No ratings yet
Cit 351
102 pages
cs project01
No ratings yet
cs project01
25 pages
CSC 490
No ratings yet
CSC 490
5 pages
MAXON CINEMA 4D S24: A Tutorial Approach, 8th Edition
From Everand
MAXON CINEMA 4D S24: A Tutorial Approach, 8th Edition
Prof. Sham Tickoo
No ratings yet
Learning Solidworks 2018: A Project Based Approach
From Everand
Learning Solidworks 2018: A Project Based Approach
Prof. Sham Tickoo
No ratings yet
CS-23 C# Prelims Paper 2025
No ratings yet
CS-23 C# Prelims Paper 2025
2 pages
Sai Krishna: Summary of Qualification
No ratings yet
Sai Krishna: Summary of Qualification
2 pages
bank application step by step
No ratings yet
bank application step by step
6 pages
Labelling Tips and Tricks
No ratings yet
Labelling Tips and Tricks
50 pages
Pasos para Cromebook
No ratings yet
Pasos para Cromebook
4 pages
Eqommand: User Manual
No ratings yet
Eqommand: User Manual
53 pages
Dynamic Resource Allocation Scheme in Cloud Computing: Sciencedirect
No ratings yet
Dynamic Resource Allocation Scheme in Cloud Computing: Sciencedirect
7 pages
Installing The BIRT Viewer in Tomcat and Jboss
100% (2)
Installing The BIRT Viewer in Tomcat and Jboss
3 pages
ArcGIS Toolbar Manual V8i
No ratings yet
ArcGIS Toolbar Manual V8i
9 pages
Forrssea Nav Cam User Guide
No ratings yet
Forrssea Nav Cam User Guide
29 pages
ANCILE UPerform 4.50.0 Quick Reference
No ratings yet
ANCILE UPerform 4.50.0 Quick Reference
13 pages
Cloud Application Integration - Technology and Security Overview June 2019
No ratings yet
Cloud Application Integration - Technology and Security Overview June 2019
21 pages
Course Specification: Umm Al-Qura University
No ratings yet
Course Specification: Umm Al-Qura University
3 pages
Introduction To Cloud Computing 1
No ratings yet
Introduction To Cloud Computing 1
22 pages
E Wallet
No ratings yet
E Wallet
20 pages
File Handling Using Visual Basic 6
No ratings yet
File Handling Using Visual Basic 6
29 pages
Setting Up An Acquisition: Best in Class
No ratings yet
Setting Up An Acquisition: Best in Class
2 pages
Dreamboard Theming HowTo
No ratings yet
Dreamboard Theming HowTo
7 pages
531B Project Report
No ratings yet
531B Project Report
48 pages
Moodle Features Students
No ratings yet
Moodle Features Students
14 pages
Registering Service Principal Names for a Kerberos Service Account in Active Directory - SAP Help Portal
No ratings yet
Registering Service Principal Names for a Kerberos Service Account in Active Directory - SAP Help Portal
2 pages
00 - Table of Contents - EPIC
No ratings yet
00 - Table of Contents - EPIC
6 pages
SAP Quality Management Training
50% (2)
SAP Quality Management Training
5 pages
Viva Piñata (PC) Install Guide (2022)
No ratings yet
Viva Piñata (PC) Install Guide (2022)
2 pages
Sinumerik 840D SL
No ratings yet
Sinumerik 840D SL
8 pages
Guidelines & Specifications For Advertising On The Sojern Platform
No ratings yet
Guidelines & Specifications For Advertising On The Sojern Platform
14 pages