If there is no progress compared to Deliverable 4, give 0.
Any comments from Deliverable 4 must be addressed.
For any comment that was not addressed, deduct -2 points.
(10 points) Your team must complete at least one feature whose progress was incomplete in the prior deliverable. This includes automated tests.
-7 points for each feature delivered where the commit history shows it was not developed using test-driven development, which means writing the test before the implementation code. See the test-driven web development class and class recording, and use your use cases! Not recoverable by regrade because you can’t go back in time to use TDD. Do not squash your commits such that you can’t tell TDD was used. -7 points.
Your team must develop 2 to 3 core user stories/features of your app.
(15 points each) At least 2 new features are started
If no feature implementation is started, or there are no automated tests, give 0.
At least 3 automated tests written for each feature (which may be failing i.e. is commented out)
Use the process Dr. Greg demonstrated in class for test-driven web development for a use case.
-7.5 points for each feature delivered where the commit history shows it was not developed using test-driven development, which means writing the test before the implementation code. See the test-driven web development class and class recording, and use your use cases! I will be strict about this. Not recoverable by regrade because you can’t go back in time to use TDD. Do not squash your commits such that you can’t tell TDD was used. -7.5 points.
If you did not use TDD, if I see a bug in your implementation that a simple test could have caught, -5 additional points.
At least some new HTML, React, CSS and Typescript code is present for each new feature. It is expected each feature will have at least 6 hours of development time total at a minimum and the code should be commensurate with that. So get help fast from your team if you get stuck!
(5 / 15 points each) For each feature developed, submit the mockup that was made first before implementing the feature. Put this in the 1-6 minute video, then show the feature as implemented/progressed on. There can be some changes from the mockup / don’t avoid improving the UI just to match the initial mockup.
It is best practice to make a simple UI mockup/sketch before implementing any UI more complicated than a single button or HTML element
Record a short 1-6 minute video showing the progress your team has made, walking through, for each feature, the user story/use case/mockup, tests, then code, then website in the browser, and people contributing to the development for each.
If this video is missing, -15 points
Your video must show you going over your commit history showing that you did TDD for the feature. Otherwise, -7.5 points as specified above for not doing TDD. I will be strict about this!
This is meant to simulate the demo that happens with the Product Owner and stakeholders in an industry sprint review
If the working web application is so far behind it’s UI does not resemble your application, -30 points
If login is not finished, -10 points
The developers should read this and are expected to, as needed, review/complete parts of the Interactive React Textbook earlier than other team members.
All team members are expected to do self-directed learning using Google, StackOverflow, other online resources, and ask people or other classmates questions. Developers are expected to help any other team members with technical questions.
Use the example applications found/submitted from Assignment 4 to help you here
Communicate with other teams to get help with problems and advice, using Discord. Your team may use their code/resources like any other resources, just requiring citation.
Setting up the build environments and the necessary dependencies.
Your README file should detail the installation and build process for your application. Make sure it works on each person’s machine.
If there is nothing, -10 points.
You must upload a video to your team Discord channel in the COS420 Discord, from a synchronous team meeting/screenshare on Discord or Zoom, where each team member shares their screen showing the app working on their machine, to show that this has been set up and works for each team member. No video editing, one person on the team should record their screen continuously through the meeting (you can use the Zoom record meeting feature to do this easily).
Previous submission of the video counts if all team members were present
Your team’s short 1-6 minute video counts if all team members show they did some code and show the app running on their machine
If this is not present, -20 points.
For each team member not showing it works on their machine, -10 points
If you’re having trouble here, get help early and often by asking questions in the #question channel.
New version of the application ( /40 or /50)
If there is no progress compared to Deliverable 4, give 0.
Any comments from Deliverable 4 must be addressed.
For any comment that was not addressed, deduct -2 points.
(10 points) Your team must complete at least one feature whose progress was incomplete in the prior deliverable. This includes automated tests.
-7 points for each feature delivered where the commit history shows it was not developed using test-driven development, which means writing the test before the implementation code. See the test-driven web development class and class recording, and use your use cases! Not recoverable by regrade because you can’t go back in time to use TDD. Do not squash your commits such that you can’t tell TDD was used. -7 points.
Your team must develop 2 to 3 core user stories/features of your app.
(15 points each) At least 2 new features are started
If no feature implementation is started, or there are no automated tests, give 0.
At least 3 automated tests written for each feature (which may be failing i.e. is commented out)
Use the process Dr. Greg demonstrated in class for test-driven web development for a use case.
-7.5 points for each feature delivered where the commit history shows it was not developed using test-driven development, which means writing the test before the implementation code. See the test-driven web development class and class recording, and use your use cases! I will be strict about this. Not recoverable by regrade because you can’t go back in time to use TDD. Do not squash your commits such that you can’t tell TDD was used. -7.5 points.
If you did not use TDD, if I see a bug in your implementation that a simple test could have caught, -5 additional points.
At least some new HTML, React, CSS and Typescript code is present for each new feature. It is expected each feature will have at least 6 hours of development time total at a minimum and the code should be commensurate with that. So get help fast from your team if you get stuck!
(5 / 15 points each) For each feature developed, submit the mockup that was made first before implementing the feature. Put this in the 1-6 minute video, then show the feature as implemented/progressed on. There can be some changes from the mockup / don’t avoid improving the UI just to match the initial mockup.
It is best practice to make a simple UI mockup/sketch before implementing any UI more complicated than a single button or HTML element
Record a short 1-6 minute video showing the progress your team has made, walking through, for each feature, the user story/use case/mockup, tests, then code, then website in the browser, and people contributing to the development for each.
If this video is missing, -15 points
Your video must show you going over your commit history showing that you did TDD for the feature. Otherwise, -7.5 points as specified above for not doing TDD. I will be strict about this!
This is meant to simulate the demo that happens with the Product Owner and stakeholders in an industry sprint review
If the working web application is so far behind it’s UI does not resemble your application, -30 points
If login is not finished, -10 points
The developers should read this and are expected to, as needed, review/complete parts of the Interactive React Textbook earlier than other team members.
All team members are expected to do self-directed learning using Google, StackOverflow, other online resources, and ask people or other classmates questions. Developers are expected to help any other team members with technical questions.
Use the example applications found/submitted from Assignment 4 to help you here
Communicate with other teams to get help with problems and advice, using Discord. Your team may use their code/resources like any other resources, just requiring citation.
Setting up the build environments and the necessary dependencies.
Your README file should detail the installation and build process for your application. Make sure it works on each person’s machine.
If there is nothing, -10 points.
You must upload a video to your team Discord channel in the COS420 Discord, from a synchronous team meeting/screenshare on Discord or Zoom, where each team member shares their screen showing the app working on their machine, to show that this has been set up and works for each team member. No video editing, one person on the team should record their screen continuously through the meeting (you can use the Zoom record meeting feature to do this easily).
Previous submission of the video counts if all team members were present
Your team’s short 1-6 minute video counts if all team members show they did some code and show the app running on their machine
If this is not present, -20 points.
For each team member not showing it works on their machine, -10 points
If you’re having trouble here, get help early and often by asking questions in the #question channel.