BMCS2713 Introduction To Python Programming (Q)
BMCS2713 Introduction To Python Programming (Q)
Instructions to Candidates:
● Choose only ONE (1) Project out of the three Projects given.
● This is the final assessment. You MUST answer the assessment questions on your own
without seeking any assistance from other third party/people.
● In preparing the final assessment answers, you MUST adhere strictly to the University’s
plagiarism policy.
● You must contact your lecturer should there be any questions whilst preparing the final
assessment answers.
● It is your responsibility to ensure all pages of the answer script are submitted. You will not be
notified for any missing pages or incorrect submission of answer scripts.
● You must submit your answers to the designated location by the submission deadline stated in
the final assessment.
● For students who submit their answers late, PENALTY WILL BE IMPOSED as follows:
○ Late submission of 1 - 3 days after deadline of submission: minus 10 marks
○ Late submission of 4 - 7 days after deadline of submission: minus 20 marks
○ Late submission of > 7 days after deadline of submission: 0 mark
● For Extenuation Mitigating Circumstance (EMC) encountered, if any, the application must be
submitted to the faculty within 48 hours after the submission date of this final assessment. All
EMC applications must be supported with valid reasons and evidence. The TAR UMT EMC
Guidelines apply.
Instruction: Choose one from the three projects in this assessment. Each carries 100
marks. Submit a report based on the report template in each project.
(equation 1)
where Cash flowt, and r are cash flow in the period t and interest rate, respectively.
1.2 Instructions:
1.3 Requirements:
In this project, you will create a Python script to simulate a simple banking system. This system will
allow users to create accounts, deposit money, withdraw money, and check their account balances
using procedural programming. This mini project will help banking students gain hands-on experience
with Python programming and understand how to implement basic banking operations using
procedural programming. They will learn how to create functions, manage data, and interact with
users through a simple console-based interface.
2.2 Objectives
2.3 Prerequisites
4. Additional Tasks
o Create additional features for the application such as online bank transfer to other
account holder, registration of new account with new username and password as well
as username and password verification for access to the system.
2.5 Report Template
1. Overview
Provide a brief overview of the banking system simulation.
2. Flowchart
Provide a flowchart for the algorithm of your program.
4. User Interaction
Detail the menu-driven interface and how users can interact with the system.
5. Testing
Summarize the testing process and the results of various transactions.
6. Conclusion
Discuss any challenges faced during the implementation and any potential improvements for future
versions.
In this project, you will create a simple game using the Pygame library. The player will control a
character that moves around the screen and tries to avoid falling obstacles. The game will include
basic game mechanics like player movement, collision detection, and score tracking. This mini project
will help students learn the basics of Pygame and game development, including setting up a game
loop, handling user input, and implementing basic game mechanics.
3.2 Objectives
3.3 Prerequisites
Allow changes in speeds of falling objects and more sophisticated graphics and animations.
1. Testing
o
Run the game and test player movement, obstacle creation, collision detection, and
score tracking.
o Ensure the game ends correctly when a collision occurs.
2. Documentation
o Add comments to the code explaining each function and major block of logic.
o Document the purpose of each section in a brief report.
1. Overview
Provide a brief overview of the game created.
2.Flowchart
Provide a simple flowchart describing your algorithm.
4. Player Controls
Describe how player movement is implemented.
5. Falling Obstacles
Detail the creation and management of falling obstacles.
6. Collision Detection
Explain how collisions are detected between the player and obstacles.
7. Score Tracking
Summarize how the score is tracked and displayed.
8. Testing
Provide a summary of the testing process and results.
9. Conclusion
Discuss any challenges faced during the implementation and any potential improvements for future
versions.
For every single project, full marks of 100 marks will be awarded based on the following assessment
rubric: