hi. please assess how much does it costs?
Department of Computer Science Summative Coursework Set Front Page Module Title: Programming Module Code: CS1PR16 Lecturer responsible: Chris Maynard Type of Assignment: Coursework Individual / Group Assignment: Individual Weighting of the Assignment: 29% Page limit/Word count: 6 pages excluding: code output, title page(s) and references. Expected hours spent for this assignment: 24 hours total: 8 contact hours (lab practical’s) + 3 independent study hours a week for 5 weeks. Items to be submitted: One PDF document Work to be submitted on-line via TurnitIn by: 27/03/2020 at 12:00 Work will be marked and returned by: 21/04/2020 (15 working days) NOTES By submitting this work, you are certifying that it is all your sentences, figures, tables, equations, code snippets, artworks, and illustrations in this report are 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 University’s 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 complete an Extenuating Circumstances form and submit it to the Student Support Centre before the deadline, or as soon as is practicable afterwards, explaining why. Department of Computer Science-SMPCS Ver. 02 CS2AO17-Courswork-Labs-pg. 2 1. Assessment classifications The detailed assessment sheet is included in the lab handbook which demonstrates how the marks are distributed. The following classification should provide general guidelines for the expectations. First Class (>= 70%) Well written report, game design and new features clearly described. Extended feature(s) are relevant and non-trivial. Choice of language and programming style well justified. Implementation and development carefully documented, including deviations from the original design. Illustrative use of diagrams. Testing strategy clearly described. Carefully considered conclusions. Upper Second (60-69%) Quality of report is generally good. The feature description is generally good and the features implemented are non- trivial. Some justification of language and programming style. Implementation and development adequately described. Diagrams included. A testing strategy included. Some conclusions. Lower Second (50-59%) A reasonable report. A basic design is included with some feature description. Basic justification of language and programming style. The implementation and development are adequately described. Basic diagrams. Description of testing strategy is adequate. Basic conclusions. Third (40-49%) Only some of the sections are completed, the quality of the report is generally unsatisfactory, in total, the provided features are trivial. Pass (35-39%) The minimum understanding of the game is demonstrated, but the generally report quality is poor and implemented extensions are trivial. Fail (0-34%) The report isn’t readable, and the descriptions are confused or absent. 2. Assignment description The aim of the project is to assess your ability to analyse, design and implement an extension to an existing C/C++ program. The given program is a platform game that uses the SLD2 library for the graphics. Your task is to extend the platform game starting from the provided skeleton code. Hence, you must design at least one new feature, then adapt, modify and develop the code to realize this feature. You are free to add any features you wish. You will be assessed on the complexity of your contribution and the quality of the report to document this contribution. Hence, the reasonable extension/modification you make should be non-trivial (see marking criteria). The assessment will take the form of a report on the game you develop describing the design and implementation of the changes you make. You may develop the program under Windows or Linux on the machines in the CS labs or on your own machine. However, we must be able to inspect and compile the program and comprehend the development process, i.e., you must attach a trail of the Git history and changes to the original version to your report and give us (Christopher Maynard, Mohamad Al-Khafajiy, Julian Kunkel) read access to your Git repository. Department of Computer Science-SMPCS Ver. 02 CS2AO17-Courswork-Labs-pg. 3 You have been provided with a skeleton of the platform game which you imported into the Visual Studio IDE in the tutorial for Week 1. This skeleton uses the SLD2 library for graphics, sound, and keyboard interaction. In Week 5, during the practical, we followed the online tutorial from parallelrealities.co.uk on how the program had been constructed. The skeleton code is written in C using structs as the main data structure. You are free to develop the code in this style or to enrich it using C++ classes using an object orientation style. Either way, you must justify your choice in the report and demonstrate this was a sensible choice for the features you have employed. Additional information Support is provided during the weekly lab practical, the drop-in session, by email, or in the Slack channel. 3. Assignment submission requirements The submission shall be made via Blackboard and TurnitIn. Front page of the submission Module Code: CS1PR16 Assignment report Title: Programming Project Student Number (e.g. 25098635): Date (when the work completed): Actual hrs spent for the assignment: Assignment evaluation (3 key points): Content of the required work The content is described in the following coursework manual. 4. Marking scheme Each student’s report will be marked out of 100 according to the marking scheme. Section Details Marks Introduction Content: Project Goals. Game features. Programming style. Quality: How well report is written, how good is the description. 5 5 5 10 Design Content: Feature design Description of how the game play is to work. Illustrative diagrams (UML, flow control etc). Quality: How well the report is written, Quality of diagrams. 5 5 5 5 5 Implementation and development Content: Description of implementation. Use of novel features. Description of changes and adaptations from the original design. Justification of changes. Description of the development process. How the game and features were tested. Quality: How well the report is written, illustrative use of code fragments, pseudo-code or screen shots. 5 5 5 5 5 5 Conclusions Content: Considered conclusions, project evaluation. What did the student learn, what would they change? Quality: How well the report is written 5 5 5 Department of Computer Science-SMPCS Ver. 02 CS2AO17-Courswork-Labs-pg. 4 Git repository diff Result of the diff operation from the initial commit to the final code in the CS Gitlab repository is provided. Quality of code comments. 10 Total 100 The report contents are vital to demonstrate your understanding and to express students work authenticity. Marks may be lost if the given justification is not adequate or convincing. A report must be submitted as PDF-file and must include self-developed or modified code fragments, figures, and references to all used material. Note that you do not have to provide already existing code again but must reference the material correctly.