Complete CS3003 Software Engineering Threshold Assessment/Coursework in which I received a passing grade. The document contains the coursework brief, followed by the answers, containing diagrams and referencing.
CS3003 Software Engineering
Assessment/Coursework for 2020/21
TABLE OF CONTENTS
Main Objective of the assessment…………………………………………………………………………………………………………………1
Description of the Assessment………………………………………………………………………………………………………………………1
Learning Outcomes and Marking Criteria………………………………………………………………………………………………………2
Format of the Assessment…………………………………………………………………………………………………………………………….2
Submission Instructions………………………………………………………………………………………………………………………………..3
Avoiding Plagiarism………………………………………………………………………………………………………………………………………3
Late Coursework…………………………………………………………………………………………………………………………………………..3
Assessment Title Assessing Quality of Code from a Metric Perspective
Module Leader Steve Counsell
Distribution Date Tuesday 3rd November 2020
Submission Deadline Monday 14th December 2020
Feedback by Wednesday 23rd December 2020
Contribution to overall module assessment Pass/Fail (Threshold assessment)
Indicative student time working on assessment 60 hours
2,000 words (this does not include the cover page,
Word or Page Limit (if applicable)
contents page, figures, plots, graphs or references)
Assessment Type (individual or group) Individual
MAIN OBJECTIVE OF THE ASSESSMENT
In this assessment, you will be analysing some metrics in relation to how they reflect quality an open-source
system and preparing a report on the results of your analysis. The aim of your report will be to discuss whether,
based on your analysis, aspects of the systems show good or poor quality. You will choose data from a system
and you will write a report based on your findings.
Note: Use Excel (or any equivalent statistical tool of your choice) to analyse the data in your system.
DESCRIPTION OF THE ASSESSMENT
1. Select all the rows of a system of your choice from the large dataset called “coursework_data.xlsx”
provided in the CS3003 assessment folder. The system name is in column A of the dataset. Store those
rows in a separate dataset so that you can begin your analysis of them.
2. Next, as well as BUGS (in column N) choose an additional **FOUR** metrics from the dataset columns
that you believe will help explore this system. These metrics start in column D in the dataset. You
should recognise these metrics from the lab sheets that you have been working on. So, in total you’ll
have 5 metrics to work with.
3. Now, analyse the data in your chosen system. Explore, the relationship between BUGS and each of the
other four metrics you chose and discuss the relationships you find. Produce any charts and graphs
(e.g. bar charts, box plots and/or scatter plots, etc.) showing the features of each relationship.
4. You should also use other statistics (i.e., correlation) to identify any major differences in the data (see
the previous lab sheets for what you’ve done in this way already). Try to understand any differences
and similarities and explain why you think these differences may exist. Is there anything noteworthy
(unusual, interesting or surprising) resulting from your analysis? You will need to document all your
findings in your report.
Updated October 2020
1 of 3
, Department of Computer Science
LEARNING OUTCOMES AND MARKING CRITERIA
Learning outcomes for the assessment Assessment and marking criteria
LO1: Describe the attributes of quality software and Provide evidence of a systematic understanding of
the implications of poorly designed software. software quality and the use of metrics to assess
this (throughout the sections of the report).
LO2: Describe and evaluate the processes and Provide evidence of a systematic understanding of
techniques which may be used to produce quality the processes and techniques used to produce
software and be able to create software artifacts quality software (throughout the sections of the
which display these attributes. report).
LO3: Critically evaluate, select and appraise software Demonstrate the ability to select and assess suitable
metrics in order to assess software process and metrics (throughout the sections of the report).
product attributes.
An overall pass or fail will be awarded for the report you submit. A pass or fail will be awarded for each section
of your report. All sections must be passed to pass the assessment overall. This coursework document contains
various indications on what differentiates a basic attempt from a good attempt. Although you can pass this
coursework with a basic attempt, a more comfortable pass can be achieved by going further and being more
ambitious. Although a ‘good’ attempt will not attract any more marks for this coursework, it is worth
remembering that there may well be questions based on this assessment in an end of year exam question.
Those going beyond a basic attempt at this coursework are likely to be able to gain higher marks in response to
that exam question.
FORMAT OF THE ASSESSMENT
You must produce a report containing the following sections. All reports must provide an accurate word count
at the beginning of the document.
**Please number and add a title to each section in your report so that every section is clear**.
Section 1: This section relates to point 2 on the previous page. All well as BUGS, state which other FOUR metrics
you chose. Why are these four metrics important? Provide any references you think are relevant to the
discussion to back-up your argument in the references section (Section 3 described below).
<<Approximately 350 words>>
Section 2: Analysis and Discussion of results: This section relates to points 3 and 4 on the previous page. Provide
graphs/charts/plots/correlations etc. summarising what your analysis of the relationship between BUGS and
the other four metrics has shown. Provide a discussion of each of your findings; this discussion should highlight
important features of your results and comment on what those results mean. **Each graph/chart provided by
you should be numbered and given a caption (e.g., Figure 1. BUGS versus CBO) so that it can be referred to
in the report and understood by the marking team**.
<<Please note that figures/graphs/charts are not included in your word count>>
<<Approximately 1650 words>>
Section 3: Provide a list of references of source material you have referred to in your coursework (15 references
maximum).
<<References are not included in your word count>>
Updated October 2020
2 of 3
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller BrunelCompSci. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $27.10. You're not tied to anything after your purchase.
