513364245300CP1401/CP5639 Assignment 2 Developers Journal
513364245300CP1401/CP5639 Assignment 2 Developers Journal
Your name
Assignment 1 Reflections and Lessons
Work Entries
Summary
The following is a copy of the journal section of the assignment for your reference Delete this section when you have finished.
A significant desired outcome for this subject is you learning to develop solutions to problems systematically and thoughtfully. That is, we are not only interested in the final product but in your process and the lessons you have learned through your experience. To encourage you in learning the systematic problem-solving process, you will record your work experiences and insights in a simple journal for this assignment submitted as a PDF file.
There are three parts to this journal:
Assignment 1 Reflections and Lessons
Work Entries
Summary
Assignment 1 Reflections and Lessons:
Before you begin working on this assignment, take some time to reflect on what you learned about your process through assignment 1, including how you will make changes this time based on any feedback you received. You could consider your previous reflection exercise from the practicals: https://github.com/CP1401/Practicals/tree/master/prac_07#reflection
Work Entries:
Each time you work on the assignment, record an entry in your journal that includes:
Date and time you worked, including duration
What you worked on with simple details, enough that someone reading it would understand
Any difficulties you faced and how you overcame them
Please do not include multiple entries for tiny work sessions. If you did 7 minutes, took a break then came back and did 37.5 minutes we don't need this level of detail just include a single entry of about 45 minutes. These entries can be quite short, but make sure your focus is on your process, not your actual code/work.
Summary:
Summarise the lessons you learned about the problem-solving process (not about Python code) through doing this assignment. This is the most important part where you reflect on your process and show what you have learned. Did anything you considered or changed based on assignment 1 reflection prove important or useful? How are you improving in terms of following a systematic development process? What would you differently next time?
Please note that the only reasonable way to write a journal is regularly, as you develop your solution. A journal that is completed at the end of the assignment after you've finished everything is not a journal and will not aid your learning experience as much.
Here is a sample journal entry that shows a 'satisfactory' level:
20/04/2024, 8:30 9:30am
Work: Wrote pseudocode for main function; nearly completed start and menu section.
Challenges: It took a few goes to remember how to deal with lists and functions in pseudocode. I checked the "Pseudocode Guide" and followed the examples, which helped. I am so grateful for the excellent guides and high-quality teaching in this subject :)
Criteria Exemplary (9, 10) Good (7, 8) Satisfactory (5, 6) Limited (2, 3, 4) Very Limited (0, 1)
JournalSLO120% Good first reflection showing learning; significant number of entries showing good problem-solving process including starting with planning; summary highlights useful lessons. Exhibits aspects of exemplary (left) and satisfactory (right)Some first reflection; reasonable number of entries but not enough; process is not exemplary (e.g., planning or testing are missing or not in appropriate order); summary lacks insight and clear lessons.Exhibits aspects of satisfactory (left) and very limited (right)No journal or trivial effort.
