The database system is one of the information system components that play essential roles in managing the vast data that the file system cannot control. The system will be crucial for Dante, an organization offering beauty services to a wide range of customers. Currently, the organization has no software or database system in place to manage most of its crucial activities, which has led to difficulties in the management function. The project shall give a solution to the issue through the implementation of a database management system.

Project objectives

Specific Objective

To develop customer appointments and Billing database management system that will help the organization in the management of records.

General objectives

· To conduct a study on the best way to implement the solution to the problem through the use of the database management system.

· To collect the system requirements that will be critical for the development of the database management system.

· To analyze the requirements about the system and furnish them for proper implementation of the system.

· Develop the conceptual data diagram that will lead to the implementation of the system.

· To test the database system

· Write the SQL statements to query the database management system

Feasibility study and Analysis

The feasibility study is one of the crucial activities conducted before arriving on the decision to implement a project. The activity goals are to find out the viability of the project before implementation or execution. The project team members ought to consider several factors surrounding the concerned scheme and other external factors having an impact on the project.

Some of the goals of the feasibility study include. First, to gain an understanding of the features of the project, concepts, and plan. Second, feasibility creates awareness of potential issues anticipated in the project implementation process. Finally, a feasibility study helps to determine the viability of the project after the consideration of all the significant factors. The following consists of the factors that the project will consider.

Economic Factors

The economic study feasibility study determines whether the project is viable, considering the prevailing economic factors. It is essential to assess the economy of the business to determine if it has enough resources to develop and implement the project xxxx. Also, the factor finds out the effects of the project on its finances after the implementation of the database system project.

Currently, Dante has enough resources to fund the project; the business offers the best services presently as compared to other firms in the industry, which has resulted in substantial revenues. Also, the cost of operating the database system is minimal as compared to the file system currently in place that is prone to errors and damages. Therefore, the implementation of the project shall greatly help Dante to manage its resources and activities effectively result in the generation of more revenues.

Technical factor

Though Dante does not have any computers to implement the project, the financial resources that it generates are far much enough to buy the equipment, which consists of software and hardware. The project will not require expensive resources that will strain the financial capability of the organization.

Also, the database will require the organization to hire a database administrator will foresee the activities in the system after implementation. However, the anticipated benefits that t organization will realize shall enable it to meet the cost associated with hiring this technical employee.

Legal Factors

The legal factors that affect the implementation of the database system are critical, since if the organization breaks will lead to detrimental effects that might drain its financial resources. There are not current issues associated with the database implementation that might affect its application. However, the organization should adhere to the legal requirements that govern the use of the system.

Scheduling

It is essential to consider the time factors or the period that the project will take to its implementation. Time has direct proportional to the project cost. Therefore, if the time increases, the expenses of the project will also rise.

This project will not take a considerable amount of time if all the requirements and resources are available. Therefore, on availing or the funds, the project will take approximately one month to implement, which viable considering the cost the whole process will take.

Cost and Time Estimates

The size of the project determines the cost and the time it will take to implement it. The project manager has to come up with the estimates and present them to Dante’s management fo approval. The following consist of the time and costs estimates of the project.

Project Cost Estimates

The costs are subdivided into different categories according to various cost resources and services offered in the process. The following are different costs associated with the project.

Project Activity or Resource	Cost
Labor	200
Software Resource	200
Hardware	350
Database Development	500
Maintenance	250

Project Time Estimates

The time that the project takes for implementation should be reasonable enough considering the resources available and the cost of each activity in the process. The following are some of the events and their estimated duration. The time excludes the weekends.

Project Activity	Duration (Days)
Requirement Gathering Analysis	2
Database Design	5
Implementation	5
Testing and Evaluation	10
Deployment	2

Project Justifications

The database project is crucial for the organization because it solves the issues the organization is currently going through due to the ineffectiveness of the current system. The following justify why Dante requires the system.

First, the organization, through the current system, has experienced lots of problems keeping the records of the customers. Therefore, it brings issues associated with categorizing so that they can serve them effectively. The system will enable us to understand the customers and the services that these customers want.

Second, the customers make appointments to avail time of service might. The current file system has no functionality to schedule the appointments of the client. Some of the clients end up missing the appointments, which make the organization to lose customers and resources.

Third, billing has is another issue facing the current system. It is challenging for the management accounts for payment made by clients and the cost of inputs. The database system shall, therefore, help the organization to keep records regarding different bills incurred.

Lastly, Dante has experience issues regarding the management of its employees. Therefore, it has experience issues regarding the control of the employees. For instance, the problems have affected the process of accomplishing payments to its staff, which might lead to unaccounted for amounts.

System Design

Conceptual Database Design

Before the actual development of the database, it is important to come up with concept of its implementation. The is process is where we come up with conceptual design of the product.

Database Entities

The relation database is composed of entities which represent it tables. The entities interact with each other in the database to perform different action. The relationship among the entities show how each is related to each other and when writing queries to extract and manipulate the data. The following are some of the entities that our system will have.

Customer Entity

image1.emf

CustomerCustomer_IDPKCustomer_nameCustomer_telephoneBilling

The customer entity records the information regarding the customer who wants Dante’s services. The data or attributes that this entity will record include the customer ID, Age, telephone Number, and Billing information.

Employee Entity

image2.emf

EmployeeEmployee_IDPKEmployee_nameTelephoneCustomer

The entity will record the information concerning the employees in the organization. The employee servers the customer, deals with billing information’s and confirms appoints from the customers. The diagram below. Show the employee entity.

Appointments Entity

image3.emf

ApointmentAppointment_IDPKAppoinment_DateEmployeeCustomer

The appointment entity is used to records the appointments made by the clients. The information that is included in this entity include the information customers information and employee information. Therefore, the entity is related to the customer and employee entities.

Billing Entity

image4.emf

BillingBilling_IDPKCustomerEmployee

The billing entity records the information regarding the bills made in the process offering services in the organization. the information includes in this entity include the customer information of whom the service is offered, the employee serving the customer, and the information regarding billing.

These entities record the crucial information regarding the services offered by Dante Beauty. It through this information that the organization will be able to offers different services in the organization without any issue. For example, if the client makes call to of the employee to make appointments, he or she will be giving information regarding cost of services they wants and the available time to be scheduled. Also, it will be possible to track different billings to identify the responsible customers and clients (Tomoda, Isoda, & Ushijima2019). Lastly, the system allows the management to know the number of appoints and decide on whether or not they should her contractual employee based on the bulk of work.

Entity Relationship Diagram

An entity relationship diagram is a conceptual representation of the information captured in the databases and how different entities relates to each other. The diagram helps the database designers to describe the overall design of the database concisely and accurately xxxx. The database designer can easily transform the diagram into relation schema which hasten the design process.

The diagram has entities which as attributes thus writing queries to deal with the information in the databases will be an easy process. the following is the entity relationship diagram for the organization.

image5.emf

EmployeeCustomerBillingAppointmentEmployee_IDPKEmployee_NametelephoneCustomerFKCustomer_IDPKCustomer_TelephoneCustomer_TelphoneBilling_IDPKCustomerFKEmployeeFKappointment_IDPKAppointement_dateCustomerFKEmployeeFK

The entity relationship diagram was designed to prevent anomalies associated with the database systems. These anomalies can affect the data integrity as well as the security. The database design in our case has removed the anomalies through the following ways. First, all records will be containing data; there will be no null entry. Secondly, the database also has implemented accuracy regarding to the data by ensuring consistency; the approach prevents the perceived data integrity issues. Thirdly, the database will not allow the existence of the similar data in the entire database, which will avoid the data redundancy in the database(Kadivar, 2015).

The database will be therefore free from any kind of anomalies that might arise when it has been deployed to a working environment. The team will conduct vigorous test to ensure that the anomalies are resolved in the database system.

Database SQL Statements

The database operates through SQL statements that are designed to perform certain task in the database. There different language with different functions used in the database. These languages include Database Manipulation Languages (DML), Database Definition Language (DDL), Database Control Language (DCL), and Transaction Control Language (TCL).

The DDL is used for creating the database schemas, which are the skeletal structure represent the logical view of the database (W3schools, 2020). The DDL and other database language operates through the use of SQL statements. The following statements are the DDL which create the database and table schemas of the Dante’s Database

Statement to Create the Database

create database dante_database;

Statement to create the tables for the database

Statement to create customer table

create table customer (

customer_ID INT (255),

customer_Name TEX (255),

cutstomer_telephone (255)

PRIMARY KEY (customer_ID)

);

SQL Statement to create Employee table

create table employee (

employee_ID INT (255),

employee Name TEXT (255),

customer (255),

Telephone (255)

PRIMARY KEY (employee_ID)

FOREIGN key (customer) REFERENCES customer(customer_ID)

;

SQL statement to create Billing Table

create table billing (

billing_ID INT (255),

employee INT (255),

customer INT (255),

PRIMARY KEY (billing_ID)

FOREIGN key (customer) REFERENCES customer(customer_ID)

FOREIGN key (Employee) REFERENCES customer (Employee_ID)

);

SQL statement to create appointment table

create table appointment (

appointment_ID INT (255),

employee INT (255),

customer INT (255),

PRIMARY KEY (appointment_ID)

FOREIGN key (customer) REFERENCES customer(customer_ID)

FOREIGN key (Employee) REFERENCES customer (Employee_ID)

);

Database Administration

The database administration is concerned with making of the database to perform some specific task. We use the DML to query the data to perform certain operations with data such the extraction of the data. The data manipulation is the main target of the database so that it retrieves the desired information during regular work time.

SQL statements to support the efficient execution of transactions

The following are some of the SQL statements to perform some of the crucial function.

i. The SQL statement to retrieve information from the customer name, appointment date, and billing amount.

SELECT customers. customerName, appointment.appointment_date, billing.amount FROM customer INNER JOIN Customers ON billing.customer_id=customers.customer_id;

ii. The SQL statements to retrieve billing information with the associate customer

SELECT customers. customerName, billing. amount FROM customer INNER JOIN Customers ON billing.customer_id=customers.customer_id;

iii. SQL statement to insert data into the customer table

INSERT INTO Customers (Customer_ID, customer_name, billing, Customer-telephone) VALUES ('234578', 'Tom B. Erichsen', '20', '1235456');

Backup Recovery Model

It is important to backup the data so that they can be retrieved back in case the data in the local database is lost. The retrieval process of the data happens through the use of the backup recovery model. The choice of the model depends on the data that an organization is targeting. The Dante database shall implement the full recovery model (Martin et al., 2017).

image6.emf

CustomerCustomer_IDPKCustomer_nameCustomer_telephoneBilling

The full back recovery plan is the best since it retrieves all the data that had been ack. Therefore, no single data will be compromised or lost.

References

Martin, C. B., Poyatos, J. M., Sierra, M. R., & Pérez, A. S. (2017). Performing data mining operations within a columnar database management system. 9,798,783. Washington, DC: U.S.

Tomoda, A., Isoda, Y., & Ushijima, K. (2019). Database management system and method

Washington, DC: U.S. Patent and Trademark Office.

Kadivar, M. (2015). Entity relationship diagram approach to defining cyber-attacks (Doctoral dissertation, Carleton University).

W3schools. (2020). MySQL what is DDL, DML and DCL? Retrieved from https://www.w3schools.in/mysql/ddl-dml-dcl/

� EMBED Visio.Drawing.15 ��

EmployeeEmployee_IDPKEmployee_nameTelephoneCustomer

BillingBilling_IDPKCustomerEmployee

ApointmentAppointment_IDPKAppoinment_DateEmployeeCustomer

Employee Employee_ID int FK PK Employee_name int FK PK Telephone int FK PK Customer int FK PK

Billing Billing_ID int FK PK Customer int FK PK Employee int FK PK

Employee Customer Billing Appointment Employee_ID int FK PK Employee_Name int FK PK telephone int FK PK Customer int FK PK Customer_ID int FK PK Customer_Telephone int FK PK Customer_Telphone int FK PK Billing_ID int FK PK Customer int FK PK Employee int FK PK appointment_ID int FK PK Appointement_date int FK PK Customer int FK PK Employee int FK PK M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4

Apointment Appointment_ID int FK PK Appoinment_Date int FK PK Employee int FK PK Customer int FK PK

Customer Customer_ID int FK PK Customer_name int FK PK Customer_telephone int FK PK Billing int FK PK