Assignment title: Information


Tasks Please read the case study below. With reference to Part 1: 1. 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. 2. Using the provided template, document your requirements. 3. Produce a risk register for this project. With reference to Part 2: 4. Review and update the requirements. Change request documentation must be used. 5. With reference to the requirements engineering lifecycle and the literature, and using examples from this case study, discuss the management of requirements. You should make specific reference to the following: a. Explanation of the term "requirements management" b. The stakeholders for this project, the techniques for eliciting requirements, and and explanation of which technique/s you would recommend or reject for these particular stakeholders c. Approaches that could be adopted to understand the problem d. Approaches that could be adopted to derive 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). 6. 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 Explanation of requirements management 5 Discussion of agile requirements management 3 Elicitation techniques 5 Ensuring requirements quality 3 Requirements qualification and acceptance 3 AA March 2016 Application to the case study LO1, LO2, LO4 Use of specialist software Understanding of the process Application to the case study LO3 Requirement management and change control 5 Requirement management and risk management 5 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 Risk register 6 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