0% found this document useful (0 votes)

275 views175 pages

Final Report

This document is a dedication and acknowledgements section of a report on developing a web and mobile application to facilitate access to services by Cameroon Postal Services (CAMPOST), known as Campost-In-Hand. The application aims to provide financial, digital and postal services. The document dedicates the work to the author's parents and acknowledges contributions from supervisors, colleagues, friends and open source communities who supported the project. It includes lists of figures, tables and the overall contents of the report.

Uploaded by

chijou ervane

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

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

275 views175 pages

Final Report

Uploaded by

chijou ervane

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

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

You are on page 1/ 175

DEVELOPMENT OF A WEB AND MOBILE

APPLICATION WHICH FACILITATES ACCESS TO

CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)

DEDICATION

I dedicate this work to my lovely

parents for their great support,
advice and their unconditional
sacrifices for my academic success.

Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering
at AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE,
Academic Year 2020 – 2021
xi
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)

ACKNOWLEDGEMENTS
The accomplishment of this great work would have not been possible without the important
contributions of a good number of people who gave me a huge support either academically,
professionally, financially or spiritually. I then direct my special thanks to;

 God the Almighty for his guidance.

 Mr. Armand Claude ABANDA, the resident representative of AICS Cameroon for
creating the anglophone section offering the training on software engineering, and also
for his advices and follow-up.
 Mr. Pierre KALDADAK, the General Director of CAMPOST for welcoming me in his
institution.
 Mr. SCHWAMA Samuel, my professional supervisor for his encouragement, moral
supports and kindness during my 4 months internship.
 Mr. TAGNE TOKAM Cedrick Gaetan, professional supervisor and elder brother
for his professional follow-up, academic, financial and moral supports.
 Mr. NJOMO Yannick, my academic supervisor for his strict follow-up and
encouragements.
 The staff of AICS Cameroon for their work during the academic year.

 A special on to my family members for their presence in my life.

 To all my classmates, students of our promotion or batch, for their knowledge,

collaboration, love sharing, and also the great moment we are spending.
 The many countless contributors of the open-source programming community, for
providing the numerous tools and systems we have used to produce both these results and
this report. The entirety of this report has been completed using such technologies and we
consider it to have been an enormous benefit.
 All those who contributed in the realization of this project in one way or the other.

SUMMARY
Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering
at AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE,
Academic Year 2020 – 2021
xi
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)

DEDICATION................................................................................................................................i

ACKNOWLEDGEMENTS..........................................................................................................ii

SUMMARY...................................................................................................................................iii

LIST OF FIGURES......................................................................................................................iv

LIST OF TABLES......................................................................................................................viii

GENERAL INTRODUCTION.....................................................................................................1

CHAPTER 1 : INSERTION PHASE...........................................................................................2

CHAPTER 2 : SPECIFICATION DOCUMENT.....................................................................12

CHAPTER 3 : ANALYSIS PHASE...........................................................................................28

CHAPTER 4 : CONCEPTION PHASE....................................................................................83

CHAPTER 5 : IMPLEMENTATION PHASE......................................................................112

CHAPTER 6 : USER GUIDE...................................................................................................127

GENERAL CONCLUSION.....................................................................................................153

ANNEXE....................................................................................................................................153

BIBLIOGRAPHY......................................................................................................................153

WEBOGRAPHY........................................................................................................................153

CONTENT..................................................................................................................................153

LIST OF FIGURES

Figure 1: campost localisation plan.................................................................................................7

Figure 2: organization chart of campost (source : campost)............................................................8
Figure 3: project gantt diagram......................................................................................................25
Figure 4: uml diagrams organisation.............................................................................................44
Figure 5: 2tup development process..............................................................................................45
Figure 6: use case diagram formalism...........................................................................................48
Figure 7: generat use case diagram...............................................................................................52
Figure 8: use case diagram <<manage financial services>>.........................................................53
Figure 9: use case diagram <<manage postal services>>..............................................................54
Figure 10: use case diagram <<manage loan request>>................................................................55
Figure 11: use case diagram <<manage users and habilitations>>...............................................56
Figure 12: use case diagram <<manage campost services>>........................................................57
Figure 13: use case diagram <<manage camo account>>.............................................................58
Figure 14: use case diagram <<manage bank account>>..............................................................59
Figure 15: use case diagram <<manage postal box>>..................................................................60
Figure 16: use case diagram <<manage loan>>............................................................................60
Figure 17: activity diagram formalism..........................................................................................66
Figure 18: activity diagram <<authenticate>>..............................................................................68
Figure 19:activity diagram <<grant permission>>........................................................................69
Figure 20:activity diagram <<accept bank account creation request>>........................................70
Figure 21: activity diagram<<transfer fund>................................................................................71
Figure 22:activity diagram <<pay a service>>..............................................................................72
Figure 23:communication diagram formalism..............................................................................73
Figure 24: communication diagram <<authenticate>>.................................................................75

Figure 25: communication diagram <<accept bank account creation requuest>>........................76

Figure 26:communication diagram <<pay a service>>.................................................................77
Figure 27:state machine diagram formalism.................................................................................78
Figure 28: state machine diagram <<bank account request>>......................................................80
Figure 29:state machine diagram <<bank account>>....................................................................80
Figure 30: state machine diagram <<loan>>.................................................................................81
Figure 31: interaction overview diagram formalism.....................................................................88
Figure 32: interaction overview diagram <<pay a service>>........................................................89
Figure 33: component diagram formlism......................................................................................90
Figure 34: component diagram of the solution.............................................................................92
Figure 35: deployment diagram formalism...................................................................................93
Figure 36: deployment diagram of the solution.............................................................................94
Figure 37:package diagram formalism..........................................................................................95
Figure 38: components of a package diagram...............................................................................96
Figure 39:package diagram of the solution...................................................................................97
Figure 40:sequence diagram formalism.........................................................................................98
Figure 41: sequence diagram <<authenticate>>..........................................................................100
Figure 42:sequence diagram <<transfer fund>>.........................................................................101
Figure 43: sequence diagram pay a service.................................................................................102
Figure 44: timing diagram formalism..........................................................................................103
Figure 45: timing diagram for a loan request..............................................................................104
Figure 46: class diagram formalism............................................................................................105
Figure 47: class diagram of the system........................................................................................107
Figure 48: object diagram formalism..........................................................................................108
Figure 49:components of object diagram....................................................................................109
Figure 50: object diagram of the system......................................................................................110
Figure 51: 3 tier physical achitecture...........................................................................................120
Figure 52: mvc logical architecture.............................................................................................121

Figure 53: js, angular and ts logo.................................................................................................122

Figure 54: ionic logo....................................................................................................................123
Figure 55:spring boot logo...........................................................................................................124
Figure 56: angular firebase deployment......................................................................................130
Figure 57: firebase welcome page...............................................................................................130
Figure 58:firebase add project.....................................................................................................131
Figure 59: firebase login success.................................................................................................131
Figure 60:firebase cli configs......................................................................................................132
Figure 61: deploying ios and adnroid application.......................................................................132
Figure 62: download node js........................................................................................................134
Figure 63: install node js step 2...................................................................................................135
Figure 64: install node js step 4...................................................................................................135
Figure 65: install node js step 3...................................................................................................135
Figure 66:install node js step 1....................................................................................................135
Figure 67: install node js step 5...................................................................................................136
Figure 68: install node js step 6...................................................................................................136
Figure70: installing wamp server step 2......................................................................................136
Figure69: installing wamp server step 1......................................................................................136
Figure 74: installing wamp server step 6.....................................................................................137
Figure 73: installing wamp server step 5.....................................................................................137
Figure 72: installing wamp server step 4.....................................................................................137
Figure 71: installing wamp server step 3.....................................................................................137
Figure 69: campost in hand landing page....................................................................................138
Figure 70: campost in hand - campost services...........................................................................139
Figure 71: campost in hand - financial services..........................................................................139
Figure 72: campost in hand - search page...................................................................................140
Figure 73: campost in hand - map...............................................................................................141
Figure 74 : campost in hand - map road view.............................................................................141
Figure 75 : campost in hand - register page.................................................................................142

Figure 76 : campost in hand - login page....................................................................................142

Figure 77 : campost in hand - user dashboard.............................................................................143
Figure 78 : campost in hand - exchange fund..............................................................................143
Figure 79 : campost in hand - user transactions.........................................................................144
Figure 80 : campost in hand - user accounts page.......................................................................144
Figure 81 : campost in hand - loans.............................................................................................145
Figure 82 : campost in hand - pay a service (rapid payment)......................................................145
Figure 83 ; campost- in hand - price simulator............................................................................146
Figure 84 : campost in hand - notification page..........................................................................146
Figure 87 : mobile - menu...........................................................................................................147
Figure 86 : mobile - register........................................................................................................147
Figure 85 : mobile - login............................................................................................................147
Figure 92 : mobile - transactions.................................................................................................148
Figure 93 : mobile – settings.......................................................................................................148
Figure 90 : mobile - pay service..................................................................................................148
Figure 91 : mobile - bank accounts..............................................................................................148
Figure 89 : mobile - exchange.....................................................................................................148
Figure 88 : mobile - dashboard....................................................................................................148
Figure 94 : admin - dashboard.....................................................................................................149
Figure 95 : admin customers transactions...................................................................................149
Figure 96 : admin - campost services.........................................................................................150
Figure 97 : admin - manage offices.............................................................................................150
Figure 98 : admin - add postal office...........................................................................................151
Figure 99 : admin - manage bank account...................................................................................151
Figure 100 : admin – loan............................................................................................................152
Figure 101 : admin -loan detail....................................................................................................152

LIST OF TABLES
Table 1: human resources..............................................................................................................21
Table 2: software resources...........................................................................................................21
Table 3: hardware resources..........................................................................................................22
Table 4: estimated cost of the project............................................................................................22
Table 5: list of participants............................................................................................................23
Table 6: project planning...............................................................................................................24
Table 7: limitations of the existing system and proposed solutions..............................................34
Table 8: components of a use case diagram..................................................................................49
Table 9: identification of actors and their use cases......................................................................50
Table 10: <<authenticate>> textual description............................................................................61
Table 11: <<grant permission>> textual description.....................................................................62
Table 12: <<accept bank account creation request>>> textual description..................................63
Table 13: <<transfer fund>> textual description...........................................................................64
Table 14: << pay a service textual description>>..........................................................................65
Table 15: components of activity diagram....................................................................................67
Table 16: components of a communication diagram.....................................................................74
Table 17: components of a state machine diagram........................................................................79
Table 18: components of a component diagram............................................................................91
Table 19: components of a sequence diagram...............................................................................99
Table 20: components of a class diagram....................................................................................106
Table 21: software tools...............................................................................................................124

GLOSSARY

CAMPOST: Cameroon Postal Services

DIS: Director/Direction of Information System

2TUP: Two Track Unified Process

API: Application Programming Interface

AICS: African Institute of Computer Sciences

CD-ROM: Compact Disk - Read Only Memory

DBMS: Database Management System

GUI: Graphical user Interface

ICT: Information and Communication Technology

IDE: Integrated Development Environment

MVC: Model View Controller

OOP: Object Oriented Programming

PDM: Physical Data Model

SQL: Structured Query Language

UML: Unified Modelling language

JS: JavaScript.

TS: TypeScript.

Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering at
AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE, Academic
Year 2020 – 2021
xi
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)
ABSTRACT

Cameroon is technologically and digitally improving, hence Cameroon public institutions such
as CAMPOST must also be on permanent improvement so as to cope with the current changes. Due to
the presence of private institutions offering the same kind of services, CAMPOST must then improve
the quality of its services so as to satisfy, retain and remain competitive nationally and internationally.

CAMPOST offers variety of services concerning financial, postal and digital domains. Some of
their services are being managed and maintained manually and others using digital solutions. The
services offered by CAMPOST are quite good, important and cheaper relative to private solutions, but
not all these services or solutions are available online or are not easily accessible. Furthermore, not all
Cameroonians are aware of the advantages, services, and different solutions that CAMPOST offers to
them.

It is with this mind that we decided to setup a web and mobile application that can ease access
to CAMPOST services by their customers. Hence the theme: DEVELOPMENT OF A WEB AND
MOBILE APPLICATION WHICH FACILITATES ACCESS TO CAMPOST SERVICES. In fact, we
are also planning to set up a mobile application allowing all users to have access to the various services
offered by CAMPOST at any time and in any place with the help of a CAMPOST account. This web
platform is likely to be able to give this company not only the possibility of registering, processing and
responding to various customer requests but also, giving the possibility of making optimal searches
quickly and also filtering the search results in the database thereby permitting the company to save time
in processing operations.

The conception and realization of this platform was effective thanks to the use of the
development tools; UML 2.5, ANGUALR, IONIC, NODE, GIT, SPRING BOOT, JAVA, HTML,
CSS, JAVASCRIPT, POSTMAN, TOMCAT, APACHE, VISUAL PARADIGM, VISUAL STUDIO
CODE, MySQL, WAMMP.

Keywords : CAMPOST, Postal services, digital services, Financial services.

RESUME
Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering at
AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE, Academic
Year 2020 – 2021
xi
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)

Le Cameroun s'améliore technologiquement et numériquement, c'est pourquoi les institutions

