The Student Competency Assessment Solution (SCAS) is specifically developed to enhance the assessment of complex student skills in diverse educational settings. Leveraging the capabilities of the existing Ruby platform, this solution is designed to enable educators to more effectively evaluate student abilities, resulting in both individual and aggregated class-wide competency reports. This initiative is primarily aimed at teachers and administrators, offering in-depth insights into the learning progression of students as the educational landscape progresses towards high-stakes certification processes.
Our primary goal is to cater to the needs of educators, academic institutions, and students by promoting the accuracy and reliability of educational assessments and credentials. By addressing key challenges such as the need for assessment consistency, the reduction of teacher workload, and the enhancement of the efficiency and accuracy of evaluations, SCAS seeks to empower stakeholders within the educational ecosystem.
Target Audience: Our solutions are designed with educators, academic institutions, and students in mind, focusing on the pivotal need to support educational excellence through reliable and insightful assessment methodologies.
Team members: Jianqiao Song, Hanying Li, Mingchong Li, Heng CHEN, Yutian Fan, Danning Feng, Weihuang Wu, Haocheng Wang, Hao Guan, Aoxiang Xiao
Industry partner: Narelle English(on leave), Jason Pietzner, Richard Xu
Supervisor: Afsana Imam
- For sprint4&5, we uploaded all meetings within sprint 4&5 to the meetings subfolder.
- For sprint4&5, we attached our trello board link here: trello.
- For sprint4&5, we uploaded Acceptance criterias and Acceptance Tests to the test folder.
- For sprint4&5, we uploaded sprint 4&5 reviews and sprint 4&5 retrospectives to the agile ceremonies folder.
- For sprint4&5, we uploaded Data sample to the Data samples folder.
- Based on sprint3 feedback, we have updated the Mentor feedbacks with the advice from the mentor meeting.
- For sprint4&5, we uploaded user story map to the user story folder.
- For sprint4&5, before generated the high fidelity prototypes, we discussed about it together and generated the mood board.
- For sprint4&5, we created high fidelity prototypes to the high fidelity folder. Also, a quick look of high fidelity prototypes is provided. In addition, all of the elements and UIs we used were from the original Ruby platform, so there is no new UI created.
- For sprint4&5, we present the project our work of this semeter, and the presentation file was uploaded.
- For sprint4&5, the handover document was generated for the client and the semester 2 develop team.
- For sprint4&5 and handover, we uploaded the usability test video on Youtube.
- For sprint4&5 and handover, we sent the handover file together with release notes to client, and recorded it.
- For sprint4&5, we have update the Repository Structure in README file.
- Based on sprint2 feedback, we created a new folder named agile ceremonies in the docs directory and uploaded the reviews and retrospectives for sprint1 and sprint2 that were not previously uploaded.
- Based on sprint2 feedback, we have made corresponding modifications to the Repository Structure section of the README according to the format changes in the GitHub repository.
- Based on client's feedback, we have uploaded two files to the user story subfolder, one is User Stories confirmed with Client(user stories that are updated after being confirmed by the customer), and another one is User Story Feedback and confirmation From Client(client's feedback and confirmation of user stories).
- For sprint3, we have uploaded all meetings within sprint 3 to the meetings subfolder.
- Based on sprint3 feedback, we have updated the Mentor feedbacks with the advice from the mentor meeting.
- For sprint3, we created Task scenarios based on the high priority user stories.
- For sprint3, we created low fidelity prototypes in both hand drawn and Figma.
- For sprint3, to generate usability test tasks, we anylized the user stories, and prepared 5 tasks/scenarios for usability test.
- For sprint3, during the client meeting, we have taken notes, and had a further analysis of future plan.
- For sprint3, we have written the Sprint Review and Sprint 3 Retrospective for sprint3 and the future sprint review will be update in this file as well.
- For sprint3, we have renamed all meeting notes in meetings to present them in a clear time sequential order.
- For sprint3, we have changed Roles and Responsibilities, Mingchong Li is our new Scrum Master.
- For sprint3, we met with our client to do usability testing and recorded Usability Test Video.
- For sprint3, we uploaded trello board screen shot.
- For sprint3, We have conducted a typo check and corrected errors in all the documents that have been uploaded.
- Based on sprint1 feedback, we have removed sprint1 subfolder.
- Based on sprint1 feedback, we have update our Project Background. Updated what is the problem why need solution and what is the solution? and the target audience has been identified.
- Based on sprint1 feedback, we have update our Requirements Elicitations. Added roles and responsibility and has been identified.
- Based on sprint1 feedback, we have update README file and display the team members and stakeholders.
- Based on sprint1 feedback, we have add changlogs for each sprint in README file.
- For sprint2, we have upload the evidence that the process to create personas which include DBF list and Motivational model in the before persona subfolder.
- For sprint2, we have made and upload the personas that followed the Motivational model and our team research. The personas strictly follow the file format required by the unimelb.
- For sprint2, we have made and upload the user stories cover the capabilities required by the client in user story subfolder. The user stories strictly follow the file format required by the unimelb.
- For sprint2, we have build meeting with mentor subfolder in meeting foler, and we have upload one mentor meeting recording. The team meeting notes include the sprint stand-up and planning sessions.
- For sprint2, we added the team meetings in team meeting subfolder.
- For sprint2, we have update the Repository Structure in README file.
- For sprint2, we have write the sprint review for sprint1 and the future sprint review will be update in this file as well.
- For sprint2, we have write the mentor feedback and the future mentor feedback will be update in this file as well.
- For sprint1, we have upload Project Background in the sprint1 folder.
- For sprint1, we have upload Requirements Elicitations in the sprint1 folder.
- For sprint1, we have upload Roles and Responsibilities in the sprint1 folder.
- For sprint1, we have followed the checklist provided by the unimelb.
- For sprint1, we have strictly according to the unimelb's requirements in the sprint1 checklist and rubric.
Below is a detailed outline of the repository's structure, providing a clear overview of the organization of documents, tests, prototypes, UI assets, and data samples.
-
data samples/- Provides documents and data necessary to simulate or demonstrate the prototype, encompassing all inputs required for effective testing and presentation. -
docs/- Contains all documentation files related to the project. Documentation is organized into subfolders for better structuring and ease of access.docs/agile ceremonies- Contains sprint reviews and sprint retrospective according to each sprint.(Sprint plannings and Sprint stand-ups are included in the Team Meetings)docs/meetings- Contains the client meeting, internal team meeting and mentor meeting recording & meeting notes, also the mentor feedback is included.docs/persona-justification- Contains the evidences that the process to create personas has been followed, include DBF list and Motivational model.docs/personas- Contains five personas based on the research done by our team and the discussion with the industry partners, strictly follow the file format required by the unimelb.docs/Project Background.md- Contains the project background include description of the project that accurately and adequately defines the problem and outlines the scope of the solution.docs/Requirements Elicitation.md- Contains our requirements elicitation methods and roles/responsibilities during the meeting with industry partner.docs/Roles and Responsibilities.md- Contains our roles and responsibilities with our team.docs/user story- Contains user stories(include initial and confirmed with client version) completely cover the capabilities required by the client, strictly follow the file format required by the unimelb. Contains one user story feedback and confirmation from client, which help us refine some of the errors and details in the user story. Contains one user story map.docs/Trello board screen shot.jpg- offers our Trello board.docs/Task scenarios.pdf- include the details of five scenarios.docs/SWEN90004_SC-Bluring_Handover.pdf- the handover document for the client and the develop team of next semester.docs/images- contains all images used in md files.docs/Handover- contains the handover record.
-
prototypes/- This directory is split into two subfolders to differentiate between the stages of prototyping:prototypes/low fidelity/- Includes low-fidelity prototypes such as initial handdrawn sketches, Figmaprototypes/high fidelity/- Contains high-fidelity prototypes, including prototype present and source files(edit mode and prototype mode) that closely resemble the final product.
-
tests/- Houses user and system tests that are crucial for ensuring the reliability and functionality of the SCAS.tests/usability test/tests/usability test/low fidelity/- Includes low-fidelity usability test videos, notes, feedbacks from client and action plan to address comments/issues as part of the high fidelity prototype.tests/usability test/high fidelity/- Contains high-fidelity usability test related files.
tests/Acceptance Criterias.pdf- Offers some acceptance criterias for our project.tests/Acceptance Tests.pdf- Offers some acceptance tests for our project.
-
ui/- No new UI elements have been created; all user interfaces are derived from the original Ruby platform. Additionally, no images have been produced for high-fidelity prototypes. -
README.md- Offers an up-to-date overview of the project repository, including its structure and the contents of each directory. The README file is essential for new contributors, providing them with all the information needed to understand and participate in the project effectively.