CHC5049 Database Coursework 1: Define Data Application
CHC5049 Database Coursework 1.
Learning Outcomes
The two coursework of this module address the following learning outcomes:
-
- Use SQL and XML to define data applications appropriate to a specified problem.
-
- Use a conceptual modeling language to specify and analyze data requirements and apply
database design principles to map system requirements to an efficient (e.g., normalized)
database.
-
- Explain and design transaction-based processing in database systems.
-
- Exploit techniques for storing and querying XML data.
COURSEWORK OUTLINEA leading multinational corporation with a diverse portfolio of businesses is seeking to enhance its data management and integration capabilities by developing a comprehensive online platform to manage employee and organization information. The company has a vast workforce spread across multiple regions, departments, and subsidiaries, making it crucial to have a centralized system for efficiently managing employee and organizational data. The company has adopted the XML format for efficient data management. They require the information to be consolidated into a single XML document structured by the organization to streamline the process further. Within each organization element, the employee details should be included, ensuring seamless organization and accessibility of the data.
The company is now looking to employ the advantages of the JSON format to enhance data management, interoperability, and seamless integration with various systems across the company. Accordingly, the given information should also be consolidated into a single JSON document following the above criteria for further in-depth analysis and exploration.
DELIVERABLES [20 marks total]
You have been asked to:
1) Spot the errors in the given ‘Organizations_sample.dtd’ file. You should provide:
a. b. c.
An image of the DTD with the errors circled in red, along with a brief note of each
error. The file should be called ‘1_DTD_sample_Errors.jpeg’.
A corrected version of the external DTD file. The file should be called
‘2_Corrected_sample.dtd’.
Provide a screenshot called ‘3_Validation_sample.jpeg’ after validating the ‘Organizations_sample.xml’ file against the corrected external DTD through a validator, proving that they validate with no errors.
2) Two XSLT transformation and output files. One to export the XML data and the other to export the JSON data. Your XSLT files must be correctly formatted and be able to run against the XML files (‘Organizations.xml’ and ‘Employees.xml’) supplied by the company. The following specifications must be followed:
a. XML:
-
The XSL file must be called ‘4_Transformation_to_XML.xsl’.
-
It must use XSLT v1.0 as requested by the company.
-
You have to provide comments to explain your reasoning and work.
-
The XML output file must contain a root element called ’eCorporation’.
-
The XML file should contain the organization and the relevant employee data
ordered by the country and then by the organization.
-
The XML file that is provided must be called ‘5_Output.xml.’
-
A related external DTD must be automatically referenced in the output.xml file and not be manually added.
-
DTD Details:
Create a new external DTD file that describes the output XML file. So that the company can validate the XML output file and ensure it is correct. The DTD must adhere to the following requirements:
1. It must follow a logical structure of the data as follows:
eCorporation Country
Organization
... Organization details
Employees
... Employee details
Employees
... Employee details
Organization
... Organization details
Employees
... Employee details
Employees
... Employee details
Country Organization
... Organization details Employees
...
... Employee details Employees
... Employee details
-
Well-written external DTD structure.
-
Logical naming convention of elements and attributes.
-
Nested elements correctly declared.
-
At least one attribute should be used.
-
The DTD file must be called ‘6_Structure.dtd’.
-
It should be validated against the output XML file through a validator, and
a screenshot called ‘7_Validation_XML.jpeg’ should be attached, showing that they validate with no errors.
b. JSON:
-
The XSL file must be called ‘8_Transformation_to_JSON.xsl’.
-
You have to provide comments to explain your reasoning and work.
-
Ensure that the content of the JSON file accurately represents the data from
the XML files and save the converted file as '9_Output.json'.
-
Validate the JSON file, capture a screenshot of the validation, and save it as
'10_Validation_json.jpeg' to demonstrate that the file has no errors.
Submission bundle
The specification for the structure of the submission is as follows:
-
A ZIP file uploaded via the online portal.
-
The ZIP bundle must be named ‘coursework1_StudentID.zip.’
-
File names must be EXACT, including the specified file extension.
