1 / 7

StuartNet: A location-aware multimedia tour system.

Explore the Stuart Art Collection at UCSD with this mobile tour system, offering interactive experiences and visitor information. Learn about the collection's history, sponsored art pieces, and architectural design while navigating the campus. Discover the challenges faced and agile process utilized for the system's development.

mackeye
Download Presentation

StuartNet: A location-aware multimedia tour system.

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. StuartNet: A location-aware multimedia tour system.

  2. Outline • Introduction & Process • Frank Uyeda • Presentation by Workflows • Requirements • Erez Perelman & Matt Ferlo • Architecture • Rares Saftoiu • Implementation • Barry Demchak & Lucas Lee

  3. The Stuart Art Collection • Founded in 1982 under an agreement between the University and the Stuart Foundation • 15 sponsored art pieces located across the UCSD campus • Numerous visitors and tours each year.

  4. Overview • Goal: Mobile location-aware multimedia tour system • Objectives • Design Artifacts (process documents, architecture & design, software) • Working prototype system • Customer Satisfaction (Stuart Collection) • Challenges • Several unknowns (requirements, platform, team abilities) • Very short time scale.

  5. An Agile Process • Customized the Rational Unified Process • Four Workflows • Requirements • Architecture • Implementation • Testing • Four Phases • Inception (1 week) • Elaboration (1 week) • Implementation (2.5 weeks) • Transition (0.5 weeks)

  6. Agile Process Cont. • Six roles • Process Manager • Business Manager • Requirements Manager • Architect • Developer • Tester

  7. Team Results • Focused and frequent customer interaction • Several iterations on each workflow • Team meetings twice per week • Weekly progress reports and feedback from Prof. Krueger • Archived all artifacts on the web • http://www.tpsoft.com/CSE210/

More Related