QHO543 Object Oriented Design and Development


Southampton Solent University in Partnership with QAHE

Coursework Assessment Brief AE1

Assessment Details


Module Title: Object Oriented Design and Development
Module Code: QHO543
Module Leader: Dhouha Kbaier
Level: 5
Assessment Title: Group Project – HitTastic!
Assessment Number: AE1
Assessment Type: Software Development
Restrictions on Time/Word Count: 5 min presentation; 200 word integration report
Consequence of not meeting time/word count limit: There is no penalty for submitting below the word/count limit, but students should be aware that there is a risk they may not maximise their potential mark.


Assignments should be presented appropriately in line with the restrictions stated above; if an assignment exceeds the time/word count this will be taken in account in the marks given using the assessment criteria shown.

Individual/Group: Individual
Assessment Weighting: 40%
Issue Date: 08/07/2022
Hand In Date: 02/09/2022
Planned Feedback Date: Within 4 weeks of submission
Mode of Submission: on-line
Number of copies to be submitted: 1

Anonymous Marking


This assessment: is exempt from anonymous marking.


Assessment Task


Please note that this resit uses a completely different scenario to the original, and has significantly different requirements. It is also, for logistical reasons, unrelated to the resit AE2 assessment.


HitTastic! – an online music site


Your task is to develop, as a group of two or three (which will be allocated by the tutor) HitTastic!, a music website using Java and JSP, allowing users to search for and buy physical copies of music online.


There must be no more than three in the group under any circumstances. Note that under exceptional circumstances you may work individually on the assignment – see “What if I have to work individually?”, below.


You should include the following features.


Group Member A:


  1. a) A user should be able to search for songs by artist or by title.


  1. b) A user should be able to buy one or more physical copies of a song. For the purposes of this assignment, this should create an order, and increase the sales of the song by the appropriate amount. This should be linked to task a).


  1. c) A user should be able to view their order history.


Group Member B:


  1. d) A user should be able to sign up for an account, and login with a username and password. The system must be able to distinguish between regular users and administrators.


  1. e) An admin user should be able to view a list of all users.


  1. f) An admin user should be able to edit the details of a current user and delete a current user.


Group Member C (only applicable if a group of three; if a group of two, these requirements need not be implemented):


  1. g) A user should be able to see a list of all songs, showing their sales. It is not necessary to sort them.


  1. h) An admin user should be able to add a new song.


  1. i) An admin user should be able to modify the details of a song (for example the price, or to correct typos in the song name) and delete a song. This should be linked to task f).





How to do the assignment

Groups should divide the work up between members so that each member takes responsibility for one of the three groups of tasks above (Group Member A, B or C). If you are in a group of two, each member should implement either the Group Member A tasks or the Group Member B tasks – you should not implement the Group Member C tasks.


Each group member should then produce a class diagram for their individual tasks, showing classes needed, their attributes and methods, and relationships between classes. Each member should also create a simple JSP project in NetBeans to implement their own tasks. Focus on implementing a simple JSP application. There is no need to use more advanced topics from the module, such as Spring Framework, web services, or JPA for this assignment – even to reach a high grade. There is also no need for an overly-complex design. However, you should not put all your code inside the JSP – you must create other appropriate classes (at least two to three will be needed) and document them in your class diagram!





When each member of the group has got their requirements working, you should, as a group, integrate all the requirements to produce a working application. As part of this, ensure that only logged-in users can download songs, or (if in a group of three) change the details of a song. The group should produce a short report (around 200 words) describing the integration process and any problems encountered, and a series of unit tests on the final product to ensure it works.




Each group member should produce a 5-minute multimedia presentation describing their individual implementation of their own tasks. You need not include the integration process. The sound quality must be good – you must test this; the assessor will not attempt to listen to quiet or distorted audio, and such presentations will not pass.


What if I have to work individually?


It is recognised that, as it is the summer, there may be communication issues between group members. If you have made every effort to work with your other group member(s) but it is not possible, you may work on this individually. Select the tasks for either Group Member A or Group Member B, and work on them individually.


Then, in the integration report, talk about what steps you would have taken to integrate your work with the other set of tasks (from Group Member B or A), what problems might arise, and how you would solve them. For the unit tests, test your individual tasks alone.



How you should hand-in the work


Each individual student should upload a ZIP file to SOL by the specified deadline, containing:


– the code for the whole group project, written by all group members. Each group member must clearly mark the code that they wrote using comments; any code with no apparent author will not be marked. Include unit tests (the unit tests will be common to the whole group)

– the integration write-up of around 200 words (shared across whole group)

– the 5-minute multimedia presentation (individual)

– your class diagram (individual)


Assessment criteria

  A1-A4 B1-B3 C1-C3 D1-D3 F1-F3
Class diagram (10%) (individually marked)



Clear and complete class diagram Largely clear, complete class diagram


Class diagram  mostly complete but with some omissions or unclear aspects Class diagram apartly complete but with significant omissions or unclear aspects Predominantly unclear and/or inaccurate class diagram
Individual Implementation (40%) (individually marked) All individual tasks covered to a high standard. The vast majority of individual tasks covered. There may be very occasional errors Most tasks covered with a few omissions. Some errors may be present but the code should be runnable and testable


A significant effort made on the tasks but with significant omissions. Some errors may be present, but the code should be runnable and testable Code which does not run successfully. Minimal effort made
Presentation (20%) –  (individually marked) Clear and detailed presentation describing all individual tasks  in technical detail. Mostly clear and detailed presentation with occasional omissions or unclear sections Mostly clear and detailed presentation with a number of omissions or unclear sections Presentation partly complete but with significant omissions or unclear sections


Predominantly unclear and/or inaccurate presentation Little understanding demonstrated.



Testing (10%) (group marked) Wide ranging and comprehensive unit tests implemented, with clear results. Wide ranging and comprehensive unit tests implemented, with clear results. A small number of omissions Many unit tests implemented, with clear results – but a number of omissions Unit tests implemented but with significant omissions Minimal tests implemented
Integration Report (20%) (group marked) Clear and detailed report of integration process Mostly clear and detailed report with occasional omissions or unclear sections Mostly clear and detailed report with a number of omissions or unclear sections Report partly complete but with significant omissions or unclear sections Predominantly unclear and/or inaccurate report. Little understanding demonstrated.


Learning Outcomes


This assessment will enable students to demonstrate in full or in part the learning outcomes identified in the unit descriptors.

Late Submissions


Students are reminded that:


  1. If this assessment is submitted late i.e. within 5 working days of the submission deadline, the mark will be capped at 40% if a pass mark is achieved;
  2. If this assessment is submitted later than 5 working days after the submission deadline, the work will be regarded as a non-submission and will be awarded a zero;
  • If this assessment is being submitted as a referred piece of work then it must be submitted by the deadline date; any Refer assessment submitted late will be regarded as a non-submission and will be awarded a zero.


Extenuating Circumstances

The University’s Extenuating Circumstances procedure is in place if there are genuine circumstances that may prevent a student submitting an assessment. If students are not ‘fit to study’, they can either request an extension to the submission deadline of 5 working days or they can request to submit the assessment at the next opportunity (Defer).  In both instances students must submit an EC application with relevant evidence.   If accepted by the EC Panel there will be no academic penalty for late submission or non-submission dependent on what is requested.  Students are reminded that EC covers only short term issues (20 working days) and that if they experience longer term matters that impact on learning then they must contact the Student Hub for advice.


Please find a link to the EC policy below:




Academic Misconduct

Any submission must be students’ own work and, where facts or ideas have been used from other sources, these sources must be appropriately referenced. The University’s Academic Handbook includes the definitions of all practices that will be deemed to constitute academic misconduct.  Students should check this link before submitting their work.


Procedures relating to student academic misconduct are given below:





Ethics Policy

The work being carried out by students must be in compliance with the Ethics Policy. Where there is an ethical issue, as specified within the Ethics Policy, then students will need an ethics release or an ethical approval prior to the start of the project.


The Ethics Policy is contained within Section 2S of the Academic Handbook:




Grade marking

The University uses a letter grade scale for the marking of assessments. Unless students have been specifically informed otherwise their marked assignment will be awarded a letter grade. More detailed information on grade marking and the grade scale can be found on the portal and in the Student Handbook.





Guidance for online submission through Solent Online Learning (SOL)




Leave a Comment

Your email address will not be published. Required fields are marked *

+1 587-331-9072
We will write your work from scratch and ensure that it is plagiarism FREE, you just submit the completed work.