DPS924 Projects Fall 2014

Overview

• build a useful and interesting Android app
  • real users/clients
• be innovative
  • market research
  • start-up companies and career opportunities
    • seven Canadian tech startups (2014) [1]
    • 1000 startups [2]
    • startup companies in Toronto [3]
  • startup career in Toronto [4]
  • entrepreneurs and Star-tups (Ontario Centres of Excellence) [5]
• demonstrate your potentials, creativity, and technical skills

Project Milestones

• 1.0 [DONE]
  • due: 11:59 pm, September 9 (Tuesday)
  • Task: Identify 1-3 application domains or user/client groups for your project.
    • detailed requirements
  • Example: application domain: Guide for International Students, user group: international students at Seneca
• 1.1 Project Proposal (Draft Version) [DONE]
  • due: 11:59 pm, September 23 (Tuesday)
  • requirements posted below
• 1.2 Project Proposal (Revised Version)
  • revise the draft according to the professor's feedback
  • due: 11:59 pm, October 7
• 2.0 Design and Implementation of Essential Features.
  • Based on the use cases, submit a list of essential features you are going to design and implement on a weekly basis. This list will be used as a checklist when we go through SCRUM exercises. It is understood that the list of essential features may be refined and modified as we go through the iterations.
    • due(Design): October 11:59 pm, October 7
• 2.1 User Feedback & Evaluation.
  • Collect feedback from real users and submit a brief report.
• 2.2 Rework the design and implementation.
• 3.0 Design and Implementation of Additional Features.
• 3.1 User Feedback & Evaluation.
• 3.2 Rework the design and implementation.
• 4.0
  • due: December 3, 2014
  • Project Presentation & Evaluation

Project Proposal: Requirements

Imagine that you are submitting a proposal to a group of investors who may fund your project.

1. What is the business value or possible impact of your project?
2. Who are your users/clients? (You should have at least 3 users and only one of them may be your classmate.)
3. What are the use cases of your Android app? (Include some diagrams if possible.) This should be the core section of your proposal. You should provide enough details for each use case.
4. What is your Testing Environment?
   • configuration of emulators
     • Note: An emulator does not support Google Maps unless you do additional configuration. Check out the Discovery Zone on the course wiki.
   • configuration of real Android devices (if available)
   • Read the Dashboards to support your choice of the API level. [6]
5. What is the timeline for your project?
6. What resources do you need to complete the project?
   • 1 or 2 developers (names), specific Android device, other devices,...
7. What is the description of your Android app?
   • Read "App Developer Best Practices", especially the section on creating "a great app listing page"! [7]
   • Draft a concise description of your Android app.
8. Submit your project proposal (Word document or PDF) at Blackboard. Give a name to your project and it should also be the name of your Word document. If you are working as a team of 2 people, one submission is sufficient. Note: If you want to receive A or A+, your proposal must be free of spelling errors and address all the questions listed above.

Design Requirements for Your Proposed Android Application

• a user-friendly AND responsive application
• application of relevant UI design principles (in Dr. Olivier St-Cyt's course)
• application of relevant Android Design Principles and Patterns
• Reference
  • Building Mobile Experiences Frank Bentley and Edward Barrett. MIT Press, 2012. (Available as eBook from Seneca Library.)
    • Figure 2.1

The Android Platform

• Dashboards [8]