Online Peer Evaluation System Team Green Apple Team

Online Peer Evaluation System Team Green Apple Team Members Ada Tse Amber Bahl Tom Nichols Matt Anderson Faculty Mentor Prof. M Lutz Project Sponsor RIT Online Learning

Overview • • • Project Overview Process Requirements Process Challenges Downfall: Current System Features: New System Reflections Future Goals Questions

Project Overview • The RIT Online Learning department is in need of an online peer evaluation system that can enhance the collaborative learning experience. Currently, peer evaluation is supported by the use of online surveys provided by the RIT Clipboard system, which is difficult to setup and lacks good reporting functionalities.

Process: Scrum • Scrum Methodology: – The whole project will be delivered in chunks depending on the requirements prioritization. Development team will split the whole project into sprints. On an average the team would deliver each sprint within 2 to 3 weeks. • Scrum Team: – Cross-functional comprised of Scrum Master, Developers, -Tester, UI Designers etc. QA

Process Model Characteristics: – – Produces highly reliable system Rely on self-organization Produces system with large growth envelope Manages risks • Increased Product Visibility • Increased Progress Visibility • *User Feedback

Requirements • Mainly elicited by: – In Person Interviews • Project Sponsors • Subject Matter Experts • Online Learning Technical Staff – UI Mockups – Evaluating • RIT Clipboard • Peer evaluation templates

Requirements Process • Requirements Elicitation for the first 5 weeks.

Downfall: Current System • • Hard to setup Lacks good reporting functionalities Technically weak Not integrated with My. Courses

Challenges • Grading System • Faculty View • Instructional Designer (Help Desk)

Design and High-level Architecture Three Tier Architecture

High-level System Design

Features: New System • Integrated with My. Courses • Broken down into 3 modules – Setup • Create Question Templates • Create Evaluations – Evaluation – Reporting • Effective ways of representing different patters – By Group – By Question (Field)

Reflections • On Schedule • In all 3 Sprints • Progress Key Features Progress Requirements Elicitation DONE Requirements Analysis (SRS) DONE High Level Architecture DONE Initial Setup (DB, Environment) DONE Requirements Prioritization DONE Sprint 1 Planning IN PROGRESS

Future Goals • In all 3 Sprints – Sprint 1 • Feature 2 – Sprint 2 • Feature 1 • Feature 2 – Sprint 3 • Feature 1 • Feature 2

Questions • Thank you!