ICT502

Object Oriented Programming Assignment Help

ASSESSMENT GUIDE

ICT502

OBJECT-ORIENTED PROGRAMMING

Semester 2, 2024

Assessment Overview

Note: * denotes ‘Hurdle Assessment Item’ that students must achieve at least 40% in this item to pass

the unit.
 

Referencing guides

You must reference all the sources of information you have used in your assessments. Please use the IEEE referencing style when referencing in your assessments in this unit. Refer to the library’s referencing guides for more information.

• https://elearning.vit.edu.au/pluginfile.php/473840/block_html/content/VIT%20Library%20Refer encing%20-%20IEEE%20-%2007042020.pdf

Academic misconduct

VIT enforces that the integrity of its students’ academic studies follows an acceptable level of excellence. VIT will adhere to its VIT Policies, Procedures and Forms where it explains the importance of staff and student honesty in relation to academic work. It outlines the kinds of behaviours that are "academic misconduct", including plagiarism.

Late submissions

In cases where there are no accepted mitigating circumstances as determined through VIT Policies, Procedures and Forms, late submission of assessments will lead automatically to the imposition of a penalty. Penalties will be applied as soon as the deadline is reached.

Short extensions and special consideration

Special Consideration is a request for:

• Extensions of the due date for an assessment, other than an examination (e.g. assignment extension).
• Special Consideration (Special Consideration in relation to a Completed assessment, including an end-of-unit Examination).

Students wishing to request Special Consideration in relation to an assessment the due date of which has not yet passed must engage in written emails to the teaching team to Request for Special Consideration as early as possible and prior to start time of the assessment due date, along with any accompanying documents, such as medical certificates.

For more information, visit VIT Policies, Procedures and Forms.

Inclusive and equitable assessment

Reasonable adjustment in assessment methods will be made to accommodate students with a documented disability or impairment. Contact the unit teaching team for more information.

Contract Cheating

Contract cheating usually involves purchasing an assignment or piece of research from another party. This may be facilitated by a fellow student or friend or purchased on a website. The unauthorized use of generative Artificial Intelligence (AI) is also considered cheating. Other forms of contract cheating include paying another person to sit an exam in the student's place.
 

Contract cheating warning:

• By paying someone else to complete your academic work, you don’t learn as much as you could have if you did the work yourself.
• You are not prepared for the demands of your future employment.
• You could be found guilty of academic misconduct.
• Many of for pay contract cheating companies recycle assignments despite guarantees of

“original, plagiarism-free work” so similarity is easily detected by TurnitIn.

• Penalties for academic misconduct include suspension and exclusion.
• Students in some disciplines are required to disclose any findings of guilt for academic misconduct before being accepted into certain professions (e.g., law).
• You might disclose your personal and financial information in an unsafe way, leaving yourself open to many risks including possible identity theft.
• You also leave yourself open to blackmail - if you pay someone else to do an assignment for you, they know you have engaged in fraudulent behaviour and can always blackmail you.

Grades

We determine your grades to the following Grading Scheme:

Assessment Details for Assessment Item 1:

Overview

Introduction

You will submit work in tutorial activities during the study period. This is an individual assessment.

Part A

This is an individual assessment in which you will develop programs using Java programming concepts and OO principles based on problem definitions provided. You will be required to complete tutorial questions, laboratory exercises and a supervised programming test.

Setup your Environment or installation of Software’s:

Install For Java, JDK 18, NetBeans 19 or latest version

For Python, Python 3.7.0, Atom, Jupyter or latest version

Problem Description: Comparing Loans

Write a program that lets the user enter the loan amount and loan period in number of years and displays the monthly and total payments for each interest rate starting from 5.00% to 8.00%, with an increment of 1/8. Here is a sample run:

<Output>

Loan Amount: 10000 Number of Years: 5

<End output>

Use the formulas below to compute monthly payment and total payment.

𝑚𝑜𝑛𝑡ℎ𝑙𝑦𝑃𝑎𝑦𝑚𝑒𝑛𝑡 =

𝑙𝑜𝑎𝑛𝐴𝑚𝑜𝑢𝑛𝑡 ∗ 𝑚𝑜𝑛𝑡ℎ𝑙𝑦𝐼𝑛𝑡𝑒𝑟𝑒𝑠𝑡𝑅𝑎𝑡𝑒

