CT4030

Object Oriented Programming

& Software Design

Assignment-1
YOUR GAME NAME

May 2024
Contents
1. Introduction...................................................................................................................................3
a. Video URL..................................................................................................................................3
2. System Requirements....................................................................................................................3
3. Object Oriented Software Design..................................................................................................3
a. Usecase Diagram.......................................................................................................................3
b. Class Diagram.............................................................................................................................3
c. Sequence Diagram.....................................................................................................................3
4. Application Testing.........................................................................................................................3
5. Conclusion.....................................................................................................................................4
References.............................................................................................................................................4
 1. Introduction
Motivation (2-3 lines).

Gameplay objectives overview (3-4 lines).

a. Codebase disclaimer
Example:

The code not marked with my student ID at the beginning of a class is borrowed from (provide URL).

The classes A, B and C are borrowed from (provide URL).

Briefly discuss the reason for this decision.

b. Video URL
A URL to your video demonstration. This could be a YouTube link, a OneDrive link or an attached file.

2. System Requirements
Bullet points and/or MoSCoW analysis (4-6 key requirements, prioritised)

3. Object Oriented Software Design

UML design approach, meaning,

a. Usecase Diagram
A Usecase diagram that has correlation to the key requirements.

Accompanied discussion (4-8 lines).

b. Class Diagram
(600-1500 words)

A Class diagram that can be seen fulfilling most requirements.

Highlight how classes were shortlisted.

Highlight where in the design OOP was adopted/used.

Provide examples of inheritance and polymorphism in your class diagram.

Discuss what benefits, if any, OOP/polymorphic behaviour has brought to the design.

Use code snippets where necessary.

Make sure that the class diagram has the same classes as the code.

c. Sequence Diagram
Optional.

If you provide one, it should have the same classes as in the class diagram.

4. Application Testing
At the minimum a test suite.

Tes Test Description Inputs Expected Actual Status

 t Outcomes Outcomes
no.
1 The user can successfully login Username, Main System FAIL.
provided correct credentials. Password windows crashed. The
should load. system
crashed
because
of an
uncaught
exception.
1.a Main Main Pass.
windows windows
should load. should load.

5. Conclusion
What percentage of the requirements were completed. This could be a table or a list, same as
‘System Requirements’ section but now added with a ‘status’ column.

What worked well (2-3 lines).

What didn’t work well and why (3-4 lines).

References