代写C语言 IGRAPHICS GAME PROGRAMMING 和

日期：2018-04-22 10:02

IGRAPHICS GAME PROGRAMMING EXERCISE

A major high street bank has commissioned you to write a

graphical game to entertain their customers while they wait

to see a personal banker at one of their busy branches. The

premise of the game is to be based on simple physics,

involving the user launching a projectile across a graphical

space, while incorporating in the projectile’s trajectory

environmental factors, such as wind and physical obstacles

present in the projectile’s path.

As the game will ultimately be ported onto a number of different platforms (including the

bank’s mobile app) and have additional features added to it (such as advertising), as well as

creating the game and making it playable, your task is to produce a written report that will

make the hand-over of your work to a team of software engineers as effective as possible.

Specifically you should provide:

a) A program written in C implementing a playable, graphical game that has the user launch

a projectile towards a target, with its visible trajectory following the laws of physics,

including gravity, at least one physical obstacle that the player seeks to avoid, and a scoring

and/or reward system. In addition, you will need to apply at least one extended feature into

the game, such as introducing sound effects associated with game events, creating a musical

soundtrack as the game plays, adding animation or applying additional game mechanics.

You will also want to make the game relevant for the customer, a bank, by, for example,

having the projectile look like a coin and the distance or height of its trajectory

corresponding to money invested or savings earned.

b) A 10-page written report and an Appendix of the source code. The report (except for

the abstract, see below) is written for professional software engineers who have a similar

level of knowledge as you. You may add an additional title page, which along with the

Appendix will not count as one of the 10 pages. The report must contain the following main

numbered sections, with specific content in each as described below:

1-Abstract – a short, top-level summary of the contents of the report (max 300 words), and

unlike the rest of the report this should be written at a level that a general audience will be

able to understand (e.g. your bank customer).

https://www.wired.com/images_blogs/wiredscience/2010

/09/trajec-660x508.jpg

ELE00037I

2-Problem Analysis – describes the problem, including a description of the game, the

general approach to creating it, the physical laws and models applied, and any limitations or

special conditions in the design and implementation.

3-Specification – describes program design, algorithms and methods used, including

libraries, user inputs and outputs, and prescribed features as well as the extended feature(s)

you have added to the scenario. You should also include a plan for testing your code,

including user testing, and the criteria for evaluating successful completion (e.g. positive

user feedback, customer satisfaction).

4-Evaluation – review and analysis of program design, code, performance and overall

quality, any limitations, unsolved problems (e.g. bugs), conclusions on your evaluation

criteria, and suggestions for improvements or further work.

APPENDIX – contains the C source code of the program, including comments, header files,

assets (e.g. images), and any special conditions or notations. Please do not include your

name however, as the submission is anonymous.

HAND-IN

Your Individual work should be submitted compressed into a single ZIP file (maximum size

30MB) and uploaded to the module’s VLE submission point by the deadline on the cover

page. Work should be anonymised (using your exam number instead of your name when

referring to yourself).

YOUR SOFTWARE

Your code should be well-commented, and well-structured, making good use of variables,

functions, arrays, pointers and structures, according to the scenario, analysis, criteria and

specifications as set out in the report.

CONTENT OF SUBMISSION

The submitted ZIP file should contain the following items:

 The Code:Blocks project folder, including source files (.c), header files (.h), the

Code:Blocks project file (.cbp) and any resources needed to run the project on

Departmental computers.

 A single written document (.doc, .docx or .pdf).

MARKING SCHEME

You will be marked by a panel according to the following scheme:

100% Individual Assessment