Your task is to create a portfolio that demonstrates your application of our Requirements analysis, System design, and Testing (weeks 2-11) skills to your team's project. Follow the steps below to complete this assessment task.

Assessment Task

Your task is to create a portfolio that demonstrates your application of our Requirements analysis, System design, and Testing (weeks 2-11) skills to your team's project. Follow the steps below to complete this assessment task.
Demonstrate each skill by developing the relevant thing (list, table, diagram, etc.). Limit the demonstrations to one page per skill.

• For written demonstrations, such as list and tables, you must submit them as (editable) MS Word documents. Please don't submit files like PDFs, which are difficult to edit, or links to Google Docs.
• For other demonstrations, such as diagrams, you may develop them using any common software that allows you to submit a file that we can open and edit. In our course, we recommend software like MS PowerPoint, MS Excel, MS Visio, and Loopy, all of which are available on MyDesktop or for free on the Internet. Please don't submit files like PDFs, which are difficult to edit. Then, you must put an image of your demonstration in your MS Word document.
• So, you'll have a main MS Word document submission that demonstrates all skills and, possibly, a set of other digital appendix files.

Please follow structure and advice below for you Final Portfolio.

• Include a title page that includes the assessment task name (i.e., Final Portfolio), the project title, the system, and each student's name and ID.
• Include a table that indicates each member's contribution to the various sections.
• Include the up-to-one-page demonstrations of the various skills, naming the skill on each page.
• Include references in RMIT Harvard style, including in-text references and a reference list.
• Include a table of your responses to all feedback comments on your Draft Portfolio. Use the sample table in our Final Portfolio template as a guide.
• Appendices are optional. They are not assessed but may provide evidence of your work. Refer to each appendix in your Portfolio.
• Exclude executive summaries, introductions, conclusions, and any other conventional-reporting components because we won't assess them.
• Use the assessment rubric as a guide to what an outstanding Portfolio looks like. Note the criterion about the amount of extension of our skills.

Summary of Assessment Requirements

The assessment required students to develop a Final Portfolio that demonstrated their practical understanding and application of Requirements Analysis, System Design, and Testing concepts covered during weeks 2–11 of the course. Each of these skills needed to be presented through relevant artefacts such as lists, tables, and diagrams, limited to one page per skill.

The portfolio also required students to:

• Include a title page with project and student details.
• Provide a team contribution table showing individual inputs for each section.
• Demonstrate each required skill (requirements analysis, system design, testing) in a concise, visually clear format.
• Include RMIT Harvard-style referencing for all sources used.
• Address all feedback comments from the draft submission using a structured response table.
• Optionally attach appendices as supporting evidence of work completed.

The portfolio served as a professional record of the student’s technical competence and ability to integrate multiple systems development skills into a cohesive project framework.

Step-by-Step Approach Guided by the Academic Mentor

The Academic Mentor guided the student through the process in a structured and practical manner to ensure the portfolio met both technical and presentation standards. The mentoring process was divided into the following stages: