Your small development team has been working hard to implement their Researcher Assessment Program (RAP) desktop application. During the implementation, you must have noticed the much-needed updates in the original design document and extensions required for comprehensive application testing. Your report will update the previously produced design document including structured scenarios and UML artefacts. Moreover, address the white box tests that are required for the application. Results from black and white-box testing are also included. Submission Yoursubmissionwillincludethefollowingdeliverables: Deliverables For an assignment to be assessed a complete submission with the following deliverables is a must. 1. A pdf version of the report 2. Peer assessment by each team member - check the peer assessment form for this assignment for details. The starting point For this report, you will start by revisiting your “software design” and “test plan” submissions. Improve these submissions based on the feedback provided from the evaluation and your improved understanding of the system during the development process. You will most likely see some outcomes from your assignment implementation by the end of week #10. This will be good to address this assignment in parallel. In an Agile SDLC design and code works in parallel or at least have substantial overlapping. A good design is the reflection of code and vice versa. In this assignment, we are mimicking this activity in the sequential flow of this unit. From OO model to WPF-based application In the OO model, each view is a separate class, which in WPF corresponds to defining a UserControl for each major view. Because this may complicate some of the event handling code, it is acceptable in the assignment to place separate views directly within the main window. Note, however, that the HD level of the Use of WPF assessment criterion requires that at least one user control be defined and that defining your own controls will actually make each individual source file easier to manage. The development approach ● Start from the first use case and dry run it against the code you have generated. Check the structured scenarios and their steps. Do they match your current implementation? if not either update your design or your system implementation to match the specification as closely as possible. Consequently, visit your sequence diagram to match the structured scenarios. Perform this task with every use case in your design document. ● Next step, Class diagram. Re-evaluate your class diagram, properties, methods, and relationships with the developed code. Update the class diagrams accordingly. ● Third step, Test cases. Evaluate all black box test cases and note down their outcomes (either pass or fail) in the testing report template. Since you are familiar with the code. Develop white box tests for each use case and evaluate them against your code. Note down the test outcomes in your testing report template. Remember it is not required that your code passes all the black and white box tests. Be creative and think of ways in which your code is going to fail. 2 KIT506 - Software Application Design & Implementation ● Fourth step, Report organisation. Accumulate the updated design and test plan in one report and log all the changes made in either design, test cases or source code into a traceability matrix/table. This table may have columns such as Impacted artefacts, complexity/effort required for the update, timestamp of change (DoU) implementation, description of the change (DoC), and team members involved in the update. Following is an example, you may add more columns if required. KIT506 - Software Application Design & Implementation # DoU Complexity Impacted phase Impacted artefact(s) DoC Team member low / medium / hard design / coding / testing Use case # / class name, line # / Test case title or method etc. ● The final step is Critique. Summarise the changes and project outcomes and reflect upon the design, testing and coding changes made during this assignment. Relate this work to an Agile approach and if given the opportunity how will you develop it again?