MIS604 Requirements Engineering (MIS604 Entire Course)

Subject Code: MIS604-REQUIREMENT-ENGINEERING

MIS604 Assessment 1 Requirements Elicitation Report

MIS604 Assessment 2 - Requirements Documentation & Lifecycle Management Report

MIS 604 Assessment 3 - Agile Requirements Analysis & Management Report

---------------------------------------------------------------------------------------------

MIS604 Entire Course/Assignment

 

MIS604_Assessment_1 - Requirements Elicitation Report

Task Summary 

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: 

1. A Stakeholder Engagement Plan detailing:

a. Stakeholder list

b. Areas of influence and Power mapped on a Power/Interest Grid

c. Definitions of the stakeholder’s power and interest. 

2. An Elicitation Activity Plan detailing: 

a. Four elicitation methods

b. An explanation of each method and why it has been selected

c. A tailored and customised example of the information gathering tool you will use for each  method

d. Which stakeholders will be engaged for the elicitation activity and why? 

Context

Business Analysts work with organisations to improve organisational processes and systems. One of the most important parts of a Business Analysts 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 Business Analyst 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 this area and to lay down the foundation of knowledge for your future professional practice.

Task Instructions 

1. Please read the attached MIS604_Assessment_Case Study.

2. Write a 1500 words (+/-10%) requirements elicitation plan for the case organisation. 

3. Review your subject notes to establish the relevant area of investigation that applies to the case. Reread any relevant readings for module 1 and 2 for this subject. Perform additional research and investigation and select five additional sources in the area of elicitation methods to add depth to your explanation of method selection.

4. Plan how you will structure your ideas for your report and write a report plan before you start writing. The report does not require an executive summary or abstract.

 5. Please structure the report as follows:

A professional custom title page with the subject code and subject name, assignment title, student’s name, student number and lecturer’s name 

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 two specific areas:

• A Stakeholder Engagement Plan including: 

i. Stakeholder list

ii. A Power/Interest Grid

iii. Definitions of each stakeholder’s power and interest 

• An Elicitation Activity Plan.

i. Four elicitation methods

ii. An explanation of each method and why it has been selected 

iii. A tailored and customised example of the information gathering tool you will use for each method 

iv. Which stakeholders will be engaged for the elicitation activity and why?

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

6. 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, due attention should be given to pagination to avoid loss of meaning and continuity by unnecessarily splitting information over two pages. Diagrams must carry the appropriate captioning. 

7. You are strongly advised to read the rubric which is an evaluation guide with criteria for grading the  assignment. This will give you a clear picture of what a successful report looks like.

Referencing 

There are requirements for referencing this report using APA referencing style and it is expected that students reference any lecture notes used and five additional sources in the relevant subject area based on readings  and further research.

Submission Instructions 

Submit Assessment 1 via the Assessment in the main navigation menu in MIS604 Requirements


 
MIS604_Assessment_2 - Requirements Documentation & Lifecycle Management Report


Task Summary

This Assessment requires you as a group to write a requirements document and lifecycle management report in response 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. This is a group report of 2500 words (+/- 10%) and should focus on the following two areas:

a) Requirements Documentation

b) Requirements Lifecycle Management

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

Context

The focus of Assessment 1 was on the elicitation of requirements. In this second assessment, you will come together as a team and progress to the next step in the requirements process: requirements analysis & documentation, and requirements lifecycle management. Here you will focus on specifying, modelling, verifying and validating requirements using Business Analysis best practice after which you will focus on Requirements Lifecycle Management. This assessment aims to assist you in developing workplace relevant business analysis skills in a predictive planning context.

Task Instructions

1. Team Formation

a. You are required to form teams of 4-5 members

b. The deadline for team registration is 11:45pm AEST Friday end of Module 1.2 (Week 2)

c. To register your team, you are required to send your Learning Facilitator an email with “[MIS604] Team Registration” in the subject line. In the body of the email, please list the names and student ID numbers of all the members of your team.

d. You are required to send the registration email to our facilitator before the registration deadline.

e. After the registration deadline, those students who are not in a team will be allocated to a team by the Learning Facilitator.

2. Please read MIS604_Assessment_Case Study.

3. Write a 2500 words (+/-10%) requirements document and lifecycle management group report.

4. Structure of the Group Report

• The report does not require an executive summary or abstract.

• A professional custom title page with the subject code and subject name, assignment title, student’s name, student number and lecturer’s name

• 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 two specific areas:

o Requirements Documentation

 Requirements scope

 Two business goals (SMART) & objectives to be achieved

 Map out a swim lane diagram of one key process which will be supported by the system

 Two business requirements

 Two actors within the system

 Five functional requirements

 Five non-functional requirements

