Senior Design 1 Project Android Pilot Nation Stellar Sea Lions Team –Andrew Olivier –Jordan Fryer –Karen Echon –Jacob Hahn University of Portland School of Engineering Advisor Dr. Steve Vegdahl Industry Representative Jason Favors Ben Foran

Senior Design 2 Introduction Project Android Pilot Nation is an Android application whose purpose is to create a mobile community for the University of Portland athletic fans. University of Portland School of Engineering

Senior Design 3 Scorecard Previous Plans –Purchase development phone. Solve or bypass Calendar interfacing issue using the developer phone. Completed Plans –Purchased development phone. Uncompleted Plans –Solve Calendar interfacing issue using the developer phone University of Portland School of Engineering

Senior Design 4 Calendar Interfacing Issue Previous Thoughts –Emulator did not have a Google Calendar Application to test on –Difficulty installing on the emulator –All Android phones come with Google Calendar Application Current Thoughts –No API for making use of developer phone Calendar App –Every phone implements the Calendar App differently –No online examples of people attempting to interface with the Calendar came close to working –The online Google Calendar has an API we can use University of Portland School of Engineering

Senior Design 5 Additional Accomplishments Small Android programs loaded and run on development phone Created dummy classes for each class based on the design document. Finished initial coding for the APN_Driver, APN_API, and APN_Storage classes. Just began testing phase of above classes. University of Portland School of Engineering

Senior Design 6 Plans for Upcoming Month Have the API sections of our project coded and tested (without Activities) Have implemented the Central Menu and Activity Organizer sections of our project coded so that we can begin visual testing of API with our Menu Choose either XML or Java for UI by next week. University of Portland School of Engineering

Senior Design 7 University of Portland School of Engineering Milestones StatusDescriptionOriginal Target Previous Target Present Target MissedDesign Document First Draft5 Nov 10 9 Nov 10 CompleteFinal Budget Set12 Nov 10 CompleteDesign Document v Nov Nov 10 MissedDesign Document Approved24 Nov Nov 10 On ScheduleImplement API30 Jan 11 On Schedule Test API 13 Feb 11 Implement Central Menu and Activity Organizer 20 Feb 11 Test Central Menu and Activity Organizer 6 Mar 11 Implement News Feed Activity 13 Mar 11 Implement Calendar Activity 13 Mar 11 Final Report First Draft 13 Mar 11 Test News Feed Activity 27 Mar 11 Test Calendar Activity 27 Mar 11 Final Report Version Apr 11

Senior Design 8 Concerns/Issues We are now forced into taking a backdoor approach to using the Calendar which still allows us to achieve full functionality. Deciding between using XML (which we are weaker on) or Java code (which makes changes more code intensive) for the GUI of our application. Our project file keeps becoming corrupt and not compiling, despite good src code. University of Portland School of Engineering

Senior Design 9 Conclusions A lot of work ahead of us. We are not yet in stress mode nor in relaxation mode, as of yet the project is moving forward. Difficulties encountered already forecast that we may need to treat the project with more “respect.” Might take more man hours than anticipated. University of Portland School of Engineering

Senior Design 10 Questions? University of Portland School of Engineering

Senior Design 11 Understanding Milestone Dates The Milestones slide is one of the most important slides in your presentation. It can be tricky to get the dates correct. The milestones you place on this slide should come directly from your last document that has been approved to version 1.0 (functional specification or design). If this is your first program review (September) just create a milestone for the major tasks you foresee including each of the major versions of your functional specification (0.9, 0.95 and 1.0). After September, you will have more milestones than can fit on one slide. Select the five milestones whose original deadlines immediately proceed the current date and at least five more milestones that follow the current date. The Original Target date is the date when you stated you would complete this document in your functional specification or design. In September, this will be the due dates specified in the course schedule. The Previous Target date is the expected completion date you had in your last program review presentation. I.e., copy the date that was in the “Present” column in your last presentation. For your September program review, leave this column blank. The Present Target date is the date that you currently expect to complete each milestone. If the milestone is complete, then you should put the completion date here. Color code your milestones slide appropriately (see next slide) University of Portland School of Engineering

Senior Design 12 Color-Coding Milestones The background color of row in your milestones table should vary depending upon the status of that milestone. Use pale shades of the colors for easy readability. Red (missed)– This milestone’s Original Target date has passed since the last program review and you failed to complete the task on time. Orange (delayed) – This milestone’s Original Target date has not passed, but you believe that you will not complete the milestone on time (i.e., the Present date is later than the Original date). Yellow (behind) – You are currently behind on this milestone but have plans to catch up and meet your date. Green (completed) – This milestone has been completed by the team since the last program review and it was completed on or before the original scheduled date. White – everything else. This will include milestones you completed before the last program review. This will also include milestones that are not yet completed and don’t appear to be in any danger. University of Portland School of Engineering

Senior Design 13 Spring Milestones University of Portland School of Engineering StatusDescriptionOriginal Target Previous Target Present Target Implement API3 Sep 10 Test API 16 Sept 10 Implement Central Menu and Activity Organizer 20 Feb 11 Test Central Menu and Activity Organizer 6 Mar 11 Implement News Feed Activity 13 Mar 11 Implement Calendar Activity 13 Mar 11 Final Report First Draft 13 Mar 11 Test News Feed Activity 27 Mar 11 Test Calendar Activity 27 Mar 11 Final Report Version Apr 11 Final Report Approved 8 Apr 11 Test System 11 Apr 11 Project Presentation 12 Apr 11