publiques camerounaises telles que CAMPOST doivent également être en amélioration permanente
afin de faire face aux changements actuels. Du fait de la présence d'institutions privées offrant le même
type de services, la CAMPOST doit alors améliorer la qualité de ses prestations afin de satisfaire,
fidéliser et rester compétitive au niveau national et international.
CAMPOST offre une variété de services concernant les domaines financier, postal et
numérique. Certains de leurs services sont gérés et maintenus manuellement et d'autres à l'aide de
solutions numériques. Les services proposés par CAMPOST sont assez bons, importants et moins chers
par rapport aux solutions privées, mais tous ces services ou solutions ne sont pas disponibles en ligne
ou ne sont pas facilement accessibles. De plus, tous les camerounais ne connaissent pas les avantages,
les services et les différentes solutions que CAMPOST leur propose.
C'est dans cet esprit que nous avons décidé de mettre en place une plateforme pouvant
faciliter l'accès aux services CAMPOST par leurs clients. D’où le thème : CONCEPTION D’UNE
APPLICATION WEB ET MOBILE QUI FACILITE L’ACCESS AUX SERVICES DE LA
CAMPOST. En effet, nous prévoyons également de mettre en place une application mobile permettant
à tous les utilisateurs d'accéder aux différents services proposés par CAMPOST à tout moment et en
tout lieu à l'aide d'un compte CAMPOST. Cette plateforme web est susceptible de pouvoir donner à
cette entreprise non seulement la possibilité de s'inscrire, de traiter et de répondre aux diverses
demandes des clients mais aussi, de donner la possibilité d'effectuer des recherches optimales
rapidement et également de filtrer les résultats de recherche dans la base de données permettant ainsi à
l'entreprise pour gagner du temps dans les opérations de traitement.
La conception et la réalisation de cette plateforme a été efficace grâce à l'utilisation des outils
de développement ; UML 2.5, ANGUALR, IONIC, NODE, GIT, SPRING BOOT, JAVA, HTML,
CSS, JAVASCRIPT, POSTMAN, TOMCAT, APACHE, VISUAL PARADIGM, VISUAL STUDIO
CODE, MySQL, WAMMP.

Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering at
AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE, Academic
Year 2020 – 2021
xi
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)

GENERAL INTRODUCTION
Our legacy platforms have served us well for decades, but we're running out of upgrades
that will keep us ahead. Technology is changing too fast, and our enemies are too adaptable. We
are then facing a situation where technology is seen as the shield for enterprises against
competitors who are also evolving technologically. The appropriate solution for an enterprise to
remain competitive, retain and satisfy his customers is to provide a digital solution that will
render their day-to-day operations easier.

It is with a competitive spirit that CAMPOST assigned to me the theme “Development of

a platform which facilitates access to CAMPOST services”, such a platform will be of great
importance to them in the sense that customers are in real need of information concerning their
services, customers are in real need of facilitator for their day-to-day operations regarding
CAMPOST services.

Providing such a solution for such a company was a great challenge for me, but thanks to
my skills got from AICS, this could be made available. So, to attain these objectives, I used
UML coupled to 2TUP as methodology to do the analysis and some well-known technologies for
the coding part. The different phases used are described below;

- Insertion phase; which will present the host company.

- Specification book; which will summarize the client’s need along with an estimate of the
project.

- Analysis phase; which will present a detail analysis of the existing system and the awaited
system.

- Conception phase; which will present the generic and detail conception of the project.

- Realization phase; which will present the choice of the technologies and the technics
necessary for the implementation of our solution

- User Guide; which will present a user friendly and graphical description of each functionality
of the application.

CHAPTER 1 :
INSERTION PHASE

Preamble
The insertion document presents the internship environment, the structure of the
organization, the conditions in which the interns were received, as well as the project to be
realized during the internship.

Content:

Introduction
I. WELCOME AND INTEGRATION INTO
CAMPOST
II. GENERAL PRESENTATION OF CAMPOST
III. ORGANISATION OF CAMPOST
IV. PRESENTATION OF INTERNSHIP THEME

CONCLUSION

INTRODUCTION
The insertion phase is the period during which a student must become familiar with the
environment in which he will perform his internship. It is also the integration of an individual
into a foreign group or environment where the language, the actions, the way of thinking must be
purely professional.

With the aim of putting into practice what have been thought at the African Institute of
Computer Sciences (AICS) Cameroon office (Paul Biya Technological Center of Excellence),
the school integrate an internship with a duration of 4 months, which is the reason why we
integrate CAMPOST. The goal been to convert our theoretical knowledge into practice that can
help to provide a solution to a specific problem.

II. GENERAL PRESENTATION OF CAMPOST

1. History of CAMPOST
In 1999, the postal sector of the Ministry of Posts and Telecommunications was subject
to a restructuring which led, through Law n ° 99/002 of April 7, 1999 governing postal activity,
to the creation of two distinct companies: The National Company posts (SONAPOST) and the
Postal Savings Bank of Cameroon (CEPC).
All these reforms, which take place in a context of economic liberalization and the
development of new information and communication technologies (NICT) also participate in the
policy of disengagement of the state from the commercial sectors of the national economy. In the
postal sector (still unregulated but very buoyant), they are reflected in an acceleration of
competition between private operators (who have conquered significant market shares) on the
one hand and the public and incumbent operator (the CAMPOST) to ensure the missions of
universal postal public services on the other hand.
Decree No. 2004/095 of April 23, 2004, the company CAMPOST was created by
merging SONAPOST and the Postal Savings Bank CEP. A restructuring and debt settlement
plan has been put in place. In 2007, following a call for tenders, the Canadian group Tecsult
International was selected to administer CAMPOST and clean up its accounts, the State
remaining the shareholder. State company with public capital of one billion (1,000,000,000), it is

currently managed by a Cameroonian. CAMPOST has an average of ten regional offices

represented in the ten regions of Cameroon, 238 post offices distributed throughout the territory.

2. Principal missions of CAMPOST

The main missions of Cameroon Postal Services are:
 Develop and operate postal networks and services.
 Provide postal services of a financial nature.
 Promote national saving,
 Offer services related to fund transfer.
 Offers a medium for services payment.
 Offers digital services like hosting through its data center.

3. Global products and services offered

a. Postal services
CAMPOST provides to its customers a varied range of postal products and services that meet
current market requirement such as Express Mail service, postal box, postal parcel.

b. Financial services

CAMPOST also interacts in the financial domain by offering financial services such as;
saving, loans, fund transfers, payment of services.

c. Digital services

CAMPOST through his data center offers digital services such as hosting and connectivity.

b. Location plan

F IGURE 1: CAMPOST LOCALISATION PLAN

F IGURE 2: O RGANIZATION CHART OF CAMPOST ( SOURCE : CAMPOST)

The DIS is composed of 3 main departments;

 The maintenance, network and telecommunications department.

 The operations department.

 The research, study and development department.

a. The maintenance, network and telecommunications department

The head of this service is M. DAYANG ALAIN, their main roles are;

 Design, deployment and administration of networks.

 Establishment of network security policies.

 Inventory of all CAMPOST IT equipment.

 Management of IT equipment.

 Interconnection and cabling of sites.

 Centralized management of services, data, applications and users.

b. The operations department

The head of this service is M. NSANGOU IBRAHIM, their main roles are;

 Administration of CAMPOST applications.

 Ensures the integrity of operating systems used.

 Backup management.

 Deployment and update of applications.

 User’s training.

c. The research, study and development department.

At the head of this department, we have M. SCHWAMA SAMUEL, this department basically
have 3 main roles;

 Researches based on technology updates.

 Studies: concern the analysis of the company's various offers, to see if the offer meets the
company's expectations
 Development: software development (Java under Oracle…). This service uses technology
updates which can allow CAMPOST to carry out its missions.

CONCLUSION
My insertion at CAMPOST helped me to have a clear idea of its missions, objectives and
its activities as we pursued our academic internship. The contact with the various departments,
ongoing projects and the personnel of CAMPOST enabled us to attain the objectives cited by the
African Institute of Computer Sciences, that is the integration of its interns in a professional
environment and adaptation of academic knowledge to enterprise needs will be achieved. At the
end of this phase, the theme “DEVELOPMENT OF A PLATFORM WHICH FACILITATES
ACCESS TO CAMPOST SERVICES” was given to me. The next step in this book will be the
elaboration of a preliminary study which will be in line with the academic and professional
needs.

CHAPTER 2 :
SPECIFICATION
DOCUMENT

Preamble
The specification book is the part of the document that gives the relative directives of the
product to be produced and delivered. It carries the set of steps and procedures permitting to
understand and define the work to be realized and what the client is expecting from the software.
This document also presents the functional and non-functional need of the application.

Content:

Introduction
I. CONTEXT AND PROBLEM DEFINITION
II. OBJECTIVES
III. EXPRESSION OF NEEDS
IV. ESTIMATED COST OF THE PROJECT
V. LIST OF PARTICIPANTS
VI. PROJECT PLANNING
VII. PROJECT CONSTRAINTS
VIII. DELIVERABLES

CONCLUSION

INTRODUCTION
Specification is a critical part in software development process. For this reason, care must
be taken when elaborating the specification document in order for the solution to clearly satisfy
the client’s need. The specification book permits to specify the expectations of the customer as
well as the standards that will govern the project for a good, smooth, precise and concrete
project. It establishes a certain agreement between the client of the project and the person who is
supposed to realize the project. It presents the objectives and needs of the system to be
developed. The present specification book relates to the context and justification, the needs of the
project, the plan and the deliverables.

CAMPOST has 232 post offices over the territory where they offer their 3 main categories of
services (financial, postal and digital services) but these services are not still known by
Cameroonians who are considered to be the first CAMPOST customers.

CAMPOST already propose other software-based solutions but these solutions are not
centralized nor harmonized. In order to facilitate the access to services offered by CAMPOST,
CAMPOST-IN-HAND offers a package of solutions that contains all the services proposed by
CAMPOST (financial services, postal services and digital services) which will permit users to
access to all the services in one App or to be directed to the appropriate postal office which can
provide a desired service. On the other hand, CAMPOST-IN-HAND will provide to CAMPOST
an administrative interface from where they can manage all their users and their different
operations.

2. PROBLEM DEFINITION
One of the major problems the earth will ever encounter is the lack of information, not
having an information on how something can be done or not having an information that
something exist is a real problem.

On the other hand, those who are informed about CAMPOST services don’t have a real time
and remote access to these services.

CAMPOST customers don’t have an online solution enabling them to get in touch with
CAMPOST services.

Postal offices are open just during the week, so a customer in need of a service during the
weekend cannot be satisfied.

The current pandemic condition of COVID-19 does not permit us to be in movement all the
time, that is going to a postal office so as to have an account balance or other information
concerning his account or moving from one postal office to another in search of a particular
postal service.

We then have as major problem the digital absence of CAMPOST, this absence then causes
variety of problems concerning the absence of CAMPOST services.

II. OBJECTIVES
1. GENERAL OBJECTIVES
The general objectives of my internship were firstly to gain professional experience on
how things are being done in the professional milieu and secondly the development of a software
for CAMPOST customers and CAMPOST administration for partial fulfilment of the award of
Higher Technician Diploma in software engineering. The mobile application of this solution will
be a free downloadable, accessible and user-friendly app composed of 2 parts that is the part
dedicated to CAMPOST customers and the other part dedicated to CAMPOST administrators at
the head quarter.

The part dedicated to CAMPOST customers will both be available for IOS and Android
users and a web portal for both clients, which will assist them by giving them the right
information about CAMPOST services and postal offices and also by enabling them to handle
each and every service that CAMPOST offers to its customers. The user’s information which are
collected are kept private and anonymous, all the financial transactions will be handled and
administered by the right CAMPOST authority in charge of finances, the postal transactions
administered by the head of postal affaires of the institution, digital administration by the DATA
CENTER.

The administration sector will mainly be for management and control over their customer and the
task they perform.

2. SPECIFIC OBJECTIVE
A project consists of several specific objectives for it to be able to bring change in order to
solve the given problem. It is at this level that we mention all the paths to follow in order to have
the general objective. At this level, we express the benefits of this new software in the
environment. Some of benefits are;

 Have access to all CAMPOST services at any time and place.

 Gain in time and cost for fund transfers.

 Have the adequate information on services.

 Easy payment of services

 A centralized information concerning user transactions (For administrators)

III. EXPRESSION OF NEEDS

1. FUNCTIONAL REQUIREMENTS
The functional requirements are based on the functionalities of the system It will help us to
answer to the question “what does the system do?”. CAMPOST-IN-HAND will have the
following functionalities;

A. Customers

 View information concerning CAMPOST services.

 Geolocate postal offices.

 Search postal offices offering a particular service.

 Management of bank account.

o Account creation.

o Transaction history.

o Consult account statuses.

 Management of fund transfers.

o Transfer of fund national and or international level

 Credit request (School credit or other forms of credit).

 Payment of services (customs fees, train tickets, school fees etc..).

 Consult package position (package tracking).

 Request price simulator for package transfers.

 Management of postal box.

o Create a postal box.

o Follow up on postal box

 Order School books and manuals.

 Order stamps in bulk.

 Request for hosting and or connectivity.

B. Administrators
 Management of users and habilitation: The main administrator will be able to give rights
and privileges to certain users on some specific tasks.

 Management of services: The administrators will be able to either add, delete or edit a
