Faculty FACULTY OF ENGINEERING AND TECHNOLOGY

Assessment Name End Assessment Paper Code CJAV/G23E

(Eg: End/Sup)

PROGRAMMING IN
Module Name Module Code C7-JAV-11
JAVA

Submission Mode Turnitin &

Semester Jul-Dec 2023
( E.g Jul-Dec-2021)
(E.g Turnitin, Blackboard
blackboard, hardcopy)

Total Marks Duration 4 WEEKS

100 (E.g.,
mins/hours/days/weeks

Submission Date
Assessment Type
(Applicable for
(Eg: Submission 08th Nov 2023
submission-based
Written/Practical/Sub
exams only)
mission)
Eff Date: 09-08-2023

Instructions

Deadline for submission is 8th November 2023 on or before 23.59

1. Read the Scenario and the requirements really well and do as the requirements say.
2. The project is to be done as individuals.
3. All Code must be in Java, and the Database of preference is MySQL, however any other RDBMS is allowed.
4. You are required to write a report for your project.
5. The report is to be written in a visible font not exceeding a font size of 12 for regular text.
6. Along with your artefacts, submit an SQL script that will create your database and tables and entries in your
database if needed.
QP-ASR-001|Rev 001

7.
8. Submission of your Report should be on Turnitin.
9. Submission of Artefacts should be on Blackboard.
10. Usage of AI tools in this assessment is not allowed.
11.
12.

Page 1 of 5
 Project: Apartment Management System

Scenario:
In this scenario, you are a new graduate who has just completed his/her Honors degree in Computing, and has
been taking on some freelance software development projects. At this time there is a real-estate company in
your city, Greenview Estate that has been thriving in the recent past after building new apartment complexes.
However, the estate has been facing some challenges with the daily running operations of the entire company
across its different complexes, and they seek your services to build a software system that tackles some of their
challenges.

Challenges:

1. Tracking tenants complaints

2. Tracking rent payments
3. Property Maintenance

Solution Needed:
The real estate company needs a desktop application to run their daily operations, this desktop application
Eff Date: 09-08-2023

should have a connection to a database, preferably MySQL Database. This database should house a whole host
of data regarding the all the property and tenants and their rent payments.

Functional Requirements:
A. Authentication

 The admin should be able to create all types of accounts,

 The landlord can create a tenant,

 A tenant can create their own account but such accounts have to be verified by the landlord for
them to start working. All tenants should be older than 18 years.

 All Users should be able to login using their email/username and password. The passwords should
QP-ASR-001|Rev 001

be hashed before storing them in the database.

B. Profile Management

 All users should be able to update information on their profiles

C. Property Management

 The landlord should be able add, update and archive property and the property’s details like
address, building/block number, number of units etc.

Page 2 of 5
  The landlord should be able to assign tenants to apartment blocks and rooms.

D. Complaints Management

 The landlord should be able to assign a person of interest to a particular complaint so that they can
see to it that the complaint is taken care of.

 Track the complaint:

(a) Who lodged the complaint,

(b) When did they lodge the complaint,

(c) Status of the complaint,

(d) When was the complaint closed.

E. Notification Center

 The landlord and the Admin should be able to create a notification or announcement.

 All users should be able to view the announcement board.

Eff Date: 09-08-2023

F. Payments Center

 The Landlord should record the receipt of payments from tenants with details like date / date and
time.

 The tenant should be able to view all the payments made

G. Reports Center

 The landlord should be able to generate reports:

(a) Financial Reports(rent payments)

(b) Maintenance logs

QP-ASR-001|Rev 001

H. Event Logging

 All events should be logged to the file called logs.txt

Project Guidelines:
1. Proper Naming Conventions should be followed.

2. Code should be well organized into packages and classes.

3. Code should be written in a modular fashion.

4. Proper Implementation of Exception handling is required.

Page 3 of 5
 5. Data from forms should be validated.

6. The User Interface should be user-friendly, proper use of Layouts is required.

7. All data should be stored in database.

8. The report should have proper structure with clear headings and sub-headings.

9. All diagrams in the report should be clear.

Marking Guidelines:
Artefact:
Item Marks
[70]
1) Database Connectivity : 3
2) Authentication :
a) Registration 4
b) Login 3 7
3) Profile Management:
Eff Date: 09-08-2023

a) All users should be able to edit and update their personal details 4
4) Property Management:
a) Add new property – Admin and Landlord 3
b) Update property details – Admin and Landlord 3
c) View the occupied apartments 3
d) Assign empty apartment to a tenant 3 12
5) Complaints Management:
a) Lodge a complaint - Tenant 3
b) View the status/progress of the complaint – Tenant, landlord and admin 3
c) Change status of the complaint. - Landlord 3 9
6) Notification/Announcement Center:
a) Post an announcement – Landlord and admin 3
b) View the announcement board – All users 3 6
7) Payments Center:
a) Record Receipt of payment in the system- Landlord 3
QP-ASR-001|Rev 001

b) Retrieve and view payments made by tenants –Tenants and landlord 3 6

8) Reports Center:
a) Generate Rent Received Reports according to timeframe chosen by user – Landlord and Admin 3
b) Generate a report for the maintenance logs – Landlord and Admin 3 6
9) Logging events 3
10) Exception Handling 2
11) Good Coding practices 3
12) Appearance 3
13) Presentations
a) Voice Clarity 2
b) Content Delivery Approach 2
c) Clarity of concepts 2 6

Page 4 of 5
 Documentation(Report):
Items Marks
[30]
1) Introduction to the project – Explain the problem and how you tackled the problem 3
2) Database Design –
Create an ERD to show the database design.
The database should be Normalized to the 3rd form – show how your database design is said to be in 6
3rd normal form
3) Design Diagrams:
a) Flowchart 3
b) UML Diagrams (Class diagram, Use Case Diagram) 6 9
4) Labeled Screenshots of the running of the program 4
Eff Date: 09-08-2023

5) Challenges faced, 2
solutions found & 2
Future possibilities 1 5
6) References 3
QP-ASR-001|Rev 001

Page 5 of 5