PRG2104 Object Oriented Programming Final Assessment

Late submission will be awarded 0 mark.

Create a submission folder named “Project_yourID”. Put your project folder and documentation report into this submission folder. Zip it and submit this zipped file to the Microsoft Team.

In Microsoft Team, the zip file can be attached to the assignment page with a softcopy of reports

Please use the assignment link for code versioning. The record in git repository will be used to support originality of the work.

Students are required to demonstrate the ability to apply their knowledge of inheritance and polymorphism in their implementation of the solution. Students also need to make use of the scalaFX GUI library to create a GUI Application. Other GUI libraries are not acceptable.

This system should make use of object-oriented programming features.

Students should propose additional classes or traits to achieve a good design that reduces code repetition.

Students are required to design their user interface for ease of use.

The complexity of the system will determine the grade of the project. The more you demonstrate your object-oriented skills, the higher your possible grade will be, which aligns with the uniqueness and originality of your program.

The following are examples of projects you can explore:

• Food Distribution Management: Track and manage the distribution of food supplies.
• Nutritional Information Database: Provide information on the nutritional content of various foods.
• Agricultural Resource Management: Manage resources for sustainable agriculture.
• Community Engagement Platform: Facilitate communication and collaboration among community members.

Attention:

If you refer to any sources from youtube, github or other code repositories in creating the application, please do cite. Any works that are not created by you will not be considered in marking.

If you refer to sources from your senior, you will be caught for plagiarism. The lecturer will check and compare your code to the previous submission library.

• SBT builder (Any Latest Version)
• Any IDE of your choice
• Java 21 Library
• Scala 3 Library
• ScalaFX 21 (other GUI libraries are not allow)

• A cover page (use the template provided).
• A documentation report includes the UML diagrams that describe the classes/objects identified from the problem domain, and their relationships among these classes/objects used in the program. – in softcopy
• A description that shows the program is working for all 4 features.
• Your GitHub Account username, which you used to enrol in the GitHub assignment
• An A4 page to be written by you on the personal reflection that includes:
  • A description of how you applied the above object-oriented concepts in your assignment.
  • The problems encountered during this assignment and how you solved these problems.
  • An evaluation of the strengths and weaknesses of your submitted work.
• The project/solution files, including the source code and application program. – in softcopy
• A video that shows the running of your application.

NOTE: Submitting the assessment means you have agreed that your work is original and comply with the rules and regulations (refer to Academic Impropriety)

• Paper size — A4 (Use only one side of the paper)
• For the personal reflection write-up — Paragraph format
• 1.5-line spacing
• Font size — 12 points

*subject to change anytime without prior notification

The work that you submit must conform to those regulations.

Refer to ASSESSMENT CRITERIA FOR Project table for further elaboration of marking distribution.

• Correct and complete
• Classes – both basic classes and the “collection” class
• Identification of data fields, visibility modifiers and types.
• Constructors
• Additional features / operations provided.
• Originality and Uniqueness.
• Github record provide very good confidence of originality.

• inheritance
• polymorphism
• abstract class
• generic programming.

• Perfectly correct diagram.
• All notations are correctly used.
• Class members are complete, and
• The diagram is consistent with the class design.

• Menu navigation
• Execution of all the required operations
• Input validations
• Completely correct, efficient and elegant use of programming constructs.
• Methods are extensively used to achieve complete modular programming.

• Illustrated an excellent mastery in Event Driven Programming and correct use of layout classes.
• GUI Components and layout component are design and use correctly.

• Full adherence to naming convention with appropriate, meaningful and correctly spelt identifier names.

• An excellent correct use of third-party libraries to solve problem.
• No errors in utilizing the third-party libraries.
• Demonstrated in depth understanding of third-party library model.

• Complete and well written documentation.
• All Required section is included.
• Table of content is formatted properly.
• Very few typo or spelling mistake.

• Correct and complete
• Classes – both basic classes and the “collection” class
• Identification of data fields, visibility modifiers and types.
• Constructors
• Quite original and uniqueness
• Github records gives good confidence of originality.

• inheritance
• polymorphism
• abstract class

• Complete with only one very minor error in notations used.
• Diagram is consistent with class design.

• Menu navigation
• Execution of all the required operations
• Correct and efficient use of programming constructs.
• Methods are used to achieve a high degree of modular programming.

• Illustrated a good mastery in Event Driven Programming and correct use of layout classes.
• GUI Components and layout component are design and use correctly with minor error.

• Adherence to naming convention with meaningful, appropriate and correctly spelt identifier names.

• Make a good use of some third-party libraries to solve problem.
• No errors in utilizing the third-party libraries.
• Demonstrated in good understanding of third-party library model.

• Complete and well written with only one very minor error in documentation.
• Not all required section is included only miss one section.
• Table of content is formatted reasonably.
• Few typo or spelling mistake.

• Correct and complete
• Basic classes
• Identification of data fields, visibility modifiers and types.
• Constructors
• Partial originality and uniqueness
• Github records give moderate confidence of originality.

• inheritance
• polymorphism

• Quite complete with not more than two minor errors in notations used.
• Diagram is consistent with class design.

• One or two minor errors.

• Illustrated an average mastery in Event Driven Programming and correct use of layout classes.
• GUI Components and layout component are design and use correctly with some error.

• General adherence to the naming convention with one or two minor errors.

• Make use of some third-party libraries to solve problem.
• Minor errors in utilizing the third-party libraries.
• Demonstrated in average understanding of third-party library model.

• Quite complete and good written with only few minor error in documentation.
• Not all required section is included only miss few section.
• Table of content is formatted.
• Few typo or spelling mistake.

• Some errors or 1 incomplete basic class.
• No originality with some uniqueness
• Github records give poor confidence evidence of originality.

• Correct application of inheritance

• Some errors in notation or diagram’s consistency with class design.

• Incomplete application program.
• Some errors.

• Illustrated a poor mastery in Event Driven Programming and correct use of layout classes.
• GUI Components and layout component are design and use correctly with few error.

• Limited adherence to naming convention.

• Make use of a third-party libraries to solve problem.
• Some errors in utilizing the third-party libraries.
• Demonstrated in poor understanding of third-party library model.

• Incomplete in documentation with few major error.
• Not all required section is included with missing lot of section.
• Table of content is partially formatted.
• Lot of typo or spelling mistake.

• Very major errors or more than 1 incomplete basic class.
• Github records give very poor confidence of originality.

• Illogical inheritance hierarchy

• Major errors in notation or diagram’s consistency with class design.

• Grossly incomplete application program.
• Very major errors.

• Illustrated a very poor mastery in Event Driven Programming and incorrect use of GUI components.

• Serious lack of adherence to the naming convention.

• Make use of a third-party libraries.
• Major errors in utilizing the third-party libraries.

• Grossly incomplete in documentation with major error.
• Major required section is not included.
• Table of content is not formatted.
• Lot of typo or spelling mistake.