DPS924 Projects Winter 2015

Overview

• Learning Objectives.
  • Build a useful and interesting Android app by the end of the semester.
  • Have a sense of achievement after building an operational Android app with feedback from end users.
  • Develop your applied research skills as you need to search for additional knowledge in order to complete the project.
    • use Android packages not covered by this course
    • integrate with another API (e.g. a Web API, Twitter API, Facebook API, Flickr API,...)
  • Demonstrate your potentials, creativity, and technical skills.
  • Use GitHub to build an Android app.
  • Use agile software development approach.
    • user stories(from the perspective of end users)
    • sprints (i.e. iterations)
    • weekly standup meetings
• 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 start-ups (Ontario Centers of Excellence) [5]
• Team size: 1-2 persons.

Project Milestones

• Exploration of Project Ideas. [Week 1 - Week 3]
  • Identify an application domain for your Android project.
  • Gather information from end users (i.e. people who will use your app).
  • Do market research (e.g. Google Play Store) if needed.
• Submission of a Project Proposal. [Week 4 - Week 5]
  • date of submission: February 15, 2015
  • Watch the video (approx. 7 minutes) about creating user stories. [6]
  • Create a business statement.
    • key questions
      • What kind of Android app are you going to build?
      • Have you found similar apps on the market (e.g. Google Play Store)? If so, please include some links in your proposal.
      • How does your app differentiate from other similar apps on the market?
    • focus: application domain, end-user needs, business values
  • Create user stories (or use cases).
    • key question
      • How is a user going to use your app?
    • SCRUM User Stories (from the perspective of an end-user) [7] [8]
    • an example from a CDOT project [9]
  • Create a list of features on your app.
  • Create a sketch of your design.
    • Note: The design may change as your project goes through the iterations.
  • Create a system diagram of your app.
    • identify the key components (e.g. UI, database, Web API, server)
      • an example:
  • Create a tentative timeline.
    • based on the priorities of user stories/use-cases
    • identify checkpoints/milestones
  • Your proposal must include the name of your app, names of team members, and the date of submission.
• Design and Implementation. [Week 7 - Week 12 (February 15 - March 31); 6 weeks]
  • Design Report 2.0
  • GitHub activities
  • Weekly standup meetings on Fridays [10]
    1. What have I done since the last Scrum meeting (yesterday)?
    2. What will I do before the next Scrum meeting (tomorrow)?
    3. What prevents me from performing my work as efficiently as possible?
  • Sprints (i.e. iterations) [11]
• Project Presentation and Final Report. [Week 14]
  • April 13, 2015 (Monday)