object oriented programming

Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

ASSESSMENT GUIDE

ICT502

OBJECT-ORIENTED PROGRAMMING

Semester 1, 2024

FEBRUATY 2024

Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

Assessment Overview

Assessment tasks Learning Outcome Mapping

Assessment ID

Assessment Item

When due Weighting ULO# CLO# for MITS

CLO# for GDITS

CLO# for GCITS

1 Tutorial and Programming Exercises/Test (Individual)

Part A Tutorial Questions

Part B Laboratory Exercises

Part C Practical Test

Part A - Session 2

Part B – Session 4

Part C – Session 6

3 x 10 % = 30%

1, 2 1, 3 1, 3 1, 3

2 Mid-Semester Test (Individual)

Session 7 20% 1 1, 2 1, 2 1, 2

3* Application Development (Group)

Part A – Design

Part B –

Implementatio n.

Part A – Session 8

Part B –

Session 12

Part A – 20%

Part B –

30%

1, 2, 3, 4

1, 2, 3, 4

1, 2, 3, 4 1, 2, 3, 4

Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

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 the purchase of an assignment or piece of research from another

party. This may be facilitated by a fellow student, friend or purchased on a website. Other forms of

contract cheating include paying another person to sit an exam in the student's place.

Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

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:

Grade Percentage

A 80% – 100%

B 70% – 79%

C 60% – 69%

D 50% – 59%

F 0% – 49%

Page | 5 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

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

Interest Rate Monthly Payment Total Payment

5.000% $188.71 $11,322.74

5.125% $189.28 $11,357.13

5.250% $189.85 $11,391.59

7.875% $202.17 $12,129.97

8.000% $202.76 $12,165.83

Assessment tasks Learning Outcome Mapping

Assessment ID Assessment Item When due

Weightin g

ULO# CLO# for MITS

1 Tutorial Questions

Part A (Individual) Session 2 10%

1,2 1,3 Tutorial / Laboratory Exercise Part B (Individual)

Session 4 10%

Tutorial Practical Test Part C (Individual)

Session 6 10%

Page | 6 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

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

o Account Number (String)

o Account Holder Name (String)

o Balance (Double)

o Account State (String) (for later use only)

Page | 7 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

 Constructor

o Takes all above fields as parameter

 Methods:

o Accessor

o Mutator

o 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 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 C

Page | 8 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

For this tutorial session, students are required to appear in practical test by demonstrating

the execution of a Java program implementation loops.

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 (Lab 5).

3. Only one attempt is allowed.

Note: Submission will be allowed during tutorial hour only.

Page | 9 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

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)

Assessment criteria Exceptional >=80% Admirable 70% – 79% Creditable 60% - 69% Acceptable 50% - 59% Unsatisfactory <=49

Tutorial/Laboratory

Part A

10 marks

Demonstrated advanced

techniques by completing the

tutorial (10)

Demonstrated some advanced

techniques by completing the

tutorial (7.5)

Demonstrated some

advanced and some basic

techniques by completing

the tutorial (6.5)

Did not complete the laboratory. Show some basic techniques by completing the tutorial. (5.5)

Limited or Not Submitted or

Academic Misconduct. (0)

Tutorial/Laboratory

Part B

10 marks

Demonstrated advanced

techniques by completing the

tutorial (10)

Demonstrated some advanced

techniques by completing the

tutorial (7.5)

Demonstrated some

advanced and some basic

techniques by completing

the tutorial (6.5)

Did not complete the

laboratory. Show some basic

techniques by completing

the tutorial. (5.5)

Limited or Not Submitted or

Academic Misconduct. (0)

Tutorial/Laboratory

Part C

10 marks

Demonstrated advanced

techniques by completing the

tutorial (10)

Demonstrated some advanced

techniques by completing the

tutorial (7.5)

Demonstrated some

advanced and some basic

techniques by completing

the tutorial (6.5)

Did not complete the

laboratory. Show some basic

techniques by completing

the tutorial. (5.5)

