Internship project - Disability compensation using new technologies

Internship Project
M2 Advanced Wireless Communications Systems
Disability compensation using new
technologies
Author
Wassim EL BOURI
Supervisors
Raul JIMENEZ GOMEZ
Matthieu ROMBAUT
September 5th
, 2018

Abstract
The present work, done within Ericsson France as a graduation project, is
in the purpose of obtaining my Resarch Master diploma in Advanced Wire-
less Communications Systems from CentraleSupelec and my Engineering
diploma in Telecommunications from the High School of Communications of
Tunis.
The aim of this work is to aord a global solution, based on new tech-
nologies, for autistic persons to help them have a normal life.

Dedication
I would like to dedicate my work to my family who was always by my side
through all these years of study.
This is a small act compared to what my parents have done for me till
now. They encouraged me whenever I felt weak. They gave me advice and
provided me with guidance any time I was in need. Moreover, they taught
me the importance of perseverance and how to be responsible in life.
This book is also dedicated to my ancee who was always encouraging
me to reach my goals and to succeed. She gave me the strength I needed to
keep going toward my dreams. She povided me with company whenever I
felt alone. Furthermore, her faith in my skills presented an important boost
to me along this year.
i

Acknowledgement
At rst, I would like to express my deep gratitude to my internship tutor M.
Raul JIMENEZ GOMEZ for the valuable opportunity he oered me. It was
such a great honor to work with him.
Moreover, I wish to thank my supervisor M. Matthieu ROMBAUT for
his important remarks and constructive suggestions during the internship.
Afterwards, I acknowledge the help of all the coworkers in the Ericsson
Garage especially Merouane SELLAMI and Paul DE THOISY who were with
me in the same team along this period.
I am also grateful to my referent professor M. Mohamad ASSAAD for
accepting the topic of my internship.
ii

Contents
General introduction 1
1 Project Context 3
1.1 Hosting Organism . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.2 Philosophy . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Project Presentation . . . . . . . . . . . . . . . . . . . . . . . 5
1.2.1 Problem description . . . . . . . . . . . . . . . . . . . 5
1.2.2 Proposed solution . . . . . . . . . . . . . . . . . . . . . 5
1.3 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2 Architecture and Solution Design 7
2.1 Technical Architecture and Choices . . . . . . . . . . . . . . . 7
2.1.1 Technical Architecture . . . . . . . . . . . . . . . . . . 7
2.1.2 Technical Choices . . . . . . . . . . . . . . . . . . . . . 9
2.2 Requirements Specication . . . . . . . . . . . . . . . . . . . . 9
2.2.1 Functional requirements . . . . . . . . . . . . . . . . . 9
2.2.1.1 Users functionalities . . . . . . . . . . . . . . 10
2.2.1.2 Administrators functionalities . . . . . . . . . 10
2.2.2 Non-functional requirements . . . . . . . . . . . . . . . 10
2.2.2.1 Users functionalities . . . . . . . . . . . . . . 10
2.2.2.2 Administrators functionalities . . . . . . . . . 11
2.3 Solution Design . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3.1 Global use case diagram . . . . . . . . . . . . . . . . . 11
2.3.2 Sequence diagram . . . . . . . . . . . . . . . . . . . . . 13
2.3.3 Class diagram . . . . . . . . . . . . . . . . . . . . . . . 13
2.4 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
iii

3 Achievements of the internship 16
3.1 Application Development . . . . . . . . . . . . . . . . . . . . . 16
3.1.1 Preliminaries . . . . . . . . . . . . . . . . . . . . . . . 16
3.1.2 Development phase . . . . . . . . . . . . . . . . . . . . 17
3.1.2.1 Practiced methods . . . . . . . . . . . . . . . 18
3.1.2.2 Method inventory . . . . . . . . . . . . . . . . 18
3.1.2.3 Skills list . . . . . . . . . . . . . . . . . . . . 18
3.1.2.4 Games . . . . . . . . . . . . . . . . . . . . . . 19
3.2 IoT Accelerator exploration . . . . . . . . . . . . . . . . . . . 19
3.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.2.2 Integration phase . . . . . . . . . . . . . . . . . . . . . 20
3.3 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Conclusion and perspectives 22
References 23
iv

