Data Science: AAS Database Implementation Report - Assessment 2024

This report provides a detailed overview of the AAS (likely referring to a specific system or application, but not defined in the assignment brief) database implementation. It covers key aspects such as functional dependencies, normalization up to the third normal form, and the mapping of an ER diagram. The report includes examples of SQL queries designed to retrieve specific data, such as services not requiring part replacements, mechanics with high labor charges, and clients with multiple vehicles. The report highlights learning points, including database reporting and SQL queries. While the report doesn't highlight major difficulties, it mentions minor issues with validation checks. The conclusion summarizes the database's functionality and normalized parameters, referencing supporting materials like ER diagrams and normalization techniques, referencing external sources like Lucid Software and teach-ict.com.

Student ID –
Date -
Module Tutor -
1 | P a g e

Implementation Report
Introduction
The AAS database implementation is being described in the report. All details about
functional dependency and normalization is being shown in the report.
Normalization
Mapping of ER Diagram to Third Normal Form
(Lucid Software Inc. 2015)
Functional Dependency
Employee
Employee (EmployeeID, EmployeeName, Street, City, State, Postcode, Phone)
Information of more employees may be similar e.g. Name, Address etc. Therefore, to
find the specific employee, a unique key is required and EmployeeID is working as a
unique key to find an employee.
EmployeeName  EmployeeID
State  EmployeeID
2 | P a g e

PartType
PartType (PartID, PartDescription, PricePerUnit)
Information of more parts may be similar e.g. price, description etc. Therefore, to find
the specific part, a unique key is required and PartID is working as a unique key to
find an employee.
PricePerUnit  PartID
Normalisation Demonstration
The third normalisation process is achieved by the following rules-
- All tables are containing unique data.
- Al tables are containing primary key.
- Transitive dependency should not be shown in any table.
Tables Employee and PartType are in third normal form as shown below-
Employee (EmployeeID, EmployeeName, Street, City, State, Postcode, Phone)
PartType (PartID, PartDescription, PricePerUnit)
(teach-ict.com n.d.)
3 | P a g e

SQL Queries
Query 1
Query 1 is presenting the services which do not need the replacement of any type of
part.
Query 2
Query 2 is presenting the mechanics whose labour charge is greater than 300.
Query 3
Query 3 is presenting the highly costly service.
Query 4
Query 4 is presenting the total number of complaints done by each client.
4 | P a g e

Query 5
Query 5 is presenting the client who has more than one Ford vehicle.
Query 6
Query 6 is presenting the last 3 months services.
Summary Report
5 | P a g e

Learning Points
There are lots of learning features in the assignment like below-
- Database report
- SQL Queries
Complex Requirements
There are not so much difficulties or complexities in the assignment. But I found very
small issues in the following tasks-
- Database report
- Validation checks
Conclusion
The report is nothing except database implementation of AAS. Complete database
detail with functionality and all important features is mentioned in the report. The
report is showing database detail with all normalized parameters.
References
Lucid Software Inc. (2015), ER Diagram Symbols and Meaning, [Online]. Available:
http://www.sparxsystems.com/enterprisearchitectuserguide/modelinglanguages/
dataflowdiagrams.html. [Accessed: 18-September-2017]
teach-ict.com (n.d.), Third Normal Form, [Online]. Available:
http://www.teach-ict.com/as_a2_ict_new/ocr/AS_G061/315_database_concepts/
normalisation/miniweb/pg9.htm. [Accessed: 18-September-2017]
6 | P a g e