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

2. Agenda Project Overview Current System Our Product Features Product Architectural and Design Software Process Risk Analysis and Mitigation Metrics Requirements Process Status & Future Goals Demo

3. Problem Statement The RIT Online Learning department is in need of an online peer evaluation system that can enhance the collaborative learning experience. Existing Tool: –Paper Alternative –Clipboard Survey System

4. **Importance Group work is an important aspect in today's education system –I would like to add some data here. We can email Richard on this. The average SE graduate does about 16 group projects

5. Current System: Clipboard Create, Deploy and Analyze –Does provide different views for analysis but more effective for analyzing surveys then Peer Evaluations. –Very Hard to identify problem groups Not integrated with myCourses Survey System Can’t deploy evaluations per group Hard to setup Reporting does not show group weaknesses No control over who takes the survey

6. Current System: Reporting View View: Percentage/ Graph

7. Current System: Reporting View

8. Solution: Custom Application

9. Peer Evaluation System Integrated with myCourses –Login Pass-through –Course and Group Data Imported directly from myCourses Setup Workflow –Tailored for peer evaluations Question Templates –Reusable –Shared between Instructors

10. Application Workflow Instructor Main -Create Eval Student main -Take Eval Instructor Main -Reporting 1. Create Evaluation 2. Take Evaluation 3. Analyze Results WOW!!

11. **Instructor Main Instructor Main List of global and personal questions templates Evaluation Status Evaluations listed per course

12. Solution: Create Evaluation Select Template Eval Setup Info

13. Solution: Create Templates Global/ Personal

14. Solution: Students View Instructions

15. Solution: Reporting Reporting (Provided with the help of multiple views) –Multiple levels of detail By Group By Student –Sorted by groups or individuals –Quickly identify problem groups

16. **Solution: Reporting View

18. Product Architecture and Design

19. **Architectural Design Now looks at our products Architectural Design and quality attributes.

20. **High-level Design Key Classes/ Package Diagram –Tom

21. **Deployment Diagram

22. Software Process

23. Process: Scrum What is Scrum? –Scrum is an iterative, incremental process for developing any product or managing any work. It produces a potentially shippable set of functionality at the end of every iteration (Sprint).

24. Scrum: Sprint Delivers working software –Typically between 1-4 week iterations Cross-functional tasks per team member Total focus—no unwanted diversion –No interruptions/changes from the outside New work may be uncovered by the team during development

25. Our Methodology Flavor of Scrum Similarities: –The whole project was implemented in chunks (Sprints) depending on the requirements prioritization (Sprint Backlogs). Differences: –Upfront requirements –Extended the Sprint one delivery date

26. Requirements Process Mainly elicited by: –In Person Interviews Project Sponsors Subject Matter Experts Online Learning Technical Staff –UI Mockups –Evaluating RIT Clipboard Peer Evaluation Templates

27. Requirements Analysis Use Case Analysis Workflow Diagrams –Workflow Steps Constant user feedback at the end of each Sprint

28. Risk Analysis and Mitigation

29. Risk Analysis New Technologies –.NET Integration with myCourses –LDAP Authentication –XML Feeds –Testing

30. Risk Mitigation Software Process Methodology Task Planning Tooling

31. Risk Mitigation: Task Planning Specified tasks according to skill set New Technologies –Team members started off with small/simple programs –Experienced team members educated the team LDAP Authentication –Great help from the Online Learning

32. Risk Mitigation Plan: Software Process Use of Scrum *User Feedback (Allows for midcourse corrections) Deployable Deliverable (At the end of each Sprint) Increased Product Visibility Increased Progress Visibility –Sprint Planning Through many sprints the requirements were revised many times to ensure that clarity is achieved. Throughout every sprint, each decision will be evaluated to make sure that it aligns with the overall goals of the project. We conducted many team building events as deemed necessary by the team.

33. Risk Mitigation: Tooling Subversion for revision control –Include all project documents Trac provides web based management –View files and Changesets Automated synchronization of project documents to web site Provides an integrated bug tracking system

34. Date Collection

35. Metrics Backlogs –Product –Sprint Number of tasks completed for a particular sprit (Work effort distributed for each sprint) Number of bugs –By Feature –By Severity –Per Sprint Total effort (man hours) for all phases

36. Effort Metrics

37. Bugs Per Feature

38. Current Status Progress Key FeaturesProgress Requirements ElicitationDONE Requirements Analysis (SRS)DONE High Level ArchitectureDONE Initial Setup (DB, Environment)DONE Requirements PrioritizationDONE Sprint 1DONE Sprint 2DONE Sprint 3DONE Integration TestingIN PROGRESS About 95% of High Priority requirements addressed.

39. Future Enhancements More views for Reporting Better support for Answer type

40. **Reflections Great Team!!! –All team members were Free Agents (oops!) Software Process Model Delays in Sprint 1 –Unknown Technologies –.NET 2.0

41. **Demo LINK COMES HERE

42. Questions Thank you!

43. Supporting Data

45. Challenges Uniformity –Rating System –Question System Faculty View Different User Types Synchronization with myCourses