Description

The objective of the second assignment is to develop a web client that communicates via the already-specified API with the web server developed from Assignment 1. The web client should satisfy the list of user stories provided via Learn. Taken together, the web client and the web service, with the API, provide a petition site.

 

1  Required technologies

 

For this assignment, you must use Vue.JS to the version levels that are used in the labs. We will provide a standardized web service (on a VM test server) so you should not develop the web client based on your own web service from Assignment 1. (We will explain how to access the web service – e.g. the IP address or URI – in due course.)

 

You may choose to use additional JavaScript libraries etc., depending on your

implementation, provided these libraries are sourced from a recognized repository (content delivery network), and provided these packages do not break dependencies on Vue.JS, or on the Node.js and Express versions in the labs.

 

You do not have to develop your applications only in the labs, you may use your own computing resources. You should maintain your source code under Git version control.

 

2  Indicative criteria used in the assessment

 

In this assignment your commitment to the user experience should be front-and-centre. This doesn’t mean flashy UI features or “look-at-me” interfaces, though.

 

The requirements are provided in the form of User Stories in the “Assignment 2 backlog” below. Implement as many as you can (each story counts in the assessment).

 

As stated in the introduction, your app must run in a prescribed way from a lab workstation (see below) to be marked, and we will assess using the installed version of Chrome.

 

We shall be assessing:

 

1. Correctness and ease of use for each implemented story when run against an instance of the reference Assignment 2 API implementation (a buggy or broken story won’t improve your grade). This is the main component of assessment.

 

2. Robustness and stability. An app that crashes or fails will be hard to assess. We’ll also expect that your application will perform simple field validations and access checks.

 

3. Visual appeal and general creativity (‘going the extra mile’).

 

3  Compulsory lab for Assignment 2

 

We intend to use a version of crowdsourced testing to contribute to the assessment of the Assignment 2. Each assignment will be ‘exercised’ by a randomised set of students during the final week of labs.