List of Figures
1.1 Commercialization steps in Ericsson Garage . . . . . . . . . . 4
2.1 Application architecture . . . . . . . . . . . . . . . . . . . . . 8
2.2 Global use case diagram . . . . . . . . . . . . . . . . . . . . . 12
2.3 Sequence diagram : Test session . . . . . . . . . . . . . . . . 13
2.4 Class diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1 An example of web interface . . . . . . . . . . . . . . . . . . 17
3.2 IoT Accelerator features . . . . . . . . . . . . . . . . . . . . . 20
v

List of Abbreviations
HTTP Hypertext Transfer Protocol
PHP Hypertext Preprocessor
SQL Structured Query Language
HTML Hypertext Markup Language
CSS Cascading Style Sheets
AJAX Asynchronous JavaScript And XML
UML Unied Modeling Language
vi

General introduction
In France, around 700000 people have autistic disorders [1] . That represents
a bit more than 1% of the population. Most of autistic children and adults
need human help to have a normal life, to use means of transportation, to
go to school, to learn, to work and to play...
There are more and more tools, most of the time developed by parents,
but also associations or startups, specically designed to replace human help.
These tools are developed by individuals and for isolated cases, without a
holistic approach.
There are also many situations where technology can replace human help,
but professionals do not have enough knowledge about the available technol-
ogy
That is why, a holistic approach of technical solutions can help autistic
people to be autonomous, or at least less need for the help of other people
From that context emerged the idea of this project which consists in de-
veloping a platform that contains multiple tools for disability compensation.
This platform is divided in two parts : The rst one is a hosted web
application available to users. It provides families and caregivers with a space
to share their remarks and the details of activities that are accomplished by
the concerned autistic person. Moreover, it contains dashboards that can
help keeping track of the sleep quality of the autistic person. This tracking
is assured by a proprietary device called Sleep Box, which can be provided
on request.
The second part represents the main topic of our internship. It aims
essentially at making prole analysis. This part is in the test phase. The
access is only provided for some special users to test it before its integration
in the current web application.
1

The project's basic skeleton is organized as follows:
The rst chapter will contain a high level description of the project frame,
starting by an introduction of the hosting organization, going through its
work philosophy, then presenting the project overview.
Throughout the second chapter, we will dene the architecture of the
application and we will justify the technical choices. In addition to that,
we will specify the project's requirements and we will present the solution
design.
The achieved work will be the object of the third chapter.
2

Chapter 1
Project Context
This chapter gives the general context of the internship. At rst, we introduce
the hosting organism. Afterwards, we dene the problems to be solved and
present the proposed solutions.
1.1 Hosting Organism
This section presents briey the service in which the work is accomplished
and describes its philosophy.
1.1.1 Overview
Ericsson Garage is an incubator for exploring new ideas and developing mini-
mum viable products to show that these innovations are potential sustainable
opportunities for new business. The results from Ericsson Garage are pre-
sented to the Ericsson Garage Dragons' Den as opportunities for investment,
i.e. basis for decisions on how to commercialize the outcome.
1.1.2 Philosophy
• Ideas
Innovation ideas can come from inside Ericsson or from startups and other
external partners. All projects require a partnership with a group of people
from Ericsson and an external partner. The purpose of the partnership is
mainly about verifying that the project addresses a real problem.
3

• From Idea to commercialization
Ideas are explored in the opportunity discovery phase where the entry se-
lection criteria are worked on. The main criteria are: a clear need, a crisp
problem denition veried by an external partner and a feasible minimum
viable product denition. The decision is taken in the Entry Selection Board
with members from dierent Ericsson organizations.
Then, an incubation phase starts with a purpose to build a minimum
viable product to validate the potential in the innovation. The outcome of
this phase is considered an opportunity for investment and is presented to
the Ericsson Garage Dragons' Den.
The Dragons' Den decides whether the innovation should be commercial-
ized within or outside Ericsson or the idea should be discontinued.[2]
This 3-step process is shown in the gure below.
Figure 1.1: Commercialization steps in Ericsson Garage
• Ways of working
Traditional approaches usually expect a detailed and a validated expression
of need in the entry of realization which decreases exibility. These method-
ologies are predictive and sequential. However, it is usual that some requested
features are nally revealed useless while others, discovered along the way,
could give more value to the product.[3]
That is why, Ericsson Garage chose the agile approach that proposes to
reduce considerably the tunnel eect, caused by traditional methodologies,
by giving more visibility. This is guaranteed by involving the client from the
beginning to the end of the project and adopting an iterative and incremental
4

process. It considers that the customer requirements evolve and cannot be
static. To manage that, it proposes a lot of exibility to adapt to the changes.
To conclude, the incubation phase is characterized by a Lean Startup
inspired way of working, with fast development cycles, in close collaboration
with the partner and possible customers, and where learning fast is essential.
1.2 Project Presentation
This section contains a brief denition of the problem and a presentation of
the proposed solution.
1.2.1 Problem description
Autism is a neurodevelopmental disorder that aects communication, social
interaction, stereotyped behaviors and narrow interests.
People with autism spectrum disorders have diculties in understanding
facial expressions and problems in interactions with others.
This makes autism not only an important public health issue but also an
area where many doubts and questions remain, and where dierent concep-
tions are made.[4]
Among the existing solutions, we mention tests passed in sessions with
experts. These tests are sometimes quite heavy and involve dozens of ques-
tions that require the presence of parents and the person with autism. They
are also expensive and burden the family nancially. Besides, the availability
of the family and the expert are issues.
All these problems make this solution not convenient for many people
with autism.
That is why, the use of new technologies to support people with autism
is among the ecient ideas because the high availability of internet in these
days.
1.2.2 Proposed solution
The use of digital tools with autistic persons is not new and dates to the
1970s. However, there has been an explosion of research and common prac-
tices with these tools in recent years which is proved by the large number of
websites presenting useful computer applications for people with autism.
5

Computers and tablets are vectors of progress for the autistic person
because they are predictable thus reassuring, they represent for him a frame-
work of concentration.
For this, our solution is a web application that creates an environment
in which we provide playful tests to people with autism in a personalized
format. This solution traces the progress of these people, in dierent skills
to assess, to nd the most appropriate methods to accompany them in their
daily life.
1.3 Conclusion
Throughout this rst chapter, we presented the hosting organism that was
for us a suitable working environment. In addition to that, we laid out the
context of our internship project.
In the next chapter, we will describe the application architecture and the
solution design.
6

Chapter 2
Architecture and Solution Design
Throughout the previous chapter, we ew over the context of our internship
showing the hosting company and the project presentation.
In this chapter, we will rst start by dening the architecture of our
application. Then, we will justify the technical choices. Afterwards, we will
move to the specication of the requirements that our project has to meet
and we will present the design of the solution.
2.1 Technical Architecture and Choices
This section contains a description of the application architecture and a jus-
tication for technical choices.
2.1.1 Technical Architecture
As we mentioned in the introduction, our solution is in the test phase. In the
rst three months of our internship, the developed application was a local
web application that we can access only from our computer.
In each organized meeting, we were showing our partners our work ad-
vancement such as the new features and the modied ones. Then, we decided
to use a remote server as a host of our solution. Like that, they can use the
web application from their oces and test it in the real life. This is an im-
portant fact because they will provide us with more constructive remarks.
As a result, we can upgrade more and more functionalities to meet the need
of autistic persons.
7

To aord this remote access, we used a virtual machine hosted in google
cloud. To prepare the environment for our application, we installed LAMP
which is a model of web service stacks. This software is composed of four
components that were behind its acronym. We begin with the operating
system which is Linux. Then, we move to the APACHE that represents the
web server. It executes HTTP queries. We nd also MySQL as a database
management system. Collected data is stored in its tables. The last compo-
nent to mention is PHP. It is a server-side scripting language and it gives a
dynamic aspect to the web application by interacting with the database.
The PHP code is interpreted by APACHE via a PHP Processor module.
As a result, we have a web page which is written in HTML that is supported
by the browser.
The gure below illustrate the application architecture as well as the
dierent steps executed behind a dynamic web page request.
Figure 2.1: Application architecture
8

2.1.2 Technical Choices
Our technical choices were based on the fact that we decided to begin our
project by doing a prototype and not a complete solution from scratch. In
fact, this idea reduces the risk factor signicantly and gives the project more
exibility.
That is why, we have not chosen big data framework at rst and we have
replaced it by a database management system that is MySQL. This solution
is less complex and enables us to store the amount of data that we will collect
in the test phase.
The programming language PHP was chosen because of the compromise
it maintains between the speed of implementation and the web application
performance. Based on the large community that is using PHP, we can nd
a lot of help in the forums. This reduces greatly the time needed to correct
the bugs and to progress in the application development. PHP allows also
the use of the SQL queries to interact with the database which makes the
application dynamic.
We used also HTML which is the standard markup language for creating
web pages and CSS that denes the style of the content. To provide an
interactive web application, we used JavaScript that gives us an important
set of techniques in AJAX. These techniques permit to send and retrieve
data from a server asynchronously. AJAX allows also to change the web
page content without reloading it.
2.2 Requirements Specication
To reach the project's aim, several requirements has to be satised by the
proposed solution. In this section, we will present these requirements to
summarize our application functionalities.
2.2.1 Functional requirements
The functional requirements refer to main functions that the application,
being developed, must exhibit. Our solution is expected to deliver two types
of specic features that dier from simple users to administrators.
9

2.2.1.1 Users functionalities
In our application, we aorded these features that depend on the user role:
• Experts in the medical eld can select the methods they use in their
sessions with autistic persons. They are also allowed to suggest the add
of other methods.
• All users can see what the targeted skills by each method are. They
are able also to do things conversely by searching associated methods
and tools for each skill to know how to deal with an autistic person
based on the problems he faces. Besides, they are allowed to suggest
the add of targeted skills or sub-skills.
• People with autism can pass tests in a playful and personalized manner
and see their results after each exercise.
2.2.1.2 Administrators functionalities
Administrators have dedicated interfaces that permit them to manage easily
the web application. The functionalities they dispose are the following:
• An administrator receives the suggested methods, skills and sub-skills
by users. And based on the decision of experts they collaborate with
him, he either validate or refuse the suggestion.
• An administrator can add, delete or change methods, skills and sub-
skills after the approval of the expert who is in contact with him.
2.2.2 Non-functional requirements
The non-functional requirements are key features that are beyond the scope
of this project but they are crucial to its operation. They ensure the system's
smooth integrability in its environment. When designing the solution, they
must be taken into account to deliver a high-quality application.
2.2.2.1 Users functionalities
As the key actors of this application are the autistic persons. The environ-
ment must be adapted to their requirements. That is why, the accompanist
should guide his subject if he need his help in some tests.
10

If the test gives the possibility of making a demonstration for the child,
it is recommended that the person who accompany him do that to put him
in the context.
2.2.2.2 Administrators functionalities
From administrators and developers side, the main requirements are the fol-
lowing:
• Security: Access rights to dierent features depend on the user role.
• Integrity: Collected data is stored in a secured database.
• Ergonomics: The system must respect the uniformity of the design
across the whole application and must implement user-friendly inter-
faces to ensure a better experience to users. It must be exible and
consider autistic persons preferences not only in colors but also in con-
tent.
2.3 Solution Design
This section will present the design of the solution using dierent types of
UML diagrams.
2.3.1 Global use case diagram
In UML, a use case diagram can summarize the details of the system's users
(also known as actors) and their interactions with the system which is the
web application. To build one, we will use a set of specialized symbols and
connectors.
An eective use case diagram can help the team discuss and represent:
• Scenarios in which an application interacts with people, organizations,
or external systems.
• Goals that an application helps those actors to achieve.
To understand a use case diagram, we have to dene these two types of
relationships:
11

• include is a directed relationship between two use cases which is
used to show that the behavior of the included use case is inserted into
the behavior of the including use case. This relationship goes from the
included use case to the including use case.
• extend is also a directed relationship. It diers from include
in the fact that the behavior dened between the two use cases is usu-
ally optional
As shown in the gure below, we illustrate our system's boundaries using
a global use case diagram, to dene the dierent relationships between the
involved actors and the use cases.
Figure 2.2: Global use case diagram
12

2.3.2 Sequence diagram
Sequence diagrams are a popular dynamic modeling solution. They belong
to the behavioral diagram category of UML. Dynamic modeling focuses on
the interactions that occur within a system.
In the diagram in the next page, we are modeling the scenario in which a
user starts a test session for the concerned autistic person associated to him.
In this scenario, we show interactions between the application and the
database that lead to a several personalized interfaces for each subject. In
fact, this is important because it makes the person with autism feel comfort-
able when he passes his tests and this is a key factor to good results.
Figure 2.3: Sequence diagram : Test session
2.3.3 Class diagram
A class diagram shows the internal structure. It provides an abstract repre-
sentation of the system objects that will interact to make use cases. A same
object can be involved in several use cases. That is why, a class diagram
is not suitable to detail or illustrate the realization of a particular use case.
However, this diagram type models the concepts of the application domain.
13

As shown in the gure below, we present our web application class dia-
gram.
Figure 2.4: Class diagram
14

2.4 Conclusion
Throughout this chapter, we described the application architecture and we
argued our technical choices. Besides, we listed our application requirements
from the user side as well as the administrator side. Then, we presented the
solutions design with some explanatory diagrams.
In the next chapter, we will pass to the done tasks in our internship.
15

Chapter 3
Achievements of the internship
This chapter presents what was done during the internship. We will start by
the main task which is the application development. Then, we will move to
the discovery phase of IoT Accelerator.
3.1 Application Development
In this section, we will detail the steps done in the application development
in the chronological order.
3.1.1 Preliminaries
As the project has begun before our internship, the rst thing to be done
was the documentation reading. The project documents were detailed and
have provided us with an overview of the dierent points. First, we started to
discover what has been done. Then, we understood the technical architecture
of the existing web application and we shaped an idea of the basic projet's
requirements. These two points were important for us to make our technical
choices. In that moment, we started our research to nd the best technologies
that go with what we need and we designed the database required for our
application.
After our discussion about the technical choices with our supervisor, we
validated our choice. Afterwards, we started an online course to acquire the
basis needed to begin the development phase.
In parallel with this, we met our partner who is a collaborator from AFG
16

Autism association. This association is our major partner in this project and
its main object is to provide appropriate care for people with autism. This
involvement that has started since 2005 will help us in the renement of our
solution.
3.1.2 Development phase
After discussions with our supervisor and our partners, we have decided to do
a prototype to decrease the risk factor. Now, we can start the development.
The rst task we have accomplished was doing some modications on
the current database to be coherent with the application to develop. Then,
we started reading the documents provided by our partners to extract the
content that will feed our solution. The login for our application will be
possible for people who have an account created through the part put in
production. Our web application is available in both English and French
versions. It contains four main parts as shown, in the bar, in the gure
below.
Figure 3.1: An example of web interface
17

3.1.2.1 Practiced methods
This window is dedicated to persons who are registered as experts. It allows
them to list the methods they use in sessions with their subject.
This information will be stored in the database because when we will
collect a lot of data, we can analyze how each method is impacting dierent
subjects. Then, we will be able to design a model that clusters the subject
who have similar evolutionary behavior under the same method. As a result,
we will conclude what would be the best methods that t with each prole
type.
This page has one hyperlink that redirects the expert to the page Method
inventory which is the topic of the next paragraph.
3.1.2.2 Method inventory
This interface permits all the users to have an idea of the skills targeted by
each method. As a method is composed of dierent tools and a skill is a set
of sub-skills, we have decided to make these details exposed to all to facilitate
for parents how to choose the expert that will be associated to their child
based on the problems he is facing.
There is also a eld for methods suggestion that is available for the ex-
perts. A rst automatic mail is sent to the person who suggest the add of
a method to conrm the reception of his suggestion. Then, a second mail is
sent to give the decision of administrators that could be either positive or
negative.
3.1.2.3 Skills list
This menu proposes two web pages.
• The rst one, which is named Skills, presents to all users the list of
targeted skills for autistic persons. These skills are detailed with asso-
ciated sets of sub-skills. A suggestion eld for skills and sub-skills is
available to extend the content of our application. Administrators are
supposed to accept or refuse any add suggestion after discussions with
experts in the medical eld.
• The second page, named Skills and methods, provides persons with the
associated methods to each skill.
18

3.1.2.4 Games
This is the main part in the application. The idea behind it is to nd a way
to evaluate the skills of the people with autism in a playful manner that does
not cost as much as sessions with experts.
These games were designed particularly to take into account autistic peo-
ple preferences. In fact, when the user gets to this page, he can access to his
repertory to manage the content of his subject folders. The uploaded images
in these folders will be stored in the database and loaded when the chosen
mode of the game is the personalized one.
Before starting a game session, the user is obliged to select the subject
who will pass the test, the game mode and the images category. He can set
the background and the text color optionally and these two parameters will
be charged automatically next time when he selects the concerned subject.
In these games, we measured a set of performance criteria such as the
duration of the test, the number of correct answer, the chosen ones. This
collected data is stored in the database to draw a graph that shows the
evolution of the child throughout the passed tests.
When we collect a big amount of data, we can combine many analysis
to arrive to some useful informations. In one side, we can see the methods
used with the autistic person. In the other side, the child performances when
passing tests show if there is an improvement in some skills related to the
game topic. As a result, we are able to conclude what are the dierent skills
targeted eciently by each method.
3.2 IoT Accelerator exploration
In this section, we will present an Ericsson platform that gives the access to
many useful tools after integrating IoT devices.
3.2.1 Overview
The Internet of Things (IoT) has the potential to connect and create digital
representations of the physical world, making it possible to transform busi-
ness models. For individuals, IoT provides the potential to save time and
improve quality of life.
That is why, Ericsson decided to complement its industry-leading telecom
networks with one single end to end IoT Stack based on IoT Accelerator.
19

