In Order to Obtain the

PROFESSIONAL MASTER
In Software Engineering

Issued by:

Lebanese University Faculty of Sciences

Presented and defended by:

MARROUN Rita

DATE

On Wednesday, October 21, 2022

Title

1
 Bookbeauty System

Supervisor

Dr. Wissam HLAYHEL

Readers

Dr. Mohammad SAADEH

Dr. Omar RIFI

Lebanese University – Faculty of Sciences - www.fsciences.ul.edu.lb

TABLE OF CONTENTS

Summary 7

Acknowledgments 8

Glossary 9

Chapter 1: Project Specifications 9

1.1 Introduction 9

1.2 Project context 10

1.2.1 Company and Project Team 10

2
1.2.2 The client: GGVIE 10

1.2.3 The Trademarks 11

1.2.4 The contracts 12

1.3 The stakeholders of the project 12

1.4 The actors of the project 13

1.5 IGC Functional Requirements 13

1.5.1 Front Office (FO) IGC 13

1.5.1.1 Employee Space 13

1.5.1.2 Company Space 14

1.5.2 Back Office (BO) IGC 14

1.6 The project development cycle 14

1.6.1 The different events during the version 15

1.7 Training and various tasks in IGC 17

1.8 Conclusion 19

Chapter 2: Affiliation Process Design 19

2.1 Introduction 19

2.2 Milestones 19

2.3 Affiliation Use Case diagram 20

2.4 Use Cases’ textual Description and Sequence Diagrams 21

2.5 Database 24

2.5.1 Entity Association 24

2.5.2 Relational Schema of the Database 26

2.6 Class Diagram 27

3
2.7 Activity Diagrams 32

2.8 User Interface 32

2.9 Conclusion 35

Chapter 3: Beneficiary designation 35

3.1 Introduction 35

3.2 Universign 36

3.2.1 Principles of the Universign electronic signature 36

3.2.2 Functional integration of the electronic signature 37

3.2.3 API integration 38

3.2.3.1 Protocol used 38

3.2.3.2 Universign account 38

3.2.3.3 WEB browsers not supported 39

3.3 Milestones 39

3.4 Beneficiary Designation Use Case diagram 42

3.5 Use Cases’ textual Description and Sequence Diagrams 44

3.6 Database 50

3.6.1 Entity Association 50

3.6.2 Relational Schema of the Database 52

3.7 Class Diagram 53

3.8 Activity Diagrams 56

3.9 User Interface 57

3.9.1 Buttons 58

3.9.2 Clause choice screen 59

4
- Je souhaite seulement modifier l’ordre de la clause par défaut 62

- Je souhaite désigner un bénéficiaire unique 63

- Je souhaite répartir mon capital entre plusieurs bénéficiaires 65

3.9.3 Synthesis screen 67

3.10 Conclusion 70

Chapter 4: Accounts Aggregation Design 71

4.1 Introduction 71

4.2 Budget Insight API 71

4.3 Milestones 71

4.4 Aggregation Use Case diagram 73

4.5 Use Cases’ textual Description and Sequence Diagrams 74

4.6 Database 82

4.6.1 Entity Association 82

4.6.2 Relational Schema of the Database 83

4.7 Class Diagram 84

4.8 Activity Diagram 86

4.9 User Interface 87

4.9.1 Dashboard - My consolidated retirement savings block 87

4.9.2 Consolidated Retirement Savings Details 88

4.9.3 Repartition of my savings 89

4.9.3 Evolution of my savings 91

4.10 Conclusion 93

Chapter 5: Conclusion and Perspectives 94

5
References 94

List Of Images
1. Figure 1. The project development cycle
2. Figure 2. Affiliation Use Case Diagram
3. Figure 3. Enterprise Sign In Sequence Diagram
4. Figure 4. Affiliation Sequence Diagram
5. Figure 5. Affiliation Database Entity Association
6. Figure 6. Affiliation Class Diagram 1/4
7. Figure 7. Affiliation Class Diagram 2/4
8. Figure 8. Affiliation Class Diagram 3/4
9. Figure 9. Affiliation Class DIagram 4/4
10. Figure 10. Company’s manager activity diagram
11. Figure 11. Contracts step
12. Figure 12. Employee info step
13. Figure 13. Ayants droits step
14. Figure 14. Signature levels
15. Figure 15. Electronic signature process
16. Figure 16. Beneficiary Designation Use Case Diagram
17. Figure 17. Sign In Sequence Diagram
18. Figure 18. Beneficiary Designation (Retirement Contract) Sequence Diagram
19. Figure 19. Beneficiary Designation (Provident Contract) Sequence Diagram
20. Figure 20. View My Beneficiary Designation (Retirement Contract) Sequence Diagram
21. Figure 21. View My Beneficiary Designation (Provident Contract) Sequence Diagram
22. Figure 22. Beneficiary Designation Request Entity Association
23. Figure 23. Beneficiary Designation Request Class Diagram 1/3
24. Figure 24. Beneficiary Designation Request Class Diagram 2/3

6
25. Figure 25. Beneficiary Designation Request Class Diagram 3/3
26. Figure 26. Beneficiary Designation Request and View My Beneficiary Designation Activity
Diagram
27. Figure 27. Personal data collection screen for the insured
28. Figure 28. Beneficiary designation
29. Figure 29. Beneficiary designation - The default choice
30. Figure 30. Beneficiary designation - Second choice
31. Figure 31. Beneficiary designation - Modify order choice (drag and drop)
32. Figure 32. Beneficiary designation - Sole beneficiary - By identity
33. Figure 33. Beneficiary designation - Sole beneficiary - By quality
34. Figure 34. Beneficiary designation - Several beneficiaries
35. Figure 35. Information notice
36. Figure 36. Synthesis screen
37. Figure 37. Electronic signature
38. Figure 38. Accounts Aggregation Use Case Diagram 39. Figure 39. Sign in Sequence Diagram
40. Figure 40. Account Management Sequence Diagram
41. Figure 41. Consolidated retirement savings details Sequence Diagram
42. Figure 42. Repartition of my savings Sequence Diagram
43. Figure 43. Evolution of my savings Sequence Diagram
44. Figure 44. Aggregation of accounts entity association
45. Figure 45. Aggregation of accounts class diagram 1/2
46. Figure 46. Aggregation of accounts class diagram 2/2
47. Figure 47. Accounts Aggregation Activity Diagram
48. Figure 48. My consolidated retirement savings block
49. Figure 49. Consolidated Retirement Savings Details
50. Figure 50. Repartition of my savings
51. Figure 51. Pop-up
52. Figure 52. Evolution of my consolidated savings
53. Figure 53. Evolution of my savings by type of product

7
List Of Tables
1. Table 1. Glossary
2. Table 2. Brands
3. Table 3. Contracts
4. Table 4. Events
5. Table 5. Various Tasks Milestones
6. Table 6. Refonte Affiliation Milestones
7. Table 7. Enterprise Sign In Description
8. Table 8. Affiliation Description
9. Table 9. WEB browsers not supported
10. Table 10. Beneficiary Designation Milestones
11. Table 11. Sign In Description
12. Table 12. Beneficiary Designation (Retirement Contract) Description
13. Table 13. Beneficiary Designation (Provident Contract) Description
14. Table 14. View My Beneficiary Designation Description
15. Table 15. Agrégation de comptes Milestones
16. Table 16. Sign in Description
17. Table 17. Account Management Description
18. Table 18. Consolidated retirement savings details Description
19. Table 19. Repartition of my savings Description
20. Table 20. Evolution of my savings Description

Summary
Our project consists of developing a web tool entitled Bookbeauty a leading insurance company
in France, allowing an interface between managers and GGVIE.

