This document outlines the requirements for a journal assignment in a Data Structures and Algorithms course. Students must submit 10 programming profiles, each worth 10 marks. Each profile includes:
1) The program code that was written, which must compile and run with test cases and documentation.
2) A personal commentary reflecting on coding issues faced, competency gained, types of errors encountered, debugging and testing strategies used, code optimization techniques, and resources used.
3) Optionally, the BlueJ MILE file tracking coding efforts can also be included. The journal aims to be a record of self-reflection on growing programming skills.
This document outlines the requirements for a journal assignment in a Data Structures and Algorithms course. Students must submit 10 programming profiles, each worth 10 marks. Each profile includes:
1) The program code that was written, which must compile and run with test cases and documentation.
2) A personal commentary reflecting on coding issues faced, competency gained, types of errors encountered, debugging and testing strategies used, code optimization techniques, and resources used.
3) Optionally, the BlueJ MILE file tracking coding efforts can also be included. The journal aims to be a record of self-reflection on growing programming skills.
Computer Science 272: Data Structures and Algorithms (Java) (Revision 6)
COMP 272 R6 Journal Assignment Page 1 of 1
Journal of Programming Profiles Maximum 100 marks. Create ten (10) programming profiles. Each programming profile is worth 10 marks. Essentially, the programming profile is a self-reflection exercise, and the journal is a record of your own observations on your growth in coding competency. Marking will be based on the extent and quality of reflection exhibited for each of the ten programs. Include ten (10) programs that you worked on as part of this course in your profile. For each program, your profile should include the first two components listed below and optionally a third component. All three components should be zipped together into one file for each program. 1. Required: the program (compiles and runs; includes test cases and internal documentation). The first component is straightforward; it is exactly what youd normally submit as a solution for a programming problem assignment.
2. Required: your personal commentary on key coding issues you faced and coding competency you gained. Include two or more of the following: significant types of errors/warnings you faced whether you were able to correct them as soon as you encountered them what debugging strategy you used what commenting strategy you used (eg., Javadoc) what testing strategy you used (eg., JUnit) what code optimization techniques you followed, if any resources that you referred to any other comment that reflects on your learning to program The second component is quite fluid, and it simply attempts to record your personal learning experience, a self-reflection on your own coding habits.
3. Optional: BlueJ MILE file. The third component is also straightforward; you simply track your coding efforts using BlueJs MILE extension and submit the MILE file corresponding to that program.