Last Mile Project Evaluation and Aftermath Guidelines
The Last Mile Project V1.5 and Week 13 Evaluation involve submission deadlines, tutorial and lecture timeslots, user acceptance testing, peer evaluations, and bug resolution processes. Peer evaluations are essential for testing multiple products with varied features, providing insights and improving implementation quality. The aftermath includes bug review meetings, bug classification, severity determination, fixer assignment, and verification by the teaching assistant.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
Project The Last Mile V1.5 and Week 13 Evaluation
Tutorial Timeslot, Demo Start at B1: 00min, B2:15min, B3:30min, B4: 45min Schedule Arrive at least 15 minutes early to setup and prepare 1+ (Team Size x 3) minutes Duration 1 min for overview 3 min each for features by individual member User profile and features (Not to evaluate implementation strategy / quality) Focus
Lecture Timeslot, i3 Aud, Evaluation Phase A [~40 Minutes] User Acceptance Test Similar as user testing in week 11 Differences: Product download from IVLE (tentative) Actual bugs will affect target team's score Tester ID will be anonymized Phase B [~40 minutes] Other Evaluations Evaluate Documentation, Features and Estimate Effort Submit report using TEAMMATES
Why Peer Evaluation? How is it used? The only practical way to test 50+ products with different features Each product are tested with 3-4 dedicated testers Learn and apply testing skill in actual setting You acquire a different perspective How your result is used? The testing result is used heavily for the implementation quality Documentation, Features and Effort estimation will be used as a factor only Quality of both will be reflected for your personal milestones
Until Wed 25th April, 2359, Aftermath Team should meet and review all issues / bugs raised: Response [Accepted, Rejected, CannotReproduce, IssueUnclear] Classify accepted bug [Functionality, Documentation] Decide severity [low, medium, high] Assign fixer [which team member (if any)should take responsibility] TA will verify all issues afterwards
