DeliverablesDeliverables are submitted byteams, not individuals.0Team members and system overview descriptionJan14( 2)1Requirements, scope, and planFeb4( 5)2Architecture and designMar11( 9)3Implementation and test resultsApr1(12)4Final submissionApr8(13)30For deliverables 1, 2,and 3, we have provided a skeleton document, with headings and text that describesthe material that should appear under each heading. You should replace this text with material aboutyour team’s project.Deliverables•Deliverables consist of software and documents•All materials must be submitted on the due dates•Instructor and tutor will review submissions and provide feedback•You get a small mark (max. 5) for each deliverable•You may make changes, based on the feedback you receive•You get a larger mark (total 25) for materials in the final submission31The marking system allows for the revision that is inevitable in software development. You are markedfor your first attempt, but the mark is quite small (5/50 for each deliverable). We will give you feedbackon the deliverable and, as a result of the feedback and future work, you may revise the deliverablebefore the final submission.The deliverable is markedagainat the final submission, and so yourimprovements are taken into account.Final SubmissionThe final submission consists of the software and the following documents:•User Manualexplains the operation of the program from a user’s perspective•Design Documentsdescribe the design of the software•Implementation Notesdescribe key features of the code, problems encountered and theirsolutions, guidance for maintainers, . . .