3WSPMP.doc Page i
AVI Nutrition Application
Software Project Management
Plan
3WSPMP.doc
Final
April 17, 2013
Revisions
Version Primary Author(s)
Description of Version Date Completed Draft 1.0 Gus Delawder,
Matt Amabeli
The first draft of the SPMP. 02/25/13 Final Draft Gus Delawder Final draft of the SPMP, unless changes need
made
3WSPMPFINAL.doc Page 1
1 Introduction
1.1 Overview
The AVI Nutrition application will be used by the general public to document a person’s daily caloric intake and help promote a healthy lifestyle. Users will log into an account where they can track their caloric intake over a period of time, based on the menu rotation at the University of Mount Union’s Dining Commons.
1.2 Deliverables
- Press release 1 delivered February 14, 2013 - Press release 2 due April 4, 2013
- User manual due April 16, 2013 - Nutrition website
- Companion mobile application - Nutrition database
If not specified, the delivery date is April 25, 2013 at 12:30 PM.
1.3 Schedule
Weeks 1-6 : Meet with client for requirements gathering, create blog, rough draft and final version of SRS document, and introduction.
Week 7: High level design document draft one and begin input to nutrition database.
Week 8: High level design document final version due, continue working with database, web development subteam to begin work on the website.
Week 9: Database should be completed, continue to work on website, mobile development begins
Week 10: Detailed design document rough draft due, continued progress on web and mobile projects.
Week 11: Team project status meeting, final version of detailed design due, press release two draft and final version due, continued work on web and mobile.
Week 12: Users manual rough draft due, finish all work on web and mobile development, begin testing.
Week 13: Users manual final version due, continued testing.
Week 14: Further testing and preparation for the final presentation on April 25th. Finished after presentation.
1.4 Definitions and Terms
2 Project Organization
2.1 Software Life Cycle Model
For the duration of this project, the software life cycle model that we chose to use is the De-sign to Schedule model. We chose this model because we have a hard deadline of April 25, 2013. Our first priority is to create a working product. Once we have accomplished this, we will implement additional features as time allows.
2.2 Responsibility Distribution
Ross Allison: Team Leader – Responsible for organizing team meetings, contacting the cli-ent, creating the database, and mobile application development.
Matt Amabeli: Architect – Responsible for contributing to the database, coding for the mobile application, and website.
Kevin Placek: Architect – Responsible for contributing to the database, and coding for the mobile application.
Scott Popa: Lead Tester – Responsible for locating errors in the code for the mobile applica-tion, and coding the website.
Gus Delawder: Configuration Management Specialist – Responsible for the maintenance of the group blog, ensuring consistency between the website and mobile application, and the documentation outside of coding.
3WSPMPFINAL.doc Page 3
3 Managerial Process
3.1 Feature Prioritization
Feature Name Feature Description
Website
The main focus of the project, to allow a user to create an account and keep track of his/her weight loss goals.
Mobile application
The mobile companion to the website, so users can input their data on the go, or at the dining commons at the University of Mount Union.
Nutrition database All food served by AVI must be put in a
database with its nutritional information.
Like button
Users will be able to select a food they have eaten, and “like” it so that others will know if something was good. Also, the client will be able to use this feature to discern the popular-ity of an item, providing he/she takes into account the fact that the sample may not be well distributed.
Preparation for universal use
Three W does not have time to develop this project for further use, however the client has requested that the team prepare for the even-tuality that there will be other institutions who will be using this application.
Exercise forum
The client would like a forum/group where only registered users can post that they are going for a run at a certain time, and ask for a running partner. Another possible use of this forum would be to locate a partner for lifting weights or doubles in tennis.
QR/Barcode scanner
If time allows, the client would like the sys-tem to have the ability for a user to scan a barcode or QR code on a prepackaged food item to allow easy access to nutrition infor-mation
Special event promotion
If time allows, the client would like to in-clude special event promotion, such as a special Super Bowl themed meal.
3.2 Team Reporting Mechanisms
In addition to the weekly time card provided by Professor Cindric, the team members will have a weekly meeting to compare progress to the proposed schedule.
3WSPMPFINAL.doc Page 5
4 Technical Process
4.1 Methods
We will use the coding standards presented to us in CSC 491 by Professor Cindric. Specifics will be included in a later revision of this document.
4.2 Tools
For the iOS portion of the mobile application, the subteam will likely use Xcode. The team is reviewing the use of HTML5 for the mobile application, however. The webpage will be built using HTML and JavaScript.
4.3 Documentation Strategy
The team will be using GitHub for version control. The team will update the blog with pro-gress made on the project and the final versions of all documents to be released.
6 Architectural Design
Object-Oriented
Object oriented class hierarchy including: Meal Station class
Food subclass