0% found this document useful (0 votes)
16 views6 pages

Csi-7-Dat Coursework 2 Nov2024final

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views6 pages

Csi-7-Dat Coursework 2 Nov2024final

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Coursework Specification

CW2_Specification_CSI_7_DAT_24/25

Read this coursework specification carefully, it tells you how you are going to be
assessed, how to submit your coursework on-time and how (and when) you’ll receive
your marks and feedback.

Module Code CSI-7-DAT


Module Title Data Management
Lecturer George Ubakanma
% of Module Mark 60%
Distributed 22 Nov 2024
Submission Method Submit online via this Module’s Moodle site
Main submission 18:00 on 13 Dec 2024
Submission Deadline
Late submission 18:00 on 20 Dec 2024
Feedback and provisional marks will be available in the
Release of Feedback
Gradebook on Moodle within 15 working days of
& Marks
submission.

Coursework Aim:
To demonstrate understanding of the module subject matter and the ability to
apply it, including critical analysis and judgement. This coursework is based
on individual submissions.
Design, Implement, Test, Report on a prototype data warehouse.
Produce a single MS Word (doc/docx) format file containing all deliverables.
Using Kimball’s Dimensional Modelling Technique design a suitable Star
Schema for the specified data sets. Then using MS SQL Server and SSIS do
the necessary ETL operations, and SQL query tasks (programming
functionality) must be implemented. Finally complete with a dashboard built
utilising the 4 query tasks in Tableau or Power BI. Finally, a brief 10 min video
demo of all practical Tasks must be recorded using MS Teams (or similar).
Include the live URL to the Video Demo in your final report. Ensure your lab
tutor can access the video.

Coursework Details:
Type: Report on Prototype Database Development task
Word Count: No formal word count is required but no more than 3000 words
would be expected.
Footnotes will not count towards word count totals but must only be
used for referencing, not for the provision of additional text. The
bibliography will not count towards the word total.

Presentation: ▪ Any quoted material must be referenced, and a bibliography


provided, however, formal referencing is not an assessed criterion

1
– however the identification of technical resources consulted in
order to solve specific described problems is an assessed
criterion (see main task specification)
▪ Work must be submitted as a Word document (doc/docx)
▪ Course work must be submitted using Arial font size 11 (or larger if
you need to), with a minimum of 1 line spacing
▪ Your student number must appear at the front of the coursework.
Your name must not be on your coursework.

Referencing: Harvard Referencing should be used, see your Library Subject Guide
for guides and tips on referencing.

Regulations: Make sure you understand the University Regulations on expected


academic practice and academic misconduct. Note in particular:
▪ Your work must be your own. Markers will be attentive to both
the plausibility of the sources provided as well as the
consistency and approach to writing of the work. Simply, if you
do the research, practical and reading, and then write it up on
your own, giving the reference to sources, you will approach the
work in the appropriate way and will cause not give markers
reason to question the authenticity of the work.
▪ All quotations must be credited and properly referenced.
Paraphrasing is still regarded as plagiarism if you fail to
acknowledge the source of the ideas being expressed.

TURNITIN: When you upload your work to the Moodle site it will be
checked by anti-plagiarism software.

Learning Outcomes
This coursework will fully or partially assess the following learning outcomes for this
module.
• On completion of the module you will be able to:
o To develop an in-depth, critically evaluative knowledge of skills
required in a Data Management role.
o carry out a critically evaluative review of current Data Management
literature/software/process developments, and research.
o develop skills as self-directed learner who can set goals and select
appropriate knowledge, skills, etc...
o specifying tools/techniques for a particular Data Management purpose

Assessment Criteria and Weighting


LSBU marking criteria have been developed to help tutors give you clear and helpful
feedback on your work. They will be applied to your work to help you understand
what you have accomplished, how any mark given was arrived at, and how you can
improve your work in future.

Full details of the criteria, interpretation, weightings and rubric to be applied are
included in the main task specification below.

How to get help


We will discuss this Coursework Specification in class. However, if you have related
questions, please contact me:
George Ubakanma: [email protected] as soon as possible.

2
Resources
Course materials and Tutorials linked to from the exercises are expected to be the
main resources required for this assignment.

Quality assurance of coursework specifications


Coursework specifications within CSI division go through internal (for new modules
with 100% coursework also through external) moderation. This is to ensure high
quality, consistency and appropriateness of the coursework as well as to share best
practice within the CSI division.

Details of the moderators for this coursework specification are below:

Moderated (internal) Brahim


Moderated (CSI lead) George
Signed off by (HoD/DHoD) George

----------------For Internal use by CSI lead only-----------------


Changes required to CW? No *
Examples of good practice

* if changes are required, moderator to complete the below:


List of changes required N/A
ML Response [ML response, date]
Moderator Response [ML response, date]

3
CSI_7_DAT: Coursework 2
Coursework Nov 2024 – Dec 2024

Assignment Tasks: MARKING SCHEME AND TASKS


Complete ALL tasks listed below. Every task must be accompanied by a brief narrative (approx
1 side A4 per task) discussing the task production (your attempt success/failures)
TASK Mark Weight TOTAL

1 Subject Knowledge - Design


Use Kimball’s Dimensional Modelling Technique to design a schema diagram
(star/snowflake) data model for a prototype data warehouse using the Q100
Waste data for: WasteDataFlow - Local Authority waste management
Published by Department for Environment, Food and Rural Affairs.
http://data.defra.gov.uk/Waste/Q100_data_England_2015_2016.csv
http://data.defra.gov.uk/Waste/Q100_data_England_2016_2017.csv
Note:
• To accompany your diagram, write your assumptions that govern your
choices in identifying the fact and dimension tables for the data model.
• you need BOTH source data files merged to consider the dimensional
modelling and the rest of the assignment. 10 1 10
2 Subject Knowledge - Design
Use SSIS / DAX expressions to perform ETL, combine the 2 files and
cleansing the data and populate the data warehouse:
• there are column mismatches between the two source files, you
must resolve this so the two files are union compatible and merge
their content, as well as fixing any other issues you may come
across in the data.
• Change the ONSCode for” Kent County Council” to your student ID.
You must provide relevant screenshots for these and any other ETL tasks to
prepare the data with brief supporting narratives for your ETL work. 10 1.5 15
3 Critical Analysis – Transforming design to implementation.
Discuss and critically evaluate any data understanding issues that you
encountered. Explain and critically evaluate how specific examples of
transformations were resolved. 10 1.5 5
4 Testing and Critical Thinking Skills
Using SQL build and test tasks A-D in MS SQL Server. Provide screenshots
of all code including any examples appropriate for each task and the task
output): include ONSCode with other useful attributes in each output.
a Show the top 5 “Dry Recyclate” waste materials processed by each authority
and the total weight in TotalTonnes by quarters e.g. April-June, July-
September, October-December and January-March. (note, in each quarter the
top 5 materials may vary) 10 1 10
b Rank the top 10 authorities and the TotalTonnes of waste processed by each
of these for each six-month period. For the second period onward also show
the number of places each Authority has moved (up/down the ranking) since 1
the previous period. 10 10
c For each FacilityType in each authority, show the WasteStreamType,
TotalTonnesFromHH (households) reported for the two-year period order the
output in descending order of TotalTonnesFromHH. Export the query output as
a JSON file. 10 1 10
d Create a fourth dynamic query as a stored procedure that accepts input
parameters, utilizing a time related hierarchy of your own design that
demonstrates the full complexity of your understanding in terms of analytic
query writing. 10 1 10
5 Practical Competence
Produce an interactive dashboard combining the 4 query tasks above (in a
single view) as visualized elements, that can be used to tell an effective story
about the business in this scenario. Use either Tableau or Power BI 10 1 10
6 Personal and Professional Development
Use MS Teams to record a video demo (10 mins max) of tasks 2, 3, 4 and 5.
During the video you must demonstrate your live execution of Task 4 in your
implementation environment(s) and Task 5 in either Tableau or PowerBI.
(screen share of the applications execution with your face also clearly visible) 10 1 20

100%

4
CSI_7_DAT: Coursework 2
Coursework Nov 2024 – Dec 2024

Marking Criteria
This assignment will be marked using an adaptation of the University’s new standardised marking
criteria. It is important that you pay attention to the criteria that will be applied and address them in the
text of your report.

Please note that the primary criterion being assessed in this assignment is your understanding of the
material and your ability to analyse and reason about it. Submitting a working program is not sufficient
to demonstrate this and will not in itself obtain a high grade.

Note that marks are awarded for the following main criteria:

1. Subject Knowledge - Design (25%)


Understanding and application of subject knowledge. Contribution to subject debate.
Mainly assessed by your written explanation of system design and transformation tasks 1-2.
2. Critical Analysis- Transforming design to implementation (5%)
Assessed by the quality of the critical evaluation supporting the practical work for efficiently
coding the construction of the database. There should be a critical and evaluative supporting
narrative evaluating the technical choices behind the implementation of Task 3
3. Testing and Critical Thinking Skills – TSQL/SSIS Queries/Transformations (40%)
Design, implementation, testing and analysis of product/process/system/idea/solution(s) to
the query tasks.
Assessed based on the queries and stored procedures you develop and document. It is
important to note that very little credit will be given to any code/examples you provide without
explanation. Task 4 (A-D)
4. Practical Competence - Dashboard Design + Implementation (10%)
Skills to apply theory to practice or to test theory.
Apply theories of dashboard design in an implementation of a multi visualization dashboard
using a connection to your database from either Tableau or Power BI. It is important to note
that very little credit will be given to any code or examples you provide without explanation.
5. Personal and Professional Development – Video Demo (20%)
Record a video of your learning and innovation through self-direction, planning and reflection.
Focus on all practical Tasks.
Assessed on the basis of the quality of your 10 min Video Presentation of all practical Tasks

5
CSI_7_DAT: Coursework 2

RUBRIC
Please note the criteria weightings and general interpretation shown in bold capitals under each criterion.
Criteria Outstanding 100-80% Excellent 79-70% Very good 69-60% Good 59-50% Satisfactory 49-40% Inadequate 39-30% Very poor 29-0%

Subject Knowledge Shows sustained breadth, Shows breadth, accuracy Accurate and extensive Accurate understanding Understanding of key Some evidence of Little or no evidence of
Understanding and accuracy and detail in and detail in understanding of key of key aspects of subject. aspects of subject. superficial understanding understanding of subject.
application of subject understanding key understanding key aspects of subject. Evidence of coherent Some evidence of of subject. Inaccuracies. Inaccuracies.
knowledge/ application of aspects of subject. aspects of subject. Evidence of coherent knowledge. coherent knowledge.
appropriate techniques. Contributes to subject Contributes to subject knowledge.
DESIGN SUBJECT debate. Awareness of debate. Some awareness
KNOWLEDGE ambiguities and of ambiguities and
EXPLANATION limitations of knowledge. limitations of knowledge.
20%
Critical Analysis Outstanding Excellent demonstration Very good demonstration Good demonstration of Demonstration of critical Trivial demonstration of Little or no critical
Analysis and demonstration of critical of critical analysis of the of critical analysis of the critical analysis of the analysis of the key critical analysis of the analysis has been
interpretation of design analysis of the possible possible design strategies possible design strategies possible design strategies possible design strategies possible design strategies demonstrated.
refinement. Structuring design strategies that that could be used to that could be used to that could be used to that could be used to that could be used to
future proofing the model could be used to meet the meet the software meet the software meet the software meet the software meet the software
CRITIQUE DESIGN software requirements, requirements, and requirements, and requirements, and requirements, and requirements, and
TRANSFER TO CODE and evaluation of the evaluation of the evaluation of the evaluation of the evaluation of the evaluation of the
5% approaches chosen. approaches chosen. approaches chosen. approaches chosen. approaches chosen. approaches chosen.
Testing and Critical Outstanding Excellent implementation Competent Implementation of all Implementation of most of Implementation of only Little or no functionality
Thinking Skills implementation of all of all required software, implementation of all required software, with the required software, part of the required has been implemented.
Design, implementation, required software, with with well organised, required software, with well organised, formatted with well organised, software, with well
testing and analysis of near perfectly organised, formatted and well organised, formatted and documented source formatted and organised, formatted and
product/process/ formatted and documented source code and documented source code, and documented documented source code, documented source code,
system/idea/solution(s) documented source code, provided code, and documented demonstration of runtime and documented and documented
to practical questions/ and documented demonstration of runtime behaviour, with some demonstration of runtime demonstration of runtime
problems demonstration of runtime behaviour. missing/incorrect behaviour, with some behaviour, with some
behaviour. functionality or poor missing/incorrect missing/incorrect
IMPLEMENTATION OF quality. functionality or poor functionality or poor
SQL + PROCEDURES quality. quality.
45%
Practical Competence Outstanding descriptions Excellent explicit Good explicit descriptions Reasonable descriptions Basic examples of the Some trivial examples of Little or no evidence of
Skills to apply theory to of factual information, descriptions of all factual of all factual information, of most factual main factual information, factual information, factual information,
practice or to test theory programming techniques information, programming programming techniques information, programming programming techniques programming techniques programming techniques
or theoretical techniques or theoretical or theoretical techniques or theoretical or theoretical or theoretical or theoretical
USE OF DASHBOARD explanations being found explanations that were explanations that were explanations that were explanations that were explanations being found explanations being found
TOOLS in technical or theoretical found in technical or found in technical or found in technical or found in technical or in technical or theoretical in technical or theoretical
10% reference material. theoretical reference theoretical reference theoretical reference theoretical reference reference material. reference material.
material. material. material. material.
Personal and Outstanding report Excellent report Very good report Good report organisation, Satisfactory report Poor report organisation, Report does not
Professional organisation, structure, organisation, structure, organisation, structure, structure, presentation, organisation, structure, structure, presentation, constitute a serious
Development presentation, narrative presentation, narrative presentation, narrative narrative voice and presentation, narrative narrative voice and attempt at the
Evidence Management of voice and language. voice and language. voice and language. language. voice and language. language. assignment.
learning through self-
direction, planning and
reflection

VIDEO DEMO
20%

You might also like