7COM1025 Programming for Software Engineers Assignment Brief 2026

7COM1025 Assignment Brief

Assignment title: coursework

Module code: 7COM1025

Module title: Programming for Software Engineers

Target date for return of marked assignment: 25-05-2026

You are expected to spend about 40 hours to complete this assignment to a satisfactory standard.

This assignment is worth 50% of the overall assessment for this module.

Learning Outcomes

LO1 – Design and implement a substantial software artefact.

LO2 – Evaluate, choose, and employ appropriate data structures and algorithms.

LO3 – Refactor part of a software item to achieve a specified goal.

LO4 – Be able to design a test suite and perform a set of tests.

Submission Requirements

Students should submit on Studynet the following three items:

1. a single pdf document containing the report with the UML class diagrams and version control snapshots,
2. a zipped project folder containing the source codes folder, test folder, and an executable jar file for running the final program,
3. a screen recording video showing the functionalities of your final program.

Marks awarded for

Source code will be checked against the report and the video to confirm both that the work has been implemented by yourself, and its design.

• UML Class diagram. (10 marks)
• System functions. (40 marks)
• Use of version control, with suitable commit messages. (5 marks)
• Appropriate design and implementation. (30 marks)
• Use of JUnit testing. (10 marks)
• Report format and writing quality. (5 marks)

Total: 100 marks

Implement a system according to the following Description

The Furzefield Leisure Centre (FLC) needs software for managing the bookings of group exercise lessons made by the members. The centre offers different group exercise lessons on both Saturday and Sunday. The lessons could be Yoga, Zumba, Aquacise, Box Fit, Body Blitz, etc. Each lesson can accommodate 4 members at most.

For either day (Saturday or Sunday), there are 3 lessons per day: 1 in the morning, 1 in the afternoon, 1 in the evening. The price of each lesson is different. The lesson price for the same exercise will remain the same even if they run at a different time.

A member who wants to book a lesson needs to first check the timetable and then select a lesson on a day. A member can check the timetable by two ways: one is by specifying the day (Saturday or Sunday) and the other is by specifying the exercise name. Members are allowed to change a booking, provided there are still spaces available for the newly selected lesson. A member can book as many lessons as they want so long as there is no time conflict.

After each group exercise lesson, members are able to write a review of the lesson they have attended and provide a numerical rating ranging from 1 to 5 (1: Very dissatisfied, 2: Dissatisfied, 3: Ok, 4: Satisfied, 5: Very Satisfied). The review and rating information will be recorded in the system.

After four weeks (four weekends), the software system must print:

• a report containing the number of members per group exercise lesson on each day, along with the average rating;
• a report containing the group exercise which has generated the highest income, counting all the same exercise lessons together.

In your final deliverable, provide data covering at least 4 different types of group exercise lessons, 10 members, and 20 reviews (with rating), which can then be displayed in the output reports. You need to design at least 8 weekends of timetable (i.e., 48 lessons) by yourself.

Note: you do not need any kind of external database for this program. The final program should be self-contained. The reports can be printed to System.out, or output to a suitable GUI interface. You also do not need any kind of security protocol.

Your Tasks

1. Create a class diagram, highlighting the main Java classes in the system and their associations. Include the attributes and key methods.
2. Implement the system, using Junit tests to confirm the functionality. Record all the functionalities of your final system in a video.
3. Write a short report (no page limit, about 8 pages should be sufficient) explaining your design and implementation. Discuss:
   a. Any assumptions made about the system, in addition to the above description.
   b. The overall structure and design of your system.
   c. The JUnit tests.
   d. Any refactoring used during the development of the system.
   e. Any design patterns/design principles used.

Deliverables

A. Develop your code using any version control software. Take snapshots of your project repository and commit messages. Include the snapshots in your report.

B. Submit to Studynet:

1. Your report with the UML class diagrams and version control snapshots in a single PDF document.
2. A zipped project folder containing the source codes folder, test folder, and an executable jar file for running the final program.
3. A screen recording video showing the functionalities of your final program.

Answer

Request Answer of this Assignment