Rose-Hulman Archive Project

1
Rose-Hulman Archive Project

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

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
Essential things to finish

• Fully implement basic search capability
• Parse and display search results
• Add advanced search support
• Build the surrounding web pages
• Check compatibility with different client
  environments

9
Extras

• Implement a dynamic browsing tree
• Sort search results by relevancy
• Research better searching methods
• Fully support streaming audio and video

10
Screen shot of prototype
11
Screen shot of prototype
12
Screen shot of prototype
http//www.rose-hulman.edu/Archives/Materials/Misc
/Test/mod_1977_faculty1.jpg
13
Perl Script Example

• We will now see a search using our script

14
Diagram of New System
15
Time Analysis for Winter Quarter
16
Time Distribution for Spring Quarter
17
What We Have Learned

• Use of Prototype to elicit requirements
• Worked very well
• Gave us requirements on more than UI
• Communication with team
• Missed meetings
• Documents late
• Wasted Time

18
What We Have Learned(cont.)

• Communication with IAIT
• Needed acess to existing files
• Needed executable rights to our script
• Working with a pre-existing system
• There can be less work to do
• There can be more work to do fixing it

19
Current Status

• Interface Design is complete
• Backend Design is complete
• Ready to start implementing the system
• Waiting for dev environment to be working

20
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 We run out of time L H
D Client dislikes Interface L M
E Members abandon team L L
High Probability
Moderate Probability
A
Low Probability
E
D
B, C
Low Impact
Moderate Impact
High Impact
21
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 - We run out of time
• Request members to put more hours into the
  project, when delay is detected
• Leave behind clear and concise documentation for
  next developer
• D - Client dislikes Interface
• Modify Interface to clients new specifications
• E - Members abandon team
• Remaining team members put more hours into the
  project
• Recruit new members

22
Will we finish?

• Yes
• Currently ahead of schedule
• Feel that we know the system really well
• We have a smart hard working team