service offered by CAMPOST.

 Management of postal offices: Postal offices will be managed from this section.

 Statistics and reports: Generated reports concerning user’s transactions will be generated.

 Management of postal and financial transaction: All the transactions done by the
customers on the user section, will be managed that is approval or refusal of a request,
deleting users etc…

2. NON-FUNCTIONAL REQUIREMENTS
The non-functional requirements are the requirements which are not specific to the system
behavior but rather identifies the internal and external constraints of the system. These
requirements are;

A. Characteristics:

 Authentication: The system should be able to identify each and every user of the system
for security measures.

 Ergonomics: The system should offer to its users interfaces which are rich in content so
as to avoid the number of screens, on the other hand, user interaction with the system
should be convenient and suitable.

 Data protection: All about privacy of information. A such system containing sensible
information must keep data the private and protected.

 Offline functioning: The software should also be accessible offline for some important
operations.

 Compatibility: There should be no restriction on the operating system, the software

should run on IOS, Android and also have a web view.

 Performance: The software should be able to handle several tasks without disruption.

 Liability: The system should be trusted by its users so as to have a greater conversion.

B. System’s required configuration:

Conception environment

Running environment

WINDOWS, MAC OS, LINUX

(Browser): Minimum 32G HDD, 1G
ENVIRONMENT RAM, PINTIUM 4.

IOS Android
DEVICE: DEVICE:
Minimum Minimum
IOS 10.2 Android 6.0.1

Network environment

Running
environment
DBMS Application server

Price sources: Mercurial 2020, Microsoft.com

T ABLE 1: HUMAN RESOURCES

Human Resources
Human Resource Price Total
Quantity (FCFA)/day Duration (days) Price (FCFA)
Head of project 01 250,000 120 30,000,000
Analyst 01 150,000 20 3,000,000
Developer 01 150,000 25 3,750,000
Tester 01 150,000 10 1.500,000
Total cost for human resources (FCFA): 38,250,000

T ABLE 2:S OFTWARE RESOURCES

Software Resources
Mercurial Function Software Type Unit Total price
reference price (FCFA)
(FCFA)
37-013-160015 Operating Microsoft Proprietary 126,000 126,000
System Windows 10 PRO
32/64 bits
/ Browser Google Chrome Free 0 0
Front-End
/ Development Visual Studio Code Free 0 0
environment
Back-End
/ Development ECLIPSE Free 0 0
environment
Microsoft Microsoft office
37-013-160152 Office suite 2016 Proprietary 241,500 241,500
Collection
/ DBMS MySQL Free 0 0
/ Front-End Node Js Free 0 0
local server
/ Back-End Wamp Server Free 0 0
server

T ABLE 3: H ARDWARE RESOURCES

Hardware Resources
Mercurial Hardware Unit price Quantity Total Price
Reference (FCFA) (FCFA)
37-014-160061 Laptop ACER-ASPIRE | M, 1 228,850
INTEL COLERON 1.8Ghz,
228, 850
500giga SSD hard drive, 6giga
RAM ddr3, Wi-Fi, Bluetooth,
Webcam, 15.6” screen display
01-003-160008 USB flash drive SanDisk 3.0 23,862 1 23,862
ultra-dual drive 16G
01-007-160171 E.T.N Distributor 10,350 2 20,700
37-011-160032 HP Laser printer MFP MI125A 132,250 1 132,250
37-005-160038 HP keyboard K1500 17,250 1 17,250
HP mouse X900 5,750 1 5,750
Total cost for hardware resources (FCFA): 428,662

T ABLE 4: ESTIMATED COST OF THE PROJECT

Total estimated cost for the project

Price (FCFA)
Human Resources 38,250,000
Software Resources 1,929,675
Hardware Resources 428,662

Sub Total = 40,608,337 FCFA

Margin of errors (10%)
Margin of errors cost estimation (Subtotal * 10%) =
4,060,833.7 FCFA
Total Cost (Subtotal – margin of errors):
44,669,170.7 FCFA

V. LIST OF PARTICIPANTS
T ABLE 5: LIST OF PARTICIPANTS

Names Functions Roles and tasks

M. SCHWAMA Samuel Sub Director of Information Systems Professional Supervisor
at CAMPOST
M. TAGNE Cedrick Chief Executive Officer (CEO) of Professional Supervisor
SkyDev Solutions
CAMPOST Host company Project owner
AICs Cameroon Training school Project controller
M. NJOMO Yannick Lecturer at AICS- Cameroon and Academic Supervisor
CEO of WIN MONEY
Project head, analyst,
conception and coding
M. KAMGA Jaures Second year Student at AICS- of the project (Backend
Cameroon services modules),
testing

Task Duration (days) Period

Produce an insertion 14 days 1st June to 14th June
document
Production of a 14 days 15th June to 28th June
specification book
Analysis of the solution and
drafting of the Analysis 21 days 29th June to 20th July
document
Coding of de solution and
drafting of the design 51 days 21th July to 9th September
document
Producing the Realization 10 days 10th September to 20th
or deployment document September
Functionality Test 7 days 21th September to 28th
September
Completion and 2 days 29th September and 30th
Verifications September

Gantt Diagram

The Gantt diagram is a tool used in project management enabling the project manager to
visualize in time the various tasks components if a project. It is all about a graphic representation
that enables to graphically represent the project advancements. The Gannt Diagram for this
project is as follows.

F IGURE 3: PROJECT GANTT DIAGRAM

2. Time constraints: This system can be considered as one of the largest customer’s
solutions of CAMPOST, thus having 4 months to develop it was considered insufficient.

3. Cost: The finances available for the project are very limited

VIII. DELIVERABLES
After implementing our solution, we are expected to submit the following deliverables;
1. Project Report/ Internship report:
This report describes the task performed thought out my internship and throughout
the realization of this project. The report contains;
 The insertion document.

 Specification document.

 Analysis and design document.

 Realization document.

 A user’s guide.

2. A CD-ROM.
The CD-ROM contains.
 The source code of the software.

 Database (SQL file).

 The software setup (android and ios).

 A soft copy of the internship report.

 A corresponding PowerPoint.

CONCLUSION
Coming to an end of the establishment of the specification document, we have precisely
taken in consideration the user needs and requirements for the upcoming solution so as to
propose a better one relatively to the current system. Thereby, we have drafted the cost
estimation for this project as well as the planification of the project realization. The end of this
part will enable us to easily dive in to the drafting of the analysis document which will give more
technical details concerning the system to be developed.

CHAPTER 3 :
ANALYSIS PHASE

Preamble
The analysis permits to present the problems and its solutions, presents in detail the
functionalities to take into consideration, the different diagrams and their arrangement in order of
risk and priority so as to have a detailed understanding of the information system to be modeled.

Content:

Introduction
I. STUDY OF THE EXISTING SYSTEM
II. PROBLEMATIC
III. PROPOSED SOLUTION
IV. METHODOLOGY
V. DETAIL ANALYSIS OF THE SYSTEM

CONCLUSION

INTRODUCTION
While developing or implementing a solution, we have 2 broad components: System
analysis and System design which both help in understanding the current or existing system and
thus propose a new and ameliorated solution. The analysis phase of a project is a phase where the
system to be put in place is precisely studied. This study is based on the functional specifications
so as to obtain the exact idea of what the system will realize to the user. Thus, system analysis is
mainly based on investigating a system, identifying problems and use the information obtained to
propose a better one. This part of the report consists in describing the current system, its
limitations and proposed solution, the presentation of UML and the 2TUP method and finally the
various diagrams that meets the functional requirements.

 Develop and operate postal networks and services,

 Provide postal services to the financial landscape,

 Promote national saving,

 Provide benefits related to the transfer of funds,

 Ensure the management of insurance and wealth,

 Ease payment of services and,

 Provide digital solutions such as hosting and connectivity.

All these missions are being accomplished by 3 main services at the head quarter; the postal
service, the financial service and the digital service (DATA CENTER). For the good
management of all these services and missions, CAMPOST has as main aim to provide an
interactive platform so as the facilitate customer’s transactions and bring these customers close
to them.

2. DESCRIPTION OF THE EXISTING SYSTEM

CAMPOST offers their services through their 232 postal offices all over the territory. These
services are being grouped in 3 main categories; financial services, postal services and digital
services.

CUSTOMERS

The customers services offered by CAMPOST are the financial services, postal services and
digital services. The existing system will be studied in 3 subgroups according to their services as
follows;

a. Financial services:

The main financial services offered by CAMPOST are bank accounts, fund transfers
(national and international), CAMPOST MONEY (CAMO), savings, wages, loans and payment
of other forms of services (customs fees, school fees etc..). The existing system concerning each
financial service works as follows;

 Bank accounts: CAMPOST current have 2 types of accounts that is the current account
and the saving account. All transactions being made on the account are done at the postal
office, meaning for a customer to transfer fund from one account to another, he must
move to the postal office for accomplishment.

 Fund transfers: The current fund transfer system still works in the traditional way that is
for any fund transfer, the customer must move to the postal office, fill the form forward
the money either nationally or internationally.

On the other hand, new fund transfer solutions are not available every where that
is far localities don’t have access to those solutions.

 Savings: For the saving system, the customer don’t have complete access his saving
account, for any balance control or other operations, the customer has to go to the postal
office for the operations.

 Wages: At the end of each month, there is a queue in front of all postal offices for
salaries. Since they have to retrieve their money only at CAMPOST agencies.

 Loans: Loan requests takes too much time to be accomplished since the user have to go
to the postal office to make the demand, one his demand is accepted by the postal offices,
all the demands from all the postal offices are being forwarded to the head quarter for
treatment, hence the time for the files to reach the head quarter takes too much time.

In general, almost all the financial services offered by CAMPOST to their customers are not
yet optimal, since every is still done at the postal offices, no matter the minimum service your
need.

b. Postal services:

CAMPOST offers postal services such as creation of postal boxes and package transfers.
The current functioning of each of these postal services are as follows;

 Postal boxes: The creation and management of postal boxes by customers are being done
on spot (at the postal office in charge of the service). So in case of any information
concerning his or her postal box, the customer will have to go to a postal office in charge
of the service.

 Package transfers: To transfer a package through CAMPOST, a customer is directed to

a postal office to make the transfer, after the transfer, there is no follow up on the
package by the customer.

c. Digital services:

CAMPOST offers digital services through their data center, some of these digital services
are hosting and connectivity. The current system works in such a way that any third party in
need a of digital service will have to go to the data center so as to make a request, thus not very
optimal.

A. ADMINISTRATORS

On the other hand, we have the CAMPOST administrators at the head quarter having as task
the management of all these customers services.

a. Loans: Concerning the loans, there is no digital system to manages the loans requests
and to make a follow up on the loans that were approved and granted. Once the request
reaches the head quarter, the person in charge of loans have to pass through every
document for study, and once the loan is accorded, there is no system to make the follow
up all the loans accorded or validated, so the administrators at the end of each month
have to restudy the files to verify if all the customers respected the returned date.

b. Financial Accounts: Currently at CAMPOST we have 3 types of financial accounts that

is the current account, the saving account and the CAMPOST MONEY account. There is

no data connection amongst these 3 accounts that is the administrators don’t have a
means to get the information of a customer having the 3 account from one account. Also
from one account no one can make an operation on the other account since their data are
not synchronized.

3. LIMITATIONS OF THE EXISTING SYSTEM AND

PROPOSED SOLUTIONS
The study of the limitations of the current system is a process which will permit us to make
an evaluation on the system in place, and therefore have some basis on which we can propose a
solution. This part will enable us to expose the difficulties of the current system while laying out
the proposed solution for each of them.
T ABLE 7:L IMITATIONS OF THE EXISTING SYSTEM AND PROPOSED SOLUTIONS

Problems/Limitations Consequences Proposed solution

USERS
The solutions proposed by This usually pushes the As solution, CAMPOST-IN-
CAMPOST are not well population towards private HAND will also focus on the
known by the public, so there institutions which has as main promotion of CAMPOST
is a lack of information aim profit, so their services services, thereby increasing
concerning CAMPOST are sometimes expensive as the chance to the population
services compared to CAMPOST to get in touch with
which is a public institution CAMPOST services which
so having as main aim to are cheaper.
serve the population.
Users in need of CAMPOST This causes the movement of We propose a solution where
services don’t know the exact users from one postal office users can search a service and
postal office where they can to another in search of a they will be directed to the
be served, since all the postal service meanwhile with our postal office offering the
offices do not offer the same current pandemic condition it service closed to them, in

Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering
at AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE,
Academic Year 2020 – 2021
98
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)
is not advised to do such addition, all the postal offices
services.
movements. will be geolocated by the
system, so while proposing a
postal office, the system also
propose the exact path from
the user’s position to the
postal office.
Concerning bank accounts, Moving to a postal office to A solution called
customers still have to move make a bank transaction is “CAMPOST-IN-HAND”
to the postal office in case very tiring and time meaning having every
they want to make an consuming since you may not CAMPOST services in hand,
operation on their account. be the only customer to be so from here, customers can
served. Also, with the actual easily manage their bank
heath situation, avoiding account remotely and
movement as much as simultaneously thereby
possible is the better thing to gaining in time and energy
do.
There is a long queue in front The main consequence here is Proposing a solution where
of each postal office at the loss of time and energy CAMPOST customers have
end of each month for salary the possibility to transfer their
purposes. money into their CAMPOST
MONEY account thereby
having the possibility to
retrieve the money at any
CAMO point of sale.
School credits and other In the case of urgent need of A solution where the
forms of credits takes too this credit by a customer it demands for credits are being
much time to be achieved, will not be possible since the done online at the first level
since everything is being process takes at least 2 weeks in such way that the person in

Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering
at AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE,
Academic Year 2020 – 2021
98
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)
to be achieved.
done traditionally, that is a charge of studying the files
customer in need of a credit, can do it simultaneously
have to make a request to the while the customers are
postal office then all the demanding. Then at the
requests made by customers second level the customers
are being forwarded to the then can deposit the physical
head quarter for validation. files at a postal office for the
second level of validation so
that when the files reach the
head quarter, the different
studies have already been
made by the administrators so
approval can be made
immediately as the file
reaches the head quarter. This
reduces the demand process
to at most one week.
Customers transferring their This can be very harmful in CAMPOST-IN-HAND
packages through CAMPOST the case where the estimated proposed an online price
don’t have an online price price for the transfer by a simulator based on the type of
simulator so as to know how customer is not sufficient, package and the weight.
much it will take to transfer then he will be rejected at the
their packages before even postal office while when
going to the postal office for transferring the product.
the transfer.
After the deposition of a There can be lost of An online and real time
package for transfer, there is customers due to lack of tracking of packages is
no follow up on it by the confidence by these. implemented where at any
customer. The customer does time the customer can know

