Design, implement and test a software system using object-oriented principles in Java FX for specific client requirements. Your tutor will act as the client and it is your responsibility to elicit requirements

CSYM025 Visual Object Software

CSYM025 Assessment Brief

Assessment	Brief
Module title:	Visual Object Software	Module code:	CSYM025
Assessment code/title:	PJ1	Assessment weighting/word- limit:	100%/ 4000 words
Submission date:	29/01/2026 15:00	Feedback date:	28/02/2026
Assessment Task:		Resit date:	25/03/2026
Title (Question): Setting the scene:	Individual Coursework Project

This assessment is designed to prepare students for creating object-based solutions to software problems within a contemporary integrated development environment. The objective is to equip students with the syntax and semantics of the underlying model while promoting good practice in software construction and testing.

CSYM025 Assessment Task

Design, implement and test a software system using object-oriented principles in Java FX for specific client requirements. Your tutor will act as the client and it is your responsibility to elicit requirements and represent them as user stories. Design should include class diagrams and use case diagrams. Implementation should be in phases adopting principles of agile development. The initial implementation phase should consist of developing a console application.

The assessment consists of 3 key elements:

1. Creation of an Application/System in Java FX
2. Technical Report
3. Video Demonstration

Functional Requirements

1. The application should have a graphical user interface (GUI) built with JavaFX for user interaction.

2. The data should be persisted in data files. The application should connect to the files and perform CRUD (Create, Read, Update, Delete) operations. The objective is to assess your object-oriented design and development skills. Hence, use of database management systems and query languages (e.g., SQL) are strictly prohibited and would result in an overall failure.

3. The core entities in the application should be modelled as classes (e.g., Customer, Product, Order etc.). These classes should encapsulate data and behaviour.

4. The classes should implement principles of abstraction, inheritance, polymorphism as suitable.

5. The application should provide useful features like searching, reporting, and notifications etc.

6. The code should have sufficient documentation and comments for readability and maintenance.

7. For improved code reuse and modularity, common utility functions could be kept in a separate util package/module.

8. Exceptions should be handled properly to make the application resilient and user-friendly. Custom exception classes can be created.

9. Input data validation should be done to reject invalid/incorrect data and prevent exceptions.

10. Code should follow standard Java coding guidelines and best practices for quality and maintenance.

11. Testing should include both white box (JUnit tests) and black box (test logs).

12. The adoption of object-oriented principles should be evident in your implementation of the above requirements.

Deliverables 

A. Technical Report

The report should consist of the following sections (in the same order):

1.Username and password for all relevant accounts (if implemented).
2.UML Class Diagrams.
3.A list of all the user stories implemented in a tabular format.

For example: User Story
Details of user story 1
Details of user story 2
Implemented (Partial/Full)
Full
Any comments
No error validation.

4. Explanation of the main sections/fragments of the code. Provide information on how the code has evolved from a console application. How has the code evolved in phases? What was the process followed? You may want to refer to the class diagrams to explain code.

5. Screenshots of the system showing all key features.

6. Evidence of Testing:
a. Black box Testing: Test logs providing information of all the tests carried out (including any failed tests for functionality not implemented)
b. White box Testing: Code Listing of all the JUnit test cases.
c. List of any bugs and/or weaknesses in your system (if you do not think there are any, then say so). Bugs that are declared in this list will lose you fewer marks than ones that you do not declare.

7. References If you have borrowed some code from elsewhere (e.g., from a book or some resource n the web you must indicate clearly what they are and include references). Click here for further information.

B. Source Code

The source code must be well documented with necessary comments. Consistent and clear indentation of the code is also important.

Source code needs to be submitted in two forms:

i. As a single ZIP archive (.zip file consisting of all “.java” files, unit tests, data files).

ii. A commented full listing in a separate Word document named “Full Source Code Listing”. This should include the console application.

C. Video Demonstration