Limited or Not Submitted or

Academic Misconduct. (0)

Assessment tasks Learning Outcome Mapping

Assessment ID Assessment Item When due Weighting ULO# CLO# for MITS

2 Mid Term Test (Individual)

Session 7 20% 1 1,2

Page | 10 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

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 (April 15th - April 20th) within your tutorial session.

Assessment Details for Assessment Item 3: Overview

Assessment tasks Learning Outcome Mapping

Assessment ID Assessment Item When due Weighting ULO# CLO# for MITS

3 Application Development (Group)

Part A – Design Part

Session 8 20% 1 1,2

Application Development (Group)

Part B –Implementation.

Session 12 30% 1, 2,3,4 1, 2, 3,4

Page | 11 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

ASSESSMENT ITEM 3:

This is a group assessment (Group Size-5). You will design and implement an application after analyzing requirements given in a case study. You are required to apply basic constructs and OO programming principles in developing this software system.

Introduction (Part A) INSTRUCTIONS:

Design a VIT Ride Management System using UML(class )diagram.

The system should allow administrators to manage users, drivers, and ride requests. The application should include the following classes:

1. User:

Design a class representing the user entity in the system. Include attributes such as user ID, name, contact information, and any other relevant information. Methods: Constructors, getters, and setters. Methods for user-related functionalities (e.g., registering, removing, displaying).

2. Driver:

Design a class representing the driver entity.

Include attributes like driver ID, name, license number, vehicle information, and availability status. Methods: Constructors, getters, and setters. Methods for driver-related functionalities (e.g., registering, removing, displaying).

3. Ride:

Design a class representing a ride request or allocation. Include attributes such as ride ID, user ID, driver ID, pickup location, destination, and status. Methods: Constructors, getters, and setters, Methods for ride-related functionalities (e.g., requesting, allocating, displaying).

4.RideManager:

Design a class to manage users, drivers, ongoing rides, and ride history. Include appropriate methods for registering, removing, and displaying users and drivers.Include methods for ride management, such as requesting rides, allocating drivers, and displaying ride history. Methods for ride management (e.g., requesting rides, allocating drivers, displaying ride history).

Page | 12 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

5. Main:

Contains the main method for testing the functionalities. Creates an instance of the Ride Manager class and provides a menu system to allow administrators to interact with the system.

Create Relationships: User-Driver Relationship: Define the relationship between the User and Driver classes to represent the association between users and drivers. Ride-User-Driver Relationship: Establish relationships between the Ride, User, and Driver classes to represent the associations between ride requests, users, and drivers. You may add some more relationships from your understanding.

The classes should be designed using object-oriented principles such as inheritance, encapsulation, and polymorphism. The application should allow to perform the following tasks:

1. Register New Users:

Implement a method to register new users for the ride service, including details such as

name, student ID, and contact information.

2. Remove Users:

Implement a feature to remove users from the system based on their student ID.

3. Display All Users:

Develop a method to display a list of all users registered for the ride service.

4. Register New Drivers:

Implement a feature to register new drivers for the ride service, including details such as name, driver's license number, and vehicle information.

5. Remove Drivers:

Page | 13 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

Develop functionality to remove drivers from the system based on their driver's license number.

6. Display All Drivers:

Implement a method to display a list of all registered drivers available for rides.

7. Request a Ride:

Design functionality that allows users to request a ride by providing their current location and desired destination.

8. Allocate Drivers to Rides:

Implement a method to allocate available drivers to ride requests based on factors such as proximity and availability.

9. Display Ongoing Rides:

Develop a feature to display a list of all ongoing rides, including details about the user, driver, and current status.

10. Display Ride History:

Implement functionality to display a list of all completed rides, including information such as starting point, destination, and feedback.

Requirement for design

1. Utilize appropriate access modifiers for class attributes and methods. 2. Consider implementing appropriate getter and setter methods for encapsulation. 3. Use inheritance or interfaces where applicable to promote code reuse and

