Giving shape to your dreams

Avan’Garde Beauty Saloon Project

Project manager:Emanuela Cerchez
Powered by: Raluca,Gabriela and Raluca
Business description
 The „Avan’Garde Saloon” is a beauty parlour in Iasy that
has first started its activity in the 14th of May 2001, having
2 employees and providing only hair-style services.
Nowadays, it is a growing business that is working with 12
employees who have the necessary training to offer a large
number of services. Soon, the manager will open another
center in Tudor Vladimirescu,Iasy.
 In order to run an efficient business they need to keep
track of the increasing number of services, employees and
clients, things that have been done manually by now.
 Solution proposed
 We are interested in creating an efficient solution that will help
retaining a lot of data and its changing in time. Another
purpose is to organize data so that more than one center
could be kept track of.
 Our team offers the answers to these needs by presenting an
optimized database that will surely ease the effort.
References
Interview with ms. Mirela Dobrescu, the manager of the
Avan’Garde Saloon.
 Tel: 0741619302
 E-mail:mirela_avan@yahoo.com
 Address: street Al.Vlahuta no.17
Information requirements
 For the correct functionality of the database we need to
operate with the following types of information:
 The ‘Avan’garde Saloon’ needs to hold information
about its employees like: first name, last name,
telephone number, e-mail address (if he/she has one),
training, salary and extra hours. We uniquely identify
employees by their CNP (the correspondent for SSN in
USA). We classify employees in stylists, secretaries,
managers and “other”.
Information requirements
 We need to hold details about their clients like: full name,
phone number, address, an optional e-mail address and
its future appointment.
 For each producer we have the fiscal code, name,
address, a telephone number, a fax number and an
optional profile.
 Because of the opening of another center, for each
center we will store the fiscal code, the name, address
and phone number.
Information requirements
 For each bill we have an unique id (the code from the
pay office), value of the bill and day.
 For each service we need to know the type of service, its
price, the products used and the employee who did the
service. We generate an artificial id for each service
 For each type of product we need to know its name,
brand, expiration date, price, a short description and the
distributor that has brought the product.
Business Rules
 An employee cannot work for more than one centers.
 Only the secretary does the appointments.
 Only the secretary sends the news-letter.
 Only the secretary makes the bill.
 Each center has a manager responsible for it.
 Only the stylist does the services.
Business Rules
 A client can make an appointment for more then one
services.
 An appointment must be done for only one client.
 A type of product must be provided by only one
distributor.
 A service may use one or more types of products.
 Only one client must pay the bill.
Programmatic Rules
 When the number from Product_type entity – the
number from Quantity is lower than 5 the center brings
new products
 The clients that have an appointment have priority
 If an employee does more than 10 extra hours we will
receive a bonus at his salary
 Each employee must start work at 10 o’clock in the
morning and work at least 8 hours every day.
 If a client does not have an e-mail address the
newsletter will be sent at his address.
Assumptions and
Constraints
Assumptions
 If a product expires it will be thrown away and deleted
from the database.
 An employee does not work at more than one center.
 One bill must contain at least one service.
Constraints
 The attribute number from the Quantity entity must not
be bigger than the attribute number from the
Product_type entity.
 If the attribute type from the Stylist subentity is hair-
stylist.
Assumptions and
Constraints
If the attribute type from the Stylist sub entity is hair-
stylist then the attribute type from the entity Service
must be only hair-cut, hairdo or hair-dying.
 If the attribute type from the Stylist sub entity is
cosmetician, then the attribute type from the entity
Service must be only make-up, treatment or waxing.
 If the attribute type from the Stylist sub entity is
manicurist, then the attribute type from the entity
Service must be only manicure or pedicure.
 made by
Center receive given to
#id Transaction bill make
*name
*address work in Employee Service
*phone_no have #id Distributor
#id Salary *type use #id
*f_name receive #date *price *name
*l_name
receive correspond to *value *address
*adress
*training include be on *phone_no
* phone_no 0e_mail
correspond to
0e_mail bring
do
make Stylist done by Activity brought
make by
send Secretary
made by
Manager supervise
Product
Other #id
Client Bill *name
supervised #id *brand
by #id
*value used in *exp_date
*f_name pay
*em_name *price
*l_name contain
*date 0description
0phone_no paid by
*hour
0adress
be on
0e_mail
Service list
be on have contain

contain
Newsletter
sent by #day sent to
*description Receive list made for
contain

Appointment
made by (#1)date
given to
(#2)hour
Extra payment 0description
#date
*value
*extra_hours
Explanations
 In the entity “Other” we store the other employees like
the maid.
 The “Newsletter” contains information about the
employees, the services they practice and about the
prices for each service.
 By “Service” we understand every requirement of our
clients that the employees are taking care of.
 “Extra payment” means extra hours for an employee
except his daily job.
Mapping
Employees (EPE) Client (CLT)

Key type Optionality Column name Key type Optionality Column name
* id * id
pk * f_name pk f_name
*
* l_name * l_name
* address address
* training phone_no
* phone_no e_mail
e_mail
fk1 * cnr_id fk1 * bil_id
fk2 sly_date fk2 apt_date
* *
epe_date apt_hour
fk3 * fk3 *
Conclusion

 Our product is one of the most important steps to reach

success.
 It will help our client to structure his business in a very
efficient way in order to raise profitability with only a
slight effort and no waste of time.
Description team

 Our team members are Bujoreanu Raluca, Dabija

Gabriela and Gurau Raluca, students at the Informatics
Highschool „Grigore C. Moisil” in Iasy.

 We worked under the coordonation of our Project

Manager, teacher Emanuela Cherchez
We thank you for your attention!

We are looking forward to a future

colaboration!