Faculty of Science and Engineering

Referred Coursework - 2022/2023 Academic Year

PLEASE NOTE: If you have been referred in the COURSEWORK element of this

module and are required to be reassessed by COURSEWORK, please complete this

referred work.

Module Code: COMP2000

Module Title: Software Engineering 2

School: Engineering, Computing and Mathematics

DEADLINE FOR SUBMISSION: 09:00am on Monday 14th August 2023

Instructions to Candidates

This is an individual piece of work.

MODULE AIMS

•       To learn about topics that instil best practice into the students’ software development activity.

•       To explore a range of commonly used programming paradigms.

•      To understand the benefit of using standardised design patterns.

ASSESSED LEARNING OUTCOMES (ALO):

1.    Apply HCI and parallelism to construct more efficient and usable software.

2.    Illustrate the relative merits of various programming paradigms.

3.    Use appropriate programming paradigms to implement software that solves a given problem.

4.    Compare standard design patterns and explain why they are an important aspect of software engineering.

OVERVIEW

This document contains all the necessary information pertaining to the referral assessment

of COMP2000 software engineering 2. The module is assessed via 100% coursework.

The sections that follow will detail the assessment tasks that are to be undertaken. All assessments are to be submitted electronically via the respective DLE module pages

before the stated deadlines.

Task:

You are required to produce an Android mobile application that meets the requirement   specification in Appendix A of this assignment (design and implementation). The API for

interacting with the database is provided at this link:

web.socem.plymouth.ac.uk/COMP2000/api/referral/students

•       Use appropriate design patterns that you learnt throughout the course.

•       This application should follow the HCI guidance in designing the UIs (as defined in lectures).

•      Analyse the scenario in the appendix to identify the context of use and the users.

•       Design the interfaces using low-fidelity prototyping (e.g paper based).

•       Carry out two cycles of usability evaluation (formative and summative) using methods/ techniques you learnet throughout the module.

•      Your implementation is in the Java programming language using Android Studio.

•       The Java project will provide a graphical user interface (GUI) for usage.

•       The GUI should provide the functionality listed in Appendix A.

•       You MUST use Git version control with GitHub in your development process.

•      You are to use the GitHub Classroom set up for this module - the link for

signing up is here(https://classroom.github.com/a/xQZbfz6Q)You will be assessed on appropriate use of version control. Personal Github repo will not be accepted.

•      You must use a worker thread to handle the API connection.

Assessment Criteria:

Individual Coursework comprising one assignment with a GIT repository of

incremental development leading to a final build or release. Repository includes itemized

deliverables for final module submission. Typically, this will include your Android project

and the usability evaluation documentation in PDF, with a current build or release

executable. All code to be version controlled and commented, all 3rd party assets and

resources to be formally credited in the README file on the repository.

Deliverables

Submit the following in a zip file to the DLE submission point for this module

• A single PDF document reporting your work:

•       The design of the UIs (screenshots)

•       Usability evaluation of the project (i.e. user testing with all details)

•      A link to the GitHub repository for your project

•       Screenshots of the working system (i.e. the implementation)

•      A video rundown of your application OR a link to the video included in the main document.

Deliverables in detail

GIT Repository

An online repository of your project using the GIT service. You are Graded on the following criteria:

•       Repository readme file includes all additional resources (art, sound FX etc.) fully credited

•       No previous versions of the project are present in the repository in a .zip or other compressed format

•       Commits to the repository are appropriately commented

•       Commits are in a consistent timely manner, at least once every week

A PDF document reporting your work

A PDF document contains details of the design, implementation and evaluation studies

that were carried out including:

•       Interface design (low and high- fidelity prototyping)

•       Details of the implementation phase including screenshots of the UIs of the working system.

•       Information of user studies, participants who took part in the study, and how they were invited.

•       Details of how the studies were set, and details of the method/technique that  was adopted as well as details of the test plan; with evidence (i.e. photos or a link to a video and the consent form).

•       Details of how the results of the formative evaluation helped in designing the latest version of the app.

•       Details of how the summative evaluation could help enhance the app (i.e. recommendations)

Video rundown of your application

•       Demonstrate the functionality of your project in a short video

•       The video should be between 3-5 minutes long. Please note that you will be panelised if the video is longer that the specified guideline.

•       The sound should be clear and in the normal pace

•       No need for flashy intros please!

•       Please include:

•       Explain any design pattern implementations

•       Go through the code and explain your implementation

•       Demonstrate the program running

•      You may be invited to a zoom video call for further discussion at a later date

You must present the work carried out in a report submitted in PDF format.  No other format is acceptable.  Your report must be approximately 2000 words, please use screenshots and links to code files to illustrate functionality where appropriate and low-fidelity prototype to illustrate the design of the interfaces.