Please enable JavaScript.
Coggle requires JavaScript to display documents.
FIA3 - General Comments 2022 - Coggle Diagram
FIA3 - General Comments 2022
Academic Integrity
From previous assignment (FPA)
Do not treat exemplars as templates
Hand in all the bits (don’t open yourself to QCAA variations)
Harvard referencing
Response
Be really good at the code and back date your doco, or be really good at the doco and fake the code, or be really good at both
Turn on and take notice of spell and grammar checker
PC plus SC plus Constraints equals whole solution
If you use the word ”details” in your response, check to see you have provided the details and not just wrapped up a bunch of stuff you haven’t done with a convenient label.
Time constraints as excuse won’t wash for QCAA markers
Beware excessive boilerplate text on App pages
Make sure links in references work.
Video talk about what works, not (excessively) what doesn’t (remember it’s a prototype)
Be critical of limits on response (pages, minutes in video etc)
Data Story
Don’t have numbered attributes of the same domain in a single table (e.g. attr1, attr2,…, attr
n
)
Don’t include occluded lines in DFDs, no double headed arrows
Most working applications asked for Student name on booking even though it should have been available in the session data – hangover from PTAPP?
Pseudo code
Don’t allow word wrap in pseudo or real code
Get pseudo code blocks right: BEGIN/END, END-IF, etc
Pick the most important processes to model as IPO charts and pseudocode (e.g. Make a booking)