Georgia Institute of TechnologyChristina M. Gardner, PhD
Printable Version of this PageHome PageRecent ChangesSearchSign In

Final Project

CS Principles - Final Project
Click here for full assignment: Final Project.docx
Click here for rubric: Final Project_Rubric.docx

Examples of completed student projects:
Student #1


Student #2


Final Project
A novel project created for this class will account for a significant portion of your grade. It is not possible to pass this class without submitting a Final Project and Portfolio. This project will be based on an idea of your choice related to the class and will require a significant amount of time to develop. We will discuss this requirement in detail during class.

Your Final Projects is an opportunity to:
  • Exercise your creativity and use computing to bring your ideas to life
  • Develop a mobile application that addresses a need
  • Apply basics concepts of programming
  • Speak intelligently about mobile computing and how to develop it

Final Project ideas must be approved by the instructor for appropriate scope and complexity. All projects will be done independently unless a substantial enough project is proposed by a multi-disciplinary pair of students.

Note, failure to turn in the completed project will result in a failing grade for the project (even if you completed a portfolio).

Oral Presentations
Everyone will present their final project during the time allotted for finals. Presenters will be selected at random. You must be present during all presentation days in order to receive credit for your presentation. Missing a day of presentations will result in a zero for your presentation.

Deadlines:
Project Part 1: Proposal (7/2/2012)
Project Part 2 – User Interface Progress Demonstration & Screenshots (Due 7/10/2012)
Project Part 3 – App Behavior Progress Demonstration & other updates (Due 7/17/2012)
Project Part 4 – Testing & User Survey (Due 7/24/2012)
Final Project - Completed Final Project (Due July 31, 2012)
  • Completed App
  • User Testing Feedback
  • What you learned
(Due: July 31, 2012) Updated Portfolio with all HW, class, and project artifacts



Project Days: July 2nd and July 3rd – Work on Project Proposal
Project Proposal (Due July 2, 2012)
1. Project Idea: Find at least 3-4 existing apps that are similar to what your are thinking of doing. Search on the Web or on the Android or iPhone Market.
  • Make a chart listing the name of the apps you’ve found and their functionality
  • Come up with a name for your app and

2. Portfolio Page: Create a Portfolio page for your projects under the Projects tab.
  • Write a brief description of your app and its functionality.
  • Add your Similar App Chart to your portfolio
  • Summarize your findings from your search of similar apps and the opportunities in the market for your App.

3. Prepare an Elevator Pitch for Monday, July 9, 2012 (Part of class participation grade)
  • Write a 1-minute "elevator pitch" – i.e., a brief description of your project – that you can use to "sell" your project idea. Here's a possible template:
1. [name of app] is a
2. [kind of thing it is]
3. for [the people who would use it]
4. that, unlike [the major alternatives],
5. [the major distinguishing feature of your app]

Project Part 2 – User Interface Progress Demonstration & Screenshots (Due 7/10/2012)
4. Design Document: Design your app. What will the user interface look like? How will the user interact with it? What events will be handled? On your portfolio page Include:
  • A snapshot of how the screen will be layed out when the app starts.
  • A series of event-response descriptions – i.e., for each event that will occur, how will your app respond.
  • Update your portfolio with all project materials.
Project Part 3 – App Behavior Progress Demonstration & other updates (Due 7/17/2012)
5. Update the Design Document:
  • Update your design document with any changes you’ve made to your app
  • Add a Flow chart – High level how does your app work from the perspective of a user, low level – map out the algorithms from the perspective of your app in your program (include user input, data storage, other program flow details)
  • Add a Structural diagram – user interface and how it maps to the underlying code and structure of your database or other storage and indicate any sensors that you use
  • Update your portfolio with all project materials.

Project Part 4 – Testing & User Survey (Due 7/25/2012)
6. Implementation and Testing. Leave ample time to implement and test your app. Have your friends try it. Leave time to get help from the TAs or instructor when you run into debugging issues.
7. Update your portfolio with all project materials.

Final Project - Completed Final Project (Due July 31, 2012)
8. Completed Project - Includes
  • Completed App – Zip file
  • User Testing Feedback – Summarize the feedback you received from test users of your App. What did users like about your app? What improvements do testers suggest for your app?
  • Describe what you have learned from this project and class.
  • Update your portfolio with all project materials.


Last modified 9 August 2012 at 12:29 am by cmgardne