Replenish & Restore
& UWS | Replenish & Restore Database Design | COMP09049: Project |
Student: B00209572
12/12/2012
|
Contents Introduction 3 Replenish and Restore Research 3 Requirement conclusions 3 Conceptual Entity Diagram 4 Database Systems Research 6 Normalisation 6 Logical Entity Diagram 7 Database Relational Schema Description 8 Table Descriptions 10 Data Dictionary 12 ASP.NET Data Entry Web Application 19 Screenshots 19 Home – Table List 19 Appointment 20 AppointmentPurchaseType 21 Client 22 Doctor 23 Practitioner 23 Product 24 Treatment 24 TreatmentAppointment 26 TreatmentQuestion 26 SQL Statements 27 Test 1: 27 Test 2: 28 Test 3: 28 Test 4: 29 Test 5: 29 Test 6: 29 Test 7: 30 Test 8: 30 Test 9: 30 Test 10: 30 Test 11: 31 Test 12: 31 Test 13: 31 References 32
Introduction
This report specifies the database design and implementation required for Replenish and Restore.
Replenish and Restore is a company offering body and skin treatments, including skin peels, sport massages, Botox, derma filers and other remedial therapies.
A collection of paper based documents were provided as the source for creating a database. The documents consisted of questionnaire and consultation forms, treatment advice and treatment appointment records. The website at http://www.replenishandrestore.co.uk was also used to gather information relevant to designing a database.
The database supports a wide variety of data, primarily intended to be used in an appointment booking system. It holds client specific details, appointment details and product and treatment details. The limitation of the database system is that it does not fully support a payment system e.g. it does not hold client credit card details, but functionality can be added by linking into the existing appointment and product purchase tables.
The physical database was developed using a Microsoft SQL Server 2008 R2, running on
Student: B00209572
12/12/2012
|
Contents Introduction 3 Replenish and Restore Research 3 Requirement conclusions 3 Conceptual Entity Diagram 4 Database Systems Research 6 Normalisation 6 Logical Entity Diagram 7 Database Relational Schema Description 8 Table Descriptions 10 Data Dictionary 12 ASP.NET Data Entry Web Application 19 Screenshots 19 Home – Table List 19 Appointment 20 AppointmentPurchaseType 21 Client 22 Doctor 23 Practitioner 23 Product 24 Treatment 24 TreatmentAppointment 26 TreatmentQuestion 26 SQL Statements 27 Test 1: 27 Test 2: 28 Test 3: 28 Test 4: 29 Test 5: 29 Test 6: 29 Test 7: 30 Test 8: 30 Test 9: 30 Test 10: 30 Test 11: 31 Test 12: 31 Test 13: 31 References 32
Introduction
This report specifies the database design and implementation required for Replenish and Restore.
Replenish and Restore is a company offering body and skin treatments, including skin peels, sport massages, Botox, derma filers and other remedial therapies.
A collection of paper based documents were provided as the source for creating a database. The documents consisted of questionnaire and consultation forms, treatment advice and treatment appointment records. The website at http://www.replenishandrestore.co.uk was also used to gather information relevant to designing a database.
The database supports a wide variety of data, primarily intended to be used in an appointment booking system. It holds client specific details, appointment details and product and treatment details. The limitation of the database system is that it does not fully support a payment system e.g. it does not hold client credit card details, but functionality can be added by linking into the existing appointment and product purchase tables.
The physical database was developed using a Microsoft SQL Server 2008 R2, running on
References: 1. Dave, P. (2009) SQL Server Journey with SQL Authority. blog.sqlauthority.com [Online]. Available at: http://blog.sqlauthority.com/2009/09/09/sql-server-difference-between-sql-server-express-and-mysql/ 2. Didiano, D. (2012) Microsoft SQL vs MySQL: How to Choose Between Them. ultraunboxing.com [Online]. Available at: http://ultraunboxing.com/microsoft-sql-vs-mysql-how-to-choose-between-them/ 3. Emasri, R. and Navathe, S.B. (2011) Fundamentals of Database Systems (6th ed). Addison-Wesley: Boston 4. Ketabchi, M.A., Mathur, S., Risch, T. and Chen, J. (1990) Comparitive Analysis of RDBMS and OODBMS: A Case Study. user.it.uu.se [Online] Available at: http://user.it.uu.se/~torer/publ/COMPCON1990.pdf 5. Kolahi, S. and Libkin, L. (2006) On Redundancy vs Dependency Preservation in Normalization: An Information-Theoretic Study of 3NF. www.cs.toronto.edu [Online]. Available at: http://www.cs.toronto.edu/~solmaz/docs/pods176-kolahi.pdf 6. Lin, C. (2003) Object-Oriented Database Systems: A Survey. users.soe.ucsc.edu [Online] Available at: http://users.soe.ucsc.edu/~lcx/courses/cmps277/cmps277-project.pdf