Terrapin Trader Transformation

by

Oliver Stohr - Olga Kuznetsova Tyler Cordrey - Brett Holbert

December 9, 2008

Outline:Intro:

Problem/Purpose Solution User Needs

Development: Low-fidelity Prototypes Technical Specs Final Prototype (Demo)

Testing: Usability Tests Results

Conclusion: Revisions Lessons Learned

Intro: Problem/PurposeWhat is Terrapin Trader?

Terrapin Trader is the University of Maryland’s surplus management organizationWhy Terrapin Trader?

Closely related to sustainability with their efforts of re-using/re-cycling existing products and because it is a UMD facilityWhat’s the problem with the existing process?

Currently the surplus submission is a completely manual process that requires handling of several paper forms by the user as well as updating static HTML files to refresh the online inventory by the

webmaster.

Intro cont.: SolutionWhat can we do? Tried to semi-automate this process by creating a dynamic submission system that allows University of Maryland personnel to log in to Terrapin Trader’s website, fill out all necessary online forms and submit a surplus property request over the internet.

Additionally, these online submissions are automatically queued for review by the webmaster. If the webmaster accepts the surplus request he can publish the item on their website with a click of a button without modifying any HTML source. The online submission system and inventory display is based off a database backend that stores all necessary information.

Intro cont.: User NeedsWho are the user types and what are their needs? Three types of users:

1. University of Maryland personnel o This user has some sort of property that is not being used or required by his or her

department anymore and it can be released to Terrapin Trader for management and/or resale through an easy to use online submission process.

2. Administrators of Terrapin Tradero This user is currently in charge for the upkeep and management of the University of

Maryland's surplus system. To ease the process from a management perspective it will be possible for Terrapin Trader personnel to manage all parts of the submission/publishing process online through an interface.

3. People searching for surpluso People who are interested in purchasing published surplus products. These users could

be members from other University of Maryland departments as well as the general public. They will interact with the online catalog that displays available surplus property.

Development: First PrototypesFirst Prototype Design (home page):

Development cont.: First PrototypesFirst Prototype Design (submit page):

Development cont.: First PrototypesSecond Prototype Design (home page):

Development cont.: First PrototypesSecond Prototype Design (submit page):

Development cont.: Technical SpecsTechnologies used:

PhotoShop (graphics) PHP5 (frontend) HTML (frontend) JavaScript (frontend) SQLite3 (backend) Apache Webserver (local testing)

Development cont.: Final PrototypeEnded up using a hybrid of the two prototypes

Main design from first prototype Implement main menu bar from second prototype

Testing: Usability TestsThe usability test was run on several participants. Half of the subjects were given the task of searching first, and half were given the task of submitting first in order to test the different approaches to the website. Structure of Tests:

Pre-test questions e.g.:o Have you ever heard about Terrapin Trader before? o Have you ever utilized any other surplus product sites before?o …

Test with tasks to fulfill e.g.:o Navigate to ‘About us’ and read about the websiteo Navigate to ‘New User’ and create an account using a umd address and sample information o Logino …

Post-test questions e.g.:o Overall reactions to the systemo Screen Layoutso Use of terminologyo …

Testing cont.: ResultsThe usability tests were a great success and resulted in a lot of constructive feedback. Compiled a list of possible enhancements and ranked them by importance.

Overview of user feedback:

Conclusion: Revisions

Implemented 16 of the suggested 39 fixes so far.

Will continue to work on revisions and possibly re-run a second usability test.

Conclusion cont.: Lessons Learned

Doing proposals, prototypes…are great guidelines for the whole project/schedule Usability tests work Working in groups can be challenging especially

o using specific technology implementationso time managemento different skill levels

Great to work on a complete project (start to finish)

Thank you!

Any Questions?