1 − 1

(1 + 𝑚𝑜𝑛𝑡ℎ𝑙𝑦𝐼𝑛𝑡𝑒𝑟𝑒𝑠𝑡𝑅𝑎𝑡𝑒)12∗𝑛𝑢𝑚𝑏𝑒𝑟𝑂𝑓𝑌𝑒𝑎𝑟𝑠
 

𝑡𝑜𝑡𝑎𝑙𝑃𝑎𝑦𝑚𝑒𝑛𝑡 = 𝑚𝑜𝑛𝑡ℎ𝑙𝑦𝑃𝑎𝑦𝑚𝑒𝑛𝑡 ∗ 12 ∗ 𝑛𝑢𝑚𝑏𝑒𝑟𝑂𝑓𝑌𝑒𝑎𝑟𝑠

Design: (Describe the major steps for solving the problem.)

Coding: (Copy and Paste Source Code here. Format your code using Courier 10pts)

Output screenshot: (Paste your output screenshot here. You need to apply the currency and percentage formats as well)

Submission Instructions

You will be marked based on your submitted zipped file on Moodle. You are most welcome to check your file with your lab tutor before your submission. No excuse will be accepted due to file corruption, absence from lecture or lab classes where details of lab requirements may be given.

Note: All work is due by the due date and time. Late submissions will be penalized at 20% of the assessment final grade per day, including weekends.

Part B

Write a program in java for class name BankAccount1, by creating an instance, accessing properties using accessor methods, and modifying properties using mutator methods.

• Properties/Attributes/Fields/instance variables:
  • Account Number (String)
  • Account Holder Name (String)
  • Balance (Double)
  • Account State (String) (for later use only)
     
    • Constructor
      • Takes all above fields as parameter
    • Methods:
      • Accessor
      • Mutator
      • Support methods (if required)

<Output>

Account Number: 123456789 Account Holder Name: John Doe Balance: 1000.0

Account State: Active

Updated Account Information:

Balance: 1500.0

Account State: Suspended

<End Output>

Design: (Describe the major steps for solving the problem.)

Coding: (Copy and Paste Source Code here. Format your code using Courier 10pts)

Output screenshot: (Paste your output screenshot here.)

Testing: (Describe how you test this program)

Submission Instructions

You will be marked based on your single PDF submitted through Turnitin on Moodle. You are most welcome to check your file with your lab tutor before your submission. No excuse will be accepted due to file corruption, absence from lecture or lab classes where details of lab requirements may be given.

Note: All work is due by the due date and time. Late submissions will be penalized at 20% of the assessment final grade per day, including weekends.

Part C
 

For this tutorial session, students are required to appear in practical test by demonstrating the execution of a Java program.

1. Participation in person during the tutorial session is mandatory for all students. Those who do not attend the test during the tutorial session will be marked as absent.
2. Supervised testing during week 6.

1. Only one attempt is allowed.

1. ONE Double-sided handwritten A4 sheet

Note: Submission will be allowed during tutorial hour only.
 

Marking Criteria/Rubric

You will be assessed on the following marking criteria/Rubric:

Assessment Details for Assessment Item 2:

Overview(Test will be scheduled during session 7)

Instructions for Mid Semester Test

In this individual assessment, you are required to appear in mid-semester test based on contents covered from 1 to 6 sessions. The weightage of the test is 20%, comprising descriptive questions related to Java programming. The allotted time is 60 minutes, with 5 minutes designated for preparation, 45 minutes for completing the test paper, and 10 minutes for submission.

For this individual assessment, you are tasked with completing a mid-semester test based on the content covered in the first six lectures. Only one attempt is permitted, and the midterm test will be accessible for one hour during week 7 within your lecture session.

If you cannot be present, you will be deemed to receive a zero mark for this assessment.

UNIT CODE: ICT502 TEST DATE: 12/09/2024 TIME: 10:30 AM (Mel time)

This mid semester test paper is set for a Total of 20 Marks.

This paper consists of 4 Questions

Total Number of Pages in this Question Paper (including this page): 2 Pages

READING TIME: 5 Minutes WRITING TIME: 45 Minutes SUBMISSION TIME: 10 Minutes

Allowable materials:

1. ONE Double-sided handwritten A4 sheet
    

Mid Semester Sample Test

1. What is the value of size after the following statements are executed?

result = 10;

result = result - 3; result = result * 4; result = result + 7;

[2 marks]

1. Write a class named Movie with fields for a movie’s title, director, and duration in minutes. Include get and set methods for each field. Include an equals() method that indicates that two movies are equal if they have the same title and director. Write a toString() method to print the movie's details. You need to write two (2) constructors for this class: an empty constructor; a constructor to initialise all fields.

[10 marks]

1. Write the main method in the testCircle class and call relevant methods by creating the object of Circle class.

[6 marks]

1. Create 2 objects circle1 and circle2 for Circle class.
2. Set the radius and color for circle1 to 5.0 and "Red".
3. Set the radius and color for circle2 to 3.5 and "Blue".
4. Print the details of both circles using the toString method.
    
5. Print the area of both circles using the getArea method.

[2 + 2 + 1 + 1 = 6 marks]

End of Sample Mid Semester Test

Note, the actual mid semester test will have more questions.
 

Assessment Details for Assessment Item 3:

Overview

Note: * denotes ‘Hurdle Assessment Item’ that students must achieve at least 40% in this item to pass the unit.s

ASSESSMENT ITEM 3:

This is a group assessment with a maximum of five students per group, all of whom must be on the same campus. You will design and implement an application after analysing the requirements provided in a case study. You are required to apply basic constructs and object- oriented programming principles in developing this software system.

Part A: Design Using UML Diagram (20 Marks) Description:

In Part A of the project, you will focus on the design aspect of the Library Management System by creating a comprehensive UML diagram. This phase involves thoroughly understanding the system requirements and identifying all necessary classes, attributes, methods, and relationships. The UML diagram should accurately represent the system's structure, including the Book, Patron, Loan, Library, and Main classes. Each class will include its respective attributes and methods, showcasing the relationships and interactions between them, such as associations and aggregations. The UML diagram must follow standard UML conventions, ensuring clarity and precision. Additionally, a brief documentation will accompany the diagram, explaining the design decisions and how they align with the project requirements. This part aims to provide a solid foundation for the implementation phase by offering a clear and well-structured blueprint of the system.

Task Breakdown

1. Understand the Requirements (2 Marks)
   • Review the problem description and identify all classes, attributes, methods, and relationships.
   • Ensure all functionalities are well understood before proceeding.
2. Identify Classes and Relationships (4 Marks)
   • Define the classes: Book, Patron, Loan, Library, Main.
   • Identify relationships between classes (e.g., Library contains Books, Patrons, and Loans).
3. Create UML Diagram (12 Marks)
   • Draw the UML diagram with the following components:
     • Classes with attributes and methods.
     • Relationships (associations, aggregations, compositions).
     • Inheritance where applicable.
   • Ensure the diagram is clear and follows UML standards.
4. Documentation (2 Marks)
   • Provide brief explanations of each class and their relationships.
   • Justify design decisions and how they meet the project requirements.

Marking rubric for Part A (Total: 20 marks)
 

Part B: Implementation in NetBeans IDE (30 Marks) Description:

Part B of the project involves the actual implementation of the Library Management System in Java using the NetBeans IDE. In this phase, you will translate the UML diagram from Part A into a functional Java program. This includes setting up the project structure in NetBeans, defining the Book, Patron, Loan, Library, and Main classes, and implementing their respective attributes and methods. The focus will be on adhering to object-oriented principles such as encapsulation, inheritance, and polymorphism while ensuring proper error handling and user-friendly command-line interaction. The Main class will feature a command-line interface that allows librarians to navigate the system and perform tasks such as adding/removing books and patrons, checking out/returning books, and displaying information.

Thorough testing will be conducted to verify the functionality of each feature, with screenshots captured as evidence. The final deliverable will include detailed documentation, code listings, and trial run evidence compiled into a Word document, accompanied by a README file with instructions on how to run the program. This part aims to bring the design to life, ensuring the system operates smoothly and meets all specified requirements.

Task Breakdown

1. Set Up the Project in NetBeans (2 Marks)
   • Create a new project and set up the necessary packages and classes.
   • Ensure the project structure is well-organised.
2. Implement Book Class (4 Marks)
   • Define attributes and methods.
   • Ensure proper encapsulation and error handling.
