200 likes | 225 Views
Collaborative project to revamp the RHAP web interface for the Logan Library addressing speed, complexity, and consistency issues. Accomplishments, challenges, lessons learned, and risk analysis detailed.
E N D
Rose-Hulman Archive Project Team 2 Eric Lewandowski Joseph Richey Jeremy Barton Todd Windler Jonathan Knez Steven Gregory JP Gonzalez
Our Client • Logan Library • Richard Bernier • John Robson • IAIT • Sonny Kirtley
The Project • Redo the web interface for the RHAP • Create a friendly user interface • Fix search engine.
Database Diagram of Old System Query: select * from IAIT.OBJECT “Samuel + 1985” Client Web Server Table of Results Formatted Results
Dislikes of Old System • Too slow. • Client receives entire database then does its own searching • Memory intensive • Too complicated • Theme inconsistent with rest of Library page • Does not work!
Requirements of New System • It must work • It must use the existing database • Make it easily expandable • The rest is up to us
Completed Work • Search Database • Fully Functional Web Interface • Return Results and Display in Meaningful Way
Implemented Extras • Static Web Portions Contained In Templates • Audio Streaming Supported • Help Synopsis • Wildcard Search Capability
Extras (In Progress) • Functional Browsing Tree • Limit Results (10 per page)
Demo • We will now see a search using our script
Approach • Split Into Two Teams • Individual Parts Done By Sub-Teams • Workload Dynamically Allocated Amongst Team Members Based on Availability
Current Status • System Completed – Add Cosmetic Changes
Lessons Learned • Maintenance and Modification Is Tougher Than Creation • Constraints Dictate Design Decisions • Communication With Client Is Necessary • Complete Core Project First, Add Extras As Time Permits
Risk Analysis Identification and Estimation High Probability E Moderate Probability A Low Probability D B, C Low Impact Moderate Impact High Impact
Risk Analysis Mitigation • A - Decision to change the DB field structure • Modify parsing script and searching script • Migrate records from old DB to new DB field structure • B - IAIT decides to stop supporting Perl • Re-write scripts in other languages IAIT supports • C - Client does not approve of final project • Meeting were held after implementing each feature • D - The client or IAIT might need to modify Perl code • Heavy documentation in Perl code • E - Modifying our Perl code breaks the system • Code is documented • In-depth Technical Document