In addition to the report, you must submit a video demo (URL) of your assignment. The demo should be about 10 minutes long and should cover all your work in a logical way. You should explain the main phases of design and implementation covering the main fragments of code. How did the code evolve in phases from a console application? Your face and voice need to be clear in the video. It should also include a walkthrough of using the software and must demonstrate the key features. The module tutor reserves the right to invite you for an online viva-voce. Poor demo/viva could negatively influence other sections in the marking criteria and may result in an overall fail grade. You may also be referred for a suspected academic misconduct investigation.

Submission

To submit your work, go to the ‘Assessment and Submission’ area on the NILE site and use the relevant submission points/links:

1. E-Submission of documents through Turnitin on NILE as TWO separate WORD documents [Document 1 = Report & Document 2 = Full Source Code Listing].
2. E-Submission of a single ZIP archive that contains all the source code files (.java), unit tests, data files, ReadMe file, Properties file and so on. The archive must be named with your student ID, e.g. 12345678.zip where 12345678 is your student ID.
3. Public link (url) to video demonstration. Use of Kaltura (Kaltura MyMedia – University of Northampton) is recommended. You must ensure that the video link is accessible to the marker (do not set it to private access).
4. Failure to follow the above submission guidelines may result in a capped or fail grade.

Learning Outcomes

On successful completion of this assessment, you will be able to:

i) Select and explain current principles underlying the object-oriented (OO) approach to developing software systems which are complex, conceptually challenging.

ii) Demonstrate understanding of how OO techniques help in the development of correct, robust and reliable software systems, through the application to technical problems.

iii) Select and explain current practical issues associated with the technology, design, and operation  f GUIs, in line with professional practice.

iv) Select and successfully implement appropriate testing methodologies of software systems

v) Demonstrate a consistent and positive work ethic that indicates a preparedness to take appropriate risks, explore multiple options and create opportunities for self-development in a purposeful manner.

vi) Apply a wide range of software implementation methods.

💡 Need Help with UML Diagrams & Agile Phases?

Request to Buy Answer

CSYM025 Assessment Guidance

You will find a link to your online reading list on NILE in the “About this module” section.

Use of Generative AI

Artificial Intelligence within this Assessment:

Some uses of Generative AI may be deemed unethical in your Assessment. Further guidance on the conditions for allowable use of Generative AI will be given by the module team.

AI within Assessments

AI Categories: Category 1: No Gen AI allowed For this type of assessment, you are unable to use Gen AI due to the design of the assessment. For example, a closed book exam where you are required to demonstrate within controlled conditions that you have core knowledge or a skill in a particular area. As it is not possible to use Gen AI within this type of assessment, you do not need to acknowledge use of Gen AI.

Academic Practice support

The Skills Hub is a central repository where you will find a range of support for your study and assessments: University of Northampton Skills Hub

Feedback:

Feedback should be received within 20 working days.

An announcement will be sent out via NILE to inform you of when feedback is available. Instruction on Anonymity for students Further guidance is available online

CSYM025 PJ1 Marking Rubric

Pass 50-59% Work is of satisfactory quality Satisfactory design of program and user interface. Satisfactory adoption of programming principles. Class diagrams are satisfactory	Merit 60-69% Work is of commendable quality Good quality design of program and user interface. Adequate adoption of object- oriented programming principles and agile methodology. Class diagrams are well designed and presented	Distinction 70-100% Work is of exceptional quality Excellent design of program and user interface. Adherence to good object-oriented programming principles and agile methodology. Class diagrams are very well designed and presented
Most basic system requirements are met by adopting agile development process.	All basic and some advanced requirements are met by adopting agile development process. MVP shown in class.	All basic and many advanced requirements are met by adopting agile development process. MVP and incremental developments shown in class.
Evidence of either white box or black box testing with satisfactory code coverage	Evidence of both white box and black box testing with good code coverage	Evidence of both white box and black box testing with extensive code coverage
Some thought has been given on how the code is structured. Some work on error handling	Code is well structured to enable white box testing, reusability and debugging. Good work on error handling	Code is very well structured to enable white box testing, reusability and debugging. Excellent work on error handling
Satisfactory engagement in timely completion of Codio exercises and agile methodology	Good engagement in timely completion of Codio exercises and agile methodology