Assignment: A High-Intensity Interval Training Tool

Hello, if you have any need, please feel free to consult us, this is my wechat: wx91due

Assignment: A High-Intensity Interval Training Tool

Scenario

High-Intensity Interval Training (HIIT) workouts are composed of multiple periods of intense work, separated by periods of lighter alternative work, or rest. Your challenge is to create a customizable fitness web-app that allows users to create and participate-in bespoke HIIT workouts.

Core features:

  • A user should be able to
    • Build a custom HIIT workout from scratch.
    • Create multiple activities, where each activity has:
      • a name (e.g. Squats, Lunges, Rest)
      • a description
      • a duration
    • Start, stop and pause workouts
  • When a workout is started it should:
    • Accurately keep time
    • Keep the user informed about
      • what they are supposed to do, and
      • when to change activities
Among the advanced features you might consider adding are:
  • Adjustable difficulty levels (e.g. reduce all rest times)
  • Record keeping: so the user can see a history of their workouts.

There are many existing apps, tools and videos that implement different aspects of what you're being asked to create. You can refer to these for ideas, just make sure you credit them.

Prototype Submission

You will submit a prototype to Canvas before the prototype submission deadline. We will do this in class so that:

1. You are clear about what you have to do to successfully submit your work for marking,

2. Your prototype can be reviewed by us, helping you to focus your work during the last weeks before submission.

Delivery Requirements

1. Your web application must be delivered in a single zip file, with the node_modules folder removed.
2. The file should be named upXXXXXXX.zip (replace upXXXXXXX with your real student id).
3. We mark anonymously. Make sure there is nothing in your application's UI or source code that can identify you. Violating anonymity is an assessment offence.
4. Any HTTP server should listen on port 8080.
5. If in doubt about using third-party code (incl. libraries, frameworks, web services or build systems), please ask your lecturers - we are testing your abilities with the core language tools so third-party runtime code is not allowed.
5.1. No server-side libraries.
Other than express.js and SQLite you must build everything yourself.
5.2. No Frameworks or Template Engines.
e.g. Angular, React, Bootstrap, jQuery, EJS, Vue, etc.
5.3. No Build Systems.
e.g. TypeScript, Babel, WebPack, etc.
5.4. No Web Services.
e.g. Firebase, Mongo Atlas, etc.
6. If your application requires a configuration step (e.g. to set up a database), this must be achieved via the command npm run setup
7. The server must launch with npm start
8. When assessing the work:
8.1. We will extract the files from your zip
8.2. We will then run …
npm install
… and then, if necessary
npm run setup … and then, finally
npm start
8.3. If your server does not start when we do this, we will assess your work based on the source code without the benefit of seeing it run, therefore, please test that everything works from your supplied zip, following the same steps as outlined in 8.1 and 8.2 above.
9. You must include a README.md file that:

9.1. Introduces the key features, tells us briefly how to find & use them, and describes the reasons behind the design decisions you made in their implementation. If you omit this, we may not find features, may not consider them maintainable and your marks may suffer.

9.2. Details your use of AI, listing of the prompts you used, and whether the results formed or inspired part of your final submission and where we can see this (and if not, why not?). There is an example later on in this document.

9.3. Discusses why and how you have improved your artefact since the prototype deadline.

Sample README.md

Copy the text below and paste it into your empty README.md to get started

# HIIT upXXXXXXX <-- your student number here
## Key features
REMOVE ME: Introduce the key features, paying special attention to the non-code ones. Tell us briefly how to find & use them,
and describes the reasons behind the design decisions you made in their implementation.
### Key Feature Name/Description.
Words words words. Words words words.
### Key Another Feature Name/Description.
Words words. Words words words.
Words words words words. Words words words.
Words words words words words. Words.
### Final Key Feature Name/Description.
Words.
Page 3 of 3

发表评论

电子邮件地址不会被公开。 必填项已用*标注