Hello, if you have any need, please feel free to consult us, this is my wechat: wx91due
INT101 – Python for AI (2024-25)
Assessment 1 – Code & Play Game Design Project
|
Assessment number |
1 |
|
Contribution to overall module assessment |
30% |
|
Date on which assessment given |
Monday, 10 March 2025 |
|
Submission deadline |
Sunday, 18 May 2025 |
1. Learning Outcomes for this Assessment
This assessment aims to evaluate your ability to apply the fundamental Python programming concepts and constructs covered in this module. Through the development of a small-scale game, you will demonstrate your understanding of basic Python syntax, control structures, functions, and data structures. The project will provide a practical context for you to implement these concepts while fostering creativity and problem-solving skills.
This assessment directly aligns with learning outcomes A and B, allowing you to showcase your proficiency in using Python for real-world applications and your ability to translate theoretical knowledge into functional code.
By completing this project, you will not only reinforce your programming foundations but also gain hands-on experience in designing and implementing a tangible solution.
2. The Task
|
Aspects |
Details |
|
Command-Line Interface (CLI) |
Create a main menu that displays available games (e.g., "1. Snake", "2. Minesweeper"). - Allow players to input their ID upon entering the platform. |
|
Provide clear instructions for navigation (e.g., "Enter 'q' to quit"). |
|
|
Game Implementation |
Implement at least two games (e.g., Snake, Minesweeper, Tic-Tac-Toe or any other games you interested in) |
|
Each game should have basic rules and be playable in the command line. |
|
|
Players should be able to return to the main menu during gameplay (e.g., by pressing a specific key like 'm'). |
|
|
Player Authentication and Game History |
Store player IDs and associate them with game records (e.g., scores, game duration). |
|
Allow players to view their past game records after completing a game. |
|
|
Modular Design |
Separate the code into modules for different components (e.g., 'main.py' for the CLI, ' game_snake.py' for the Snake game logic, ' record_manager.py' for managing player records). |
|
Write clean, well-commented code with proper indentation and structure.INT101 Python for AI |
3. The Written Report
4. Submission of Work
Late submission will receive penalty in the marking in accordance with the University Code of Practice on Assessment. For each working day after the deadline, 5 marks (out of 100) will be deducted for up to 5 working days. However, the mark will not be reduced below the pass mark for the assessment. Work assessed below the pass mark will not be penalized for late submission of up to five days. Work received more than 5 working days after the deadline will receive a mark of 0.
5. Use of Generative AI (GAI)
1) Assistance in Debugging: You are permitted to use GAI tools to help identify and resolve bugs in your code. When doing so, ensure that you actively engage with the feedback provided by the tool, understand the suggested changes, and apply them thoughtfully.
2) Code Generation: While GAI can provide code snippets or suggestions, you must not use these tools to generate entire sections of your project's code. The core logic and implementation of your assignments should reflect your own work and understanding.
3) Report Writing: Similarly, when writing reports or documentation for your projects, the content must be your original work. You may use GAI to brainstorm ideas, improve clarity, or refine language, but directly copying generated text is strictly prohibited.
6. Backup and Academic Offenses
7. Guidance to Marking
In the following table, each category builds on the requirements contained in the preceding category for assessment.
|
Category |
Requirement |
|
First Class(≥70%) |
Overall outstanding work. A well-structured and efficient implementation of all core requirements.
Games are fully functional, with smooth gameplay and minimal bugs. Code is modular, well-commented, and follows best practices. Report is clear, concise, and includes all required sections (screenshots, descriptions, instructions). Innovative enhancements (e.g., ASCII art, sound effects) are implemented. |
|
Second Upper (60 to 69%) |
A comprehensive program that effectively implements all core requirements.
Games are functional with minor bugs. Code is well-organized, with clear comments and proper structure. Report is complete and within the page limit, but could be slightly improved in clarity or creativity. Some optional enhancements are included. |
|
Second Lower (50 to 59%) |
A substantial program that implements most core requirements. Games are functional but may have noticeable bugs or incomplete features. Code is readable but lacks some modularity or comments. Report includes all required sections but may lack detail or screenshots. Minimal or no optional enhancements are implemented. |
|
Third (40 to 49%) |
A working program that implements basic functionality but lacks completeness or has significant bugs.
Games may be partially functional or lack key features. Code is functional but poorly structured or commented. Report is incomplete or lacks clarity, with limited screenshots or descriptions. |
|
Fail (0 to 39%) |
A program that fails to meet most core requirements or has critical errors.
Games are non-functional or barely operational. Code is disorganized, uncommented, or difficult to understand.
Report is incomplete, unclear, or missing key sections.
|
|
Non- submission
|
A mark of 0 will be awarded for failure to submit the project or report. |