Senior Design 1 Project Android Pilot Nation Stellar Sea Lions Team –Jordan Fryer –Andrew Olivier –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 –Approval for Functional Specification document. –Creation of small Android applications. Completed Plans –Approval for Functional Specification document. Uncompleted Plans –Creation of small Android applications. University of Portland School of Engineering

Senior Design 4 Small Android Applications Get HTML webpage from the Internet –Completed Switch between multiple Activities –Completed Display Pictures from file –Completed University of Portland School of Engineering

Senior Design 5 Small Android Applications Basic File IO –Load and Save files to the Android –Completed Background Counter –Have a counter run in the background –Completed Calendar Interfacing –Interface with Calendar App on the Android –Uncompleted University of Portland School of Engineering

Senior Design 6 Additional Accomplishments Continue to meet regularly to discuss and plan our project. University of Portland School of Engineering

Senior Design 7 Plans for Upcoming Month Design Document Approval Solve or bypass Calendar Emulator issue Contact IT Finalize Budget University of Portland School of Engineering

Senior Design 8 University of Portland School of Engineering Milestones StatusDescriptionOriginal Target Previous Target Present Target CompleteProject Approval Approved3 Sep 10 CompleteDownload Android SDK & Create “Hello Android” 16 Sept 10 CompleteAndroid SDK Setup (on personal computers) 21 Sept 10 CompleteFunctional Specification v Sep Sept 10 CompleteInstall Android SDK in Senior Design Room 3 Oct 10 CompleteFunctional Specification v Oct 10 MissedContact IT8 Oct Oct 10 CompleteAndroid Counter Program15 Oct 10 CompleteAndroid File IO Program15 Oct 10 MissedAndroid Calendar Interface Program15 Oct 10 5 Nov 10 CompleteFunctional Specification Approved15 Oct 10 Design Document First Draft5 Nov 10 Final Budget Set12 Nov 10 Design Document v Nov 10 Design Document Approved24 Nov 10

Senior Design 9 Concerns/Issues Support from IT Android Calendar Interface Jordan 50% less effective Introduction to XML University of Portland School of Engineering

Senior Design 10 Conclusions Functional Specification Approved Many small Android applications finished Calendar Application needs to be resolved IT needs to reached University of Portland School of Engineering

Senior Design 11 Questions? University of Portland School of Engineering

Senior Design 12 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 13 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