MIS604 Requirement Engineering Report 1 Sample

Still, Looking for a MIS604 Requirement Engineering Report 1 Sample? Don't worry, You’ve reached the Right Place!

Order Now

MIS604 Requirement Engineering Report 1 Sample

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

Please refer to the Instructions for details on how to complete this task.

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:

• The key concepts you will be addressing,

• 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.

• If diagrams or tables are used, please follow APA 7 guideline for the same. Diagrams and tables must carry the appropriate captioning (numbering, name, and source) at all instances.

• Due attention should be given to pagination to avoid loss of meaning and continuity by unnecessarily splitting information over two pages. 

Solution

Introduction:

The main purpose of creating the report is to develop a plan of requirement elicitation for Recycle4Change. The report will focus on three main points such as strategic analysis, stakeholder engagement plan, and elicitation activity plan. Recycle4Change is initiating a project in which customers can use their software according to their requirements so they are developing software whose name is Recycle4Change. For analysis, the strategic analysis of the software used method is SWOT analysis for the company. After this plan will be created by using a list of stakeholders with their type and also develop a grid of power and interest. In the last select four techniques of elicitation for developing the requirements. This task will help in understanding the method of eliciting, analyzing, and documenting requirements for the Recycle4Change and key principals of requirement management to solve the problems.
Requirements Elicitation

A. Strategic analysis:

SWOT analysis is used for Both the organization and Software Application (Satzinger, Jackson, & Burd, 2015).

SWOT analysis for an organization:

Strengths: Recycle4Change takes the contracts from companies for collecting containers, provides employment to diverse backgrounds people, provides part-time jobs, cleans waterways, and contributes to the circular economy.

Weakness: Recycle4Change should improve its software quality by adding some effective features for all the users.

Opportunities: They are hiring employees for cleaning in the region of North Geelong and Hoppers Crossing. Commit to the mission of social enterprise

Threats: when they hire some employees, they can easily get in contact with fraud people. Some companies also provide these types of services so need to update the system and process of working (Benzaghta, et al., 2021, pp. 58).

SWOT analysis for Application:

Strength:

1. R4C provides a user-friendly interface.

2. Customers can manage and create their profile according to their requirement

3. Provide the facility to add the number of bins and paid subscriptions.

4. Different management systems are available such as Customer Registration, Bin, Truck Flee, Management, Bin Collection and Distribution, Billing and Payment, and so on.

Weaknesses:

Customers can donate to the charity of R4C in any specific amount but this service is not useable by the below poverty line people. They are not able to take the paid subscription. Due to the lack of a marketing budget visibility of the application is low (Benzaghta, et al., 2021, pp. 60).

Opportunities

To improve the quality of the software need to work on digital marketing services such as ads on YouTube, Facebook, and Instagram (Blash,2019).

Threats:

With a new software competitor set to launch within the same region in the next 4 years, they should be focused on the decline of the customers.

B. Stakeholder Engagement Plan:

i. Stakeholder list:

ii. Power interest of stakeholder:

Figure 1: Power Interest Grid

Justification:

Elicitation Activity Plan:

This is the plan that defines all the required techniques for collecting the data related to the proposed application here the following points suggest 4 main techniques that can be used by the Recycle4Change.

1. Survey: in a project or application there are required to be involved stakeholders then this method is the method for collecting the data. In this method business analyst surveys with some required questions and then sends it to the stakeholders to collect their views on that question. In the project of Recycle4Change, there is a need to collect data from all over the city so it is the best technique according to the case scenario.

2. Prototyping: this is a unique method of collecting feedback from the stakeholders and then making changes to the proposed solutions. Once the developer develops a prototype of the system and then shows this to the client who is developing the project they will provide their feedback to the developer and then they make changes. The main reason behind selecting this technique in the elicitation requirement is because it boosts the participation of stakeholders. It describes the realistic models of complete application Dwivendi, 2019).

3. Interview: for extracting critical data, there is one popular technique and the name is Interview. Two types of interviews can be conducted by the BA such as one-to-one or group. For the project group interview is the best method. By using diverse opinions, business analysts gain knowledge of the requirements.

