G6046课程程序写作、Software程序辅导写作Java程序

” G6046课程程序写作、Software程序辅导、写作Java程序Software Engineering G6046 resit coursework specificationDue date Monday 24 August 2020 by 4PMSubmission format Electronic submission only via Canvas. Please ZIP all your files togetherinto a single ZIP archive and upload that ZIP onto Canvas. Ensure thatyour ZIP file unpacks correctly before submission and that it containsall the work for your submission. For text documents please use Wordor PDF file formats only.You MUST include your codebase in your submission. Do not includelinks to GitHub or other code repositories.1) IntroductionThis resit coursework is an individual project. You have been provided with some basic starter code,written in Java, loosely based on the World of Zuul adventure. This is a simple game that allowsyou to navigate a series of rooms in a game world. The starter code provides the basic ability to builda game World and navigate it using simple text commands like go north. To start the basic game,instantiate an object of the Game class and invoke the play() method. Your task is to build uponthis basic game and increase its functionality to make the game more complex and interesting toplay, and to use good Software Engineering principles to create a well-designed, documented andproperly tested Program that can be easily understood, adapted and worked upon by otherdevelopers.You will need to: Develop an appropriate software design, expressed using an appropriate combination ofhigh and low level design techniques including class diagrams, use case diagrams andsequence diagrams.G6046课程作业写作、Software作业辅导、写作Java Write the software. You have been given some starter code written in Java. You areexpected to develop the software further in Java. You can implement your work in anotherlanguage, but you must obtain the agreement of the course convenor before doing so, andyou should be prepared to explain why you wish to opt for an alternative language. Ingeneral, it is likely That it will be harder to complete this resit coursework if you do not workin Java. The software will ideally require some kind of Graphical User Interface, but this isnot a core requirement, and your focus should be on demonstrating your understanding ofthe broader Software Engineering principles, and on meeting the deliverables as set out inthis document. Develop a test plan for the software, both at a unit testing level and at a system level, todemonstrate that your software meets all the user requirements set for it. Write a short report to document the work that you have done. Give a demonstration of your completed software system.Assessment criteria for this resit coursework project can be found at the end of this document. Theassessment criteria will focus on: The quality of Your Software engineering skills. Your ability to deliver a project that meets the stated system requirements. Your ability to deliver a working and reliable software system.2) World of ZuulThe starter code That you have been given is a modified (simpler) version of the base code forpopular World of Zuul game first conceived by David Barnes and Michael Kolling. The starter codecan be downloaded from Canvas. You can also find out more about World of Zuul online, and in theclassic Barnes and Kolling books Objects first with Java ( httpss://www.bluej.org/objects-first/).3) System requirementsYour task is to enhance the starter code to make the game fuller and more interesting. The systemrequirements for this enhanced game are as follows:Functional requirements (Shall: mandatory, should: desirable)F1 The game shall consist of new fewer than 12 separate room spaces, linked togetherby exits that allow the user to navigate between rooms using either text basedcommands or a simple direction button driven graphic user interface.F2 Each room space shall fall into one of the following categories: a room with one ormore objects in it, a Room with an enemy character that must be defeated, acorridor, or an endpoint That the player must reach to win the game.F3 No fewer than 3 rooms shall be equipped with locks such that the player may onlyenter them after picking up a key game item.F4 The player shall be able to issue commands that permit travel in the direction north,south, east and west. The ability to travel in each direction shall be determined bythe connectivity of the room spaces.F4 No fewer than 6 rooms shall contain in game items. In game items shall include keys(required to unlock room spaces), swords (to fight an enemy character), a spell (forexample to make an opaque object visible) Or a health pack (to restore health afterfighting an enemy).F5 The player shall start with 100 health points. Each time the player makes a movethe health points shall be reduced by 1. Fighting an enemy shall cause loss of healthpoints, depending on the nature and strength of the enemy character.F6 The game shall End (as a loss) is the players health points falls to 0.F7 The player shall be able to issue commands that permit them to pickup gameobjects and carry them in a personal inventory (backpack). An item may only beused when it is in the backpack. Once a game object has been used, it must beremoved from the backpack inventory.F8 When objects are put down in a room, they must persist in that room space, suchthat they remain where they were last placed by the player.F9 The player shall be able to issue commands to examine game objects beforechoosing to pick them up.F10 The player shall be able to issue commands to review the contents of the backpackinventory.F11 The player shall be able to issue commands to use game objects such as spells andweapons. The nature of these spells and weapons and their role in the overall gameplay is left as choices for the developer.F12 The game shall be completed when all rooms have been explored and all enemycharacters have been defeated.F13 A back command should be available such that the player moves back to the lastroom space occupied.F14 A map option should be developed such that the layout of the room space isrevealed to the user graphically as the room spaces are explored.Non-functional requirements (Shall: mandatory, should: desirable)NF1 The software shall be written in Java (note comments in section 1)NF2 The Software should be playable either by text command entry or by simple buttondriven graphical user interface.NF3 The software should have a simple button driven graphical user interface. Eachcommand should have its own button that becomes active when the correspondingactivity is permissible. For example, a pickup button should only become activewhen there is an object in the current room that can be picked up.NF4 Any graphical user interface shall present a simple single frame graphicalrepresentation of the current room.NF5 The game should offer multi player user experience such that each player takes it inturns to move and has their own backpack.You should refer back to these requirements when you are developing an appropriate set of systemlevel tests. Remember, the job of testing is to demonstrate that software if fit for purpose. Thiscan be defined as when the software meets all of the system requirements set out for it.4) Other requirementsYou may further extend the game in any way you consider appropriate, but your main objectiveshould be delivering a piece of software that meets the system requirements set out in the previoussection. You may obtain feedback on the work and requirements at any time by emailing the courseconvenor.5) DeliverablesSubmission will be via the Esubmissions system on Canvas. You will need to produce: A project log: This should document the work that you did. The log should record what youdid and achieved for each substantive working day that you spent om the project. The logentries do not need to be detailed, but they should record important decisions made, andkey achievements. An example log might read as follows:26 June: decided that a new class BackPack was required. Identified key attributesand methods for this class. Updated the class diagram to v2. Started to implementthe new BackPack class needs another day of coding. Decided to implement 6unit tests for this class.The purpose of this project log is to demonstrate that you made a proper sustained effortthrough the duration of this resit coursework. A design document: documenting both high level and low level designs of your softwaresystems. Such a document MUST include a full class diagram and UML use case diagram,with descriptions of any new classes that you have created as part of your solution, andshould include sequence diagrams to show how your classes and their methods worktogether to Deliver key use cases. The code base: including all non-code files or other data necessary to allow your submissionto be compiled and executed by the assessors. The code should be properly documented(e.g. using Javadocs), and be commented to an appropriate standard. A testing document: showing how you tested the software at both unit test and system testlevels. It is acceptable for bugs and other issues to remain in the software as long as they areclearly identified, documented and that you have provided appropriate commentary toexplain why they exist and what you would do about them. Your unit tests shoulddemonstrate that all classes operate in their intended manner, and the system tests shoulddemonstrate that the software meets the functional and non-functional requirements setfor it. A short report: documenting how the project went for you, with a critical analysis of yourperformance, and any issues that remain unresolved in your work.When you upload your deliverables, please use Word or PDF formats for text documents. Do not useMac Pages files as these are not widely supported. For code deliverables, please remember toinclude any project (e.g. Eclipse, BlueJ), initialisation or other external files your code needs to berun.. Do not upload files that are in obscure formats. Assemble all of your documents together andcreate a single ZIP file with everything inside. Upload the zip file onto the Esubmissions system.Check that your ZIP file unpacks correctly before uploading it.You will be also be required to give a short demonstration of your project at the end of thesubmission Period. This will be an informal demonstration to the module convenor.6) Assessment criteriaYour submission will be assessed against the following criteria:Marks Description Evidenced by5 Project log Notes of progress as a word processeddocument.5 High level design documents UML use case diagram(s)15 Low level design documents Class diagram, sequence diagrams to validateclasses for all use cases40 Codebase Full code10 Code documentation Javadocs annotations, descriptions of all classes,in line commenting20 Testing documentation Evidence of unit testing, evidence of system leveltesting validated against requirements5 Short report Word processed document (1-2 sides maximum)7) Final observationsIf you do not Understand something, contact the module convenor.Remember that this is not just a coding assignment. This is a Software Engineering assignment, sojust creating a program, even if it works, is not sufficient to pass. You need to demonstrate that youhave applied Software Engineering principles to design, document and test a piece of software,And keep regular backups of your work . I lost the USB stick just doesnt cut any ice.Dr Kingsley SageModule convenor, G6046 Software EngineeringSchool of Informatics and EngineeringKhs20@sussex.ac.ukJuly 2020END.如有需要，请加QQ：99515681 或邮箱：99515681@qq.com

“