If there is no progress compared to the prior Deliverable, give 0.
Any comments from the prior Deliverable 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 without at least 2-3 automated tests. See the test-driven web development class and class recording, and use your use cases and mockups to guide development! Not recoverable by regrade if less than 2 tests for the feature; if there are problems with the tests you can fix them for regrade credit.
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 without at least 2-3 automated tests.
You must show these tests in your team's progress video to get credit.
See the test-driven web development class and class recording, and use your use cases! Not recoverable by regrade if less than 2 tests for the feature; if there are problems with the tests you can fix them for regrade credit.
If you did not have 2-3 running passing automated tests, 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 roughly 3 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! I encourage you to do some pair programming.
(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, this is for example covered in the official React documentation and also there is a longer example here in the web textbook
10 points: Record a short 4-10 minute video showing the progress your team has made, walking through, for each feature, show the user story/use case briefly, then the mockup, then the automated tests, then the code, then the website in the browser, and say who contributed what to the development for each.
This is meant to simulate the demo that happens with the Product Owner and stakeholders in an industry sprint review.
It also mimics how you need to explain your code to others during a code review.
If this video is missing, -10
Here is an example video from Deliverable 4 from Team D Fall 23. Starting 0min 34seconds is a good example for a single feature. Be sure to show the test code for each feature and briefly explain them, don’t just show that tests run.
If you are missing any of "show the user story/use case briefly, then the mockup, then the automated tests, then the code, then the website in the browser, and say who contributed what to the development for each"
-5 for each thing missing
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 and component libraries from the finding examples class 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.
You may use any code you find, you just need to cite it in comments and link to where you found it
As a reminder, you may use generative AI at any point in your development process
You just need to cite it in any code or documentation e.g.
// <Tool e.g. Claude 3.5 sonnet> was used to <ideate, research, generate, edit, debug, etc>
You must fill out this form for your AI use as per the syllabus policy
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.
Fill out these tables for the new application and submit it on Brightspace
New version of the application ( /40 or /50)
If there is no progress compared to the prior Deliverable, give 0. Any comments from the prior Deliverable 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 without at least 2-3 automated tests. See the test-driven web development class and class recording, and use your use cases and mockups to guide development! Not recoverable by regrade if less than 2 tests for the feature; if there are problems with the tests you can fix them for regrade credit. 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 without at least 2-3 automated tests. You must show these tests in your team's progress video to get credit. See the test-driven web development class and class recording, and use your use cases! Not recoverable by regrade if less than 2 tests for the feature; if there are problems with the tests you can fix them for regrade credit. If you did not have 2-3 running passing automated tests, 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 roughly 3 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! I encourage you to do some pair programming.
(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, this is for example covered in the official React documentation and also there is a longer example here in the web textbook
10 points: Record a short 4-10 minute video showing the progress your team has made, walking through, for each feature, show the user story/use case briefly, then the mockup, then the automated tests, then the code, then the website in the browser, and say who contributed what to the development for each. This is meant to simulate the demo that happens with the Product Owner and stakeholders in an industry sprint review. It also mimics how you need to explain your code to others during a code review. If this video is missing, -10 Here is an example video from Deliverable 4 from Team D Fall 23. Starting 0min 34seconds is a good example for a single feature. Be sure to show the test code for each feature and briefly explain them, don’t just show that tests run. If you are missing any of "show the user story/use case briefly, then the mockup, then the automated tests, then the code, then the website in the browser, and say who contributed what to the development for each" -5 for each thing missing
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 and component libraries from the finding examples class 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. You may use any code you find, you just need to cite it in comments and link to where you found it As a reminder, you may use generative AI at any point in your development process You just need to cite it in any code or documentation e.g. // <Tool e.g. Claude 3.5 sonnet> was used to <ideate, research, generate, edit, debug, etc> You must fill out this form for your AI use as per the syllabus policy 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.
Fill out these tables for the new application and submit it on Brightspace