Tasks Manage requirements for a project you are currently working on. This will normally be your group project. 1. Elicit requirements using appropriate techniques to produce a set of functional and non- functional requirements (e.g. look and feel, usability and humanity, performance, operational and environmental, maintainability and support, security, cultural and legal requirements). You must have at least 5 functional requirements and at least 5 non-functional requirements covering at least 4 different sub categories. You should negotiate with your tutor and group member to ensure that there is not excessive duplication in the case of a group project. 2. Using the provided template, document your requirements. 3. At appropriate stages within your project, review and update the requirements, using a risk register and change management tools and techniques as appropriate' 4. With reference to the requirements engineering lifecycle and the literature, and using examples from your own project, discuss the management of requirements. You should make specific reference to the following: a. Explanation of the term "requirements management" b. Techniques for eliciting requirements c. Approaches to understanding the problem d. Approaches to deriving a solution e. Explanation of how management of detailed requirements differ in an agile project f. Ensuring requirements quality g. Requirements qualification and acceptance h. Requirement management and change control i. Requirement management and risk management j. How a requirement management tool can assist with the capture, trace, analysis and management of changes to requirements. (Discuss, using annotated screen shots with examples from your own project). 5. You must submit the following:  Report complete with citations and references in Harvard format.  Supporting documentation e.g. screen shots, risk register/issues log, change control documentation, completed requirement templates, etc. Criteria Issues Mark Application and understanding of the theory of requirements management LO1, LO4 Application to the case study LO1, LO2, LO4 Explanation of requirements management 5 Discussion of agile requirements management 3 Elicitation techniques 5 Ensuring requirements quality 3 Requirements qualification and acceptance 3 Requirement management and change control 3 Requirement management and risk management 3 Discussion of problem 5 Discussion of solution 5 Quality of the requirements 10 Completeness of the requirements (coverage) 8 Correct use of requirements template 6 Use of specialist software Understanding of the process Application to the case study LO3 Scholarship LO4 Risk register 5 Supporting design documentation (e.g. use cases, user stories) 5 Change control documentation 5 Basic use of RM software 4 Use of RM software to capture requirements 3 Use of RM software to trace requirements 3 Use of RM software to analyse requirements 3 Use of RM software to manage requirements 3 Structure and argument of report 4 Presentation (spelling, grammar, layout, use of headings etc) Citations and references in Harvard format 6 Reference to the literature