IGC or Internet Collective Management aims to present to the end customers of GGVIE the
contractual data of forensity, health, retirement subscribed to Gan Eurocourtage, Gan
Assurances, and Groupama.

8
More specifically, IGC is secured web-based. It aims to provide qualitative management
services such as:

● Online affiliation;
● The declaration of an insurance claim;
● The declaration of contributions for companies;
● Monitoring of savings for affiliates;
● Managing company’s health contracts;
● Handling payroll;
● Issuing sickness and sick leave declarations;

In these report I will present three sub-projects:

1. Affiliation process redesign

2. Beneficiary designation
3. Accounts aggregation

These sub-projects are vital to the IGC platform.

Acknowledgments
I would like to express my sincere gratitude to my supervisor Dr. Wissam Hlayhel for providing
her invaluable guidance and suggestions and constant supervision throughout the course of the
project..

Thanks to our readers, Dr. Mohammad Saadeh and Dr. Omar Rifi for the time they spent
reading the report, their opinions, and advice.

I have taken efforts in this project. However, it would not have been possible without the kind
support and help of the Bookbeauty team. I would like to extend my sincere thanks to all of
them.

9
 Abstract
Bookbeauty is a web-based salon management application with appointment
scheduling functionality. It connects clients and salons in an online community allowing
users to browse salons , and book or cancel appointments. Users can also
write and read reviews. Salons can specify the products their selling, as well as the
services their offering. Salons can also book appointment for customers, and can view
and print schedules in convenient formats. To achieve the desired result, the functionality
of the site was analyzed by considering the system from several points of view. The
organization of the description of the system in several views is an architectural model
created by Philippe Kruchten. This report thus describes the website following Kruchten's
“4 + 1” view model.

Glossary
Terms Definition

API Application Programming Interface, an

intermediary software or a service that
allows two applications to communicate
with each other via the internet.

GET A method of HTTP request used to

request data from a specified resource,
which carries the request parameter
appended in the URL string.

QA Quality Assurance.

Kruchten “4+1” view: A view model that describes the

architecture of the software system.
Table 1. Glossary

10
Chapter 1: Project Specifications
1.1 Introduction

Being a salon client today is inconvenient. You have to remember that you need to
make an appointment, then hope you remembered during business hours, and finally
scramble to find the phone number and take time out of your busy day to make the
call.And never mind finding user reviews of local salons; tracking those down
somewhere on the web is a headache that most don’t even attempt. This is the
experience of countless salon-goers every day, even as we move well into the
twentyfirst century. There is a strong, well-articulated need for a “one-stop-shop”
online hub that connects clients to salons, putting all the information users need in
one convenient place, on demand.
So our project consists of developing a web tool entitled Bookbeauty. It is divided into
two parts : Consumer side and salon/pro side.
 BookBeauty consumer side makes it simple to find beauty services that suit the
schedule and fit into the lifestyle of the client. Search our database of verified
businesses to see who’s available at a preferred time and location, then book
them immediately – 24 hours a day, 7 days a week.
No more missed calls, confusing voicemails or unanswered DMs. Clients can book
at any time (including after hours) and get on-the-spot confirmation of the specific
appointment, even if it’s the next day. In-app tracking makes it easy to see when
Your freelancer will arrive. Plus, we verify all business listed on BookBeauty. Plus
the client can discover more ways to save money, earn rewards and fit more
beauty in his day.And with our cloud-based booking solution client will maximise
their appointments,minimise admin and reduce no-shows.
 Bookbeauty pro side ,a salon can easily reach new clients in its area, with no extra
effort. Plus, our simple and automated marketing templates will help keep its
clients coming back time and again.A salon can manage its team, tracking their

11
 sales and ordering new stock, simply running a salon can feel like a full-time job.
Relax.

 Through the Website You can:

o (a) register for an Account;

o (b) search Products and Services offered by third party service providers;

