ER Modeling and Normalizing Data DATA4200
- Subject Code :
DATA4200
Assessment1Information
|
SubjectCode: |
DATA4200 |
||
|
SubjectName: |
Data Acquisition and Management |
||
|
AssessmentTitle: |
ER Modeling and Normalizing Data |
||
|
AssessmentType: |
Report |
||
|
WordCount: |
1000 |
Words |
(+/-10%) |
|
Weighting: |
30% |
||
|
TotalMarks: |
30 |
||
|
Submission: |
Report and lucid chart, 2 submissions required, report 1000words and 2ndsubmission of lucid charts |
||
|
DueDate: |
BySunday April 13 |
||
YourTask
- Read the Assessment Instructions and complete sections (1) (4)
- Consider the rubric at the end of the assignment for guidance on structure and
- Submit your written Report (in Word) via MyKBS by Week
AssessmentDescription
Youhavebeenhiredasadatabasedesignerbyasmallbusinessthatsellsproductsonline.The businesswantstocreatearelationaldatabasetostoreinformationabouttheircustomers, products, orders, andpayments. Theywant tobeabletoviewsalesdata, customer information, and inventory levels.
CaseStudy:
KBSPtyLtdisasmallbusinessthatsellsproductsonline.Thecompanyisexpandingitsoperations and is looking to improve theirdata managementsystems.They currently have a systemthat stores customer information, product information, and order information in separate files, which has becomedifficultto manageasthebusiness grows.Theywant tocreatea relationaldatabaseto store alltheirdatainoneplace,makingiteasiertomanageandreporton.
AssessmentInstructions
- You are required to complete the following tasks:
- Design an entity-relationship model (ERM) for thedatabase using Lucid ChartsModeling tool, and include all required necessary tables, columns, and relationships.
- Normalise the tables to 3rdnormalform(3NF)usingappropriatedatanormalisation
- Create a report outlining your database design and data normalisation
- Your report should be submitted as a Word Document and include the following sections:
- Introduction: A brief overview of the business and the purpose of the
- Entity-Relationship Model: A diagram and explanation of the ERM, including all tables, columns, and relationships using crows feet notation.
- Normalisation: An explanation of the normalisation techniques used and how the tables were normalised to 3NF.
- Conclusion: A summary of your design decisions and any limitations of your database
- Please refer to the assessment marking guide to assist you in completing all the assessment
GenerativeAITrafficLights
Please see the level of Generative AI that this assessment has been designed to accept:
|
Traffic Light |
AmountofGenerativeArtificialIntelligence(AI)usage |
EvidenceRequired |
Thisassessment(?) |
|
Level1 |
This assessment fully integrates Generative AI, encouraging you to harness the technology's full potentialincollaborationwithyourownexpertise. Itwillhighlightyourabilitytodemonstratehoweffectively you can work alongside AI to achieve sophisticated outcomes, blending human intellect and artificial intelligence. |
Your collaborationwith AI must beclearlyreferencedand documented in the appendix of your submission, including all prompts and responses used for theassessment. |
|
|
Level2 |
This assessment invites you to engage with GenerativeAIasameansofexpandingyour creativity and idea generation. It will highlight your ability to complement your original thinkingwiththecapabilitiesofAI.Forexample,through brainstorming and preliminary concept development. |
Your collaborationwith AI must beclearlyreferencedand documented in the appendix of your submission, including all prompts and responsesusedfor the assessment. |
? |
|
Level3 |
This assessment showcases your individual knowledgeandskillsintheabsenceofGenerativeAIsupport. Itwillhighlightyourpersonalabilities.Forexample,to analyse, synthesise, and create based on your own understanding and learning. |
Use of generative AIis prohibited and may potentially result in penalties foracademicmisconduct, including but not limited to a mark of zero for the assessment. |
AssessmentMarkingGuide
|
Report Sections |
Criteria |
|||||
|
F |
P |
C |
D |
HD |
||
|
(1) |
Introduction(2marks) |
NoIntroduction. |
Brief overview of the business stated, but purposeofdatabasenotstated. |
Mostrequirementswereaddressed. |
Allrequirementsaddressed and the aims are clear. |
Allrequirementsaddressedand the aims are clear and contentengaging. |
|
(2) |
ERModel(10marks) |
ERM is incorrect or incomplete, contains significant errors or omissions, or does not accurately representtheentities and theirrelationships. |
ERM is generally correct but contains someerrors,omissions, or ambiguities thatcould impact the functionality of thedatabase. |
ERMisaccurate,complete, and clearly represents the entities and their relationships, meets basic database requirements. |
ERMisaccurate,complete, and demonstrates a good understanding of the business requirements. |
ERM is accurate, complete, and demonstrates exceptional understandingandinsightintothe business requirements. |
|
(3) |
Accuracy and Completeness of DataNormalisation (10 marks) |
Datanormalisationis incorrect or incomplete,lackskey details, or contains significant errors that could impact the functionality or integrity of the database. |
Data normalisation is generally correct but lacksdetailorcontains someinaccuraciesthat could impact the functionalityorintegrity of the database. |
Data normalisation is accurate, detailed, and complete,andmeetsbasic data normalisationrequirement. |
Data normalisation is accurate, detailed, and demonstrates a good understanding of data normalisationtechniquesand their application to the business requirements. |
Datanormalisationisaccurate, detailed, and demonstrates exceptionalunderstandingand insight into data normalisationtechniques. |
|
(4) |
Conclusion(4marks) |
NoConclusion. |
A summary that does notaddressallofyour design decisions and anylimitationsofyour database design. |
Asummarythataddresses most/all of your design decisions and any limitationsofyourdatabase. |
Asummarythataddressesall of your design decisions and any limitations of yourdatabase. |
An engaging and concise summarythataddressesallof yourdesigndecisionsandany limitations of your database. |
|
(5) |
QualityofReport (4 marks) |
The report is incomplete or lacks keysections,contains significant errors or omissions, or doesnot meet basic reportrequirements. |
The report is generally complete but lacks detail or contains some inaccuracies, is poorly structured, or does not effectivelycommunicate the database design and data normalisationdecisions. |
The report is accurate, detailed, and well structured,communicates the database design and data normalisation decisions effectively. |
The report is accurate, detailed, and insightful,shows a good understanding of the database design and data normalisation decisions and their impact on the businessrequirements,andis well-structuredandeffectively communicates the information. |
The report is novel, accurate, detailed, and insightful, shows a deep understanding of the database design and data normalisationdecisionsandtheir impact on the business requirements, and is well- structured and effectively communicates the information. |