Rose-Hulman Archive Project

1
Rose-Hulman Archive Project

• Team 2
• Eric Lewandowski
• Joseph Richey
• Jeremy Barton
• Todd Windler
• Jonathan Knez
• Steven Gregory
• JP Gonzalez

2
Our Client

• Logan Library
• Richard Bernier
• John Robson
• IAIT
• Sonny Kirtley

3
The Project

• Redo the web interface for the RHAP
• Create a friendly user interface
• Fix search engine.

4
The Old System
5
Diagram of Old System
Query select from IAIT.OBJECT
Samuel 1985
Client
Web Server
Table of Results
Formatted Results
6
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!

7
Requirements of New System

• It must work
• It must use the existing database
• Make it easily expandable
• The rest is up to us

8
Diagram of New System
9
Completed Work

• Search Database
• Fully Functional Web Interface
• Return Results and Display in Meaningful Way

10
Implemented Extras

• Static Web Portions Contained In Templates
• Audio Streaming Supported
• Help Synopsis
• Wildcard Search Capability

11
Extras (In Progress)

• Functional Browsing Tree
• Limit Results (10 per page)

12
Demo

• We will now see a search using our script

13
Approach

• Split Into Two Teams
• Individual Parts Done By Sub-Teams
• Workload Dynamically Allocated Amongst Team
  Members Based on Availability

14
Current Status

• System Completed Add Cosmetic Changes

15
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

16
Time Distribution for Spring Quarter
17
Time Analysis for Winter Quarter
18
Risk Analysis Identification and Estimation
ID Risk Probability Impact
A Decision to change the DB field structure M H
B IAIT decides to stop supporting Perl L H
C Client does not approve of final project L H
D The client or IAIT might need to modify Perl code L M
E Modifying our Perl code breaks the system H H
E
High Probability
Moderate Probability
A
Low Probability
D
B, C
Low Impact
Moderate Impact
High Impact
19
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

20
Questions?