4. Brainstorming: this technique is focused on the session of brainstorming that should be set up by the team with their representative. The main focus of this technique is defining the problem, setting the rules, facilitating selection, selecting the stakeholders, and then warming up the activities with their ideas.

Customized Example:

1. Survey: The business analyst does plan for a survey at the North Geelong and Hoppers Crossing regions, so they can identify the requirements of the customers and what type of application they want them. They want to make a customized application for all types of customers. The government of Victoria has started schemes for their people to clean the regions so they can also participate in the survey, For example, Questions for the survey used such as what type of bins they want, how many services are required for collecting the bins of wastage (Wick, 2021).

2. Interview: this is also the same as the survey but in this business analyst ready an interview with the person in which he or she asks some questions to the participants such as what is the requirement from the application that we can add in the new features. They also want that there should be a truck for collecting the beans and they introduced it by using ads. Drivers can be hired from the application.

3. Prototyping: the company wants to make an application in which they want to add features like bin collection and distribution management, billing payment, map integration, and communication and notification, all these are developed in a type of application and then send this to the people of the Victoria, they will provide feedback to the developers and then the developer will update according to the people requirements.

4. Brainstorming: this session is done for awareness and to promote the application of the Recycle4Change. First, need to set the rule that there should be no criticism at the time of this phase. The manager of the phase is TOMRA Cleanaway Victoria and volunteers. Marketing team, graphic designers, and department of sustainability. Assign all the responsibilities to the clients and their personal care people.

Conclusion:

Recycle4Change is an application that is established for using containers for recycling systems. They already completed some projects now the government has a contract to collect the sort containers in the north Geelong and Hoppers crossing region. They are developing a user user-friendly system and this report consists the two types of plans after analyzing the strategy of the projects. The strategic analysis is performed by using the SWOT analysis of the company and application. After analyzing the weaknesses and opportunities perform a stakeholder engagement plan and elicitation activity plan. Four main stakeholders identified such as TOMRA Cleanaway Victoria, Developers, the Victorian Government, Recycle4Change, and customers. After they categorized them according to their power and interest by using the P/I grid. In the elicitation activity plan select 4 techniques which is suitable for the project Survey, interview, prototyping, and brainstorming. The last report provides a customized example of 4 activities for all the selected stakeholders. This report will give the idea of developing a BA report related to the application.

References:

Benzaghta, M. A., Elwalda, A., Mousa, M. M., Erkan, I., & Rahman, M. (2021). SWOT analysis applications: An integrative literature review. Journal of Global Business Insights, 6(1), pp.55-73. https://digitalcommons.usf.edu/cgi/viewcontent.cgi?article=1148&context=globe

Blash, G. (2019, May 29). What is the role of the business analyst? [Video file]. https://linkedin.com/learning/business-analysis-foundations-4/what-is-the-role-of-a-business-analyst-15244956

Dwivendi, N. (2019, September 18). Elicitation techniques [Video file]. https://www.linkedin.com/learning/software-design-developing-effective-requirements

Satzinger, J. W., Jackson, R. B., & Burd, S. D. (2015). Systems analysis and design in a changing world (7th ed.). Cengage Learning. https://ebookcentral.proquest.com/lib/think/reader.action? docID=6351182&ppg=326 https://ebookcentral.proquest.com/lib/think/reader.action? docID=6351182&ppg=326.

Wick, A. (Updated: 2021, March 08). Elicitation overview [Video file]. https://www.linkedin.com/learning/requirements-elicitation-and-analysis/elicitation-overview-8360495

Fill the form to continue reading
Would you like to schedule a callback?
Send us a message and we will get back to you

Main Services

Highlights

Earn While You Learn With Us
Confidentiality Agreement
Money Back Guarantee
Live Expert Sessions
550+ Ph.D Experts
21 Step Quality Check
100% Quality
24*7 Live Help
On Time Delivery
Plagiarism-Free

Our Samples

Get Instant Help
University Assignment Help

Still Finding University Assignment Help? You’ve Come To The Right Place!


CAPTCHA
AU ADDRESS
81 Isla Avenue Glenroy, Mel, VIC, 3046 AU
CONTACT
+61 493416265
EMAIL
support@uniassignmenthelp.net