0. Format

In a GitHub issue titled journal_1_<cwl> filed to your 310 journal repository (e.g., journal_<cwl>), answer the questions below (example issue title: journal_1_kdchin). 

IMPORTANT: If your journal is not submitted exactly this way, you will not receive credit; the ability to follow this straightforward instruction cannot be waived! The creation time / last edit for this issue must be before the submission deadline (Friday, October 18th @ 6pm).

Your responses will be assessed by course staff for their thoroughness and completeness. Additionally, you will have a one-on-one reflection with your lab TA in the lab immediately following the journal submission deadline, based on your submitted written responses. Both the written and oral components will factor into your final bucket grade for this assignment.

1. Reflection

This part of Journal 1 asks you to reflect on your development process for C1. It covers two Learning Areas: LA1: Testing and LA4: Construction.

1.a) Reflect on how your team collaborated by writing about one rose (something that went well), one bud (something that is emerging that you want to continue to build upon), and one thorn (something that should be addressed) with your code review process and/or your teammate agreement. You may choose to discuss these with your partner to improve collaboration for C2!

1.b) Reflect on the planning you completed for C1 (either as a part of J0, or independently). How did the work that you planned to do differ from the work that you actually ended up doing? Name at least one reason why you think it differed. (If you accomplished exactly what you planned, what did you do to ensure this?)

1.c) How many new tests did you add in C1 that made new kinds of assertions (either from your partner's C0 tests or new tests that you added while writing your implementation)? How does this number differ from the amount that you had predicted in J0--is it lower, higher, or about the same? Why do you think this happened?

1.d) Examine your code with a critical eye toward code quality. If you were to give it a bucket grade (beginning, acquiring, developing, proficient), what would you give it, and why? Name at least 3 linked code examples from your project repository to support this assessment.

1.e) If you were to ship your C1 code, how many defects do you think exist in your system right now? What factors went into your analysis?

2. Planning

This part of Journal 1 asks you to apply your learning toward planning for C2. It covers the LA0: Process Learning Area.

You may do this part collaboratively with your teammate(s).

2) Describe three new features that you will implement for C2, in the format of user stories. Each of the user stories should detail how a portion of the C2 spec will be built by your team. Create your user stories in your project_teamXXX repo using GitHub's user story issue template and provide links to each of them in your journal. Each team member should create their own user stories in collaboration with their other members (e.g., there should be 3*<#teamMembers> unique user stories). Ensure your teammate(s) understand your user stories well enough that they could implement them without additional information: engineering tasks can be a big help here!.