1 / 10

RNG Implementation

RNG Implementation. Release 1. Agenda. Current state of project Scheduling Design work Test planning Implementation Demo Unresolved Issues and planning Rollout Alpha test. Old Schedule. Had to be reworked Delays obtaining and setting up development machine Code dependency problems

gallowaye
Download Presentation

RNG Implementation

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. RNG Implementation Release 1

  2. Agenda • Current state of project • Scheduling • Design work • Test planning • Implementation • Demo • Unresolved Issues and planning • Rollout • Alpha test

  3. Old Schedule • Had to be reworked • Delays obtaining and setting up development machine • Code dependency problems • Normal extraordinary circumstances • Two releases instead of three • Release 1 demo today • Release 2 scheduled for 5/5/03

  4. New Schedule • Increase Rollout time • Instead of 2 weeks, 4 • Decrease Beta test time • Instead of an entire release, 1 week Alpha test • No anticipated change in team test time

  5. Timeline • 4/7-4/11: continue development on R2 use cases, get in touch with testing departments, work on a basic set of documents. • 4/14-4/18: alpha test, continued development on R2, begin rollout process with ITS • 4/21-5/2: develop, test, and documentation time. Continue making transition to ITS systems. • 5/5: Release 2, containing full functionality, well tested. • 5/5-5/16: take application "live" on ITS servers, complete and distribute documentation, offer training to departments and helpdesk. • 5/12-5/16: final project presentations for SE department.

  6. Design • Largely unchanged • Low-level design complete for both releases • Last unknown: Automatic expiration • Have written Executioner class which removes articles from feed based on expiration date • Need to figure out how to run it daily

  7. Testing • Test Scripts complete • Reviewed at last phase gate • Available on team website (http://www.se.rit.edu/~evensteven) • Unit testing proceeding with development • Have set up bug tracking utility (roundup)

  8. Implementation • Current functionality: Add news items to feed • Exercises all modules of design • LDAP lookup • Database Access • File system management • News Item and RSS generation

  9. Unresolved Issues • Various bugs • Month-related errors • Apostrophes in database strings • Location of configuration file • Scheduling: how to handle additional delays • Quota management • Should be easy to add quota management into config file • May be more difficult to integrate with OS quotas

  10. Demo

More Related