0% found this document useful (0 votes)
41 views16 pages

Geolocation App for Housing in Cameroon

This document presents a specifications sheet for a project to develop a housing geolocation application in Cameroon. It describes the project context, the needs and expected functionalities, the stakeholders, the scope, and the deliverables.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
41 views16 pages

Geolocation App for Housing in Cameroon

This document presents a specifications sheet for a project to develop a housing geolocation application in Cameroon. It describes the project context, the needs and expected functionalities, the stakeholders, the scope, and the deliverables.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Specifications

Theme: Geolocation of housing locations

Written by: TCHINGUE MAKAMTE PATRICIA KEVINE

Academic Year: 2021/2022

1
I. Project presentation

The current project titled Geolocation of Housing Points in Cameroonian Territory is being carried out as part of a project to
defense in view of obtaining the Higher Technician Certificate (BTS).
Indeed, finding housing in a city in Cameroon remains a challenge today; which is why we are proposing ourselves.
to solve this problem by implementing a geolocation application for housing points.

II. Problematic

Case study

We will study the methods used by the homeless and property owners to respectively find housing and a tenant.
but clearly to bring out the shortcomings.
The homeless, in order to find housing, are faced with the obligation to:
publish housing search notices via their social media accounts;
consult the newspapers and various advertisements;
inquire from acquaintances.
The owners, for their part:
publish tenant search notices via their accounts on social media;
-inserts advertisements in newspapers;
-formulate written requests on signs in front of their houses.
2
This tedious process keeps the real estate sector in Cameroon at an embryonic stage, hence the need to bring about a real change to the system.
in place.
2. Case critique

We will identify the main weaknesses of this system and the difficulties faced by the different stakeholders.
Housing owners have no means of tracking their properties, making it difficult for a homeless person to find points of
housing. While the offer is available.
Housing availability announcements are not sufficiently disseminated and therefore do not reach the homeless directly.
The distance between the owner and the tenant creates a lack of communication between the parties, leading to a lack of information.
Once installed, tenants tend to arrange the premises as they see fit, especially in terms of layout, which leads to
conflicts that sometimes lead to legal proceedings.

III. Interest of the project

The purpose of this project is to address the shortcomings mentioned above. We therefore propose the solution that seemed most suitable to us.
We are going to develop a geolocation application for housing locations, which will allow an owner to:
easily find a tenant by registering your property(ies) on the platform;
post a notice when one of its properties is available and ready to be occupied;
to record all reservations and visit dates of his accommodation made through the application by a client;
gather all information related to a tenant;
And for a homeless person:
view the various listings made by owners;
discover the list of accommodations already registered on the platform;
-access the necessary information (for rent payments by housing) and the different contacts to reach in case of issues with arrangements or
technique.
3
IV. The expected needs or features

1. Functional requirements

The business needs to be covered by our application are:


Locate housing: allow a user to find a housing point in a city in Cameroon;
Create housing: give a property owner the opportunity to register their dwelling(s);
Accommodation booking: the owner may validate a reservation made by a user following an advertisement;
Provide users with availability announcements and a list of registered accommodations;
Record the information related to tenants and landlords;
Provide information regarding rent payment and contact details for technicians to reach in case of problems or breakdowns.
2. Non-functional requirements

These present the internal requirements of the system; hidden from users:
Ergonomic requirements:
A user-friendly, readable, and easy-to-use interface;
A very short response time.
Security:
Traceability of transactions and executed operations;
Authentication: to manage access between users.

V. Target population

These are individuals or legal entities who will be using the application, also referred to as actors.
Administrator:
4
Notify the users;
Manage the accounts.
Property owner:
-Post announcements for housing availability;
create their assets with all relevant information;
consult the information left by a tenant;
validate a reservation or a request for a site visit.
Homeless:
consult the availability announcements as well as the list of accommodations;
make a reservation or request to visit the habitat;
Tenant :
Consult the information left by an owner (information on payment of rent fees and technician to contact in case of issues).

VI. Project Scope

Our project is limited to the establishment of a web application for geolocation of housing points in Cameroon and its deployment.
from the obtained solution.

VII. Definition of project stakeholders

Names Roles Description of Functions

5
role and level
of intervention
[Link] Trainer Supervise Teacher
I academic the evolution of permanent to
project the IUES/INSAM
[Link] Trainer Supervise Responsible
professional the evolution of technique at
project FM
Ms. Analyst Analyze student at
TCHINGUE programmer organize and the IUES/INSAM
KEVINE execute it
project

VIII. Means of communication

In order to achieve a satisfactory result, we had to seek the help of people with experience and knowledge in the field.
This is how the work was able to be done, as presented in the table below:

Phases People Means of

6
resources communications
Analyze and Analyst Meetings and
specification programmer group
related needs framer whatsapp
to the project academic and
professional
Conception Analyst Astah
programmer
framer
academic and
professional
Implementation Analyst Programming
programmer web (FM script)
Implementation Analyst FM
programmer (application)

IX. The deliverables related to the project

