写作CFS2160设计程序、Python，C++

” 写作CFS2160设计程序、Python，C++THE UNIVERSITY OF HUDDERSFIELDSchool of Computing and EngineeringASSIGNMENT SPECIFICATIONModule detailsModule Code CFS2160Module Title Software Design and DevelopmentCourse Title/s MEng/BSc Software Engineering, MSci/BSc Computer Science,MComp/BSc Computing, BSc Computer Science with…, BScComputer Systems EngineeringAssessment Weighting, type and contact detailsTitle Coursework 2: Developing a Full ProgramWeighting 50%Mode of working forassessment taskIndividualNote : if the assessment task is to be completed on an individualbasis there should be no collusion or collaboration whilst working onand subsequently submitting this assignment.Module Leader Ilias Tachmazidis Contact details:Submission and feedback detailsHand-out date 18 January 2021How to submit yourwork.Via Brightspace (to be automatically checked by TurnItIn)Submission date/s andtimes04-05-2021 23:59 BSTExpected amount ofindependent time youshould allocate tocomplete thisassessment30 hours, Including time spent in practicals for the moduleSubmission type andformatA zip file (or similar) containing the software developed and anaccompanying report. Details below.Date by which yourgrade and feedback willbe returned25 May 20214Additional guidance informationYourresponsibilityIt is your responsibility to read and understand the University regulationsregarding conduct in assessment.Please pay special attention to the assessment regulations (section 4) onAcademic Misconduct.In brief: ensure that you;1. DO NOT use the work of another student – this includes students fromprevious years and other institutions, as well as current students on themodule.2. DO NOT Make your work available or leave insecure, for other students toview or use.3. Any examples provided by the module tutor should be appropriatelyreferenced, as should examples from external sources.Further guidance can be found in the SCEN Academic Skills Resource and UoHAcademic Integrity Resource module in Brightspace.If you experience difficulties with this assessment or with time management,please speak to the module tutor/s, your Personal Academic Tutor, or theSchools Guidance Team.Requesting aLateSubmissionYou are reminded to back-up your work as late submission requests will notbe given for lost work, which includes work lost due to hardware and softwarefailure/s.Late submission requests will only be approved if you can demonstrategenuine, unexpected circumstances along with independent supportingevidence (e.g. medical certificate) that may prevent you submitting anassessment on time.Submit your request for Late Submission via MyHud/MyStudies within 2working days of the due date.Late submission requests, up to a maximum of 10 working days, but typically 1-5 working days, will be considered provided that there is appropriate evidencewhich clearly indicates reasons for the request.You will have 5 working days after submitting a request to provide theevidence. Failure to Submit evidence will result in the request being rejectedand your work being marked as a late submission (see below).If you are unable to submit work within the maximum late submission period of10 days, contact the Schools Guidance Team. (sce.guidance@hud.ac.uk), asyou may need to submit a claim for Extenuating Circumstances (ECs).4Additional guidance informationExtenuatingCircumstances(ECs)An EC claim is appropriate in exceptional circumstances, when an extension isnot sufficient due to the nature of the request, or it concerns an examination orIn-Class Test (ICT).You can access the EC claim form on the Registry website; where you can alsofind out more about the process.You will need to submit independent, verifiable evidence for your claim to beconsidered.Once your EC claim has been reviewed you will get an EC outcome email fromRegistry. If you are unsure what it means or what you need to do next, pleasespeak to the Student Support Office Room SJ1/01An approved EC will extend the submission date to the next assessment period(e.g July resit period).LateSubmission(No ECsapproved)Late submission, Up to 5 working days, of the assessment submission deadline,will result in your grade being capped to a maximum of a pass mark.Submission after this period, without an approved extension, will result in a 0%grade for this assessment component.Tutor ReferralavailableNOResources Please note: you can access free Office365 software and you have 1 Tbof free storage space available on Microsofts OneDrive Guidance ondownloading Office 365.4Coursework 2: Developing a Full Program1. Assignment AimsTo develop skills in modelling using UML.To develop skills in defining classes.To develop skills in writing programs.To develop skills in testing programs.To demonstrate the need to document software.2. Learning Outcomes:This assignment addresses all learning outcomes for the module.3. Assessment BriefYou are required to design, implement, test and document a Java program (set of classes) for one (1)of the following problem specifications:Problem 1 – Supermarket Checkout SimulationA large supermarket chain would like a simulation of their checkout system for training anddevelopment purposes. You will need to define classes to represent the checkout system. Youshould try to design your system and the classes that you will need before starting coding.Your simulation must have a graphical user interface to display the state of the checkouts at alltimes.To obtain a bare pass your checkout simulation should: Include a minimum of two checkouts Include of list of products (for simplicity no more than 10 are required) that can be scanned withappropriate product code, description, and price Enable items to be scanned using the product code Keep track of the Total cost of items scanned for each customer Enable goods to be paid for in cash Print out a list of items scannedTo gain a higher mark you will need to implement some extensions to your checkout simulation.Some suggestions might be: The facility to have more than two checkouts in the system i.e. an arbitrary number of checkouts The facility to have different types of checkouts such as 10 items or less, cash only etc. Enable the system to keep track of total payments made by all customers4 The facility to pay for goods by credit card A loyalty card Stock controlProblem 2 – Who wants to be a Zillionaire?The problem is to define classes suitable for playing a game of Who Wants to be a Zillionaire. Thisgame is a cross between the successful TV quiz shows Who Wants to be a Millionaire andMastermind. Players choose a category on which to answer questions. Questions are of a multiplechoicenature with the answer being one of four possibilities. If the player answers the questioncorrectly an amount of money is credited to that player. Questions have a difficulty level accordingto the amount of money players are awarded for answering that question correctly. The questionsare asked in ascending order of difficulty and, therefore, value. Players take turns to answerquestions. If a player cannot answer a question, help is available as follows: Ask the Public. This involves a simulation of each possible answer being given a rating according tothe likelihood that it is the correct answer. Ratings for all four possible answers must add up to 100%in total. Half-and-half. Two of the possible answers are removed leaving only the right answer and one wronganswer.Players are only allowed to use each help facility once per game. If a wrong answer is given thatplayer is out of the game. The winner is the player with the most money credited at the end of thegame.To obtain a bare pass your game should have most of the following functionality: Allow two players to play the game Include a selection of questions that players could be asked Allow a player to choose the category of each question (for simplicity have three categories, one ofwhich should be general knowledge) Display a question at random from the available questions Provide a facility for the player to enter the answer to each question Inform the player whether the answer is correct, or not Keep track of the amount of money credited to each player Implement the help facilities Allow a player to winTo gain a higher mark you will need to implement some extensions to your game. Some suggestionsmight be: Allow more than two Players to play the game. Facility for easily adding extra questions. Add another help facility, e.g. Give us a Clue. Ensure that the same question is not asked twice in any one game. Include the use of sound or animation to make the game more interesting. Display the ratings for Ask the Public in graphical format e.g. a bar chart.4Getting started: You will need to identify the use cases and define classes to represent the problemyou have chosen to implement. In addition, your system must include a graphical user interfaceshowing the state of the system at all times. This interface must be written using JavaFX. Youshould try to design your user interface and the classes that you will need before starting coding.When you are ready to begin coding start with a basic program that has a very simple user interfaceand some of the simpler functionality to obtain a pass. When this is working properly improve theuser interface and try implementing some of the more complex functionality. Finally, add one ormore extensions to gain a better mark.Remember that the extensions given are just suggestions, and you do not need to implement themall (or indeed any of them, if you can think of some of your own) to gain a high mark. However,there is no limit to the extensions you can implement; the only limit is your imagination (andprogramming skills!).Formative Feedback: You are invited to submit for formative feedback a one-page use-case diagramand a one-page class diagram of the design of your software. These should be as complete aspossible and so the use-case diagram should show the actors and associated use cases, and the classdiagram should show fields, methods, visibility etc., as well as relationships between the classes.Bring your diagrams to any practical class before March 8, 2021.Final Submission: By the deadline of 04-05-2021 23:59 BST, you must submit:1. An electronic copy of your classes (including test classes). Electronic copies should be within anIntelliJ project. All code should be professionally written (including comments and indentation, useof sensible variable names, etc.).2. An electronic report that includes: The final design documentation for your system, to include as a minimum a one-page use-casediagram showing the actors and associated use cases and a one-page class diagram of the design ofyour software. Note that this should be an updated version of the diagrams you presented forformative feedback, improved to take into account any feedback received or any changes made as thesoftware has been implemented. This design documentation should be produced using the VisualParadigm UML modelling software. You should also include brief notes (maximum of 500 words) toexplain your design. A test plan showing the application tests that you have used. This could include the use of JUnitTesting where appropriate, along with full system testing. You should include a list of test cases,based upon the system requirements. Examples might be to Scan an item in the supermarketcheckout simulation program, or to Start a Game in the Who wants to be a Zillionaire? game. Youshould include all the test cases you can think of along with a pass/fail indicator to say whether yoursoftware passes that particular test (the obvious implication here being that you need to list testcases for features that do not actually work). You should also include screen shots of your software toshow how it works as you perform these tests. These screen shots should provide a walk through ofthe software.How and where to hand in: Please create a folder labelled with your student ID and name (e.g.:LastName_FirstName_u1234567). Place your IntelliJ project in this folder with your report.4Compress the folder using standard compression software and submit the compressed file(preferably a zip file) to Brightspace. There will be a link for this under Assessment.4. Marking SchemeThe reports will be marked as follows: the UML models will be assessed for completeness, correctness, and adherence to UML standards,and will contribute 30% of the marks for this assignment the testing will be marked on completeness and correctness (including tests to show what does notwork – this is essential) and will contribute 30% of the marks for this assignment. the submitted code will be examined and assessed on completeness, correctness, code quality andadherence to software development standards, and will contribute 40% of the marks for thisassignment.A marking sheet for this will be made available to students via Brightspace in advance of thesubmission date.5. Grading RubricThe following grade descriptors give an idea of the standard of work required to achieve each grade:Grade A (70%+)The code will be complete, well written, well-structured according to object-oriented principles, andreliable. It will be accompanied by high quality and accurate UML documentation and thoroughtesting. The software will perform all core requirements and a significant number of additionalrequirements and will have a high-quality user interface.Grade B (60-69%)The code will be mostly complete, well written, well-structured according to object-orientedprinciples, and mostly reliable. It will be accompanied by good quality and mostly accurate UMLdocumentation and detailed testing. The software will perform all core requirements and someadditional requirements and will have a good quality user interface.Grade C (50-59%)The code will be mostly complete, well written, well-structured according to object-orientedprinciples, and mostly reliable, but may have a few minor bugs or functional omissions. It will beaccompanied by good quality and mostly accurate UML documentation and reasonable testing. Thesoftware will perform almost all core requirements and at least one additional requirement and willhave a reasonably good user interface.4Grade D (40-49%)The code will perform the majority of the core requirements but will have few if any additionalfeatures. The structure and quality of the code will be sub-optimal but workable. The report mayhave errors and omissions but will at least attempt to provide a usable UML model and some testing.Grade E (30-39%)The code is buggy and does Not provide a usable proof of concept implementation. The report isincomplete and/or has significant errors in the models and the testing.Grade F (0-29%)Very poor attempt with no working software and a poor report with significant errors and omissions.Grade U (0%)No work submitted.如有需要，请加QQ：99515681 或WX：codehelp

“