maintainability. 4. Consider any additional classes or interfaces that may be necessary to support the

outlined functionalities.

Page | 14 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

Submission Instructions

Submission: The report Application Development Design report of not excessing 2000 words must be submitted in the zipped folder through the Moodle submission link for assignment 3 Part A.

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 marking criteria/Rubric:

Assessment criteria Exceptional >=80% Admirable 70% – 79% Creditable 60% - 69% Acceptable 50% - 59% Unsatisfactory <=49

Class Design(5)

The class diagram is

exceptionally clear,

comprehensive, and

anticipates future

enhancements.

The class diagram is

admirable in clarity,

completeness, and

understanding of

entities.

The class diagram is

creditable, providing a

clear representation

but with minor gaps.

The class diagram is

acceptable, capturing

the fundamental

elements.

The class diagram is

unsatisfactory, lacking

clarity and

completeness.

Relationships(5)

Relationships are

accurately defined,

demonstrating a deep

understanding and

foresight.

Basic relationships are

present with potential

inaccuracies or areas for

improvement.

Relationships are

correctly defined,

showing a clear

understanding of

entity interactions.

Relationships are

acceptable, capturing

the basic interactions

but with noticeable

gaps.

Relationships are

unsatisfactory,

hindering the

understanding of entity

interactions.

Attributes and

Methods(5)

Attributes and methods

are well-defined,

showcasing a keen

understanding of best

practices.

Basic attributes and

methods are present but

with room for

improvement in

completeness.

Attributes and

methods are

creditable, providing

effective functionality

but lacking some

completeness.

Attributes and methods

are acceptable,

capturing fundamental

functionalities but with

noticeable gaps.

Attributes and methods

are unsatisfactory,

hindering effective

functionality.

Inheritance/Interfaces(5)

Inheritance/interfaces

are used optimally,

reflecting a deep

understanding and

forward-thinking.

Limited or unclear use of

inheritance/interfaces,

with potential for

improvement.

Appropriate use of

inheritance/interfaces,

contributing to a well-

organized class

hierarchy.

Inheritance/interfaces

are acceptable,

providing some level of

code reuse but with

room for improvement.

Inheritance/interfaces

are unsatisfactory,

causing confusion in

system design.

Page | 15 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

Introduction (Part B) This assignment will be completed in groups. INSTRUCTIONS:

This assignment is an extension of assignment 3 Part A, that is the team is working on the same case study

as in assignment 3 Part A, and Implement a VIT Ride Management System in Java.

Using the feedback provided by the teaching instructor, update the requirements of the VIT Ride application. Based on the conceptual class diagram of the whole system showing all classes and relationships, you are expected first to develop software application in Java implementing functionalities 1 to 10.

The system should allow administrators to manage users, drivers, and ride requests. The application should include the following classes:

1. User:

Instance Variables :name (String): User's name.,userID (String): User's ID, contactInformation (String): User's contact information.

Methods: Constructors, getters, and setters. Methods for user-related functionalities (e.g., registering, removing, displaying).

2. Driver:

Instance Variables: name (String): Driver's name, licenseNumber (String): Driver's license number, vehicleInformation (String): Driver's vehicle information.

Methods:Constructors, getters, and setters.Methods for driver-related functionalities (e.g., registering, removing, displaying).

3. Ride:

Instance Variables: user (User): User associated with the rid, driver (Driver): Driver assigned to the ride, currentLocation (String): Current location for the ride, destination (String): Desired destination for the ride, status (String): Current status of the ride (e.g., ongoing, completed).

Methods: Constructors, getters, and setters, Methods for ride-related functionalities (e.g., requesting, allocating, displaying).

4.RideManager:

Page | 16 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

Instance Variables:users (List<User>): List of registered users.drivers, (List<Driver>): List of registered drivers.,ongoingRides (List<Ride>): List of ongoing rides.,rideHistory (List<Ride>): List of completed rides.

Methods: Constructors., Methods for registering, removing, and displaying users and drivers.

