1. Capstone Project “the name of your product” “the name of your sponsor” Team Member 1 Team Member 2 Team Member 3 Team Member 4 Team Member 5

2. Sample Slides  The following slides are samples of what your presentation should cover. I’m using a fake example involving an app that provides info on where a person can get cheap gas in places where you might need to see an example Your may use these as templates – that is just fill them in with your own content You may build your own from scratch – just make sure that this information is covered in your presentation.

3. Product Overview The problem it addresses  Gas prices may vary between different stations  Drivers want to know where the least expensive gas will be along a route  Product X shows a list of gas stations within a mile of a planned route, ordered by current gas prices

4. Background - give some information about why your product is needed  Recent Oregonian article: Gas prices varied between $2.05 and $1.95 per gallon of regular  Drivers may find a cheaper station down the road after getting a fill-up

5. Who is your audience?  Drivers who plan on taking a pre- defined route  Have a WAP-enabled cell phone  Will be traveling within the Portland metro area

6. What are their characteristics? what do we know about them?  At least 250,000 registered car owners - drive 100,000 miles a day  Over half between 25 and 35 years of age  Most have a computer at home  Most common kind of cell phone is a Nokia ABC - only 25% pay for WAP service

7. Your Product – you may have this summary slide and a separate slide for each feature  Features Feature 1 – enter trip route Feature 2 – show list of stations within a mile of route Feature 3 – order station list by price or distance from route Feature 4 – another cool function

8. Feature 1 – you may have a separate slide for each feature  This feature is shown using the screen capture (use Alt-PrtScr to capture a screen image) and explained within the context of the “typical user”

9. Feature 2 – you may have a separate slide for each feature  This feature is shown using the screen capture (use Alt-PrtScr to capture a screen image) and explained within the context of the “typical user”

10. Feature 3 – you may have a separate slide for each feature  This feature is shown using the screen capture (use Alt-PrtScr to capture a screen image) and explained within the context of the “typical user”

11. Feature 4 – you may have a separate slide for each feature  This feature is shown using the screen capture (use Alt-PrtScr to capture a screen image) and explained within the context of the “typical user”

12. Product Demo This might be a good place to break the power point presentation and do a demo The Demo should take us through a typical “use” of the application – for example, use story telling – “Joe is driving to his friend’s house at 7605 N. Wabash – he’ll be leaving his office at 1200 NW Grand …”

13. The Architecture of the System  What are the major parts of the system?  What does each part do? it’s inputs? it’s outputs?  A picture would be nice here …

14. Customer Feedback  Discuss whatever feedback your customer shared with you: how well does it meet their needs future enhancements they’d like to see general feedback

15. The Process  What steps did you go through  briefly define each step  indicate how much time and effort went into the step (estimated per the project plan and actual)

16. Show Your Schedule go to http://office.microsoft.com/en-us/templates/default.aspx JANFEBMARAPRMAYJUN Sample Text On Time! To edit the timeline, select the timeline object, and then click Ungroup on the Draw menu.

17. Additional enhancements - additional enhancements that could be made?  Future enhancements Optionally list stations that accept user’s gas cards Option to only list stations that sell diesel Allow user to enter nearest intersection of highway milepost marker and provide a list of the ten closest stations ordered by gas price

18. Project Dynamics -How did your team divide up the work?  Team member 1: Gathered user information, responsible for reverse engineering site  Team member 2: Wrote proxy, designed intermediate database  Team member 3: Did some other stuff

19. Lesson Learned  Lesson 1  Lesson 2  Lesson 3