not know the exact location the exact location of his

of his package after a long package.
time.
Concerning digital services The main consequence here is A solution from which all the
such as connectivity, to get in the lost of time, finance, and digital requests are being
touch with a digital service to energy done online.
customer have to go the data
center. What if the customer
is not in the same town as the
data center?
ADMINISTRATORS
The study of loans request is Too much work leading to A computerized solution for
still done manually the use of excess fatigue and time the study of demands.
papers and pens consuming
No system for the follow up There can be lost in finance A follow up system for the
of loans approved loans
No centralized information on Too much work by the A solution where all the
the different types of administrators in case of customers information will be
accounts synchronization of centralized and visible from
customer’s information one place.

II. PROBLEMATIC
One of the major problems the earth will ever encounter is the lack of information, not
having an information on how something can be done or not having an information that
something exist is a real problem. For example, we still send packages through private
institutions meanwhile the costs are high, this is due to lack of information cause an informed
person will have known that the same package can be sent through CAMPOST at a relative low
cost, people from far places don’t have access to solutions as Orange money and MTN mobile

money for their fund transfer, they have to move around in search of it since they are not
informed of the availability of this same services at CAMPOST meanwhile CAMPOST is
present everywhere in such a ay that each Cameroonian can easily have access to CAMPOST
services

The major problems encountered by the Cameroonian society relative to CAMPOST services
are as follows:

A. Customers

 Lack of information concerning the CAMPOST user services, pushing them towards
private institutions which are sometime relatively more expensive than CAMPOST since
it is a public institution.

 Payment of bills and other services are still done in the traditional way or through private
institutions or solution which are sometimes expensive.

 CAMPOST users still have to go to a postal office so as to make a transaction on their

banking accounts.

 School credits or other credits in CAMPOST takes averagely 2 weeks to be achieved, due
to the fact that there is no automation.

 Fund transfers between CAMPOST users is still done in postal offices.

 Those in need of postal services don’t really know in which postal office to go since all
the postal offices don’t offer the same services, so they keep on moving from one postal
office to another in search of a particular service, and these movements are not secured
due to the current health situation.

 Cameroonians still transfer packages either at the national or international level through
private companies at a huge cost.

 Those who make use of CAMPOST services to transfer their packages don’t have a
follow up on them.

 There is a queue at each postal office at the end of the month for salary purposes.

 For developers and IT specialists, they completely rely their databases on external servers
and data centers.

B. Administration

 No system for the follow up of loans/credits.

 Information concerning their users are not centralized.

 Credits applications and requests from far regions relative to the head quarter takes too
much time to be accomplished since the applications have to be transferred to the head
quarter for study.

 No control on their external users and their financial transactions

III. PROPOSED SOLUTIONS

The study of the functioning of CAMPOST permits us to point out some criticism concerning
their operations. Based on these critics some of the majors’ questions we are trying to point out
are;

 What are the different innovations or amelioration that we can implement on the current
system so as the render it more optimal?
 Who are our targets on the new solution to put in place?

The study we earlier made enabled us to discover some lacunae on the current system.
Having as main objective to bring out solutions that will solves those lacunae, we are asking
ourselves the main question; how can we facilitate CAMPOST customers in the use of

CAMPOST services and how can we facilitate CAMPOST administrators in their

management process on these services?

In order to overcome these problems, I proposed a solution called CAMPOST-IN-

HAND, a firmware that encompasses all the user services made available by CAMPOST to their
customers. The different solutions are stated below accordingly with the problem they resolve.

A. CUSTOMERS

 CAMPOST-IN-HAND integrate CAMO (CAMPOST Money) from which payments of

bills (CAMWATER, ENEO), services (bus station, shopping bill etc..), school fees,
customs fees, and tax payments can be made. This solution will eradicate the old or
traditional method of bills payment, which was time and energy consuming.

 Instead of moving from one place to another in search of OM or MOMO for those in far
regions, CAMPOST is available every where in Cameroon, so we propose a solution
where you can easily refund your account from everywhere.

 This system proposes a solution where each and every CAMPOST customers will have
their ‘banking account in hand’ from where all transactions on their account can be made
by them remotely and will therefore prevent them from moving to post offices during this
pandemic period.

 Through CAMPOST-IN-HAND, we propose a solution where credit requests and

applications can be done remotely by customers, the customers provide required
documents online, so that these documents can be studied instantaneously, while waiting
for the physical document to arrive the head quarter. This solution can reduce the demand
and approval process to approximately 3 days maximum.

 CAMPOST-IN-HAND enables the instantaneous and remote transfer of fund amongst

CAMPOST customers, solving the problem where to make a fund transfer the customer
had to go a postal office making the process very slow and dangerous regarding the
world’s current health conditions.

 CAMPOST-IN-HAND also solve the problem of lack of information, some people in

need of postal services don’t really know in which post office they should go. We solve
the problem by giving the adequate and right information to the customer in need, in
addition, we guide the customer to a particular post office by providing him a map toward
that office.

 We provide a solution that gives in real time the exact position of a package being
transferred.

 Those receiving their wages at CAMPOST, the lineup problems at the end of each month
are solved by CAMPOST-IN-HAND where the salaries can be transferred from the
current account to CAMO (CAMPOST Money) account hence increasing the number of
agencies from where he can retrieve his money.

 Provide an online DATA CENTER service where a user can request for hosting and or
connectivity.

B. Administration

CAMPOST-IN-HAND proposes an administration part from where management

and follow up can be done by CAMPOST on their customers, where there will be an
emphasis on the follow up of approved credits and from where CAMPOST can have a
centralized customer’s information relative to all the user services they offer.

UML was standardized in January 1997 by the OMG (Object Management Group) which
is an American association created in 1989 which aims to promote and standardize the object
model in all its forms. UML is now known and that since September 2013 in its version 2.5 Beta
2.

The Unified Modelling Language (UML) was created to forge a common, semantically
and syntactically rich visual modelling language for the architecture, design and implementation
of complex software systems both structurally and behaviorally. UML has applications beyond
software development such as process flow in manufacturing.

It is analogous to the blueprints used in other fields, and consists of different types of
diagrams. In the aggregate, UML diagrams describe the boundary, structure and the behavior of
the system and the objects within it.

UML is not a programming language but there are tools that can be used to generate code
in various languages using UML diagrams. UML has a direct relation with object-oriented
analysis and design

A. ADVANTAGES OF UML
UML is standardly used to visually describe a program, specifically an object-oriented
program. UML helps to organize, plan and visualize a program. In addition, being a standard, it
is widely used and accepted as the language for outlining programs. UML is used in a variety of
purposes and its readability and re-usability make it an ideal choice for programmers.

A UML diagram is a visual representation of the relationships between classes and entities in
a computer program. A class is an object in programming that organizes similar variables and
functions in one location. To understand a program, it is essential to understand what each class
object does, the information it stores and how it relates to other classes in the program.

By showing this information in a diagram, it is easy to understand and visualize a program’s

relationships

b. Readability and re-useability

A UML diagram is beneficial in that it is very readable. The diagram is meant to be

understood by any type of programmer and helps to explain relationships in a program in a
straightforward manner. Traditionally, to understand a program, a programmer would read the
code directly. This could be thousands or millions of lines of code in very large programs.
Having a UML diagram running helps to quickly illustrate those relationships. Additionally, by
using a diagram to show the code running in a program, a programmer is able to see redundant
code and reuse portions of code that already exist rather than rewrite those functions.

c. Standard

UML is the current standard for programming in object-oriented programming languages.

When creating classes and other with relationships between each other, UML is what is used to
visually describe these relationships. Because it is used as a standard, it is widely understood and
well known. This makes it easy for a new programmer to step into a project and be productive
from day one.

F IGURE 4: UML DIAGRAMS ORGANISATION

Y as shown in the figure below.

This process is articulated with three essential phases/branches:

 The functional branch: This branch captures business needs, resulting in a model6
focused on the end-users’ business.

 The technical branch: This branch proposes a generic design from the technical needs,
identifies the materials, tools and technologies to be used.

 The implementation: The implementation phase consists of bringing the two branches
together, providing the application design and finally the delivery of a solution adapted to
the needs.

A. THE VARIOUS BRANCHES OF 2TUP

a. Functional branch (left branch):
 Capture of Business (functional) needs: This part minimizes the risk of producing
an inadequate system with the needs of users and also verifies its consistency.

 Analysis: This is the study of specifications to find out what the system will be made
of in terms of the business rules. We have the following diagrams: Use case, Activity,
State machine, Communication.

b. Technical branch (right branch):

 Capture of Technical Needs: This stage consists of the identification of tools,

materials and technologies to use in developing the system. This technical
architecture will be presented in this stage.

 Generic design: The technical architecture will be presented in this stage. We have
the following diagrams: Mockup7 Design.

c. Implementation Branch (middle branch):

 Preliminary Design: This is the stage in where the analysis model is integrated into
the technical architecture. The goal here is to know what technical component will be
used depending on the features from the analysis. We have the following diagrams:

Interaction Overview, Component, Deployment, Package and Composite structure

diagrams.

 Detailed Design: This is the detailed design of each feature of the system. We have
the following diagrams: Class, Object, Sequence and Timing diagrams.

 Coding and Tests: This is the programming phase of the designed features,
alongside testing of the coded features.

 Recipe (Results): This is the validation phase of the functions of the system
developed

B. CHARACTERISTICS OF 2TUP
The Two Track Unified Process was built to be used with the Unified Modelling Language
and has the following characteristics;

 It is user oriented: 2TUP is built from users’ expectations

 It is component oriented: It offers flexibility to the model by supporting the re-use of

components

 It is an iterative process: Processes are being done in iterations and each iteration shows
a precise level of abstraction.

 It is an incremental process: Allowing a better technical and functional risk

management and thus constituting the deadlines and the costs control.

3. JUSTIFICATION ON THE CHOICE OF THE ANALYSIS

METHOD
Our choice was based on the modeling language UML associated to it a method of analysis
2TUP due to certain criterion which are as follows;

 UML is based on the object-oriented approach.

 UML is a modeling language which mainly focused on user’s needs and expectations.

 UML associates data and treatments.

 2TUP is a process based on object-oriented approach and it is built from UML.

 2TUP facilitates the modeling of complex systems which can further be readjusted or
modified.

V. DETAIL ANALYSIS OF THE SYSTEM

1. CAPTURE OF THE FUNCTIONAL NEEDS
The capture of the functional needs is the first step in the left branch of the Y cycle. It
formalizes and explains in details what have been presented in the preliminary study. Our work
consists of analyzing and designing and application that will be use to interconnect freelance
instructors with driving students base on their availability and also permit to test their knowledge
on the issue.

A. Use Case Diagram

i. Definition:
The use case diagram simply shows the functionalities of system, their interdependence
and how they can be linked with actors of the system. It also clearly defines the boundaries of
the system.

ii. Formalism:

<<include>>
Name of usecase 1 Cas_2

Acteur_1

<<extend>> Cas_3

Cas_4

Acteur_2

F IGURE 6: USE CASE DIAGRAM FORMALISM

iii. Components of a use case diagram

T ABLE 8: COMPONENTS OF A USE CASE DIAGRAM

Element Description and Main properties Notation

Actor Represents an entity that directly
interacts with the system. The actor is
what performs the different possible
actions of the system.

performed by an actor.
Association It indicates that an actor takes part in a
use case. B

Actor_1

Inclusion An inclusion relation denotes that an

<<include>>
included action must be performed A B
before another action can be performed.
A includes B signifies that B is a
compulsory part of A.

Exclusion It denotes that an action may be

performed while another one is being <<extend>>
A B
performed. A use case B extends A
means B is an optional part of A.

Inheritance It is the only possible relation between

Acteur_3
Acteur_4

actors.

Generalization This shows that a uses case is a kind of

another. This relation also permits to Actor_1 Actor_2

decompose a complex case into smaller

