Your final portfolio submission should include the following: • Your requirements document (individual work) • An indication as to whether these have been fully met, partially met (which tasks are complete/not complete) or not met. It doesn’t matter if some are incomplete or not yet started No need for detail, just say not met, or if partially met, cross ref with the list of tasks (individual work). • Your list of tasks with an indication as to whether these have been fully met, partially met, not met (group or individual, it doesn’t matter which) • Your completed change request form (individual work) • Your updated risk register (individual work) • A copy of your Excel solution which should be named with your group name (if you worked as part of a group). The marks are for the managing of the requirements not for the development, but as you have worked hard at the solution, I am sure that you would like some feedback. (group work) The second is for your final report. The academic report itself is worth 40% and is where you bring it all together and I advise you to follow the following approach for maximum marks. Read the marking scheme and the tasks very carefully. These broadly mirror the IBM manual that I provided you with and that the slides are support. Put the most effort For each point, this is likely to be a couple of paragraphs. Start off with a definition relating to the literature. You can use the manual, the chapter in the Sommerville book or the Robertson and Robertson book. Cite and reference as you go. Paraphrase or summarise! Do not copy and paste or you will be referred to the plagiarism panel, even if you cite your sources. Do not copy and paste and then change a few words. Turnitin will pick this up and it is still plagiarism. The theory by itself doesn’t show understanding, but application of the theory to your project does, so follow the definition with an example of how you applied it in your own project – screen shots will help you with this. Make use of the Turnitin link to submit early and review your similarity score. Don’t just look at the percentage, also look for blocks of colour or a patchwork effect where there is lots of colour interspersed with white. These sections need to be rewritten in your own words. When do I get feedback for my interim submissions? The purpose of the interim submissions is so that I can assess the extent to which the process has been managed throughout the lifecycle rather than all of the assignment being completed the day before it is due, so providing that you have submitted for all 3 interim submission points, and there is evidence of the requirements having been managed in the meantime (there are additions to the paperwork, the risk register changes over time, etc) you will have met this criteria and I can assess it from the date stamps. We gave you all some detailed feedback for the first submission to make sure 3 you were on the correct path, but this was a one off. These are in class reviews; you will get formative feedback during the class, and this is the time to ask questions if you don’t understand something. You have your last in class review next Tuesday. Don’t waste it! Where they should incorporate the additional requirement (change request) last week? In the requirement document? Clients often request changes to their system. Changes always have knock on effects with other parts of the project, some minor, and some major e.g. it might take an extra couple of hours to build (minor), or it might meant that the system is no longer compatible with the database it feeds (major). Before implementing a change, any potential new risks should be identified as a result of the implementation. Sometimes the knock on effects may mean that the request is not accepted, which itself highlights a previously unidentified risk. If the risks of implementation outweigh the risks of not implementing, then the request may be rejected. So what you are considering is what are the risks/benefits if I implement this versus what are the risks/benefits if I don’t. This is why the change request form is completed, and then the project board will make a decision as to whether to accept the change request based on the contents of the form. The change request you have been given is a legal requirement, so it WILL be accepted. This means that you will need to write additional requirement/s and also you should update your risk register if necessary. Each change is considered by means of completing the change request form How many risk items you would like them to put in the risk register? Sufficient to show your understanding. Aim for 10, but bear in mind that you will get higher marks for 6 excellent ones than 20 rubbish ones. How do I start with Polarion? Firstly you need to sign up for an account using your UWL email account with University of West London as the company which will give you access to the demo version. You can follow the instructions/tutorial that I have provided. There are also online user guides and tutorials. The grade that you get for this task will roughly equate with the time and effort that you spend learning how to use the tool. How you would like them to use Polarion? Do you want them to link the requirements with the task in Polarion? Yes, because this is how you demonstrate traceability. What they should screenshot for the Polarion? Sufficient to show that (a) you know how to use Polarion, and (b) that you understand how it supports the requirements management process. (a) can be by screenshots e.g. first of all I created some tasks and annotate the screen shot. Then I created some test cases etc. Then I linked the test cases and requirements etc. Then I 4 created some tasks and linked the requirements etc. etc. Also include a matrix view screenshot when you are done. (b) is for the higher grades and will show that you know the purpose and usefulness of the difference views.