1 / 16

try again, er something. February 17, 2005

This project aims to upgrade the current "try" system by streamlining submission, testing, grading, and script collection processes. The new system focuses on improving learning curve, assignment management, portability, and performance. Major use cases include actions for students, graders, and professors. The project follows a spiral process with key milestones, involving framework development, submissions and grading, testing, code completion, and finalization stages. Requirements are sourced from various documents and experiences, with bug tracking facilitated via Bugzilla. The design incorporates web-based technology, J2EE, distributed testing, and finalized database structures. The current status reveals challenges in schedule adherence but highlights strong requirements and design for future success.

darlenepeterson
Download Presentation

try again, er something. February 17, 2005

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. try again, er something. February 17, 2005 Greg Giacovelli – Nick Mancuso – Shaun Newsum – Jean-Paul Pietraru – Nick Stroh

  2. Agenda • Project description • Project plan • Risks • Requirements • Design • Current status • Domain experience

  3. Project Description • The current “try” system • submission, testing & grading • collection of scripts • New system goals • ease learning curve & assignment management • portability • performance

  4. Major Use Cases • Students • Submit assignments • View test results • View grades • Graders • View submitted files • View test results • Assign grades • Professors • Create assignments / activities / tests

  5. Process • Spiral • R1 – The Framework (January) • R2 – Submit & Grade (February) • R3 – Compile & Test (March) • R4 – Code Complete (April) • R5 – Gold (May) • Why • immediate feedback • ship even if slip

  6. Risks Key: 1 = low risk / impact 5 = high risk / impact

  7. Requirements - Elicitation • Sources: • project proposal • customer engagement • existing interface documents (XML) • old “try” system • manuals • sample lab • personal experience • Use cases • Preliminary database & architecture designs

  8. Requirements • All known system requirements documented • prioritized (1-3) • divided among iterations • tested against old “try” manuals • Data dictionary is critical to the system • Each requirement is independent & numbered • Bugzilla used to track bugs

  9. (numbers as of 2/10/05)

  10. (numbers as of 2/10/05)

  11. Design • Justifications • Web based system • J2EE • Distributed test processing • Process • Finalized requirements • Designed database / file structure • Presentation / business logic / data

  12. Architecture flow

  13. Architecture flow

  14. Current Status Key: white = pending; green = delivered on time; red = late

  15. Experience so far • Active customer involvement crucial • the bad… • Slipping schedule • Project management • resource allocation • time estimates • multitasking • minutes • …and the good: • Solid requirements & design will ensure smooth sailing from here • Good communication / teamwork • Constant customer interaction

  16. questions?comments?concerns?

More Related