DEPARTMENT OF COMPUTER SCIENCE SUMMATIVE COURSEWORK ASSIGNMENT BRIEF KEY INFORMATION

• Module Title: Java (Android Programming)
• Module Code: CS2PJ20
• Lecturer responsible: Dr Sadhana Jha
• Type of Assignment: Online Project Report and Demonstration
• Individual / Group Assignment: Individual Assignment
• Weighting of the Assignment: 40%
• Page limit/Word count: six A4 pages
• Expected time spent on this assignment (hours): Collection of weekly tasks (30hr).
• Items to be submitted and demonstrated:

o Face-to-face demo of the program of self-assessed demo sheet o A report in PDF, six pages A4 o A Zip file containing (i) source code (ii) APK (iii) README

• Work to be demonstrated face-to-face in Lab: Week 10 and 11 (March 16 and 23).
• Work to be submitted online via Blackboard by 12:00 noon 24th March 2023.
• Work will be marked and returned: 15 working days after the submission deadline (14^th April, 2023).

NOTES By submitting this work, you are certifying that the sentences, figures, tables, equations, code snippets, artworks, and illustrations in this report are yours, original and have not been taken from any other person's work except where explicitly the works of others have been acknowledged, quoted, and referenced. You understand that failing to do so will be considered a case of plagiarism. Plagiarism is a form of academic misconduct and will be penalised accordingly. The Universitys Statement of Academic Misconduct is available on the University web pages. If your work is submitted after the deadline, 10% of the maximum possible mark will be deducted for each working day (or part of) it is late. A mark of zero will be awarded if your work is submitted more than 5 working days late. You are strongly recommended to hand work in by the deadline as a late submission on one piece of work can impact on other work. If you believe that you have a valid reason for failing to meet a deadline then you should make an Exceptional Circumstances request and submit it before the deadline, or as soon as is practicable afterwards, explaining why. To make such a request log on to RISIS and on the Actions tab select Exceptional Circumstance: as explained at https://www.reading.ac.uk/essentials/The-Important-Stuff/Rules-and-regulations/ExceptionalCircumstances 1. ASSESSMENT CLASSIFICATIONS Your assignment will be marked according to the mark scheme outlined in Section 4. The mark scheme is designed so that the mark obtained in this way will correspond to the following qualitative degree classification descriptions: Degree Classification Description First Class (>= 70%) Strong technical knowledge and skill showed through development, proving a strong grasp of object orientation and advanced programming. Design choices are validated in the report, and the work shows the implementation of techniques beyond the standard material. Upper Second (60-69%) A solid grasp of the developed program with a good selection of advanced programming methods Report and code show some elements of creativity and originality and makes good use of existing work. Lower Second (50-59%) A reasonable range of grasp of the developed program, with few technical errors. Relevant and relatively well-organised code structure and report. Third (40-49%) Evidence of appropriate implementation showing success in progress towards providing a solution with the most technical content correctness. The work relies on simple examples or uses methods inconsistently. Pass (35-39%) Shows some evidence of study and implementation, but partially unfinished, flawed, or irrelevant, whilst showing some attempt to present a coherent solution. Fail (0-34%) Unsatisfactory work. 2. ASSIGNMENT DESCRIPTION SUMMARY In this coursework, you are required to IMPLEMENT AN ANDROID GAME and produce an APK from it that can be installed on an Android phone. You will then write a report that should include game screenshots (e.g., Fig 1), OOP design, instructions on how to run your code/Program and relevant references. You can choose the theme of the game. That is, you are free to make a game in almost any style you wish, provided you follow the marking criteria. You can also modify, customise and innovate the provided Game Framework or work on a game engine you have researched. Fig.1: Screenshot of Game for inspiration PROBLEM You are required to develop an OOP design before starting the implementation of your Android Game. This should be in the practical session in Week 8. In the REPORT, you should only include OOP Design and justification. Your game should: Have functionality to start individual games on a menu screen using a separate welcome or start screen. The welcome screen must function using the Android API libraries. Display the current score while playing. You must define a scoring mechanism. The game may have characters that the user controls by touch on the screen and/or other sensors. Typical game styles are arcade games, tower defence style, strategy games, puzzle games, and educational games. Have at least three game levels o Higher marks are available for levels stored in files and for randomly generated levels. o The levels must have different layouts or opponents with different behaviours or different features/characters/themes. o The player must be able to move in at least two dimensions (i.e., x and y). o The final score can be stored online. Have Opponents o These can be opponents that the player is attempting to defeat, dodge for points, or compete with. o You must have more than one opponent on screen at some point in the game. o The opponents must 'play' the game autonomously; this could be as simple as making random movements, for example. Research and implement optimisations to the memory and speed of the game. If you have done any optimization, then include both non-optimized as well as optimized results in your report. There are marks available for improvements that extend the code or implement more features in the system (not gameplay features). These can take many forms, but some of the suggested ways to achieve these marks are below: o Creating an online high score list. o Researching and improving the multithreading of the game by using multiple threads to handle different systems in the game. o Creating a system for the users to create their own levels in-game. The game should be implemented using Android libraries. Use of game engines (e.g., Unity, Libgdx, etc.) is not recommended. You should use and modify the provided Game Framework code, and you should ensure you change the default package name of the classes in the project otherwise, it may not install during testing. Of course, you can develop your own code from scratch or use other game engines; however, you MUST distinguish your work from the available code in the engine. 3. ASSIGNMENT SUBMISSION REQUIREMENTS FRONT PAGE