and simple cases. A B

1. Identification of actors and their use cases

We will now list the actors likely to interact with the system, but at first, we will define an
actor; An actor represents the abstraction of a role played by external entities that interact
directly with the system studied. The actors of the system identified at first are:

 Authentication
 Management of users.
 Management of services.
 Management of postal offices
Director  Generate reports and statistics.
 Management of postal demands.
 Management of credit requests.
 Management of financial operations.
 Management of digital services.
 Management of credit requests.
Head of financial services
 Management of financial operations.
 Management of postal demands.
Head of postal services
 Management of postal services.
Head of digital services  Management of digital services
 Authentication
 Consult CAMPOST services
Customer
 Management of postal box
 Follow up of packages
 Order stamps
 Order school manuals
 Management of bank accounts
 Make credit/loan requests
 Payment of services
 Management of CAMO accounts
 Request for hosting

 Request for connectivity.

F IGURE 7: G ENERAL USE CASE DIAGRAM

F IGURE 8: USE CASE DIAGRAM <<MANAGE FINANCIAL SERVICES>>

GENERAL USE CASE

F IGURE 9: USE CASE DIAGRAM <<MANAGE POSTAL SERVICES>>

F IGURE 10: USE CASE DIAGRAM <<MANAGE LOAN REQUEST>>

F IGURE 11: USE CASE DIAGRAM <<MANAGE USERS AND HABILITATIONS>>

F IGURE 12: USE CASE DIAGRAM <<MANAGE CAMPOST SERVICES>>

F IGURE 13: USE CASE DIAGRAM <<MANAGE CAMO ACCOUNT>>

F IGURE 14: USE CASE DIAGRAM << MANAGE BANK ACCOUNT >>

F IGURE 15: USE CASE DIAGRAM << MANAGE POSTAL BOX >>

iv. Credit/Loan management use case diagram

F IGURE 16: USE CASE DIAGRAM << MANAGE LOAN >>

3. Use case textual description

As we mentioned earlier, a use case represents a transaction. Here, it is a question of
breaking down the use cases, making a textual description and then emphasizing on the different
detailed scenario. This will be done using diagrams known as the sequence diagram and the
activity diagram.

a. Use case <<Authenticate>>

T ABLE 10: << AUTHENTICATE >> TEXTUAL DESCRIPTION

Title Authenticate
Actor: User

Objective: Grant the user access to the application

Pre-conditions (s): - The system should be loaded

Nominal scenario: 1. The user click the login button

2. The system provides the login form
3. The user fill and submit the form
4. The system verifies the credentials
5. The system verifies the information in
the database
6. The system start the user’s session
Alternative scenario (invalid 4.1 The system display the error message

credentials) 4.2 The system returns to step (3) of the

nominal scenario
Alternative scenario (user does not 5.1 The system display thhe error message

exist) 5.2 The system returns to step (3) of the

nominal scenario
Post-conditions (s) - The user’s session is lauched

b. Use case <<grant permission>>

Title Grant permission

Actor: Director

Objective: Grant permission to a user (administrator).

Pre-conditions (s): - The system should be loaded

- The director should be logged in
Nominal scenario: 1. The director request the list of users.
2. The system load the list from the
databse.
3. The director selects a user.
4. The system load the list of
permissions from the database.
5. The director chooses a permission.
6. The system updates the user’s
permissions
Alternative scenario (No users in the 2.1 The system display error “no user”.

database)
Alternative scenario (Permission I.1 The system display error “permission

already granted) already granted”

I.2 The system returns to step (5) of
nominal scenario.
Post-conditions (s) - Permission granted.

Title Accept bank account creation

Actor: Head of financial services.

Objective: Accept customer’s bank account creation.

Pre-conditions (s): - The system should be loaded.

- The head of financial services should
be logged in.
Nominal scenario: 1. The head of financial services
demands for account creation request
list
2. The system displays the list from
database.
3. The head of financial services selects
a request.
4. The system displays the information
provided by the customer.
5. The head of financial services verifies
the customer’s information.
6. The head of financial services accepts
bank account creation
7. The system saves the bank account.
Alternative scenario (Request denied) 5.1 The head of financial services reject
customer’s request.
5.2 The system displays success message
(request rejected)
Post-conditions (s) - Bank account created

Title Transfer fund

Actor: Customer

Objective: Transfer fund from one account to another.

Pre-conditions (s): - The system should be loaded.

- The customer should be logged in.
Nominal scenario: 1. The customer request the fund transfer
form.
2. The system provides the transfer form.
3. The customer fills the submits the
form.
4. The system verifies the form enteries.
5. The system sends a request to the
database to provide the custom’s
account balance.
6. The system check the amount
validity.
7. The system performs the transfer.
Alternative scenario (Form invalid) 4.1 The system displays an error message
(the form should be filled)
4.2 The system returns to step (3) of the
nominal scenario.
Alternative scenario (Insuficient 6.1 The system displays an error message

amount) (account balance insufficient)

6.2 The system returns to step(3) of the
nominal scenario.
Post-conditions (s) - Fund transferred.

e. Use case <<pay a service>>

T ABLE 14:<< PAY A SERVICE TEXTUAL DESCRIPTION >>

Title Pay a service

Actor: Customer

Objective: Pay for services available and supported by CAMPOST

(bills, fees etc…)
Pre-conditions (s): - The system should be loaded.
- The customer should be logged in.
Nominal scenario: 1. The customer request for the list of services
2. The system loads the list.
3. The customer selects the desired service.
4. The system displays the payment form.
5. The customer fills and submits the form.
6. The system verifies the form enteries.
7. The system request the customer’s account balance
from the API.
8. The system checks the payment amount validity.
9. The system performs the payment.
Alternative scenario (Form 4.1 The system displays an error message (the form

invalid) should be filled)

4.2 The system returns to step (3) of the nominal
scenario.
Alternative scenario 6.3 The system displays an error message (account

(Insuficient amount) balance insufficient)

6.4 The system returns to step(3) of the nominal
scenario.
Post-conditions (s) - Service payed.

ii. Formalism
Partition 1 Partition 2 Partittion 3

Activi ty_1 Condition

Activity_2

Activi ty_4

Deci sion_1 Deci sion_2 Deci sion_3 Deci sion_4

Activi ty_3

Activi ty_5

Activity_6 Condition

F IGURE 17: ACTIVITY DIAGRAM FORMALISM

Element Description and Main properties Notation

Activities An activity is a round cornered rectangle

Activity_1
enclosing all actions control flows and other
elements that make up an activity.

Synchronization It is used to decompose the “fork” treatment or

bar to spread it when multiple treatments have
been done

Control flow It shows the flow of control from one action to

the next.

Initial node An initial node is a control node that splits a

flow into multiple concurrent flows.

Final node It denotes the end of a single control flow.

Decision and It is used either for decisions or merge.

Decision_1
merge nodes

Graphical representations of activities

Authentication (both by administrator and customer)

F IGURE 18: ACTIVITY DIAGRAM << AUTHENTICATE >>

F IGURE 19: ACTIVITY DIAGRAM << GRANT PERMISSION >>

F IGURE 20:ACTIVITY DIAGRAM <<ACCEPT BANK ACCOUNT CREATION REQUEST>>

b. Customer’s activity diagrams

F IGURE 21: ACTIVITY DIAGRAM<<TRANSFER FUND>

F IGURE 22: ACTIVITY DIAGRAM << PAY A SERVICE >>

ii. Formalism

<Texte par défaut>

CD: Formalism

Actors

4: Message_3

Object 1 Object 2
1: Message_1

Actor
2: Message_2
Object 3
Objects

5: Message_4

8: Message_6 Links
6: Message_5

Object 5 Object 4

Call to
self

F IGURE 23: COMMUNICATION DIAGRAM FORMALISM

Element Description and Main properties Notation

Call message A call message defines a particular

communication between lifelines of
interaction that represents an innovation of
target lifeline.

Dependency A dependency is a relationship that

2: dependency
signifies that a single or set if model elements
requires other model elements for their
specification.

Object An object represents an individual participant Object

in the interaction conversion

Generalization A generalization is a taxonomic relationship

between a more general classifier and a more
specific classifier

F IGURE 24: COMMUNICATION DIAGRAM <<AUTHENTICATE>>

F IGURE 25: COMMUNICATION DIAGRAM <<ACCEPT BANK ACCOUNT CREATION REQUUEST>>

F IGURE 26:COMMUNICATION DIAGRAM <<PAY A SERVICE>>

ii. Formalism

State machine Formalism

Transitional
Guard behavior
Trigger

Etat_1 request [request <= available] / pass Etat_2

F IGURE 27:STATE MACHINE DIAGRAM FORMALISM

Components of state machine diagram

T ABLE 17: COMPONENTS OF A STATE MACHINE DIAGRAM

Element Description and Main properties Notation

State
State A state represents situations during the life of
an object

Transition A solid arrow that represents the path between

different states of an object. A state can have
a transition that points back to itself.

Initial state A filled circle followed by an arrow

represents an object’s initial state.

Final state An arrow pointed to a filled circle nested

inside another circle represents an object’s
final state.

Join It is used to split transition or reduce two or

more transitions into one

F IGURE 28: STATE MACHINE DIAGRAM <<BANK ACCOUNT REQUEST>>

b. State machine diagram <<bank account>>

F IGURE 29:STATE MACHINE DIAGRAM <<BANK ACCOUNT>>

F IGURE 30: STATE MACHINE DIAGRAM << LOAN >>

CHAPTER 4 :
CONCEPTION
PHASE

Content:

Introduction

I. TECHNICAL BRANCH
1. GENERIC DESIGN
2. GENERIC CONCEPTION

II. IMPLEMENTATION BRANCH

1. PRELIMINARY CONCEPTION
2. DETAILED CONCEPTION

CONCLUSION

Head of digital services Management of digital services

- Management of postal demands.

Director Head of postal services
- Management of postal services.

Head of financial services - Management of credit requests.

- Management of financial operations.

- Management of users.
- Management of CAMPOST services.
- Management of postal offices.

- Consult CAMPOST services

Customer - Management of postal box
- Follow up of packages
- Order stamps
- Order school manuals
- Management of bank accounts
- Make credit/loan requests
- Payment of services
- Management of CAMO accounts
- Request for hosting
- Request for connectivity.

1. PRELIMINARY DESIGN
A. Interaction overview diagram
i. Definition
An interaction Overview Diagrams provide a high level of abstraction an interaction model.
It is a variant of the Activity Diagram where the nodes are the interactions or interaction
occurrences. The Interaction Overview Diagram focuses on the overview of the flow of control
of the interactions which can also show the flow of activity between diagrams. In other words,
you can link up the "real" diagrams and achieve high degree navigability between diagrams
inside an Interaction Overview Diagram.

ii. Formalism

F IGURE 31: INTERACTION OVERVIEW DIAGRAM FORMALISM

F IGURE 32: INTERACTION OVERVIEW DIAGRAM <<PAY A SERVICE>>

i. Definition

A Component diagram describes the organization and wiring of physical components in a

system. Physical components are elements such as executables, libraries, files, documents, etc.
which reside in a node. Component diagrams are used to visualize the organization and
relationships among components in a system. These diagrams are also used to make executable
systems.

ii. Formalism

Composant_1

Composant_5

Composant_2
Composant_3

Interface_1

Composant_4

F IGURE 33: COMPONENT DIAGRAM FORMLISM

Components of a component diagram

T ABLE 18:COMPONENTS OF A COMPONENT DIAGRAM

Element Description and Main properties Notation

Component A component is a logical unit block of the system,
a slightly higher abstraction than classes. It is
represented as a rectangle with a smaller rectangle
in the upper right corner with tabs in the upper
right corner with tabs or the word written above
the name of the component to help distinguish it
from classes.
Interface An interface (small circle or semi-circle on a stick)
describes a group of operations used (required) or 2: dependency

created (provided) by components. A full circle

represents an interface created or provided by the
component. A semi-circle represents a required
interface, like a person’s input.
Port Ports represented using a square along the edge of
Object
the system or a component. A port is often used to
help expose required and provided interfaces of a
components.

F IGURE 34: COMPONENT DIAGRAM OF THE SOLUTION

ii. Formalism

Noeud_1

InstanceComposant_1

Noeud_3

Noeud_2 InstanceComposant_1

InstanceComposant_1

F IGURE 35: D EPLOYMENT DIAGRAM FORMALISM

F IGURE 36: D EPLOYMENT DIAGRAM OF THE SOLUTION

Package is a namespace used to group together elements that are semantically related and
might change together. It is a general-purpose mechanism to organize elements into groups to
provide better structure for system model. Owned members of a package should all be package
able elements. If a package is removed from a model, so are all the elements owned by the
package. Package by itself is package able element, so any package could also be a member of
other packages.

ii. Formalism

<<import>>
Package_1 Package_2

<<access>>

<<import>>

Package_3 Package_4

F IGURE 37:P ACKAGE DIAGRAM FORMALISM

Components of package diagram

F IGURE 38: COMPONENTS OF A PACKAGE DIAGRAM

F IGURE 39: PACKAGE DIAGRAM OF THE SOLUTION

ii. Formalism

Sequence diagram

:object 1 :object 2

Actor

Message 1

Message 2

Message_5 Message_10

Message 4

F IGURE 40: SEQUENCE DIAGRAM FORMALISM

