COSC2452-Assignment 2 Solved

For this assignment, assume that you are a freelance programmer creating a small tool or a utility program of your own choosing to add to your portfolio of simple Java applications. With this project you aim to demonstrate to potential employers or clients how you can:

1. Create a small tool or utility program using (exclusively) a limited set of fundamental code concepts

2. You are able to analyse and evaluate your implementations against possible alternatives in your code documentation.

Note: You must not just “throw in the concepts” to your program just because they need to be there; it should be clear from the code why a certain concept should be there and you must further explain these through your comments. You will also need debug your code on your own and document any issues, etc.

I

You must meet Functional Requirements (4.1), Code+Justification Requirements (4.2) and Documentation Requirements (4.3) 

4.1) Functional Requirements:

Important: The functional requirements below must be implemented and justified by following the 4.2 Code+Justification requirements.

F1) 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 :

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 Canvas→Assignments→Assignment 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
 
CJ1) Single-class object oriented code using provided template with... 
•                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. 
CJ2) Variables...

 
• 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. 
 
“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.
CJ3) Constructor 
• The class has only one constructor and all object member variables, arrays, etc. declarations are explicitly initialised in this constructor before any other operations.
CJ4) Methods 
•                 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.
CJ5) Multi window user interface using GTerm...

 
•                 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, addImageIcon, setFontSize, etc. to improve presentation.

•                 Uses GTerm buttons. Performs operations on rows selected from tables.
CJ6) Conditional execution and repetition 
•                 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. 
CJ7) Arrays 
• 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 gtMain; private GTerm gtSub;

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 
D1. 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