The expected results at the end of the project are:


The technical specifications document: which provides detailed information on the analysis, design, and deployment architecture of the
solution.

X. Internal functional analysis

7
The FAST method (Function Analysis Technic)
We will show through this method the internal structure of our application.

Facilitate the Display the map


localisation

Geolocate a Google Maps


To know the
housing Know the
itineraries
chemin a suivre

Indicate your location Share its


of habitation position

XI. External functional analysis

Horned beasts
In order to better articulate our needs, the horned beast is the appropriate tool as it distinctly addresses the following questions:
Whom does he help?
What does it act on?
What is the purpose of the product?

8
Addresses of
housing
Users

Geolocation of points
housing

Facilitate access to
housing

Octopus diagram or interaction graph


It represents the relationship between a service/product and its environment.

9
Owners
Visitors/tenants

FP1
FC5
FC4
Geolocation of
housing

FC1
FC3

Peripherals FC2
(Smartphone, telephone) Security
multimedia, pc)

Environment

10
Main function (MF) Constraint functions (CF)
FP1: to allow a visitor FC1: adapt the solution to
or tenant to geolocate any type of device
registered accommodations by
a landlord.
FC2: facilitate accessibility
to the users
FC3: ensure integrity of
data
FC4: simplify the task for
visitors/tenants
FC5: simplify the task for the
owners

XII. Project Planning

Task Organization Chart

11
Project Phases Tasks No Tasks Duration
previous tasks (days
)
Pre-study Information gathering A 2
project Definition and study of requirements B A 3
Feasibility study C A 2
Definition of the project's objective D C 1
Organization of Project Plan Writing E D 1
project Definition of the scope, targets and F E 3
deliverables related to the project
Definition of functional and non-functional requirements F 2
functional
Definition of stakeholders H F 1
Means of communication I H 1
Achievement of Analysis and specification of needs J I 3
project Detailed design K J 5
Implementation L K 20
Testing and validation M K 25

Production release N M 3
Table 1: Task Organization Chart

98 days (14/08/2021 to 08/01/2022)

2. PERT Network

The PERT method (Program Evaluation and Review Technique) helps us in project planning following a dependency graph.

12
3. GANTT chart

It allows us to visualize over time the various tasks that make up a project.

13
XIII. Project cost estimation

1. Work environment

Material environment

Characteristic designation role quantity Price Price


n unit(FCFA)
Smartphone TECNO Test of 01 75000 75000
SPARK5 application
32GB, 4GB
RAM
PC SSD Entry, 01 200000 200000
500GB, RAM compilation
4Go, Core i7 and
Intel backup
some code
Modem Connection 01 15000 15000
internet
Table 1: Material resources

Software environment

Publisher Designation Version License Function Price


Windows 10 Windows 10 paying System
exploitation
FM Further free Publisher
Market
Astah UML Astah paying Design and
modeling
UML
Google browser
chrome

14
Table 2: Software Resources

2. Estimation of the workload

As part of the estimation of the workload for our project, the method
COCOMO (Constructive COst Model) which was requested due to these
numerous advantages.

Type of project Line number of Charge in Delay in months


code month/man
Simple < 50,000 lines a = 2.5 c = 2.5
b = 1.05 d =0.38
Average 50,000 <= line <= 300 a=3 c = 2.5
000 b = 1.12 d =0.35
Complex >300,000 lines a = 2.8 c = 2.5
b = 1.2 d = 0.32
Table 3: Basic COCOMO Model

The formulas:
Charge= a. (small)b
c. (charge)d
Average team size = workload / time
Or:
Kisl = kilo of source instructions delivered and a, b, c, d depend on the project.
The estimated number of lines of code for the project is 1,000,000.

We will have:
Charge = 3 * (1)1.12=3
Deadline = 2.5 * (3)0.353.7

Average team size=3 /3.7=1 Man


Thus, the estimated average size of the team to carry out the project is
of 1 man and the estimated time for completion is 4 months 3 weeks 3 days.

15
Table of contents
I. Presentton the project...................................................................................................................2
II. Problematic.................................................................................................................................2
1. Study of case............................................................................................................................2
2. Critique of the case........................................................................................................................3
III. Interest of the project..........................................................................................................................3

IV. The expected needs or functionalities....................................................................................4


The functional requirements.........................................................................................................4
2. The non-functional requirements..................................................................................................4
V. Population target..............................................................................................................................4
VI. Scope of the Project.....................................................................................................................5
VII. Definition project stakeholders5
VIII. Means of communication
IX. The deliverables related to the project..........................................................................................................7

X. Analyze internal functional.........................................................................................................7


...............................................................................................................................................................8
...............................................................................................................................................................8
XI. External functional analysis8
XII. Planning of the project..............................................................................................................11
Organizational chart stains11
2. Network PERT........................................................................................................................12
3. Diagram of GANT...........................................................................................................13
XIII. Estimation project cost..........................................................................................................14
Environment of work......................................................................................................14
2. Estimation of the workload15

16

You might also like