3. Implement Patron Class (4 Marks)
   • Define attributes and methods.
   • Handle book checkouts and returns appropriately.
4. Implement Loan Class (4 Marks)
   • Define attributes and methods.
   • Implement overdue fee calculation and information display.
5. Implement Library Class (6 Marks)
   • Manage collections of books, patrons, and loans.
   • Implement methods for adding/removing books and patrons, checking out/returning books, and displaying information.
6. Implement Main Class with Command-Line Interface (6 Marks)
   • Create an interactive menu system for librarians.
   • Ensure navigation is user-friendly and handles errors gracefully.
7. Testing and Documentation (4 Marks)
   • Test all functionalities thoroughly and capture screenshots.
   • Create a README file with instructions on how to run the program.
   • Combine design document, code listings, and trial run evidence into one Word document.
      

Second part is Video demonstration must follow the following protocols:

The whole group will be present in the video with face visible (Camera on). The whole group must introduce themselves and present their contributions. Then the team should discuss design and demonstrate the running of the system (VIT Ride Application). The video must not exceed more than 10 minutes

Workplan / Work breakdown Agreement (WBA)

You are expected to work as a group on this assignment and contribute very closely to approximately an equal amount of work (unless the special consideration policy outlined applies). In your workplan you must provide details about the contributions and how the work is organised and managed. In most cases, if this is followed, students will receive equal marks on those aspects to their teammates. The Workplan section must include the following information:

Student Name:

Contribution Description:

%age of Contribution:

I [NAME OF THE STUDENT] hereby accept the Work breakdown/contribution as agreed. [DATE]

NOTE: We will take into account your WBA while marking your assessments and the marks will be adjusted based on the WBA.

MARKING SCHEME / GUIDE

The assessment will be marked on the following criteria

Task1: Implementation (15 Marks)

1. Design in the code matches the design in the class diagram.

1. Coding standards. Applies to any code that has been touched by human hands (e.g. meaningful variable and method names, commenting, layout). We will look for meaningful identifier names (variable, classes, methods), inline comments, method header comments, class/module comments, layout.

1. Functional Completeness: All features are fully implemented, and snapshots are included in the report.
    

Task2: System Demonstrations (15 Marks)

1. Please start the video by discussing the contribution of each team member (i.e., which team member was responsible for which component in the system).

1. Students demonstrate understanding of the system, the relationship between the code and the design documents of the system.

1. Students should point out where in their code the constructs shown in their design documents are implemented.

Submission Instructions What You Have to Submit Team leader to Submit:

1. A document detailing the design of your solution in as much detail. It should include an updated UML diagram of the inheritance hierarchy as well as the component hierarchy of the system.

1. The code for each class in your design. Each class listing should be fully documented commencing with a heading that includes your name, student number, date written, and lecturer’s name, along with a brief description of the class. At the start of each method, there should be a comment clearly describing what the method does. This should be done in NetBeans only. Other IDE will not be accepted.

1. A readme.doc file with information on how to run your program. Include any extra information about your design and program that you wish the marker to know.

1. A Word document with evidence of trial runs of your program, i.e., screen printouts of the results where you have tested all the features of your code.

1. NetBeans project folder.

1. Your Recorded Video

1. Combine 1, 2, and 4 into ONE word document.

Put 3, 5,6 and 7 together in one zipped folder. Submit the zipped folder via LMS.

Submission Instructions
 

All submissions are to be submitted through Turnitin. Drop-boxes linked to Turnitin will be set up in Moodle. Assessments not submitted through these drop- boxes will not be considered. Submissions must be made by the end of session 12.

The Turnitin similarity score will be used to determine any plagiarism of your submitted assessment. Turnitin will check conference websites, Journal articles,online resources, and your peer’s submissions for plagiarism. You can see your Turnitin similarity score when you submit your assessments to the appropriate drop-box. If your similarity score is of concern, you can change your assessment and resubmit. However, re-submission is only allowed beforethe submission due date and time. You cannot make re-submissions after the due date and time have elapsed.

Note: All work is due by the due date and time. Late submissions will be penalized at 20% of the assessment final grade per day, including weekends.

Marking Criteria/Rubric

You will be assessed on the following making criteria/Rubric: