1 / 17

RNG – RSS News Generator

RNG – RSS News Generator. Team Evensteven Phil Light Becky Vanderhoff Carol Coon Lars Avery Madura Mahenthiran Chris Mamorella. RNG Background. Problem: RIT Departments had no way to post news to myRIT

hestia
Download Presentation

RNG – RSS News Generator

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 – RSS News Generator Team Evensteven Phil Light Becky Vanderhoff Carol Coon Lars Avery Madura Mahenthiran Chris Mamorella

  2. RNG Background • Problem: RIT Departments had no way to post news to myRIT • Solution: Create a tool that will enable departments with any level of technical ability to create news items to be posted on myRIT

  3. RNG • Generates XML News Feeds for RIT departments • Automates the process of composing news items and adding them to the appropriate news feed • Departments own and manage the content of their news feed

  4. Process • Requirements Gathering • Requirements • Design • Implementation • Test • Deployment and Training

  5. Process – cont. • Agile Development • Team Roles • Mandatory and Optional Weekly Meetings for Team • Weekly Meetings with Project Sponsor • Phase Gates

  6. Requirements Gathering • Ongoing process • Questionnaires • How useful • Interest • Contacts • Introduce idea into RIT community

  7. Requirements Gathering – cont. • Interviews • Interest • Gather “wishful” requirements • Problems and issues • Questionnaires and Interviews lead to changes in goals and requirements

  8. Requirements • Templates provided • Added diagrams from SE classes • //Give Requirement examples? • //Give Diagram examples? • Requirement document reviewed in Phase Gate

  9. Design – High Level • Template Provided • Added Diagrams, Architecture, Design Patterns from SE Classes • MVC Architecture • Languages: Java, JSP, Javascript • Interface: Web Page • Database: Oracle and SQL • Server: Apache Tomcat • Reviewed by Phase Gate

  10. Design – Low Level • Split Team in Half • Men – Low Level Design • Used knowledge from SE Classes • //Explanation given • Women – Test Scripts • Template Provided

  11. Implementation • Classes divided among the team • Everyone has backup for coding

  12. Tests • Unit Testing • Regression Testing

  13. Current State of Project • Release 1 • Requirements Gathering completed • Requirements completed • High Level Design completed • Low Level Design completed • Implementation started • Basic Requirements only

  14. Advantages • Project Sponsor on campus • Easier to Communicate • Good team interaction • Good Participation • Good Work Distribution • ITS has defined process and documentation • Team Web page used for posting Documents and Minutes

  15. Disadvantages • Process defined to such a low level that it is very time consuming • Lack of Development Resources • Databases • Development environment • Server • Interaction with ITS • Large number of Stakeholders to coordinate

  16. Things to Come… • Release 2 • Add More Functionality • Release 3 • Functionality completed • Debug system • Training of ITS Help Desk employees, ITS employees and end users • Help Page and User Documentation Completed

  17. Any Questions?

More Related