Milestone 1 - Proof Of Concept Presentation

Host your project at: http://code.google.com/hosting/createProject

This site will serve as your project home page:

+ All source code should be put in project SVN (Source tab)

+ Documentation, screenshots etc. should be put in their appropriate place (Downloads tab / Wiki tab / Project Home)

+ Features and Bugs (and project road-map) should be administered using the Issues tab

For the first milestone (04/07/2014) you are required to provide a proof of concept of your project. By the due date you should have created a scenario that exercises the various parts of your application (e.g. client, server, DB, external resources, etc.) and demonstrates the primary use case and novel contribution of the whole project. You are expected to show an End-to-End demo for you primary feature. Following we provide some guidelines for the work ahead:

1. PROJECT HOSTING

=================

2. FEATURE LIST

================

Please provide a short list of your top priority features (sorted from the most important to the least). This list should be published as soon as possible in the project web site in the Issues section so all team members and the workshop staff would be on the same page with project progress.

For each item state its name, description, the architectural implications of this feature, when is it due (milestone 1 / milestone 2 / final submission / nice to have) current status and estimated time needed for completion.

For example:

- Feature name: Where did you park your car?

- Description: A Google map in which one could locate where he/she parks the family car.

- Requires: adding logic to the server, working with maps api, adding client side support

- Due: Milestone 2 (BETA)

- Status: server side ready. other parts missing

- Time Estimation: 12 hours

Using the standard issue tracker for that (in your project web site) would assist you on deciding what to do next. Every decision (as well as your grade) should be derived from this list. Always work only on the next top priority feature not done.

The features should be justified by the expected use cases of your product and by the innovation of the features. Stay focused - Do not spend time on re-implementing existing functionality, use mocks and stubs as much as possible in order to focus on the main things.

We are interested only in the short list. You may also have another more detailed list for your own use.

It is important to try and estimate the complexity of the various feature as soon as possible so we'd be able to estimate what could be done till the end of the semester. In order to accomplish that you should add *time estimation* for all your features in the feature list and every time you work on a feature check how long it *actually* took. After doing so for several feature you'll improve your ability to estimate a given task.

3. PRODUCT LINK

===============

Please provide in your google code website a link to your running application (gadget/web-site). Although it may not be fully functioning till the BETA milestone, it is important to be able to know what is the *real* status of the final product in every given point.

Take a look the web page of the previous semester to see how the project site is organized: https://sites.google.com/site/cloudweb10a/teams-and-projects

4. MILESTONE PRESENTATION (PROOF OF CONCEPT)

===========================================

Prepare about 10 minutes presentation:

- Start with a live demo that shows what you have accomplished so far (5 minutes)

- focus on the application main use case(s) that highlight its novelty and contribution

- Continue with a short presentation of:

- your progress (2 minutes: how did you split the work? what was easy? what was difficult? why?)

- your feature list (2 minutes: which features are expected? how long do you expect the work would take?)

- your road map (2 minutes: what to expect in the future milestones? how is it differ from the original estimation?)

Also, please send us by email the presentation and a summary document of the above (progress, feature list, road map)

If you haven't already done so, please, create the project hosting site and features list as soon as possible and send us an email (taugadgets@gmail.com) with site address and the names of the group members.

Important note: Full grading for the milestone (15 points) will be given for teams that would .successfully show:

  1. Focusing on primary use case and taking into account our feedback (feedback summary was sent to you via email).

  2. Following the project plan while adapting dynamically.

  3. Continuously working along the semester (tip: put on the project site a report with all the time spent on the project by each of the team members. You may update this report after every programming session).

  4. Demonstrating an interesting, self contained, primary use case of your application.

  5. Good presentation (simple, clear, focused, time-framed, sincere).

If you have any questions please do not wait for the milestone meeting, use email: taugadgets@gmail.com