CIS3006 Programming Skills and Statistics

School of Technology
Assessment
Brief
Content
Assessment Details…………………………………………….2
Submission Details …………………………………………….5
Assessment Criteria……………………………………………6
Further Information …………………………………………….8
Who can answer questions about my assessment? ………..8
Referencing ……………………………………………………………………9
Submission problems …………………………………………………….9
Unfair academic practice ………………………………………………..9
How is my work graded? ………………………………………………10
Module Code Module Title
CIS3006 Programming Skills and Statistics
Academic Year Semester
2022-2023 2
Module Leader email
PJenkins2@cardiffmet.ac.uk
2
Assessment Details
Assessment title Abr. Weighting
CTEST1 Online Programming Test CTEST1 25%
PRAC1 Programming Project Retrieval PRAC1 75%
Pass marks are 40% for undergraduate work and 50% for postgraduate work unless stated otherwise.
Task/assessment brief:
3
Assessment Requirements / Tasks (include all
guidance notes)
1. Description
The assignment consists of 2 parts, an online test and a practical assignment.
Practical Part
1.1Design and build a c# program to automate an IT Repair Business, managing the business
entities:
Customers;
Equipment;
Repairs;
Engineers.
The IT Repair Business offers a range of services to customers, such as:
• Repair of a Range of IT Equipment
o The business repairs a range of PCs and Laptops, from all the major
manufacturers, for example: HP, DELL, Apple etc.
o When customers bring equipment for repair, a record of the equipment is
created containing the following information:
▪ Equip Serial No
▪ Manufacturer
▪ Type (PC/Screen/Keyboard/Printer)
▪ Issue
▪ Date
• Customers
o Information stored for each customer is:
▪ Customer Number
▪ Title
▪ First Name
▪ Last Name
▪ Address
▪ Tel no
▪ Email
▪ Total Invoiced
• Transactions
o Repair Details
▪ Repair No
▪ Customer Number
▪ Equipment serial No
▪ Date in Workshop
▪ Date complete
▪ Repair description
▪ Engineer/technician no
▪ Cost
▪ Complete (Y/N)
• Engineer
▪ Engineer No
▪ First Name
▪ Last Name
▪ Specialism
4
1.2 Your design should make use of appropriate programming structures, such as functions
(methods), and classes where appropriate. In addition, your program should keep track of
repair statistics:
• Customer with highest level of business.
• Outstanding Repairs each day or on a particular date.
• Total income to date.
1.3 You should fully document your program, including:
1.3.1 using UML diagrams and flowcharts to explain the design
1.3.2 Devise a test plan for the software
1.3.3 Provide expected results
1.3.4 Provide screenshots of the results and discuss them
1.3.5 Write conclusions and recommendations
1.4 Part 2: Data Analytics / Statistics
Using data on survival data from the Titanic sinking in April 1912, analyse the data to determine the
following information:
There are two files: titanic.csv and gender_submission.csv. The first is a list of passengers on the
Titanic and the second file is a list of female passengers and whether they survived the accident. In the
first file there is no survival data, it is predicted based on a machine learning algorithm detailed below:
• There are only two files presented for the assignment as you are not conducting the data
science model, rather a straight-forward statistical analysis.
• Firstly, you will have to cleanse the data and pre-process the data in preparation for processing
and then using Minitab:
a). Produce graphs showing:
(i) Using a line graph draw the number of passengers that survived in each class of
Passage, in order to answer the following.
(a) Of those that survived how many had a cabin?
(ii) The age of the passengers.
(iii) Summarize the survival information.
(vi) What would you expect to observe and why.
5
b). Summarize the statistical data for the following:
(i) Calculate the mode, median and average for:
(a) Passenger Survival
(b) Female Passenger survival data
(c) Passenger age

