Contact tracing: part 1: Difference between revisions

From Computer Science Wiki
(Created page with "right|frame|This a problem set for you to work through <ref>http://www.flaticon.com/</ref> This is a problem set. Some of these are easy, others are far m...")
 
No edit summary
 
Line 18: Line 18:
[[File:Contact tracing.png]]
[[File:Contact tracing.png]]


Your task is to create a system diagram for this process.
# You must create one system diagram as an overview of the entire process
# You must create 6 additional system diagrams, one for each major part of the contact tracing application
# Your system diagrams must be clear enough for a friend to explain how your program will work.


== How you will be assessed ==
== How you will be assessed ==

Latest revision as of 10:38, 26 August 2020

This a problem set for you to work through [1]

This is a problem set. Some of these are easy, others are far more difficult. The purpose of these problems sets are:

  1. to build your skill applying computational thinking to a problem
  2. to assess your knowledge and skills of different programming practices


What is this problem set trying to do[edit]

You must be able to look at a real-world problem and using computational thinking, decompose it into smaller parts

The Problem[edit]

Contact tracing is the process of identifying, assessing, and managing people who have been exposed to a disease to prevent onward transmission. When systematically applied, contact tracing will break the chains of transmission of COVID-19 and is an essential public health tool for controlling the virus.

Contact tracing for COVID-19 requires identifying people who may have been exposed to COVID-19 and following them up daily for 14 days from the last point of exposure.[2]

Contact tracing.png

Your task is to create a system diagram for this process.

  1. You must create one system diagram as an overview of the entire process
  2. You must create 6 additional system diagrams, one for each major part of the contact tracing application
  3. Your system diagrams must be clear enough for a friend to explain how your program will work.

How you will be assessed[edit]

Your solution will be graded using the following axis:


Scope

  • To what extent does your code implement the features required by our specification?
  • To what extent is there evidence of effort?

Correctness

  • To what extent did your code meet specifications?
  • To what extent did your code meet unit tests?
  • To what extent is your code free of bugs?

Design

  • To what extent is your code written well (i.e. clearly, efficiently, elegantly, and/or logically)?
  • To what extent is your code eliminating repetition?
  • To what extent is your code using functions appropriately?

Style

  • To what extent is your code readable?
  • To what extent is your code commented?
  • To what extent are your variables well named?
  • To what extent do you adhere to style guide?

References[edit]

A possible solution[edit]

Click the expand link to see one possible solution, but NOT before you have tried and failed!

not yet!