Methods for ride management (e.g., requesting rides, allocating drivers, displaying ride history).

5. Main: Contains the main method for testing the functionalities. Creates an instance of the Ride Manager class and provides a menu system to allow administrators to interact with the system.

11. Register New Users: a. Implement a method to register new users for the ride service, including details

such as name, student ID, and contact information. 12. Remove Users:

Implement a feature to remove users from the system based on their student ID.

13. Display All Users:

Develop a method to display a list of all users registered for the ride service.

14. Register New Drivers:

Implement a feature to register new drivers for the ride service, including details such as name, driver's license number, and vehicle information.

15. Remove Drivers:

Develop functionality to remove drivers from the system based on their driver's license number.

16. Display All Drivers:

Implement a method to display a list of all registered drivers available for rides.

17. Request a Ride:

Design functionality that allows users to request a ride by providing their current location and desired destination.

Page | 17 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

18. Allocate Drivers to Rides:

Implement a method to allocate available drivers to ride requests based on factors such as proximity and availability.

19. Display Ongoing Rides:

Develop a feature to display a list of all ongoing rides, including details about the user, driver, and current status.

20. Display Ride History:

Implement functionality to display a list of all completed rides, including information such as starting point, destination, and feedback.

The classes should be designed using object-oriented principles such as inheritance, encapsulation, and polymorphism. The program should not use a graphical user interface (GUI) but should instead use a command-line interface.

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.

Page | 18 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

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

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

3. 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).

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

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

2. 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,

Page | 19 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

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.

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

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

5. NetBeans project folder.

6. Your Recorded Video

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

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:

Page | 20 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829

Assessment criteria

Exceptional >=80% Admirable 70% – 79% Creditable 60% - 69% Acceptable 50% - 59% Unsatisfactory <=49

Design-Matching

Implementation (5 Marks)

Code design aligns seamlessly

with the class diagram.

Design and code

mostly align with minor

discrepancies.

Adequate alignment

with some noticeable

design/code

mismatches.

Limited alignment,

significant design/code

discrepancies.

Poor alignment,

major design/code

inconsistencies.

Coding

Standards (5 Marks)

Exceptional adherence to coding

standards, including meaningful

variable/method names,

thorough commenting, and

consistent layout.

Very good adherence

to coding standards

with minor lapses.

Adequate adherence

with noticeable lapses

in coding standards.

Limited adherence,

several lapses in coding

standards.

Poor adherence,

numerous lapses,

impacting code

readability.

Functional

Completeness (5 Marks)

Report consists Implementation

of the all modules, bug-free, and

aligns with requirements.

Report consists Mostly

complete

implementation with

minor bugs.

Adequate completion

of modules in report ,

some notable bugs.

Limited completion,

significant bugs

impacting functionality.

Incomplete

implementation,

major bugs,

significant

functionality issues.

Individual

Contribution

Presentation (5 Marks)

Clear and comprehensive

presentation of each team

member's contribution.

Mostly clear

presentation with

minor omissions.

Adequate presentation,

some gaps or lack of

clarity.

Limited presentation,

significant gaps in

individual contributions.

Poor presentation,

major omissions or

unclear contributions.

Working System

Demonstration (5 Marks)

A fully functional system, is

demonstrated effectively.

Mostly functional

system with minor

glitches.

Adequate

demonstration with

some noticeable issues.

Limited demonstration,

significant issues

affecting functionality.

Incomplete or non-

functional system

demonstration.

Understanding of

Code-Design

Relationship (5 Marks)

Demonstrates a deep

understanding of how the code

implements the design

documents.

Shows good

understanding, with

minor gaps or

inaccuracies.

Adequate

understanding, with

noticeable gaps or

inaccuracies.

Limited understanding,

significant gaps in

linking code to design.

Poor understanding,

major gaps, inability

to link code to

design.

Page | 21 Victorian Institute of Technology www.vit.edu.au CRICOS Provider No. 02044E, RTO No: 20829