(ii) Discuss the results.
Word count (or equivalent): 2000
This a reflection of the effort required for the assessment. Word counts will normally include any text,
tables, calculations, figures, subtitles and citations. Reference lists and contents of appendices are
excluded from the word count. Contents of appendices are not usually considered when determining
your final assessment grade.
Academic or technical terms explained:
N/A
Submission Details
Submission
Deadline: 1
st May 2023 Estimated Feedback
Return Date
This will normally be 20
working days after initial
submission.
Submission
Time:
By 4.00pm on the
deadline day.
Moodle/Turnitin: Any assessments submitted after the deadline will not be marked and will be
recorded as a non-attempt unless you have had an extension request agreed or
have approved mitigating circumstances. See the School Moodle pages for more
information on extensions and mitigating circumstances.
File Format: The assessment must be submitted as a word or PDF document (save the
document as a pdf in your software) and submit through the Turnitin submission
6
point in Moodle. In addition, you should upload a zipped file of the software you
developed.
Your assessment should be titled with your:
student ID number, module code and assessment ID,
e.g. st12345678 CIS3006 PRAC1
Feedback Feedback is given for the CTEST on completion of the test. For the assignment, feedback
is through GradeMark Rubrics. Those used will be the generic taught Foundation course
and Level 0 of Bachelor’s degree assessment and evaluation criteria as found in the
Academic Handbook: Academic Handbook Ah1_05 (cardiffmet.ac.uk)
Feedback for the assessment will be provided electronically via Moodle. Feedback will be
provided with comments on your strengths and the areas which you can improve. View
the guidance on how to access your feedback.
All marks are provisional and are subject to quality assurance processes and confirmation
at the programme Examination Board.
Assessment Criteria
Learning outcomes assessed
• Demonstrate an awareness of key principles of programming, including the use of variables,
looping and branching of code.
• Demonstrate an understanding of the importance of principles of good design of software
products.
• Use statistical software to describe, analyse and model data.
Other skills/attributes developed
This includes elements of the Cardiff Met EDGE (Ethical, Digital, Global and Entrepreneurial skills) and
other attributes developed in students through the completion of the module and assessment. These
will also be highlighted in the module guidance, which should be read by all students completing the
module. Assessments are not just a way of auditing student knowledge. They are a process which
provides additional learning and development through the preparation for and completion of the
assessment.
Marking/Assessment Criteria
7
Assessment Criteria PRAC1
CIS3006 Programming Skills and Statistics Assessment Feedback Marks Allocation
Software Development / Programming Skills Written Part
Program Documentation to include:
Front Cover and Contents Page 2
Introduction including Aims and Objectives 2
Literature Review of Software Development Methods 9
Program Design to include All necessary diagrams (Use Case/Class
Diagram/ Sequence Diagrams)
Screen designs
Any mathematical or programmatic calculations
9
A test plan and test data 6
Expected Results 4
Conclusions and recommendations 4
References 4
Software Development / Programming Skills Practical Part
Design and build the software for the IT Repair Business.
40
Part 2: Data Analytics / Statistics
• Firstly, you will have to cleanse the data and pre-process the data in
preparation for processing and then using Minitab:
a). Produce graphs showing:
(i) Using a line graph draw the number of passengers that
survived
(ii) Of those that survived how many had a cabin?
(iii) The age of the passengers.
(iv) Summarize the survival information.
(v) What would you expect to observe and why.
b). Summarize the statistical data for the following:
(i) Calculate the mode, median and average for:
(a) Passenger Survival
(b) Female Passenger survival data
(c) Passenger age

