COMP3297 Software Engineering Department of Computer Science The University of
Individual Assignment 1: Construction Quarantine Data Dashboard
Construction Overview
Now you¡¯ve completed Inception, you should have a good understanding of the required product, and of the Dept. of Health APIs it will consume. You should also have established your development environment. Your major goal in Construction is to implement the product.
Copyright By PowCoder代写 加微信 powcoder
After you complete Construction, you will enter Transition and deploy your product, correct any issues with it, and deliver it. The date at which you begin Transition is left to you.
The Transition worksheet covering deployment will be released near the end of the first week of Construction.
You will implement the product on Django using the templates provided. The templates assume you have split the required functionality into 3 user stories and that you will implement these in a particular order (see below).
Documents refined in Construction Vision statement
Revise if necessary
Product Backlog
Split the required functionality into 3 user stories based on user needs and adjust your Product Backlog accordingly. The user stories will obtain/derive and display:
¡¤ Total quarantine units occupied by persons in quarantine, summed across all centres.
¡¤ Total number of unoccupied quarantine units available for use, summed across all centres.
¡¤ The three centres with the highest number of available unoccupied units, listed in decreasing order
of availability. For each of the three centres, display the name of the centre and the number of unoccupied units that are available there.
¡¤ The total number of persons quarantined, summed across all centres.
¡¤ Of those quarantined, the number in the category of ¡°non-close contacts¡±.
¡¤ An indication of whether the data are consistent (as described in the overview).
The stories are sufficiently small that error handling, for failure to access the endpoint or failure to obtain data, can be included as part of the stories. It is customary to specify error handling as part of the conditions of satisfaction or acceptance criteria in the story confirmations.
Write each of the stories. For each, provide a meaningful title, a description in the who/what/why style, and a confirmation section listing conditions of satisfaction/acceptance criteria. For the first two stories (1 and 2), use the checklist style to write the confirmation section. For the third story, use the scenario style.
Implementation in Construction
Implement the product on Django. While each story is independent of the others, we will assume you will build up the functionality incrementally, story by story, beginning with Story 1 and ending with Story 3.
For simplicity, the implementation will use a single template, however you are provided with three versions of that template to use in development (they simulate how you might extend the template in practice): the first template supports Story 1, the second Stories 1 and 2, and the third Stories 1, 2 and 3. Your delivered product will, of course, include only the third version of the template.
Deliverables
None at the end of Construction, since you may need to revise your code during Transition.
However, you will deliver the following as part of your final set of deliverables at the end of Transition on Mar 15:
¡¤ Vision Statement
¡¤ Product Backlog containing fully documented user stories
¡¤ Source code for your Django project
The URL for your deployed product will be added to the set in Transition.
程序代写 CS代考 加微信: powcoder QQ: 1823890830 Email: powcoder@163.com