sill
inst-fs-syd-prod.inscloudgate.net — Private
RMIT
UNIVERSITYDescription of the Signature Assignment
(m)
“this dot”, e.g. this.gt). Descriptive variable names used and does not use vague names (e.g. numRecords) • Used in place of duplicated literals. Demonstrates understanding of primitive data types vs. class types where relevant. 03) Constructor 1×1=1 mark • The class has only one constructor and all object member variables, arrays, etc. declarations are explicitly initialised in this constructor before any other operations. 04) Methods 102=2 marks • All methods are explicitly public and non-static. Methods are created when absolutely necessary or when it reduces duplication of code. • One or more methods created by student must take parameters and one or more methods created by student must return values. Both could be demonstrated using the same method. C15) Multi window user interface using GTerm… 103=3 marks • Uses GTerm exclusively for inputs. Most, if not all, user inputs must be taken via either text fields or text areas (vs. getInputString). May use password fields and dialogue boxes. • Uses GTerm exclusively for outputs. Must use tables with headings and columns. Minimal use of .show…Dialog methods to display outputs. Uses GTerm’s methods setXY, addlmagelcon, setFontSize, etc. to improve presentation. • Uses GTerm buttons. Performs operations on rows selected from tables. C16) Conditional execution and repetition 102=2 marks • Uses if/else/else if appropriately and exclusively for non-repeating conditional execution and at least one reachable else if statement. Conditions do not include tautologies. Every code block in every if/else/else if/while structure is reachable. • Uses while-loops appropriately and exclusively for repetition. Loop condition describes all situations under which the loop will repeat and condition fails eventually. Conditions do not include tautologies. Pathways are not redundant. 07) Arrays 103.3 marks • Uses multiple arrays of primitive or shown Java API classes to maintain records. Only standard Java arrays used. (e.g. does not use ArrayLists, etc.) • Array lengths are determined at run-time (e.g. based on how many records the user wants to store). • All array manipulation performed by student using while-loops, if-statements, etc. without using other classes. Justification Requirements Note: You will not receive full marks allocated for the CJ requirements above unless each occurrence is justified as required below. Type of code Evaluate and justify your choice over other possible alternative… Declarations (also applies to method definitions) Identifier names Data types Localities of declaration (why object-level vs. parameter-level vs. method-level vs. block-level, etc.). Contents of code blocks Formulations (is there a simpler way to meet requirements without creating this code block?) Inclusions (what you have added and why?) Sequences (why are these in this order?) Exclusions (what you haven’t added and why) Conditions Formations of the logic (e.g. “is glass half full” vs. “is glass half empty”, etc.) Template/Start-up code In the most initial form, your code must take the following organisation: public class Assignment2RenameThisClass private GTerm Pt?; public Assignment2RenameThisClass() ( this.gtMain . new GTerm(600, 400); this.gtSub . new GTerm(400, 600); } // The main method must only perform the included operation. // Do not add any other code to the main method. public static void main(String[] args) ( Assignment2RenameThisClass a2obj . new Assignment2RenameThisClass(); ) } You can rename identifiers to suit. You can create the second GTerm object later but it still must be initialised in the constructor. 4.3) Documentation Requirements (3 mark penalty if requirements below not met): Important note: Documentation must match with testable, functional and justified code to attract marks. Dl. Create an illustrated PDF user guide (one file): Must be written to show a non-programmer how to make use of the functions of the application (based on functional requirements). Must include screenshots of sample inputs and relevant/corresponding outputs. Include instructions on what the user can and cannot do (e.g. what they can and can’t input). Do not refer to code in the written sections or show any code even in the screenshots.
Page 3
RMIT
UNIVERSITY
4.4) Bonus Requirements
Important note: The total mark of Al+A2+A3 is capped at 45 (for a full break-down, see CanvasAssignments). To obtain a bonus marks for this assignment, you need to be able to get full marks for the non-bonus/standard requirements of tl assignment.
B1: Submit at least 1 work-in-progress version of your assignment (minimum requirement is CJ1) and then submit your final version of assignment 2 one day before the deadline for +0.1 marks or 2 days before the deadline for +0.2 marks, etc.
5. Referencing guidelines