CPT202 Software Engineering Group Project

Coursework 1 - Software Requirements Analysis

Learning Outcome

•   A. Work as part ofa development team demonstrating effective communication and interpersonal skills to design and develop a software system.

•   B. Demonstrate an understanding of the software development process including the principal methods and issues involved in deploying systems to meet business goals.

•   C. Specify the requirements ofa software system.

•   D. Understand the role of properly written documentation in the process of software development.

Objective:

To collaboratively analyze project requirements and independently develop well-defined Product Backlog Items (PBIs) using the Scrum framework.

Coursework Process:

1.     Group Discussion and Requirement Analysis:

-      Form groups to discuss and understand the project requirements thoroughly.

-      Collaboratively identify and outline the key modules ofthe project.

2.     Module Assignment:

-      Within your group, assign each module to a different group member.

–      Ensure each member clearly understands their assigned module and its requirements.

3.     Independent PBI Development:

–      Each student will independently develop PBIs for their assigned module.

–      Use the standard PBI format, including user stories and acceptance criteria, to ensure clarity and testability.

4.     Peer Review Process:

–      Upon completion of PBI development, participate in a peer review process.

–      Evaluate a peer’s PBIs, providing constructive feedback focused on clarity, precision, and alignment with Scrum principles.

5.     Final Report Submission:

–      Compile a final report that includes the following sections:

Final Report Components:

1.     Understanding of the Scrum framework

–      Provide a clear and concise explanation of the Scrum framework, emphasizing the role of PBIs in the process.

–      Strictly limit this section to 100 words.

2.     Pre-Groomed PBI

–      Develop five pre-groomed PBIs relevant to the module assigned to you, each with a user story and acceptance criteria.

–      Ensure each PBI is well-defined and adheres to the PBI format.

3.     Collaboration and Reflection

–      Peer Review and Feedback:

•      Document your participation in the peer review process.

•      Provide constructive feedback to peers, focusing on clarity, precision, and alignment with Scrum principles.

•      Feedback should be actionable, helping peers improve their work.

•      Evaluation criteria include constructiveness, depth of analysis, and clarity of communication.

•      Strictly limit this section to 250 words.

–      Reflection on Learning:

•      Detailed reflection on what you learned from the coursework and the peer review process.

•      Discuss insights gained, personal growth, and how feedback was incorporated.

•       Strictly limit this section to 100 words.

Submission Guidelines:

•      Submit your final report as a single PDF document via Learning Mall by the above

submission date, including all sections outlined in the Final Report Components above.

•      Ensure your PBIs are clearly formatted and easy to read.

•      DO NOT submit more than 5 PBIs. Marks will only be given to the first 5 PBIs in your report.

•      Include your peer review feedback and personal reflection as separate sections in the document.

•      Name the report as CPT202-A1-StudentID.pdf

Marking Scheme

1.     Understanding of Scrum and PBI Format (10 Marks)

–      Explanation of Scrum Framework (5 Marks):

•      Clear and concise explanation of the Scrum framework, focusing on the role of PBIs in the development process.

–      Correct Use of PBI Format (5 Marks):

•      Adherence to the standard PBI format, including user stories and acceptance criteria.

2.     Quality of PBIs (20 Marks)

–      Clarity and Precision (10 Marks):

•      PBIs are clearly written and easily understandable by all stakeholders.

–      Logical and Relevance (10 Marks):

•      PBIs are logically relevant to the assigned module.

3.     Pre-Groomed PBI (30 Marks)

–      PBI 1 (6 Marks):

•      Well-defined user story and acceptance criteria.

–      PBI 2 (6 Marks):

•      Well-defined user story and acceptance criteria.

–      PBI 3 (6 Marks):

•      Well-defined user story and acceptance criteria.

–      PBI 4 (6 Marks):

•      Well-defined user story and acceptance criteria.

–      PBI 5 (6 Marks):

•      Well-defined user story and acceptance criteria.

4.     Collaboration and Reflection (40 Marks)

–      Peer Review and Feedback (25 Marks):

•      Students are required to participate in a peer review process, providing constructive feedback on another student’s PBIs.

•      Marks are awarded based on the quality, thoughtfulness, and specificity of the feedback provided.

•      Criteria for Evaluation:

–      Constructiveness (10 Marks): Feedback should be constructive, offering actionable suggestions for improvement.

–      Depth of Analysis (10 Marks): Feedback should demonstrate a deep understanding of the PBIs and Scrum principles.

–      Clarity and Communication (5 Marks): Feedback should be clearly communicated and well-structured.

–      Reflection on Learning (15 Marks):

•      Students must submit a detailed reflection (Approximately 100 words) on what they learned from the assignment and the peer review process.

•      Marks are awarded based on the depth of insight, personal learning, and application of Scrum principles articulated in the reflection.

•      Criteria for Evaluation:

–      Insightfulness (5 Marks): Reflection should provide deep insights into the learning process and understanding of Scrum.

–      Personal Growth (5 Marks): Reflection should highlight personal growth and how feedback was incorporated.

–      Feedback and Application (5 Marks): Reflection should demonstrate how feedback from peer review were applied or understood through the coursework.