Senior Design

1University of Portland School of Engineering

Project Android Pilot NationStellar Sea Lions

• Team– Andrew Olivier– Jordan Fryer– Karen Echon– Jacob Hahn

AdvisorDr. Steve Vegdahl

Industry RepresentativeJason Favors

Ben Foran

Senior Design

2University of Portland School of Engineering

Introduction

• Project Android Pilot Nation is an Android application whose purpose is to create a mobile community for the University of Portland athletic fans.

Senior Design

3University of Portland School of Engineering

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

Senior Design

4University of Portland School of Engineering

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

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

6University of Portland School of Engineering

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.

Senior Design

7University of Portland School of Engineering

MilestonesStatus Description Original

TargetPreviousTarget

PresentTarget

Missed Design Document First Draft 5 Nov 10 5 Nov 10 9 Nov 10

Complete Final Budget Set 12 Nov 10 12 Nov 10 12 Nov 10

Complete Design Document v. 0.95 19 Nov 10 19 Nov 10 18 Nov 10

Missed Design Document Approved 24 Nov 10 24 Nov 10 25 Nov 10

On Schedule Implement API 30 Jan 11 30 Jan 11 30 Jan 11

On Schedule Test API 13 Feb 11 13 Feb 11 13 Feb 11

Implement Central Menu and Activity Organizer

20 Feb 11 20 Feb 11 20 Feb 11

Test Central Menu and Activity Organizer

6 Mar 11 6 Mar 11 6 Mar 11

Implement News Feed Activity 13 Mar 11 13 Mar 11 13 Mar 11

Implement Calendar Activity 13 Mar 11 13 Mar 11 13 Mar 11

Final Report First Draft 13 Mar 11 13 Mar 11 13 Mar 11

Test News Feed Activity 27 Mar 11 27 Mar 11 27 Mar 11

Test Calendar Activity 27 Mar 11 27 Mar 11 27 Mar 11

Final Report Version 0.95 1 Apr 11 1 Apr 11 1 Apr 11

Senior Design

8University of Portland School of Engineering

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.

Senior Design

9University of Portland School of Engineering

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.

Senior Design

10

Questions?

University of Portland School of Engineering

Senior Design

11University of Portland School of Engineering

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)

Senior Design

12University of Portland School of Engineering

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.

Senior Design

13

Spring Milestones

University of Portland School of Engineering

Status Description OriginalTarget

PreviousTarget

PresentTarget

Implement API 3 Sep 10 3 Sep 10 3 Sep 10

Test API 16 Sept 10 16 Sept 10 16 Sept 10

Implement Central Menu and Activity Organizer

20 Feb 11 20 Feb 11 20 Feb 11

Test Central Menu and Activity Organizer 6 Mar 11 6 Mar 11 6 Mar 11

Implement News Feed Activity 13 Mar 11 13 Mar 11 13 Mar 11

Implement Calendar Activity 13 Mar 11 13 Mar 11 13 Mar 11

Final Report First Draft 13 Mar 11 13 Mar 11 13 Mar 11

Test News Feed Activity 27 Mar 11 27 Mar 11 27 Mar 11

Test Calendar Activity 27 Mar 11 27 Mar 11 27 Mar 11

Final Report Version 0.95 1 Apr 11 1 Apr 11 1 Apr 11

Final Report Approved 8 Apr 11 8 Apr 11 8 Apr 11

Test System 11 Apr 11 11 Apr 11 11 Apr 11

Project Presentation 12 Apr 11 12 Apr 11 12 Apr 11