1. Trippin’07 Nick Campbell, Paul Giambalvo, Jason Talis, Patrick Winters

2. What is Trippin’07? Build a narrative of your travels. Mark places visited on a world map. Associate content with each of these places

3. Customers The world traveler The tourist Anyone who wishes to keep track of their travels

4. Customers David Brown, a senior animation student at NYU. Alex Midgley, an experienced traveler.

5. Competitive Landscape No direct competition (popular) There are many applications that share some of the functionality of Trippin’07. Flickr and Picassa Some blogging engines These lack the all-in-one functionality that our application will offer.

6. Competitive Landscape Travelblog.org

7. Functional Requirements Plot travel locations and routes on a world map. The user should be able to click to place pushpins to mark visited locations. These pins can be connected with lines to denote routes taken.

8. Functional Requirements The ability to create trips and organize them by several criteria Region Date Trip title

9. Functional Requirements The ability to associate content with each point of interest. By either clicking a pushpin on the map, or through an “Add Content” page, the user can add photos, videos, journals, or other information to be associated with a trip.

10. Functional Requirements A search content function The ability to use text queries to find media and trip items.

11. Interface Requirements The system will be able to support multiple users, each with their own set of trips and information. The map used for the mapping/plotting of trips should have complex capabilities including search and zoom. It should be displayed in rich detail.

12. Nonfunctional Requirements Professional Interface -The user interface should be visually attractive. Responsive Timing -The application must be responsive and quick to return control to the user. Any Internet-dependent tasks must not take any longer than unavoidable network latency. Environmental Constraints – The application will run in the UNIX environment, utilize a relational database, and will require Internet access. Confidence - User data, media, and personal information must be secure. It will remain private unless otherwise requested by the user.

13. Use Cases

14. Navigate Map Pre-Conditions:  The map must contain all previously entered information Post-Conditions:  The state of the map will be saved when the user finishes his session. Basic Flow: 1.The user's world map will be displayed, populated with all of their pushpins and routes. 2.To navigate the map, the user will be able to zoom in and out, and pan in all directions. 3.The map can be toggled among “Map”, “Satellite”, and “Hybrid” view. 4.The user will be able to place a new pushpin on the map. After doing so, they may associate this pin with an already existing trip, or create a new trip for it. 5.Routes can be drawn with tools for connecting pins. 6.Clicking on existing pins will allow a user to view or manage that trip. 7.By entering a location in the search box, the map will navigate to the designated location, if valid.

15. Pre-Conditions:  None Post-Conditions  The trip will be saved for later access.

16. Pre-Conditions:  User must have at least one trip created Post-Conditions  Content will retain its current state until the user modifies it.

17. What is Still Unclear? Desktop or Web Application? Technology for creating a web app using C++. Is using cgicc or C++ Server Pages a reasonable way to handle this?

18. Questions?