5:07 /
sill
inst-fs-syd-prod.inscloudgate.net — Private
RMITAssignment
UNIVERSITY
(•)
7. Seeking clarification from your “supervisor” (instructor) when needed via discussion forums. 8. Create a program by recalling concepts taught in class, understanding and applying concepts relevant to solution, analysing components of the problem, evaluating different approaches.
3. Learning Outcomes
This assessment is relevant to the following Learning Outcomes:
1. Demonstrate knowledge of basic concepts, syntax and control structures in programming 2. Devise solutions to simple computing problems under specific requirements 3. Encode the devised solutions into computer programs and test the programs on a computer 4. Demonstrate understanding of standard coding conventions and ethical considerations in programming.
4. Assessment details
Note: Please ensure that you have read sections 1-3 of this document before going further.
You must meet Functional Requirements (4.1), Code+Justification Requirements (4.2) and Documentation Requirements (4.3) to obtain the full mark for this assignment. You can also attempt the Bonus Requirements (4.4).
4.1) Functional Requirements:
Important: The functional requirements below must be implemented and justified by following the 4.2 Code+Justification requirements.
Fl) Allows the user to store an arbitrary number of records of the same type. May store more than 1 type of record.
F2) Allows the user to add, remove and modify such records.
F3) Uses at least two separate windows (that can exist simultaneously): one for main menu or high-level operations and at least one more for more specialised operations (e.g. entering/editing details).
F4) Have information and operations organised within the windows using tables, text fields, buttons and presentation-related operations from weekly live lectures.
Tip: As you are not given marks for creativity or the usefulness of the program, do not spend too much time thinking of what is a “good” program. What is good depends on how well the code is written, justified and documented (refer to sections 4.2 and 4.3).
4.2) Code+Justification Requirements (15 marks): To receive marks for Code+Justification requirements, you must use the following code concepts to make a functionally cohesive program that also meets the functional requirements. You must only use concepts explained and demonstrated in the weekly live lectures held by Gayan (typically held on Monday nights). If you require the use of some additional concepts, please seek clarification through the CanvasAssignmentsAssignment 2 forum. Your work cannot be simply a renamed version of an example shown in class. Code without justification in the required format would attract no more than 50% of the mark allocated for that component. Comments without code will not attract any marks. An important note on Java code validity: A program with even one red dot (compilation error) cannot be tested and therefore will attract 0 marks for this section. Code concept Requirements (15 marks when justified as required) — No partial marks for dot points 01) Single-class object oriented code using provided template with… 1×3=3 marks • Appropriate name for java file (must not use names like Assignment2.java); Follows conventions shown in IIE solution lectures, other standard class materials and common ones in the Java API. The main method should have only one line to create an object of the main application class (refer to startup code and week 6+ weekly live lecture examples). • Consistent code and comments formatting, with comments start on the line before the documented block/statement (e.g. not on lines with code). Only relevant, reachable code+comments included. • No uses of return in middle of methods, break, continue, System.exit or similar branching (spaghetti code) anywhere in the code. 02) Variables… 0.5×2=1 mark • Some of which are object member variables (may include arrays). These are explicitly private, non-static and there should be no = signs near declarations. Every reference to an object member variable from a method starts with this. (i.e.
Page 2 of 4
RMIT
UNIVERSITY
“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. CB) 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. 05) Multi window user interface using GTerm… 1×3=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. 06) Conditional execution and repetition 1×2=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. C17) Arrays • Uses multiple arrays of primitive or shown Java I classes to maintain records. Only standard Java arrays used. (e.g.