This is intended to be another early experience with requirements documents, documentation, and software design. Note many of the required items (time tracking, etc.) will also be required for the final submission, so it will also be good practice.
You are required to develop and deposit “milestones-(initials).txt” into your code repository before leaving lab. Please generate a rubric for 40 points with weighting of your choice, one per group member.
It is normal if you have difficulty with accurately weighting tasks or determining what is easy or hard. The important aspect of this thought experiment, historically, is that it is a highly efficient exercise to help you and your groups prioritize what is needed, start early in dividing up tasks and most importantly get started as a team.
You are welcome to collaborate with your group but you must:
Discuss your proposed plan to TAs before leaving your lab for participation credit. If your individual "milestones" were completed prior to lab, you can leave lab early if and only if you can also demonstrate meaningful either by demoing your early progress or showing your time log.
We will grade this challenge using the rubric below.
+12 A time log of what you worked on for the project, which will be included in your final report to Dr. Emrich. We expect roughly >= 4 hrs of work in addition to the 1 hours in lab (5 total) +4 Evidence of a repository and code that you have checked in that matches at least one of your assigned task(s). +4 A rubric and short report on how this challenge went.
If you decide to move a task from in-lab to a “next step”, please detail in your report/plan why and how we might be able to help overcome any technical issues. Examples include but are not limited to “task much more challenging than expected” and an attempt to explain why. This rubric/plan is solely for planning and feedback purposes.
To submit your solution, you must submit a single .txt (or PDF) file on Canvas prior to the deadline with the required summary, the link to your repository and your compilable task, your individual time log and your individualized next rubric/plan.
Note: If you are using your own systems for testing, please demo your
compilable task to TAs next week in lab (if needed)