Reference no: EM133540396 , Length: word count:1500

Requirement Engineering

Assessment - Requirements Elicitation Report

Learning Outcome 1: Demonstrate methods for eliciting, analysing, documenting, and maintaining requirements in an organisational context.
Learning Outcome 2: Synthesise key principles of requirements management and communicate to stakeholders in order to solve problems.

Case Study: Recycle4Change (R4C) - Enabling a Sustainable Recycling System

Assessment Task: This Assessment requires you to respond to a case study. The same case study will be used for all three assessments so that you can develop insights into the different facets of Requirements Engineering.

For this assessment, you are required to produce an individual report of 1500 words (+/-10%) detailing a requirements elicitation plan for the case organisation. The report should contain the following:
A. Strategic Analysis
B. A Stakeholder Engagement Plan
C. An Elicitation Activity Plan

Context

Business Analysts (BA) work with organisations to improve organisational processes and systems. BA also participate to analyse, develop, execute, and evaluate organizational IT strategy. One of the most important parts of a BA job is to elicit requirements from stakeholders so that there is a clear understanding of what will be required from the new system. This requires a BA to understand who their stakeholders are, how to engage with them and which elicitation methods to use. This assessment aims to develop your knowledge and skills in these areas and to lay down the foundation of knowledge for your future professional practice.

Task Instructions

1. Please read the case study and make assumptions wherever needed.
2. Based on the given case study, you are required to write 1500 words (+/-10%) Requirements Elicitation Report.
3. Review your subject notes to establish the relevant area of investigation that applies to the case. Re- read any relevant readings for Module 1 and 2 for this subject. Perform additional research where necessary.
4. Plan how you will structure your ideas for your report and write a report plan before you start writing.
5. The report DOES NOT require an executive summary or abstract.
6. Structure of the Report
• A professional custom title page with the subject code and subject name, assignment title,
student's name, student number and lecturer's name
• Table of contents
• An introduction (100-150 words)
which will also serve as your statement of purpose for the report. This means that you will tell the reader what you are going to cover in your report. You will need to inform the reader of:
o The key concepts you will be addressing,
o What the reader can expect to find in the body of the report
• The body of the report (1200-1300 words) will need to cover three specific areas reflecting the given case study:
A. Strategic analysis
i. As part of strategic analysis, use SWOT analysis to understand the strengths, weaknesses, opportunities, threats for the organization, as well as the proposed software application.
B. Stakeholder Engagement Plan
This part will include the followings:
i. List of stakeholders, with type (e.g., internal, external). Please document using the following template:

ii. Power and interest of stakeholders mapped on a Power/Interest (P/I) grid, with justification for each stakeholder's power and interest.
C. Elicitation Activity Plan
i. Select four (04) elicitation techniques that can be used for requirement development of the proposed application, and justify why each elicitation technique has been selected.
ii. Provide a customized examples for all four (04) selected elicitation activity process (preparation, conducting the session, concluding the results), including which stakeholders will be involved.

• The conclusion (100-150 words) will summarise any findings or recommendations that the report puts forward regarding the concepts covered in the report.
• Reference list
• Appendix (if required)

7. Report Format and Layout
• The report should use font Arial or Calibri 11 point, should be line spaced at 1.5 for ease of reading and page numbers on the bottom of each page.

Referencing: Referencing this report using APA 7 referencing style.