辅导COMP2013编程、Software程序写作

” 辅导COMP2013编程、Software程序写作COMP2013-Developing Maintainable Software Coursework PreviewFor the Academic Year 2020/2021This is a preview of the forthcoming coursework. The software base will stay the same and the basicsoftware requirements will stay the same. Some of the submission details will be modified and theway the document is organized will also be modified.This coursework is about maintaining and extending a re-implementation of a classic retro game calledSokoban. The new implementation has never been completed, but at least it runs, once it is set upproperly. More information about the original Sokoban game and its history is available at Wikipedia( httpss://en.wikipedia.org/wiki/Sokoban). In addition, you will find lots of opportunities on the internetto play the original game online.To start, please download COMP2013-BestSokobanEverV6_src.zip from Moodle. Set up a project(e.g. JavaFX or Maven) in your preferred IDE (either Eclipse or IntelliJ) and embed the files that youjust downloaded. Note that the zip file you downloaded from Moodle only provides source code andresources but no project files, As it is good practice to ignore IDE-specific generated files for sourcecontrol. Add a .gitignore file to your project, ensuring that you follow this good practice as well. Setup a remote git repository at the schools GitLab server ( httpss://projects.cs.nott.ac.uk). Your remoterepository need to be named COMP2013_CW_CompSciUserName (e.g. in my case it would beCOMP2013_CW_pszps) and needs to be set to PRIVATE. Then follow the setup instructions providedin GitLab to Push an existing folder (i.e. do an initial push to upload files from your local to yourremote repository). Now you are ready for coding with version control.The marks will be split as follows: 15% for git use (e.g. push, Branch, merge, providing .gitignore) 30% for refactoring 30% for additions 15% for documentation (Readme.md + Javadocs + class diagram) 10% for a video, explaining your refactoring activities and additionsYou should roughly spend 70 HOURS on this courseworkIMPORTANT: Make sure you understand what you are writing in your code and Javadocs. We reservethe right to briefly interview you if we think that you do not understand it.What to produce: A Readme.md file (max. 500 words), documenting the work you conducted (highlighting thekey changes You made for maintenance and extension, where you made them, and why youmade them). WARNING: If you dont mention it here, dont blame us later, if we miss it! High level class diagram that shows the structure of the final version of your game (consideringonly classes (excluding fields and methods, unless they are relevant for understanding designprinciples/patterns), interfaces, relationships, and multiplicity). If you use software to reverseengineer your class diagram, make sure the delivered diagram is correct and follows the aboverequirements. The source code documentation (Javadocs) should be delivered in form of a Javadoc folderinside your project folder. Besides reading your README.md file we will look at the Javadocsto find out how you maintained and extended the game. If it is not obvious from there wemight miss it. Also we have only a limited amount of time to look at each courseworksubmitted. So, please make sure to provide informative but concise Javadocs.2 Finally, you have to make a 3 minute video (very briefly) showing your software running andthen (for the main part) explaining your refactoring activities and additions. You should alsohighlight two achievements you are most proud of.Important: This coursework is about maintaining and extending existing code. So, for the maintenancepart YOU HAVE TO USE THE CODE WE PROVIDE (COMP2013-BestSokobanEverV6_src.zip) as abasis, and not write your own Sokoban game from scratch, or use source code from othercampuses.To pass the assessment (40%): Set up a PRIVATE git repository on the schools GitLab server ( httpss://projects.cs.nott.ac.uk/)and use it actively for version control activities Do some basic maintenance of the delivered code base (this should include things like addingmeaningful Readme.md and Javadocs, organising files in a meaningful way into packages,breaking up large classes in a meaningful way to support the idea of single responsibility,improving encapsulation, etc.) Extend the delivered code base by adding:o A START screen with some Setup options to choose a wall colour (currently black) forthe game field (allowing a choice of at least 8 colours) and a button that allows goingto the GAME screen.o A HIGH SCORE pop-up, appearing at the end of each round, showing the scores fromeach round, highest at the top.For higher marks: In addition to the previous, do some of the following… Refactor the code by adding some design patterns to enhance maintainability Organise the code to adhere to the MVC pattern Create a permanent high score list (using a file to store scores) Add interesting levels to the game (either based on your own ideas or the original game) Add meaningful JUnit tests Use build files (Maven or Gradle) Come up with your own ground breaking idea … surprise us :)You have to use Java 10 or higher and JavaFX 10 or higher for the implementation. The project filesyou are submitting Need to be either compatible with Eclipse or IntelliJ.Deliverables: Three Separate files, uploaded to Moodle: A zip file containing your ENTIRE LOCAL PROJECT FOLDER (including a copy of yourREADME.md and Javadocs files). It needs to be possible to IMPORT (or OPEN) and RUN yourproject in either Eclipse or IntelliJ. To avoid disappointment later, test your final version on adifferent computer. This should help to uncover hardcoded path dependencies, which was amajor issue in previous years. Name your zip file: Surname_FirstName_IDE_JavaVersion.zip,where IDE represents the name of the IDE you used and JavaVersion the Java version youused. Here is an example: Siebers_Peer-Olaf_IntelliJ_15.zip. Your final class diagram as pdf. Please name your pdf as follows: Surname_FirstName.pdf.For me, this would be Siebers_Peer-Olaf.pdf A 3 minute video, as described above, in a commonly used video format. Please name yourvideo as follows: Surname_FirstName.EXT, where EXT represents the extension related toyour video format (either mp4 or avi). For me, this would be: Siebers_Peer-Olaf.mp4.3Note: You are gently reminded that we are at liberty to use plagiarism detection software on yoursubmission. Plagiarism will not be tolerated, and academic offences will be dealt with in accordancewith university policy and as detailed in the student handbook. This means you may informally discussthe coursework with other students but your submission must be your own work. Please also notethat it is not permitted for you to copy and paste text from another source without correct referencing.If you are unclear about this process, please discuss with the module convenors during one of our labsessions or at the end of a Teaching session.Assessment Details: This coursework is contributing 75% to your overall grade and will be marked out of 100. To give you an idea about what we are looking for when we do the marking, we have attachedour draft marking scheme as an appendix. Please note that this is only a guide for us and doesnot guarantee you marks when you have done certain things! There is always an aspect ofquality that needs to be considered as well. We also reserve the right to revise the markingscheme (within limits), if we See the need for this during the marking process.Penalties (besides late submission penalty, which follows University of Nottingham standards): Using wrong document formats (word instead of pdf) or video formats (swf instead of mp4 oravi) will lead to a penalty of -2 each Failing to comply with any naming conventions requested in this task sheet will lead to apenalty of -1 each.Questions: Dr Siebers and Dr Laramee will of course be happy to answer questions and give high levelinterim formative feedback on your assignment. If you get stuck, please get in touch!However, we might refuse to answer very detailed technical questions, or very generalquestions like What do you Think about my project so far?. Please be aware that there will also be a lot of useful tips and answered questions on theCOMP2013 Moodle page, in particular in the Announcement section.Finally, please note that we may make Some small modification to the coursework specs. We willannounce these on Moodle and keep a change log there as well.Good luck, have fun, code well :).4Appendix: Draft Marking Scheme如有需要，请加QQ：99515681 或邮箱：99515681@qq.com

“