Assessment 2 Brief MIS604 Requirement Engineering
Do you need help with Assessment 2 MIS604 Requirement Engineering Torrens University Australia?
|ASSESSMENT 2 BRIEF|
|Subject Code and Title||MIS604 Requirement Engineering|
|Assessment||Requirements Documentation & Lifecycle Management Report|
|Length||2500 words (+/- 10%)|
|Learning Outcomes||The Subject Learning Outcomes demonstrated by successful completion of the task below include: Critically evaluate requirements management as it applies to a variety of organisational environments. Demonstrate methods for eliciting, analysing, documenting, and maintaining requirements in an organisational context. Evaluate organisational requirements to maximise effectiveness and promote sustainable business practices.|
|Submission||By 11:55pm AEST/AEDT Sunday end of Week 8/Module 4.2 For Intensive class: By 11:55pm AEST/AEDT Sunday end of Week 4/Module 4.2|
|Total Marks||100 marks|
- Team Formation
- You are required to form teams of 4-5 members
- Team formation will be decided by the Learning Facilitator in consultation with the class.
- The deadline for team registration is 11:55pm AEST/AEDT Sunday end of Module 2.1 (Week 3). For
intensive class, the deadline is 11:55pm AEST/AEDT Sunday end of Module 2/Week 2
- 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 MIS604_Assessment_Case Study
- Write 2500 words (+/-10%) requirements document and lifecycle management group report which reflects the given case study.
- The report DOES NOT require an executive summary or abstract.
- 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:
- 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 (2200-2300 words) will need to cover two specific areas:
- 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
- Requirements Documentation – all items should contain unique identifier and priority (where applicable)
- 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
- 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:
|Business objectives||Business requirements||Functional requirements||Non- functi onal requi reme nts||Design element||Source file||Functions||Test cases||Status|
|The conclusion (100-150 words) will summarise any findings or recommendations that the report puts forward regarding the concepts covered in the report.Reference listAppendix (if required) 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. 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. 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. Assessment rubric 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.|
To apply for special consideration for a modification to an assessment or exam due to unexpected or extenuating circumstances, please consult the Assessment Policy for Higher Education Coursework and ELICOS and, if applicable to your circumstance, submit a completed Application for Assessment Special Consideration Form to your Learning Facilitator.
|Assessment Attributes||Fail (Yet to achieve minimum standard) 0-49%||Pass (Functional) 50-64%||Credit (Proficient) 65-74%||Distinction (Advanced) 75-84%||High Distinction (Exceptional) 85-100%|
|Visual appeal and presentation of content Title page Font, spacing and format are in accordance assignment requirements. Appropriate use of paragraphs, sentence construction, spelling, and grammar. Adheres to the word count requirement Percentage for this criterion = 15%||No title page is included. Incorrect font and size is used with poor line spacing. Report is written as a block of text with no breaks in between ideas. Separate ideas cannot be clearly discerned. Many errors in spelling or grammar obscure meaning of what student has written. Does not adhere to the word count requirement.||Title page is included but is missing most information. Either incorrect font and size is used or poor line spacing. Paragraphs are used but large blocks of text with long sentences make it difficult to understand the ideas being conveyed. Spelling or grammar has errors but meaning remains clear. Does not adheres to the word count requirement.||Title page is included but is missing key information. Some errors in font use and line spacing. One idea or concept per paragraph. Some paragraphs could be more succinctly written. Minor spelling or grammar errors. Adheres to the word count requirement.||Title page is included with most required information. Minor errors in font, spacing and format. One idea or concept per paragraph with 3-4 well constructed sentences per paragraph. No errors in spelling or grammar. Adheres to the word count requirement.||Title page is included with all required information. Font, spacing and format are in accordance the assignment brief. Expert use of paragraphs with 3-4 well constructed sentences per paragraph which follow logically from each other. No errors in spelling or grammar. Adheres to the word count requirement.|
|Knowledge and understanding Requirements Documentation: scope, goals & objectives, actors, functional and||Lack of understanding of the required concepts and knowledge. Key components of the assignment are not addressed.||Limited understanding of required concepts and knowledge. Some of the key components of the assignment are not addressed.||Adequate knowledge or understanding of the required concepts. A reasonable capacity to explain and apply relevant key concepts.||Thorough understanding of the key concepts. Discriminates between assertion of opinion and information substantiated by robust evidence from the research/course||Highly developed understanding of the field or discipline/s. Systematically and critically discriminates between assertion of opinion and information substantiated|
|non-functional requirements. Swimlane diagram Requirements Management: importance, stages including description, objectives, and activities Requirements Traceability Matrix Percentage for this criterion = 50%||Lack of application, and analysis of information to provide clear recommendations.||Limited application and analysis to provide clear recommendations.||Supports opinion and information substantiated by evidence from research to provide recommendations.||materials and extended reading. Well demonstrated capacity to apply and analyse relevant information to provide clear recommendations.||by robust evidence from the research/course materials and extended reading. Recommendations are clearly justified based on the application and analysis of information.|
|Use of academic and discipline conventions Formal tone Introduction, body and conclusion. No use of first party perspective Appropriate use of credible resources, Correct citation of key resources using APA 7 style of referencing, in- text as well as for models, diagrams, tables or tools. Percentage for this criterion = 15%||Poorly written with informal tone, using first person pronouns. Does not adhere to the assignment brief of the requirements for a short business report. No introduction attempted. Conclusion not attempted. Inconsistent and inadequate use of good quality, credible and relevant resources to support and develop ideas. No use of in-text references, or no reference list at the close of the report. Many mistakes in using the APA 7 style.||Written according to academic genre. Minor errors in the use of first-person pronouns. Introduction attempted but very generic does not clearly state the purpose of the report. Conclusion attempted but does not include summation of key concepts discussed in the report and/or key conclusions or recommendations. Consistent use of credible and relevant research sources to support and develop ideas, but these are not always explicit or well developed. Little use of in- text referencing, or||Written according to academic genre. Consistent use of credible and relevant research sources to support and develop ideas. Sound use of the introduction but does not clearly state either the purpose of the report or what the reader should expect to find in the body of the report. Sound use of the conclusion and succeeds in either the summation of key concepts discussed, or key conclusions or recommendations, but not both.||Well-written and adheres to the academic genre. Expert use of good quality, credible and relevant research sources to support and develop appropriate arguments and statements. Shows evidence of reading beyond the key reading. Good use of the introduction which clearly states the purpose of the report and what the reader should expect to find in the body of the report. Good use of the conclusion and succeeds in summation of key concepts discussed and key conclusions or recommendations.||Expertly written. Adheres to the academic genre. Expert use of high-quality credible and relevant research sources to support and develop arguments. Extensive evidence of reading beyond the key reading. Excellent use of the introduction. Secures the attention of the reader, clearly states the purpose and what the reader should expect to find in the body of the report. Excellent use of the conclusion. Succeeds in confident summation of key concepts and conclusions. Gives the reader a clear sense of next|
|inadequate references consulted and added to references at the close of the report. Some mistakes in using APA 7 style.||Good use of in-text referencing and appropriate number of references used and listed in the reference list. There are only minor errors in using the APA 7 style.||Very good use of in-text referencing. No mistakes in using the APA 7 style.||steps required. Excellent and meticulous use of in- text referencing with references listed in the reference list. No mistakes in using the APA 7 style.|
|Team Work Participates in Team Work Contributes to team achieving their goals Percentage for this criterion = 20%||Does not participate effectively in a team environment. Places individual goals ahead of the group responsibility. Hinders the group process and upsets the schedule.||Participates effectively in teams. Identifies team and individual goals, tasks, responsibilities and schedules. Contributes to group processes. Supports the team.||Contributes to small group discussions to reach agreement on issues. Works together with others towards shared goals. Renegotiates responsibilities to meet needed change.||Understands group dynamics and team roles. Facilitates team development. Renegotiates responsibilities, tasks and schedules to meet needed change.||Builds team’s identity and commitment. Leads teams. Evaluates teams’ outcomes. Implements strategies for enhancing team effectiveness.|
|The following Subject Learning Outcomes are addressed in this assessment|
|SLO a)||Critically evaluate requirements management as it applies to a variety of organisational environments.|
|SLO b)||Demonstrate methods for eliciting, analysing, documenting, and maintaining requirements in an organisational context.|
|SLO c)||Synthesise key principles of requirements management and communicate to stakeholders in order to solve problems.|