Components of sequence diagram

T ABLE 19: COMPONENTS OF A SEQUENCE DIAGRAM

Element Description and Main properties Notation

Life lines A lifeline represents an individual
participant in a sequence diagram. A lifeline
will usually have a rectangle containing its
object name as shown in the diagram below;

Asynchronous A message with a complete feedback

message

Synchronous Messages sent with no feedback

message

Self - message A self-message can represent a recursive

Message_4
call of an operation, or one method calling
another method belonging to the same
object.
Return message Return messages are results of asynchronous Message_2

messages
Object They send and receive messages
Objet_4

Fragment It is the general relationship type between

elements. This connector may include
named roles at each end, cardinality,
direction and attributes.

F IGURE 41: SEQUENCE DIAGRAM << AUTHENTICATE >>

F IGURE 42: SEQUENCE DIAGRAM << TRANSFER FUND >>

F IGURE 43: SEQUENCE DIAGRAM PAY A SERVICE

II . Formalism

F IGURE 44: TIMING DIAGRAM FORMALISM

C. Class Diagram
i. Definition

A class diagram shows the building block of any object-oriented system. Class diagrams
portrays a static view of the model, or part of the model, describing what attributes and behavior
it has rather than detailing the method for achieving operations. Class diagrams are most useful
in illustrating relationships between classes and interface, composition or usage and connections
respectively.
A class describes the responsibilities, behavior and the type of set of objects. The elements of
this set ate the instances of the class.
A class is a set of functions and date (attributes) that are linked together by semantic field.
Classes are used in object-oriented programming to model programs and to curt a complex risk
into several small simple jobs.

ii. 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)

F IGURE 46: CLASS DIAGRAM FORMALISM

Element Description and Main properties Notation

Aggregation If the parent of the aggregate is deleted,

0..1
usually, the children are not deleted

0..*
Composition If the parent of a composite aggregation is

0..1
deleted, usually all of its parts are deleted

0..*
with it.
Class A class is an element that defines the
attributes and behaviors that an object us able Classe_10

to generate. Classes may also have definitions

of constraints, tagged values and stereotypes
Nesting A nesting is a connector which shows that
source element is nested within the target
element.
Generalization A generalization is used to indicate
inheritance. It shows a parent class
generalizing a child class
Association It is the general relationship type between
elements. This connector may include named
0..1

roles at each end, cardinality, direction and

0..*

attributes.

F IGURE 47: CLASS DIAGRAM OF THE SYSTEM

An object diagram in UML is a diagram that shows a complete or partial view of the
structure of a modeled system at a specific time. It focuses on some particular set of objects
and attributes and the links between these instances. A correlated set of object diagrams
provides into how an arbitrary view of a system is expected to evolve over time.

ii. Formalism

F IGURE 48: OBJECT DIAGRAM FORMALISM

F IGURE 49:COMPONENTS OF OBJECT DIAGRAM

F IGURE 50: O BJECT DIAGRAM OF THE SYSTEM

CHAPTER 5 :
IMPLEMENTATION
PHASE

Content:

INTRODUCTION
I. THE DATABASE SCRIPT
II. THE ARCHITECTURE OF THE SOLUTION.
III. TECHNOLOGICAL CHOICE

