Avan’Garde Beauty Saloon Project Project manager:Emanuela Cerchez Powered by: Raluca,Gabriela and Raluca Giving shape to your dreams.

Slides:



Advertisements
Similar presentations
ER Modeling Case Studies
Advertisements

More Diagramming & Practice with Relationship Modeling
Welcome to IDBS Center Innovative Data Base Solutions presents: Comat Auto Service Project Project Manager: Emanuela Cerchez.
ITSF STORE BUSINESS SOLUTION PRESENTATION. STORE MODULE INCLUDES: Material Management Purchasing Components Handling Shipments Receiving of parts Store.
Welcome to EXPRESS Your Online Enrollment Tool Guided Tour Please use the Navigation Buttons at the bottom of each screen to proceed through the tour and.
Pro Shop Working at pro shop is no walk in the park Very tedious Offers variety of services Renting out different items Selling apparel Encounter many.
Chit Fund Company Flowchart.
Dimensional Modeling.
ER Modeling Case Studies
ER Modeling Case Studies
Training Presentation E-Learning Test Request. Objective Provide Test Center staff members with information about the e-learning test request process.
Ideal Practice Workflow Revenue Maximization and Cost Efficiency Contact us : 2222 Morris Ave. 2nd Floor, Union, NJ Ph: (908)
Mobile Web products Brought to you by. Background Sentido started in 2004 as a web software development company (surveys) Soon started venturing into.
Khuthala Agency Pty Ltd
Draw an ER Diagram for the following (record any assumptions):
Mapping an ERD to a Relational Database To map an ERD to a relational database, five rules are defined to govern how tables are constructed. 1)Rule for.
Fidela, another part-time stylist at Creative Lines, greets her new client, Cassandra Martin. Cassandra shows Fidela a picture of her desired hairstyle.
“Pleasure in the job puts perfection in the work” Aristotle The team: Adriana Velicu Alexandru Diaconu Gabriel Musteata Project manager: Emanuela Cerchez.
Database Design Chapter 2. Goal of all Information Systems  To add value –Reduce costs –Increase sales or revenue –Provide a competitive advantage.
Employee Central Presentation
Data modeling using the entity-relationship model Winter 2006Ron McFadyen Entity-relationship model (ER model) P. 49: “This model and its variations.
Data Model Examples USER SPECIFICATIONS.
Mapping ERM to relational database
Billing Agent. Pre-Application Checklist Introduction to IMPACT and Key Terms Application Process Starting an Application The Business Process Wizard.
Google – Local Business Center Set-up Instructions September 2010.
VIBRANT MEDIA Online Marketing & Event Administration Solutions 11 March 2009.
Careers Careers/ telephoning I. The term career is usually understood as: The particular occupation for which you are trained The sum of your life experiences.
ER Modeling Case Studies
HRMS Basics. Overview What is HRMS? HRMS Functions and Features Concepts and Terms Position/Incumbent/Funding Relationship Funding Documents Security.
Serenity Day Spa & Salon est Presented By: Angie Galjour Melissa Hall.
Conceptual Modeling with ER Diagrams Peter Chen introduced ER Diagrams.
Advanced Entity Relationship Concepts. Advanced Concepts UIDs Intersection Entities Recursive Relationships Roles Subtypes Exclusivity Historical Fan.
SMART Agency Tipsheet Staff List This document focuses on setting up and maintaining program staff. Total Pages: 14 Staff Profile Staff Address Staff Assignment.
A Beauty Salon Management Key Features of The Product:  Masters  Employee salary management  Product stock management  Services and package management.
Database Design Sections 4 & 5 Subtype, Supertype, Mutually exclusive, non-transferability, transferable, 1:1, 1:M, M:M, Redundant, Intersection entity,
Practice of ER modeling
Key Features of The Product :
Mapping from Data Model (ERD) to Relational Model
Advertising. Why Advertise? To generate funds To give others information about products and services they want and will use To improve your advertiser’s.
SQL Structured Query Language Programming Course.
1.  An introduction to data modelling  The purpose of data modelling  Modelling data relationships 2.
Presented by:- Ishir Shah Varun Desai Hima Bindhu.
1. Objectives At the end of this chapter you should be able to:  Discuss the use and features of a data model  Define the terms entity and attribute.
IST 220 – Intro to Databases Analyzing Data Needs.
3 & 4 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Keys Consists of one or more attributes that determine other.
Elk’s Lube Express Elk’s Lube Express Jeremy Miller Brandon Rich Roxana Berrondo.
Mtivity Client Support System Quick start guide. Mtivity Client Support System We are very pleased to announce the launch of a new Client Support System.
COLORS Day Care Karina Izaguirre Jake Morales Summer 2009.
Entity-Relationship Model Chapter 3 II COSC 457 Sungchul Hong.
Database Design – Lecture 6 Moving to a Logical Model.
Mobile Web products Brought to you by. This product is sold and implemented by a Franchise and Agent network.
ABCN… the missing piece. ABCN Virtual… We’re all ‘Instantly Global’ “Three out of four clients can’t be wrong!” ABCN market data.
CSCI 6962: Server-side Design and Programming Shopping Carts and Databases.
Howard Paul. Sequential Access Index Files and Data File Random Access.
Al-Imam University Girls Education Center Collage of Computer Science 1 st Semester, 1432/1433H Chapter 10_part 1 Functional Dependencies and Normalization.
Online | classroom| Corporate Training | certifications | placements| support CONTACT US: MAGNIFIC TRAINING INDIA USA :
1 Database Design Sections 6 & 7 First Normal Form (1NF), Second Normal Form (2NF), Unique Identifiers (UID), Third Normal Form (3NF), Arcs, Hierarchies.
Dept. of Computer & Information Sciences
Applicant HR Manager Job Offer Hiring Manager _ ID Name e - Mail
ER Modeling Case Studies
Presented by: Amanda Lester Jessica Hall Kim Vuong Christina Geraci
Kojima JAPANESE STEAK HOUSE
OPERATIONS 102: What Needs to be in Place to Grow to the Next Level
ER Modeling Case Studies
ER Modeling Case Studies
Mapping an ERD to a Relational Database
SALES RECEIPT Downloaded from
INVOICE Downloaded from
Mapping an ERD to a Relational Database
COMPANY PATH NAME Windows Application Software Providing worlds best Pathology Management or Laboratory Management software.
Presentation transcript:

Avan’Garde Beauty Saloon Project Project manager:Emanuela Cerchez Powered by: Raluca,Gabriela and Raluca Giving shape to your dreams

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: 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, 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 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 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.

Employee #id *f_name *l_name *adress *training * phone_no 0e_mail Secretary Other Stylist Manager Center #id *name *address *phone_no have work in Client #id *f_name *l_name 0phone_no 0adress 0e_mail Appointment (#1)date (#2)hour 0description Newsletter #day *description sent by Receive list be on contain send make made by sent to contain Bill #id *value *em_name *date *hour pay paid by make made by Activity have made for do done by Service #id *type *price include correspond to Service list be on contain be on contain Product #id *name *brand *exp_date *price 0description Distributor #id *name *address *phone_no 0e_mail bring brought by use used in Salary #date *value receive correspond to Extra payment #date *value *extra_hours receive given to Transaction bill make made by receive given to supervise supervised by

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) Key type Optionality Column name pk * id ********** f_name l_name address training phone_no e_mail fk1 * cnr_id fk2 * sly_date fk3 * epe_date Key type Optionality Column name pk * id **** f_name l_name address phone_no e_mail fk1 * bil_id fk2 * apt_date fk3 * apt_hour Client (CLT)

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!