Lifecycle Management Report Task Summary This Assessment requires you as a group to write a requirements docu

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

Course:  MIS604 Requirements Engineering