CONCLUSION

Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering
at AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE,
Academic Year 2020 – 2021
107
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)
I. THE DATABASE SCRIPT
-- phpMyAdmin SQL Dump
-- version 5.0.2
-- https://www.phpmyadmin.net/
--
-- Hôte : 127.0.0.1:3306
-- Généré le : ven. 01 oct. 2021 à 15:14
-- Version du serveur : 5.7.31
-- Version de PHP : 7.3.21
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
START TRANSACTION;
SET time_zone = "+00:00";
--
-- Base de données : `cih`
--
-- --------------------------------------------------------
--
-- Structure de la table àccount_demand`
--
DROP TABLE IF EXISTS àccount_demand`;
CREATE TABLE IF NOT EXISTS àccount_demand` (
àccount_demand_id` int(11) NOT NULL,
àccount_type` varchar(255) DEFAULT NULL,
`date` datetime DEFAULT NULL,
ìd_card` varchar(255) DEFAULT NULL,
`photo` varchar(255) DEFAULT NULL,
`signature` varchar(255) DEFAULT NULL,
ùser_id` int(11) NOT NULL,
`customer_user_id` int(11) DEFAULT NULL,
PRIMARY KEY (àccount_demand_id`),
KEY `FK21yds34yhxq27skw20fmsh1wr` (`customer_user_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
-- --------------------------------------------------------
--
-- Structure de la table `bank_account`
--
DROP TABLE IF EXISTS `bank_account`;
CREATE TABLE IF NOT EXISTS `bank_account` (
àccount_number` int(11) NOT NULL,
àccount_balance` bigint(20) NOT NULL,
àccount_type` varchar(255) DEFAULT NULL,
`creation_date` datetime DEFAULT NULL,
òwner_id` int(11) NOT NULL,

Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering
at AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE,
Academic Year 2020 – 2021
107
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)
òwner_user_id` int(11) DEFAULT NULL,
PRIMARY KEY (àccount_number`),
KEY `FKjkvh1ineiw2e4njpilogkeq2u` (òwner_user_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
--
-- Structure de la table `campost_service`
--
DROP TABLE IF EXISTS `campost_service`;
CREATE TABLE IF NOT EXISTS `campost_service` (
`service_id` int(11) NOT NULL,
`description` varchar(255) DEFAULT NULL,
`name` varchar(255) NOT NULL,
PRIMARY KEY (`service_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
-- --------------------------------------------------------
--
-- Structure de la table `hibernate_sequence`
--
DROP TABLE IF EXISTS `hibernate_sequence`;
CREATE TABLE IF NOT EXISTS `hibernate_sequence` (
`next_val` bigint(20) DEFAULT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
--
-- Déchargement des données de la table `hibernate_sequence`
--
INSERT INTO `hibernate_sequence` (`next_val`) VALUES
(96);
-- --------------------------------------------------------
--
-- Structure de la table `loan`
--
DROP TABLE IF EXISTS `loan`;
CREATE TABLE IF NOT EXISTS `loan` (
`loan_id` int(11) NOT NULL,
àmount` int(11) NOT NULL,
`loan_date` datetime DEFAULT NULL,
`loaner_id` int(11) NOT NULL,
`reimbursed_amount` int(11) NOT NULL,
`reimbursement_method` varchar(255) DEFAULT NULL,
`return_date` datetime DEFAULT NULL,
`status` varchar(255) DEFAULT NULL,
`loaner_user_id` int(11) DEFAULT NULL,
PRIMARY KEY (`loan_id`),

Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering
at AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE,
Academic Year 2020 – 2021
107
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)
KEY
`FK7s9txs3vhfgnwcyaap2h985fo` (`loaner_user_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
--
-- Déchargement des données de la table `loan`
--
INSERT INTO `loan` (`loan_id`, àmount`, `loan_date`, `loaner_id`, `reimbursed_amount`,
`reimbursement_method`, `return_date`, `status`, `loaner_user_id`) VALUES
(84, 50000, '2021-09-24 02:03:35', 40, 17000, 'Monthly', '2021-10-10 01:00:00', 'not finished',
NULL);
-- --------------------------------------------------------
--
-- Structure de la table `loan_request`
--
DROP TABLE IF EXISTS `loan_request`;
CREATE TABLE IF NOT EXISTS `loan_request` (
`loanreq_id` int(11) NOT NULL,
àmount` int(11) NOT NULL,
`date` datetime DEFAULT NULL,
ìd_card` varchar(255) DEFAULT NULL,
`loaner_id` int(11) NOT NULL,
`photo` varchar(255) DEFAULT NULL,
`reimbursement_method` varchar(255) DEFAULT NULL,
`return_date` datetime DEFAULT NULL,
`signature` varchar(255) DEFAULT NULL,
PRIMARY KEY (`loanreq_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
--
-- Déchargement des données de la table `loan_request`
--
-- Structure de la table `notification`
--
DROP TABLE IF EXISTS `notification`;
CREATE TABLE IF NOT EXISTS `notification` (
`notification_id` int(11) NOT NULL,
`description` varchar(255) DEFAULT NULL,
òwner` int(11) NOT NULL,
`title` varchar(255) DEFAULT NULL,
`date` datetime DEFAULT NULL,
PRIMARY KEY (`notification_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
-- Structure de la table `postal_office`
--
DROP TABLE IF EXISTS `postal_office`;

Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering
at AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE,
Academic Year 2020 – 2021
107
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)
CREATE TABLE IF NOT EXISTS `postal_office` (
`po_id` int(11) NOT NULL,
`address` varchar(255) DEFAULT NULL,
`latitude` double NOT NULL,
`longitude` double NOT NULL,
`name` varchar(255) NOT NULL,
`telephone` int(11) NOT NULL,
`town` varchar(255) DEFAULT NULL,
PRIMARY KEY (`po_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
-- --------------------------------------------------------
--
-- Structure de la table `service`
--
DROP TABLE IF EXISTS `service`;
CREATE TABLE IF NOT EXISTS `service` (
`service_id` int(11) NOT NULL,
`description` varchar(255) DEFAULT NULL,
`name` varchar(255) NOT NULL,
PRIMARY KEY (`service_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
--
-- Déchargement des données de la table `service`
--
INSERT INTO `service` (`service_id`, `description`, `name`) VALUES
(1, 'camo', 'porte monnea virtuelle');
-- --------------------------------------------------------
--
-- Structure de la table `services`
--
DROP TABLE IF EXISTS `services`;
CREATE TABLE IF NOT EXISTS `services` (
`po_id` int(11) NOT NULL,
`service_id` int(11) NOT NULL,
PRIMARY KEY (`po_id`,`service_id`),
KEY `FK2ur0vq337ihvegs1k9s6wt7uh` (`service_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
-- --------------------------------------------------------
--
-- Structure de la table `services_offered`
--
DROP TABLE IF EXISTS `services_offered`;
CREATE TABLE IF NOT EXISTS `services_offered` (
`po_id` int(11) NOT NULL,

Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering
at AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE,
Academic Year 2020 – 2021
107
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)
`service_id` int(11) NOT NULL,
PRIMARY KEY (`po_id`,`service_id`),
KEY `FKjkf2k587ifvny41o8q1aotk8f` (`service_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
-- --------------------------------------------------------
--
-- Structure de la table `transaction`
--
DROP TABLE IF EXISTS `transaction`;
CREATE TABLE IF NOT EXISTS `transaction` (
`transaction_id` int(11) NOT NULL,
`transaction_account` varchar(255) DEFAULT NULL,
`transaction_amount` int(11) NOT NULL,
`transaction_date` datetime DEFAULT NULL,
`transaction_receiver_id` int(11) NOT NULL,
`transaction_receiver_name` varchar(255) DEFAULT NULL,
`transaction_receiver_number` int(11) NOT NULL,
`transaction_sender_id` int(11) NOT NULL,
`transaction_sender_name` varchar(255) DEFAULT NULL,
`transaction_type` varchar(255) DEFAULT NULL,
PRIMARY KEY (`transaction_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
--
-- Déchargement des données de la table `transaction`
--
-- --------------------------------------------------------
--
-- Structure de la table ùser`
--
DROP TABLE IF EXISTS ùser`;
CREATE TABLE IF NOT EXISTS ùser` (
`dtype` varchar(31) NOT NULL,
ùser_id` int(11) NOT NULL,
àddress` varchar(255) DEFAULT NULL,
èmail` varchar(255) DEFAULT NULL,
ùser_name` varchar(255) DEFAULT NULL,
`telephone` int(11) DEFAULT NULL,
`town` varchar(255) DEFAULT NULL,
`password` varchar(255) DEFAULT NULL,
`matricule` varchar(255) DEFAULT NULL,
`role` varchar(255) DEFAULT NULL,
PRIMARY KEY (ùser_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

 PHYSICAL ARCHITECTURE,

 LOGICAL ARCHITECTURE

1. 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.

Within the scope of our project, we made use of a 3-tier architecture which is popularly
known as the three layers architecture.

This architecture separates its tiers from each other based on the complexity of the user and
how they manipulated data in the database. It is important to note that with the 3-tier
architecture, only neighboring layers can communicate. Each layer has a well-defined
communication interface and the evolution of a layer is independent of the other.

The three-tier physical architecture

a. The user (presentation) tier:

At this layer, multiple views of database can be provided by the application. All views are
generated by applications that reside in the application tier. End-users operates on this tier and
they know nothing about the existence of the database beyond this layer. In other words, it acts
as an assembly of services and applications offered by the lower layer. This layer relays the
queries of the users and in return, present the result from the database.

At this tier resides the application server and the program that access the database. For a user,
this application tier presents and abstract view of the database. End-users are unaware of any
existence of the database beyond the applications.

c. The database (data) tier:

At this tier, the database resides along with its query processing languages. We also have the
relations that defines the data and their constraints at this level. It manages the access to the data
of the system.

F IGURE 51: 3 TIER PHYSICAL ACHITECTURE

2. Logical Architecture
Model view controller or MVC as it is popularly called, is a software design pattern for
developing web application. A Model View Controller pattern is made up of the following three
parts.

 Model: The lowest level of the pattern which is responsible for maintaining data.
 View: This is responsible for displaying all or a portion of the data to the user.
 Controller: Software code that controls the interactions between the model and the view.

MVC is popular as it isolates the application logic from the user interface layer and supports
separation of concerns. Here the controller receives all requests for the application and then
works with the model to prepare nay data needed by the view. The view then uses the data
prepared by the controller to generate a final presentable response. The MVC abstraction can be
graphically represented as follows.

F IGURE 52: MVC LOGICAL ARCHITECTURE

The front-end part of an application is the part interacting directly with the users, from
where requests are being send and the request results are being displayed to the user. This
part is mainly hosted or served by the application server.

CAMPOST-IN-HAND was developed using two main front-end technologies or

framework, depending on the device loading the application.

a. Web front-end:

The web front end was developed by using the framework ANGULAR, which is one of
the most commonly used web frameworks nowadays.

F IGURE 53: JS, A NGULAR AND TS LOGO

ANGULAR is a TypeScript/JavaScript framework developed by google mainly made to

develop web applications having the following advantages;

 Effective Cross-Platform Development.

 High Quality of the Application.
 Improved Speed and Performance.
 Faster Development Process.
 Readable and Testable Code.

The current mobile world is dominated by 2 different types of operating systems

(Android and IOS) running on mobile devices. Therefore, to develop a solution, the developer
should develop both the android and IOS solution. This become so tiring for the developers.

There are some frameworks nowadays permitting developers to write one code for the to
operating system.

F IGURE 54: IONIC LOGO

The IONIC framework which is a TypeScript/JavaScript framework was chosen to

develop the mobile app with, due to its numerous advantages which are as follows.

 Cross platform app development.

 User friendly interfaces.
 Good app performances.
 Easy to adopt.
ii. Back-End:

The backend part of an application is mainly responsible for the application logic. This par
receives the request from the fronts end, treats them and directs it to the database for immediate
results.

The chosen framework was Spring Boot MVC. is a Model View, and Controller based web
framework widely used to develop web applications? Spring Boot is built on top of the

F IGURE 55:SPRING BOOT LOGO

This framwork has several advantages such as;

 Provides middleware-level service.
 Supports various configuration methods;
 Allows you to freely link modules and easily test them;
 Fast and efficient.

B. Choice of tools used

i. Software resources;
T ABLE 21: SOFTWARE TOOLS

Software Logo Roles

Windows 10 OS Manage the computer’s resources

Browser Mainly used for the website rendering

and researches.

Visual Paradigm Tool used for modeling the analyzed

diagrams.

MS Word Software for the treatment of text,

used for the drafting of the final
report.
Spring tool suits IDE for the backend development

Visual Studio Code IDE for the frontend development

WAMPP Package containing some servers

such as Apache and tomcat necessary
for development and testing
Node Js Local server, for the local hosting of
the web and mobile app

Postman A powerful tool for sending HTTP

and or restful request towards and
API
MySQL Mainly used to administer databases.
workbench

ii. Hardware resources

 Operating system windows 10 64-bit
 Memory 6GB RAM
 Hard Disk 500GB
 Processor: Intel(R) Core(TM) i5 CPU 2.27 GHz

CHAPTER 6 :
USER GUIDE

Content:

INTRODUCTION
I. DEPLOYMENT OF THE APPLICATION
II. SHOWCASE

CONCLUSION

F IGURE 56: ANGULAR FIREBASE DEPLOYMENT

Once the angular app is ready the following steps are followed on order to deploy the application
on firebase.
1. Create firebase account and create a project.

F IGURE 57: FIREBASE WELCOME PAGE

We enter project name, accept terms and condition then click on create project.

F IGURE 58:FIREBASE ADD PROJECT

After the ap is created on firebase, the next steps are to setup firebase deployment environment
in our system.
2. Install the firebase tools using firebase CLI in the project with the following command;
npm install -g firebase-tools
3. Login and initialize firebase project using firebase CLI with the following command
firebase login

F IGURE 59: FIREBASE LOGIN SUCCESS

Initialize the firebase project by running the following command

firebase init

After initializing the firebase project, we will see the following properties in firebase CLI

F IGURE 60: FIREBASE CLI CONFIGS

Here was the final step to deploy our web platform on firebase hosting.

Mobile application (ANDROID and IOS)

Our mobile applications that is android and ios application will be deployed on google play store
and app store respectively.

F IGURE 61: D EPLOYING IOS AND ADNROID APPLICATION

For the android application, the following commands and configurations will be used.
 In the config.xml file the following changes are made
 The app name:

<name>CAMPOST IN HAND</name>

 The id attribute which comes with the widget tag (this is very important)

 Build and sign the android release app

The following commands are used to build and sign the app for release

ionic cordova platform add android

keytool -genkey -v -keystore my-key.keystore -alias alias_name -keyalg RSA -keysize
2048 -validity 10000

We generate the release build of our android application

$ ionic cordova build --release android

To sign the unsigned.apk file i.e to create the signed release we build run the jarsigner command
tool which is also the part of Android APK.

$ jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore my-key.keystore

android-release-unsigned.apk alias_name

At last, we used the zipalign tool to optimize the APK. The tool can be found at the

$ zipalign -v 4 android-release-unsigned.apk MyTask.apk

 Submitting the app to google play store

Now that this release APK was ready for the Google Play Store, we made sure we have
Play Store listing to upload our APK. Before we started, we visited the Google Play Store
Developer Console and created a developer account (it cost nearly $25). Once we had enrolled
with a developer account, we went ahead to “Publish an Android App on Google Play” and
followed the on-screen instructions.

Running the following command will create a keystore then deploy the spring boot
services.

java-Dspring.profiles.active=productionDkeystore.file=file:///$PWD/src/main/resources/keystore.p12 -jar
target/oauth-1.0.0.BUILD-SNAPSHOT.jar

B. Local deployment
A. Front-end application

The requirements for the local hosting or deployment of our front-end applications (angular and
ionic application) are as follows.

1. A local application server (Node Js Server)

The installation process is as follows;

F IGURE 62: DOWNLOAD NODE JS

After downloading node js, we click on the installation executable file then follow the step as
shown bellow.

F IGURE 64: INSTALL NODE JS STEP 1 F IGURE 63: INSTALL NODE JS STEP 2

F IGURE 69: INSTALLING WAMP SERVER STEP 1 F IGURE 70: INSTALLING WAMP SERVER STEP 2

F IGURE 71: INSTALLING WAMP SERVER STEP 3 F IGURE 72: INSTALLING WAMP SERVER STEP 4
Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering
at AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE,
Academic Year 2020 – 2021
107
DEVELOPMENT OF A WEB AND MOBILE
APPLICATION WHICH FACILITATES ACCESS TO
CAMPOST SERVICES. Case of: Financial, digital and
postal services (CAMPOST-IN-HAND)

II. SHOWCASE
As stated earlier and in our theme, we developed a web and mobile application (android and
IOS). We used an advantageous framework which gave us the opportunity to develop a cross
platform application that is having one source code for both the android and the web version.
CAMPOST IN HAND provides both the user and the administration portal from where all
the user requests and operations can be managed. The showcase will present both the user portal
(web and mobile application) and the administration portal (web application).
A. User portal
1. Web interfaces
a. Landing page.
The landing page of CAMPOST IN HAND is made up of 2 principal sections, we have the
welcome section and the section presenting the main CAMPOST services.

F IGURE 69: CAMPOST IN HAND LANDING PAGE

F IGURE 70: CAMPOST IN HAND - CAMPOST SERVICES

F IGURE 71: CAMPOST IN HAND - FINANCIAL SERVICES

b. Search page

By typing a service, the list of postal offices offering the services is listed to the user.

F IGURE 72: CAMPOST IN HAND - SEARCH PAGE

c. Geolocation page

The customer can then decide to geolocate all the post offices near him by clicking on the button
‘Postal offices near me’. Then the following page will be displayed he can navigate to the post
office he wants.

F IGURE 73: CAMPOST IN HAND - MAP

From the above map, the customer can have a real view of the road map to the post office he
wants. The system redirects him automaticaly toward the post office.

F IGURE 74 : CAMPOST IN HAND - MAP ROAD VIEW

d. Register page

F IGURE 75 : CAMPOST IN HAND - REGISTER PAGE

e. Login page
The user gets authenticated from here to launch his session.

F IGURE 76 : CAMPOST IN HAND - LOGIN PAGE

F IGURE 77 : CAMPOST IN HAND - USER DASHBOARD

g. Exchange page
A page from which a customer can transfer fund from any of his bank accounts (current
account, saving account or CAMPOST Money account).

F IGURE 78 : CAMPOST IN HAND - EXCHANGE FUND

F IGURE 79 : CAMPOST IN HAND - USER TRANSACTIONS

h. Accounts page
From this page a customer can manage all his bank accounts, and also have a list his
transactions.

F IGURE 80 : CAMPOST IN HAND - USER ACCOUNTS PAGE

I. Loans page
The main page from where a customer can manage his loans and or request for another loan.

F IGURE 81 : CAMPOST IN HAND - LOANS

j. Pay merchant service

Payment of all kinds of services, but the post condition is the receiver must have a current
account at CAMPOST

F IGURE 82 : CAMPOST IN HAND - PAY A SERVICE ( RAPID PAYMENT )

For the user’s web portal, these were some of the major pages, all the pages could not be
stated.

F IGURE 83 ; CAMPOST - IN HAND - PRICE SIMULATOR

l. Notification page
A CAMPOST IN HAND user gets a notification on each and every transaction.

F IGURE 84 : CAMPOST IN HAND - NOTIFICATION PAGE

2. Mobile interfaces
The mobile version was done to enhance user usability since the majority of
Cameroonians are much more having mobile devices. The mobile version contains the main
functionalities concerning financial transactions. Some of the mobile interfaces are;

F IGURE 85 : MOBILE - LOGIN F IGURE 86 : MOBILE - REGISTER F IGURE 87 : MOBILE - MENU

F IGURE 88 : MOBILE - DASHBOARD F IGURE 89 : MOBILE - EXCHANGE F IGURE 90 : MOBILE - PAY SERVICE

F IGURE 91 : MOBILE - BANK ACCOUNTS F IGURE 92 : MOBILE - TRANSACTIONS

F IGURE 93 : MOBILE – SETTINGS

The main reason for the existence of this admin section is the fact that a good and efficient
system must be administered.

a. Dashboard page

F IGURE 94 : ADMIN - DASHBOARD

F IGURE 95 : ADMIN CUSTOMERS TRANSACTIONS

b. CAMPOST services page

The main page used to manage CAMPOST services

F IGURE 96 : ADMIN - CAMPOST SERVICES

c. Postal offices
The management of CAMPOST post offices is done here by the administrator in charge of it

F IGURE 97 : ADMIN - MANAGE OFFICES

To add a new post office, clicking on the button “add an office”, displays the following interface

F IGURE 98 : ADMIN - ADD POSTAL OFFICE

d. Bank Accounts page

From this page, the administrator can manage the requests for a bank account and also
manage all the bank accounts already created

F IGURE 99 : ADMIN - MANAGE BANK ACCOUNT

e. Loans page

One of the most important page from where the head of financial services will be able to
mange the loan request and also the loans already granted.

F IGURE 100 : ADMIN – LOAN

Once a loan request is received by the administrator, he can get more details on the loan
by clicking the ‘’details’’ button on a loan. While seeing the details, he can decide to grant de

F IGURE 101 : ADMIN - LOAN DETAIL

GENERAL
CONCLUSION

Coming to an end of this project, which also marks and end to my internship, I can
conclude that this internship was very beneficial in the sense that it was of great importance for
my professional and academic career, a huge knowledge was acquired during this period and a
lot of researches made in order to overcome the great challenge.

The help I had form my academic and professional supervisor, permitted me to study the
problem that was posed, propose a solution adapted to the problem in the form of a project with
theme;” Development of platform which facilitates access to CAMPOST services. Case of;
financial, digital and postal services.”. Using UML and the numerous technologies mentioned,
I was able to design and implement a web and mobile platform that brings CAMPOST customers
closer to CAMPOST services and also helps CAMPOST administrators in their day-to-day
administrations. For the better optimization of the solution a technology was used which
permitted to develop a restfull API that as then consumed and exploited by the front-end.

Finally, a user guide was made permitting the exploitation of the solution put in place.
However, the time dedicated for the put in place of the solution was not sufficient to produce a
good solution respecting the standard of such a company (CAMPOST). Nevertheless, some
perspectives are to be implemented to make the solution useable and optimal. The internship
offered a real opportunity to truly integrate the professional milieu and acquire knowledge.

ANNEXE

BIBLIOGRAPHY

 Mr. JIONGANG Thibaut UML course AICS Cameroon 2021-2020.

 Russ Miles and Kim Hamilton, A Pragmatic Introduction to UML, O’Reilly Media, Inc.
April 2006, 288 pages;

 Mr. NJOMO Yannick OOP course (JAVA) AICS Cameroon 2021-2020.

 Spring Boot tutorials by AMIGOS Code Youtube 2020.

 Jon DUCKETT, HTML & CSS Design and build Websites, JOHN WILEY & SONS INC.
2011, 514 pages;

 Angular Spring Boot full stack course UDEMY 2021.

WEBOGRAPHY

 https://medium.com/nerd-for-tech/building-a-simple-restful-api-with-spring-boot-
2351687ecab0, visited on th learning how to build a rest api using spring boot MVC
 https://firebase.google.com/products/hosting?
gclid=CjwKCAjw7rWKBhAtEiwAJ3CWLL8PCvJWOb7bf6B22RP13v9XFtmOdYaY2
1R21JiTQDtttAhGHpm3vRoCO0EQAvD_BwE&gclsrc=aw.ds, documentation on web
hosting using Firebase Hosting
 https://getbootstrap.com/docs/4.1/getting-started/introduction/, Bootstrap documentation.

 https://start.spring.io: (Tuesday 14 July 2020 at 9:48 AM) We obtain the different

spring dependency to develop the spring boot application.
 http://spring.io: (Tuesday 14 July 2020 at 1:23 PM)

 https://spring.ioquickstart: (Tuesday 14 July 2020 at 9:48 AM)

 https://spring.ioguidessrest−service: (Thursday 16 July 2020 at 10:03 PM)

 https://spring.ioguides/saccessing−data−mysql: (Saturday 5 September 2021 at 11:31

PM)

 https://spring.ioguides/saccessing−data−rest: (Saturday 5 September 2021 at 11:42 PM)

 https://spring.ioguides/securing−web: (Thursday 24 September 2021 at 2:42 PM)

 https://spring.ioguides/rest−service−cors: (Wednesday 09 September 2021 at 2:42 PM)

 https://maven.apache.org/download.cgi: (Tuesday 14 July 2021 at 11:22 PM)

 https://spring.ioguides: (Tuesday 14 July 2021 at 10:42 PM)

 https://www.postman.com: (Monday 7 September 2021 at 9:42 PM) We obtain the
collaborating platform for API development testing.

CONTENT

DEDICATION................................................................................................................................i

ACKNOWLEDGEMENTS..........................................................................................................ii

SUMMARY...................................................................................................................................iii

LIST OF FIGURES......................................................................................................................iv

LIST OF TABLES......................................................................................................................viii

GENERAL INTRODUCTION.....................................................................................................1

CHAPTER 1 : INSERTION PHASE...........................................................................................2

I. WELCOME AND INTEGRATION....................................................................................5

II. GENERAL PRESENTATION OF CAMPOST...................................................................5

III. ORGANISATION OF CAMPOST......................................................................................8

CHAPTER 2 : SPECIFICATION DOCUMENT.....................................................................12

I. CONTEXT AND PROBLEM DEFINITION....................................................................15

II. OBJECTIVES.....................................................................................................................16

III. EXPRESSION OF NEEDS................................................................................................17

IV. ESTIMATED COST OF THE PROJECT..........................................................................21

V. LIST OF PARTICIPANTS.................................................................................................23

VI. PROJECT PLANNING......................................................................................................24

VII. PROJECT CONSTRAINTS...........................................................................................26

VIII. DELIVERABLES...........................................................................................................26

CHAPTER 3 : ANALYSIS PHASE...........................................................................................28

II. PROBLEMATIC................................................................................................................37

III. PROPOSED SOLUTIONS.................................................................................................39

IV. METHODOLOGY.............................................................................................................42

V. DETAIL ANALYSIS OF THE SYSTEM.........................................................................48

CHAPTER 4 : CONCEPTION PHASE....................................................................................83

I. TECHNICAL BRANCH....................................................................................................86

II. IMPLEMENTATION BRANCH.......................................................................................88

CHAPTER 5 : IMPLEMENTATION PHASE......................................................................112

I. THE DATABASE SCRIPT..............................................................................................114

II. THE ARCHITECTURE OF THE SOLUTION...............................................................119

III. TECHNOLOGICAL CHOICE.........................................................................................122

CHAPTER 6 : USER GUIDE...................................................................................................127

I. DEPLOYMENT OF THE APPLICATION.....................................................................130

II. SHOWCASE....................................................................................................................138

GENERAL CONCLUSION.....................................................................................................153

ANNEXE....................................................................................................................................153

BIBLIOGRAPHY......................................................................................................................153

WEBOGRAPHY........................................................................................................................153

CONTENT..................................................................................................................................153

Written by: KAMGA TOKAM ANDRE JAURES, 2nd Year Student, Software Engineering
at AICS Cameroon PAUL BIYA TECHNOLOGICAL CENTER OF EXCELLENCE,
Academic Year 2020 – 2021
107

Government College of Engineering, Amravati: A Project Report On
No ratings yet
Government College of Engineering, Amravati: A Project Report On
33 pages
DBMS
50% (2)
DBMS
67 pages
University of South Asia: Department of Computer Science
No ratings yet
University of South Asia: Department of Computer Science
46 pages
Inflow User Guide
No ratings yet
Inflow User Guide
180 pages
Travel N Tour Project Report
100% (1)
Travel N Tour Project Report
87 pages
Todo1 PDF
No ratings yet
Todo1 PDF
55 pages
E Banking
100% (3)
E Banking
33 pages
Oracle EPMA 11.1.2.4 Slient Installation
100% (1)
Oracle EPMA 11.1.2.4 Slient Installation
42 pages
EndOfStudies Report
No ratings yet
EndOfStudies Report
83 pages
Capstone Project 1 Part 2
No ratings yet
Capstone Project 1 Part 2
24 pages
Back EndPlan
No ratings yet
Back EndPlan
14 pages
Rapport de Stage Plateforme de Signature Electronique en Anglais
No ratings yet
Rapport de Stage Plateforme de Signature Electronique en Anglais
97 pages
Final Report Internship Summer 2021 Khadija Rejjaoui 1830131
No ratings yet
Final Report Internship Summer 2021 Khadija Rejjaoui 1830131
69 pages
WOW Report2016
No ratings yet
WOW Report2016
95 pages
Rapport Karim
No ratings yet
Rapport Karim
80 pages
Output 2
No ratings yet
Output 2
67 pages
Tawseela App Documantation
No ratings yet
Tawseela App Documantation
59 pages
Group1 Final SRS Yash Surma.1
No ratings yet
Group1 Final SRS Yash Surma.1
45 pages
American International University-Bangladesh (AIUB)
No ratings yet
American International University-Bangladesh (AIUB)
14 pages
Full Stack Web Development
No ratings yet
Full Stack Web Development
43 pages
City Transport Project Report
No ratings yet
City Transport Project Report
45 pages
Template Rapport ISTIC PFE
No ratings yet
Template Rapport ISTIC PFE
57 pages
Group1 SRS Yash
No ratings yet
Group1 SRS Yash
33 pages
Summer Internship Training Report
No ratings yet
Summer Internship Training Report
43 pages
Group1 SRS (Vivek)
No ratings yet
Group1 SRS (Vivek)
35 pages
TO DO List APP Final
No ratings yet
TO DO List APP Final
34 pages
Repay - Revamping The Reimbursement Process
No ratings yet
Repay - Revamping The Reimbursement Process
66 pages
Hamro Pasal
No ratings yet
Hamro Pasal
33 pages
Bus Ticket System
No ratings yet
Bus Ticket System
15 pages
LN Synopsis
No ratings yet
LN Synopsis
24 pages
Tour & Travel Management System
No ratings yet
Tour & Travel Management System
8 pages
10th PR
No ratings yet
10th PR
17 pages
Synopsis With Requirement
No ratings yet
Synopsis With Requirement
15 pages
Presentation 1
No ratings yet
Presentation 1
18 pages
1.vku - Ks.05-Exercise 1
No ratings yet
1.vku - Ks.05-Exercise 1
5 pages
Final Project Report: Location and State Sharing
No ratings yet
Final Project Report: Location and State Sharing
26 pages
Research Paper On Cloud Computing: June 2021
No ratings yet
Research Paper On Cloud Computing: June 2021
7 pages
Answer Script Template
No ratings yet
Answer Script Template
13 pages
Food Wateage Controll App Chapter 1
No ratings yet
Food Wateage Controll App Chapter 1
12 pages
Leadership Assignment
No ratings yet
Leadership Assignment
13 pages
Individial Proposal Sample #1
No ratings yet
Individial Proposal Sample #1
10 pages
MIS Assignment Question - Revised
No ratings yet
MIS Assignment Question - Revised
3 pages
CW Comp1786 CW1 22-23
No ratings yet
CW Comp1786 CW1 22-23
10 pages
CW Comp1786 CW1 22-23
No ratings yet
CW Comp1786 CW1 22-23
10 pages
Proposal For Turo App Clone
No ratings yet
Proposal For Turo App Clone
7 pages
SRS TMS
No ratings yet
SRS TMS
7 pages
LE00002351 - Proposal Document - V1.0 (1) .Docx - 0
No ratings yet
LE00002351 - Proposal Document - V1.0 (1) .Docx - 0
21 pages
Companyprofile
No ratings yet
Companyprofile
9 pages
Advance Engineering) HoangDuyThien
No ratings yet
Advance Engineering) HoangDuyThien
7 pages
Assignment Project Management
No ratings yet
Assignment Project Management
15 pages
Visual Studio Tips
No ratings yet
Visual Studio Tips
11 pages
IA Cloud Based Web Applications (50%) - Mobile Development (40%) - Algorithms and Constructs (35%)
No ratings yet
IA Cloud Based Web Applications (50%) - Mobile Development (40%) - Algorithms and Constructs (35%)
6 pages
Final Year Project (The Auction)
No ratings yet
Final Year Project (The Auction)
8 pages
PROP - Project Plan v0.2 1
No ratings yet
PROP - Project Plan v0.2 1
11 pages
Main CV Simple
No ratings yet
Main CV Simple
7 pages
Final Report Cu Mart 1
No ratings yet
Final Report Cu Mart 1
7 pages
Asif Shaikh
No ratings yet
Asif Shaikh
7 pages
Shaman Resume
No ratings yet
Shaman Resume
5 pages
PremKumar 3383665 - 01 05 - 1
No ratings yet
PremKumar 3383665 - 01 05 - 1
4 pages
BILL MANAGEMENT SYSTEM WITH TITLE Budget Planner Abstract
No ratings yet
BILL MANAGEMENT SYSTEM WITH TITLE Budget Planner Abstract
4 pages
Project Charter Template: Purpose of The Document
No ratings yet
Project Charter Template: Purpose of The Document
4 pages
Azmat Ali - CV
No ratings yet
Azmat Ali - CV
3 pages
Screening Test - Interview Questions
No ratings yet
Screening Test - Interview Questions
3 pages
Project Topics
No ratings yet
Project Topics
3 pages
Grant Dawson
No ratings yet
Grant Dawson
2 pages
Data Mining and Warehousing
No ratings yet
Data Mining and Warehousing
18 pages
LAB03-Creating An ETL Solution With SSIS
No ratings yet
LAB03-Creating An ETL Solution With SSIS
9 pages
Deepak Cs Project
No ratings yet
Deepak Cs Project
25 pages
RDBMS Practical File
No ratings yet
RDBMS Practical File
13 pages
BBA (B&amp I) 2nd Semester Regular &amp Reappear Result 2005 To 2009 Batch
No ratings yet
BBA (B&amp I) 2nd Semester Regular &amp Reappear Result 2005 To 2009 Batch
139 pages
Oracle Instance Architecture
No ratings yet
Oracle Instance Architecture
28 pages
Lab Mnanual Web Tech (KCS-652)
No ratings yet
Lab Mnanual Web Tech (KCS-652)
52 pages
Lesson 2.2 Types of Data Models
No ratings yet
Lesson 2.2 Types of Data Models
10 pages
Axxerion Workflow
No ratings yet
Axxerion Workflow
13 pages
Archit Trivedi
No ratings yet
Archit Trivedi
2 pages
Development of Smartphone Based Student Attendance System
No ratings yet
Development of Smartphone Based Student Attendance System
5 pages
Metallic Technical Overview
No ratings yet
Metallic Technical Overview
15 pages
Employee Expenses Management System: Geddada Suresh A.N.Ramamani
No ratings yet
Employee Expenses Management System: Geddada Suresh A.N.Ramamani
5 pages
Srssds
No ratings yet
Srssds
43 pages
CV
No ratings yet
CV
2 pages
Implementation Guide For Commerce Data Exchange - AX 2012
No ratings yet
Implementation Guide For Commerce Data Exchange - AX 2012
75 pages
Hangfire
No ratings yet
Hangfire
112 pages
ADBMS
No ratings yet
ADBMS
3 pages
Accuweather - Srs
No ratings yet
Accuweather - Srs
60 pages
FP - Spec - 01 - Hevy Julia Umbara - Developing Standard Geothermal Data Model For Professional Geotherma
No ratings yet
FP - Spec - 01 - Hevy Julia Umbara - Developing Standard Geothermal Data Model For Professional Geotherma
4 pages
Charan Reddy Java Backend Developer
No ratings yet
Charan Reddy Java Backend Developer
4 pages
Difference Between File System and DBMS
No ratings yet
Difference Between File System and DBMS
3 pages
Cds Deploymnet Steps
No ratings yet
Cds Deploymnet Steps
18 pages
MONETIZE CLOUD & AI: From technology innovation to business excellence
From Everand
MONETIZE CLOUD & AI: From technology innovation to business excellence
Chu Wenchang
No ratings yet
Digital Twins: How Engineers Can Adopt Them To Enhance Performances
From Everand
Digital Twins: How Engineers Can Adopt Them To Enhance Performances
Isrin Ismail
No ratings yet