o (c) purchase Products and Services offered by third party service providers;

o (d) book appointments with third party service providers.

Project objectives

The objectives of this project are:

1.3.1 Target Audience.
There are two distinct target audiences for this project.
Salon managers and owners make up the first primary audience for this project.
They will use the salon side of the web application.
Salon-goers, are the second major audience. They will use the client side of the
application, primarily using it to browse local salons,, and make appointments
online, all on demand.
1.3.2 User goals and objectives USE CASES: User - Create a new account - Log in -
Search for salons by: location ,name - View and Edit Account information - Make
an View Appointments
Salons: - Log in - Edit Salon Account Information – Add/Edit services-Add/Edit
Products.

1.2 Project context

This project was realized for AdCreators Company.

12
 Figure 1: company logo

AdCreators is a full-service creative marketing and communications agency

established in Sydney,Australia in 2012 with offices in Melbourne, Brisbane, Western
Sydney and most recently AdCreators MENA in Dbayeh Lebanon,in 2018.
This internship is realized under the supervision of the team leader Mr Sarkis Ayoub.

1.2.1 Project Team

We have implemented our project in the AdCreators company. The project members are:

● Chelsea Peters – Marketing and Product Manager

● Sarkis Ayoub - Team Leader
● Sarkis Ayoub- Developer
● Rita Marroun- Developer
● Amany Mohammad – Developer

● Rita Khoury-Designer

● Tania Elias-QA tester.

13
1.4 The actors of the project

Different actors interact directly with the system:

● Clients who are registered in Bookbeauty consumer side.
● Salons that are also registered in the Bookbeauty pro system.

1.5 Requirements

Generally, the users’ expectation will be the user requirements. These are the
function of the final system. After clarifying all the functions, the system can be
easily implemented. There are two types of requirements in a system. 1) Functional
Requirements 2) Nonfunctional Requirements
1.5.1 Functional requirements
A description of the facility or feature required. Functional requirements deal with
what the system should do or provide for users. They include description of the
required functions, outlines of associated reports or online queries, and details of
data to be held in the system". Following are the functional requirements that have
been identified through the system analysis.
1.6 The project development cycle

This section describes the development cycle of my work in this project. The time schedule was
as follows:

● Three months as internship:

● The first month has been dedicated to learning PHP, HTML, js,yii2 while using
visual studio code as a tool.[3]

● 1 year of development by Bookbeauty developers(BBD).

During the 5 weeks of development, the roles of the Bookbeauty team consist of the following
(figure 1)::

14
 ● Development of the tasks of the current version N (developments + unit tests +
refactoring);
● Taking into account the returns of acceptance and approval of the previous version N-1;
● Costing of backlog tasks for sprint N + 1;
● Analysis of production cases (if required by MOA GGVie);
● Various tasks (data extraction, functional advice, etc.);
● Delivery of the package (once completed) to the acceptance environment; ● Production
of the package from the previous version.

Figure 1. The project development cycle

1.6.1 The different events during the version

The following table identifies the tasks assigned to each actor along with the scheduling and
the envisioned goal.

What Who When Goal

15
Project committee Bookbeauty Every Monday Sharing of
project manager information on
current or
upcoming topics.
Risk estimation
and planning
adaptation.

Coding session Bookbeauty team At the end of the Define costings,

development of the common way,
the current version for unprocessed
backlog tasks

Planning GGVie (MOA + At the end of the Define the

possibly MOE) + development of provisional scope

YT the current version of the next version

Delivery in recette YT At the end of the Update the

development; acceptance
Regularly during environment with
the acceptance the integration of
phases and implemented
approval functionalities and
feedback

Production GGVie (MOA + At the end of the

possibly MOE) + YT homologation
recipe

Daily meeting MOE YT Everyday Information

sharing and

16
 synchronization on
the progress
of the project.
Highlighting
possible risks and
delays.
Table 4. Events

17