2. Team Members Jason Bender Derek Crane Cliff Crane Renan Pereira Isidro Arribas

3. Project Overview Create an iPhone application to serve as an informative and interactive tool for UCF students. Interactive map feature Event information Parking, food, and transit User driven

4. SRS

5. Event Table Map Events User performs search on map User finds their location User clicks map pin piont User views local map (no internet required) Other Events User enters data User views web based data User views embedded data

6. Case Diagram

7. Requirements Resource Requirements System requires a dedicated server to host multiple online pages and store database Require iPhone for testing on physical device. – Virtual device is a simulator not an emulator Geo-location wont work through simulator Application must allow user to alter settings Require Macintosh OSX & SDK for development Require registered developer account for distribution

8. Test Plan

9. Testing Testing continues until application is released for distribution – Application will be deemed ready when: Performs all implemented functions properly Runs continually without failing or crashing Properly multitasks with other iPhone applications All test cases have been passed

10. Test Cases Layout and Design Test Building Search Test Interactive Map Test Static Campus Map Test Scheduler Test

11. PMP

12. Software Lifecycle Process Due to the project’s highly dynamic nature, an Agile Development (XP) approach will be implemented

13. Configuration Management Version control is utilized to monitor the progress of the project All members have access to project repository and are responsible for reviewing each others work before submission A current configuration will be updated when all members agree on new configuration

14. Quality Assurance With each new configuration, the application will be run through all applicable test cases in an attempt to find faults – Includes testing on physical device Web applications will be tested by all members Team will review all deliverables before submission to insure accuracy

15. Risk Management Application becomes outdated - Fix: store all changing data in database for easy access to make frequent changes Application not accepted by Apple - Fix: follow Apple’s protocols as closely as possible to ensure application passes their standards Application not compatible on all versions of iOS - Fix: make sure to not use deprecated features and make sure all features are forward and backward compatible Team member drops out

16. Security The app is developed for open use by anyone who downloads/purchases it – There are no admin profiles Database access is handled by http requests and user has no direct access – Database passwords all stored remotely in php pages called by the request Server is only reachable through a series of predefined calls from application ensuring that an inappropriate call is not possible

17. Pert Chart