Assignment Detail:- MIS604 Requirement Engineering - Torrens University Australia
Assessment - Requirements Documentation & Lifecycle Management Report
Learning Outcome 1: Critically evaluate requirements management as it applies to a variety of organisational environments-
Learning Outcome 2: Demonstrate methods for eliciting, analysing, documenting, and maintaining requirements in an organisational context-
Learning Outcome 3: Evaluate organisational requirements to maximise effectiveness and promote sustainable business practices-
Assessment Part
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 Documentationb- Requirements Lifecycle Management
Part Instructions
1- Team Formation
a- You are required to form teams of 4-5 membersb- Team formation will be decided by the Learning Facilitator in consultation with the class-
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-
You are required to send the registration email to our facilitator before the registration deadline-
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 Assessment_Case Study
2- Write 2500 words -+/-10%- requirements document and lifecycle management group report which reflects the given case study-
3- The report DOES NOT require an executive summary or abstract-
4- Structure of the Group 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 -2200-2300 words- will need to cover two specific areas:o Requirements Documentation - all items should contain unique identifier and priority -where applicable-» Project scope» Major features of the project over initial and subsequent releases» Three -03- business requirements» Five functional requirements as requirement catalogue -following the characteristics of‘good' requirement-» Five non-functional requirements -e-g-, performance, usability, security, safety, availability perspectives-- This also need to follow the characteristics of ‘good' requirement-» Map out swim lane diagrams for two -02- key processes, which will be supported by the system
o Requirements Life Cycle Management-» Discus five knowledge areas/activities for the Requirements Lifecycle management: trace, maintain, prioritise, assess, and approve and justify for the given case study-» From requirement management best practices, select three -03- most important practices for the given case study and describe them briefly- Then justify why you think they are most important-» A Requirements Traceability Matrix -RTM- 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- An example of RTM template can be like the following:
• 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-
5- Report Format and LayoutThe 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- Due attention should be given to pagination to avoid loss of meaning and continuity by unnecessarily splitting information over two pages- Diagrams and tables must carry the appropriate captioning-
6- Peer evaluationGroup 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 scorematrix -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-
Attachment:- Requirement Engineering-rar
Most Recent Questions