• Module Code: CS2PJ20
• Assignment report Title: Android Game
• Student Number (e.g., 25098635):
• Date (when the work is completed):
• Actual hrs spent on the assignment:
• Assignment evaluation (3 key points):

1. .
2. .
3. .

ASSIGNMENT CONTENT Please follow these instructions carefully. You may lose credit if you do not follow these instructions. If you exceed 4 pages, any content after Page 4 may be ignored. SUBMISSION REQUIREMENTS:

1. An electronic report in PDF on Blackboard by the specified deadline. [4-page max]
2. A Zip containing (i) Source Code, (ii) installable APK and (iii) instructions to run code (README).

ON THE DAY OF DEMO (16^th March & 23^rd March)

1. Bring the filled self-assessed demonstration sheet.
2. Demonstrate your app to a Staff member in the Lab.

4. MARKING SCHEME REPORT AND DEMO WEIGHTAGE

Section	Percentage of grade
Report	30%
Demonstration See the demonstration self-assessment sheet for a breakdown	70%

REPORT MARK SCHEME

Page No.	Section	Mark (100)
Page #1	Title Abstract Maximum 50 words overview of the entire project covering important features/results	10
Page #1	Section 1 Introduction and Showcase A short informal graphical presentation of the application which may include screenshots with some description of the characters, levels, total points, etc.	20
Page #2	Section 2 OOP design A brief description of (a few sentences about) the design of the app (marks are also given for the description of unimplemented and/or unfinished features). This includes: OOP design with a critical description of how the design helped you in the implementation A statement on finished and unfinished classes	20
Page #3	Section 3 Memory usage and Speed improvements A short description (a few sentences) about the improvement of memory efficiency and speed efficiency for your game	20
Page #3	Section 4 Improvements/extensions A short description (a few sentences) about new extensions you have researched and implemented (cite the articles you researched)	20
Page #4	Section 5 Conclusions A maximum 50 words summary of the essential results and conclusions Reference Correctness of the submission	10
Total = 100

DEMO MARKING SCHEME

Section	Description	Marks (100)
1	Code style (2 marks for each point): Following Java code conventions throughout the project variable and class names method names indentation rules Using inline comments, frequency Javadoc comments for every function (except getters/setters)	10
2	Overall OOP design and API usage: Appropriate use of inheritance (2 marks) Appropriate use of Abstract classes (2 marks) Use of Android API classes/methods (Other than in base code) (3 marks) Greater than 3 original classes (3 marks)	10
3	Functionality: On-screen menus (1 mark) Scores (1 mark) Controllable character (1 mark) Sensor interaction (touch/ accelerometer/ etc) (1 mark) The game has levels. If works correctly (4 marks), if only attempted (2 marks) Use of standardised data structures (e.g., List, Vector, Collection, Date) If works correctly (10 marks), if only attempted (5 marks) Randomly/procedurally generated features: If works correctly (10 marks), if only attempted (5 marks) Opponents (AI): If works correctly (4 marks), if only attempted (2 marks)	32
4	Design quality (both game and other game screens) (1 mark each): Professional looking Understandable game flow Can locate start in the code Feedback to a user instead of crashing or recovering Runs smoothly without interruptions Installs without error Starts/exits without error. Program does not crash	8

5	Improvements marks: Online high score list o Works (10 marks) o Attempted (5 marks) Multithreading improvements o Works (10 marks) o Attempted (5 marks) Memory optimisation o Works (5 marks) o Attempted (3 marks) User Level Creation o Works (5 marks) o Attempted (3 marks)	30
6	Other extension/improvement / innovation Works (10 marks) Attempted (5 marks) Note: either the attempted marks or the works marks will be given (so you can only receive 5 marks per attempt max, and there is a maximum of 10 marks for this section but tick off any extra work done anyway!) For attempted marks to be awarded, the feature must be at such a state that the code could have worked but does not due to bugs or similar reasons.	10

Attachments:

Java-Work.pdf