With its growing set of functionalities, this platform leverages the scale, speed
and lower cost of a cloud-based solution to address use-cases and applications
for Enterprises and Service Providers.
The purpose of this platform is to be able to connect IoT devices. As a
result, the data provided by these devices is made available to applications
that can, in turn, use it to create new revenue streams for service providers
and enterprises. Besides, this solution includes control of the devices/sensors
(turn them on/o, provision new ones, etc.), as well as providing the ability
of billing related events in the devices/sensors, or usage of them.[5]
3.2.2 Integration phase
The IoT Accelerator platform allows and makes easier the connection between
sensors/devices and applications in an end-to-end and data-centric approach,
by including Business Support functions such as analytics, billing and API
onboarding.
The gure below shows this platform functionalities.
Figure 3.2: IoT Accelerator features
This rich set of features made us decide to integrate the Sleep Boxes,
that are a part of the global solution for disability compensation, in this IoT
platform. These devices give accompanists an idea of the sleep quality of
their subjects which help them to anticipate a prospective restless behavior
during the day. Therefore, they can adapt the planned activities to avoid
problems.
To accomplish this task of device integration, we started reading the
documentation related to Ericsson solution. This documentation aords a
20

tutorial that explains how to send the data from the device and visualize it
in real time in the platform.
We have test this functionality using a client simulator to replace the IoT
device. The test was successful. Then, we have tried to integrate the device
to make his remote control possible and to receive data from it. In this step,
we have found problems because the protocol with which we send the data
from the IoT device was not adapted to what IoT Accelerator is supposed to
receive. As this task is not the rst priority, we will let it to the last weeks
of the internship.
3.3 Conclusion
Throughout this chapter, we showed the achieved work during this intern-
ship. First, we detailed the tasks during the application development process.
Then, we presented briey the exploration phase of IoT accelerator.
21

Conclusion and perspectives
Throughout this report, we described the several steps taken to design and
implement a tool for disability compensation using new technologies. We
have been enrolled to work within a skilled team, and we learned a lot from
this experience in Ericsson.
In the present work, we started by introducing the host company Erics-
son as well as its philosophy, then we presented an overview of the project
including the main problem as well as our solution. Throughout the second
chapter, we described the application architecture and we explained our tech-
nical choices. Afterwards, we specied the requirements of our application
and we presented the ultimate design. Finally, in the last chapter, we went
into details to present the tasks we have accomplished during this internship.
Our project would hopefully succeed in being a universal solution that
would give autistic people an opportunity to test and discover their skills
and have fun at the same time. As a result, the application ts the needs
of children. We have also designed our solution in a way that makes it
personalized, which means that it would provide a comfortable atmosphere
for the children. Besides, we provided parents and experts with a tool with
which they can follow up the child's evolution. The main object of all these
features is to collect a lot of data to analyze it to be able to do the proling
of autistic people. This will allow us to provide an almost ideal environment
for all autistic people to thrive and feel more integrated in their societies.
However, the work that we have just nished is considered as a rst step
or as a preliminary version. Various perspectives are imminent for our project
in order to enhance it and expand it. We can add other connected devices to
monitor the behavior of autistic persons. Furthermore, we can improve our
analyses, based on the collected data, using IoT Accelerator. Last but not
least, we may improve our application by connecting it to other applications
to reach a bigger community and provide users with the needed help.
22

References
[1] https://www.inserm.fr/information-en-sante/dossiers-information/autisme
(visited on 18/07/2018)
[2] Internal documents
[3] https://agiliste.fr/introduction-methodes-agiles/ (visited on 25/07/2018)
[4] https://hal.archives-ouvertes.fr/hal-01634962/document (visited on 10/08/2018)
[5] Internal web site
23

Internship project - Disability compensation using new technologies

More Related Content

Similar to Internship project - Disability compensation using new technologies (20)

Recently uploaded (20)

Internship project - Disability compensation using new technologies