o Requirements Life Cycle Management.

 Explain the importance of managing the requirements lifecycle and implications of not managing this lifecycle

 Discus each stage of the Requirements Lifecycle: trace, maintain, prioritise, assess and approve:

 A description of each stage

 The objectives of the process in each stage

 The main activities of the process in each stage

 Outputs of each stage

 A Requirements Traceability Matrix to manage the requirements through each stage of the requirements lifecycle populated with the requirements identified in the first part of this assessment. You may use Excel for your Requirement Traceability Matrix

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

5. 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, due attention should be given to pagination to avoid loss of meaning and continuity by unnecessarily splitting information over two pages. Diagrams must carry the appropriate captioning.

6. Peer evaluation

Group participation will constitute the final 20% of the mark for Assessment 2.

Participation will be determined as follows:

• Each student in the team will evaluate the other members’ contributions using a participation score matrix (see Group Participation Score Matrix attached)

• Individually, each team member will assign a “Group participation score” (from 1-5) for each member of the group using the score matrix.

• Each student is to assess peers’ contributions according to the Peer Evaluation Grading Scheme.

• The participation score matrix submitted by each individual student via the Assessment 2 link at the same time as the final group digital presentation submission.

The Facilitator will use the average “group participation score” for each member to determine the weighted ‘Teamwork’ criterion row in the final marking rubric for this assessment.

• All peer evaluation submissions are confidential not viewed by the other team members.

7. You are strongly advised to read the rubric which is an evaluation guide with criteria for grading the assignment. This will give them a clear picture of what a successful report looks like.

 

Referencing

There are requirements for referencing this report using APA referencing style and it is expected that students reference any lecture notes used and five additional sources in the relevant subject area based on readings and further research.

It is essential that you use appropriate APA style for citing and referencing research.

 

MIS604_Assessment_3 - Agile Requirements Analysis & Management Report


Task Summary

This final assessment requires you to respond to the case study used in Assessment 1 and 2 so that you can develop insights into the different facets of Requirements Analysis. In this assessment you are required to produce an individual report of 2000 words (+/-10%) detailing the following:

1. A Product Roadmap and a Product Backlog of coarse granularity including Epics and user stories

2. A Persona who typifies the future system end user

3. Decomposition of an Epic in user stories for first release

4. Story Mapping - ordering user stories according priority and sophistication

5. Minimum Viable Product definition for first release

6. Story elaboration of the stories for MVP to ensure that the User Story is clear

7. Well considered acceptance criteria for the stories to ensure that ‘definition of done’ is clear to all stakeholders.

8. A paragraph detailing the similarities and differences between traditional predictive requirements analysis and management and Agile requirements analysis and management.

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

Context

In the second assessment you would have developed capability in the areas of requirements analysis and requirements lifecycle management, which are well recognised Business Analysis skills and capabilities. However, Agile has become a recognised software development approach which is both adaptive and iterative in nature. This has necessitated the development of new and differentiated requirements analysis and management skills, techniques, and capabilities. This assessment aims to assist you in developing well-rounded skills as a Business Analyst who uses a spectrum tools and techniques. In doing so, you can draw irrespective of the approach your future employer may take to software development.

Task Instructions

1. Please read attached MIS604_Assessment_Case Study.

2. Write a 2000 words Agile Requirements Analysis & Management Report as a response to the case study provided.

3. Review your subject notes to establish the relevant area of investigation that applies to the case. Reread any relevant readings for Module 1 and 2 for this subject.

4. Perform additional research and investigation and select five additional sources in the area of elicitation methods to add depth to your explanation of method selection. Plan how you will structure your ideas for your report and write a report plan before you start writing.

5. Please structure the report as follows:

The report does not require an executive summary or abstract.

A professional custom title page with the subject code and subject name, assignment title, student’s name, student number and lecturer’s name

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:

• Overview of the problem you’ve been asked to research.

• 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 (1700-1800 words) will need to cover the following areas:

• A Product Roadmap and a Product Backlog of coarse granularity including Epics and user stories

• A Persona who typifies the future system end user

• Decomposition of an Epic in user stories for first release

• Story Mapping - ordering user stories according priority and sophistication

• Minimum Viable Product definition for first release

• Story elaboration of the stories for MVP to ensure that the User Story is clear

• Well considered acceptance criteria for the stories to ensure that ‘definition of done’ is clear to all stakeholders.

• A paragraph detailing the similarities and differences between traditional predictive requirements analysis and management and Agile requirements analysis and management.

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

6. 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, due attention should be given to pagination to avoid loss of meaning and continuity by unnecessarily splitting information over two pages. Diagrams must carry the appropriate captioning.

7. You are strongly advised to read the rubric which is an evaluation guide with criteria for grading the assignment. This will give you a clear picture of what a successful report looks like.

Referencing

There are requirements for referencing this report using APA referencing style and it is expected that students reference any lecture notes used and five additional sources in the relevant subject area based on readings and further research. 

Ii is essential that you use appropriate APA style for citing and referencing research