(ii) Discuss the results.
2
2
2
2
2
2
2
2
2
2
Your TOTAL MARK 100
8
Marking Criteria – PRAC1
70 – 100%
(1st)
An excellent piece of software that shows a very good understanding of the
end-user and context. The software package has been designed in such a
way that it demonstrates a very good understanding of the principles of
good UI design, has been tested and operates with limited functional or
code-errors. Code is very well organised, adhering to professional
standards, with appropriate use of naming conventions, modularisation and
commenting.
60-69%
(2:1)
An good piece of software that shows a good understanding of the end user
and context. The software package has been reasonably well designed and
shows some consideration of principles of good UI design. The software
has been tested and operates with limited functional or code errors. Code is
well organised, largely adhering to professional standards, with appropriate
use of naming conventions, modularisation and commenting.
50-59%
(2:2)
A reasonably basic software that shows some understanding of the end
user and context, although this is limited in places. The software package
has been reasonably well designed. The software has been tested but
operates with some functional and/or code-errors. Code is does not
extensively adhere to professional standards, including appropriate use of
naming conventions, modularisation and commenting.
40-49%
(3rd)
A basic software that shows some but limited understanding of the end user
and context. The software package has been very basically designed with
limited demonstration of an understanding of principles of good UI design.
The software has been tested but operates with some functional and/or
code-errors. Code does not extensively adhere to professional standards,
including appropriate use of naming conventions, modularisation and
commenting.
35-39%
(Narrow
Fail)
A very basic software that shows limited understanding of the end user and
context. The software package has been very basically designed with
limited demonstration of an understanding of principles of good UI design.
The software has not been sufficiently tested and operates with some
functional and/or code-errors. Code does not extensively adhere to
professional standards, including appropriate use of naming conventions,
modularisation and commenting.
<35%
(Fail)
A poor project with limited inclusion of functionality in places. There is a
very basic interface included. The software has extensive errors and there
is limited to no evidence of testing. The code is poorly written with limited
consideration of professional practice.
.
Further Information
Who can answer questions about my
assessment?
9
Questions about the assessment should be
directed to the staff member who has set the
task/assessment brief. This will usually be the
Module Leader. They will be happy to answer
any queries you have.
Staff members can often provide feedback on
an assignment plan but cannot review any
drafts of your work prior to submission. The
only exception to this rule is for Dissertation
Supervisors to provide feedback on a draft of
your dissertation.
Referencing and independent learning
Please ensure you reference a range of
credible sources, with due attention to the
academic literature in the area. The time
spent on research and reading from good
quality sources will be reflected in the quality
of your submitted work.
Remember that what you get out of university
depends on what you put in. Your teaching
sessions typically represent between 10%
and 30% of the time you are expected to
study for your degree. A 20-credit module
represents 200 hours of study time. The rest
of your time should be taken up by selfdirected study.
Unless stated otherwise you must use the
HARVARD referencing system. Further
guidance on referencing can be found in the
Study Smart area on Moodle and at
www.citethemrightonline.com (use your
university login details to access the site).
Correct referencing is an easy way to
improve your marks and essential in
achieving higher grades on most
assessments.
Technical submission problems
It is strongly advised that you submit your
work at least 24 hours before the deadline to
allow time to resolve any last minute
problems you might have. If you are having
issues with IT or Turnitin you should contact
the IT Helpdesk on (+44) 2920 417000. You
may require evidence of the Helpdesk call if
you are trying to demonstrate that a fault with
Moodle or Turnitin was the cause of a late
submission.
Extensions and mitigating circumstances
Short extensions on assessment deadlines
can be requested in specific circumstances. If
you are encountering particular hardship
which has been affecting your studies, then
you may be able to apply for mitigating
circumstances. This can give the teachers on
your programme more scope to adapt the
assessment requirements to support your
needs. Extensions and mitigating
circumstances policies and procedures are
regularly updated. You should refer to your
degree programme or school Moodle pages
for information on extensions and mitigating
circumstances.
Unfair academic practice
Cardiff Met takes issues of unfair practice
extremely seriously. The University has
procedures and penalties for dealing with
unfair academic practice. These are
explained in full in the University’s Unfair
Practice regulations and procedures under
Volume 1, Section 8 of the Academic
Handbook. The Module Leader reserves the
right to interview students regarding any
aspect of their work submitted for
assessment.
Types of Unfair Practice, include:
Plagiarism, which can be defined as using
without acknowledgement another person’s
words or ideas and submitting them for
assessment as though it were one’s own
work, for instance by copying, translating
from one language to another or
10
unacknowledged paraphrasing. Further
examples include:
• Use of any quotation(s) from the
published or unpublished work of other
persons, whether published in textbooks,
articles, the Web, or in any other format,
where quotations have not been clearly
identified as such by being placed in
quotation marks and acknowledged.
• Use of another person’s words or ideas
that have been slightly changed or
paraphrased to make it look different from
the original.
• Summarising another person’s ideas,
judgments, diagrams, figures, or
computer programmes without reference
to that person in the text and the source
in a bibliography/reference list.
• Use of assessment writing services,
essay banks and/or any other similar
agencies (NB. Students are commonly
being blackmailed after using essay
mills).
• Use of unacknowledged material
downloaded from the Internet.
• Re-use of one’s own material except as
authorised by your degree programme.
Collusion, which can be defined as when
work that that has been undertaken with
others is submitted and passed off as solely
the work of one person. Modules will clearly
identify where joint preparation and joint
submission are permitted, in all other cases
they are not.
Fabrication of data, making false claims to
have carried out experiments, observations,
interviews or other forms of data collection
and analysis, or acting dishonestly in any
other way.
How is my work graded?
Assessment grading is subject to thorough
quality control processes. You can view a
summary of these processes on the
Assessment Explained Infographic.
Grading of work at each level of Cardiff Met
degree courses is benchmarked against a set
of general requirements set out in Volume 1,
Section 4.3 of our Academic Handbook. A
simplified version of these Grade Band
Descriptors (GBDs) with short videos
explaining some of the academic terminology
used can be accessed via the Facilitation of
Learning resource page.
We would strongly recommend looking at the
Study Smart area of Moodle to find out more
about assessments and key academic skills
which can have a significant impact on your
grades. Always check your work thoroughly
before submission.