H N L

Introduction 1.1. Background 1.2. 1.3. 1.4. Existing Problem Statement of Problem

Significance of the Project

Software Requirement Specification 2.1. Introduction 2.1.1. Purpose 2.1.2. Scope 2.1.3. Definition, Acronyms, and Abbreviations 2.2. Overall Description 2.2.1. Product Perspective 2.2.2. User Interfaces Methodology 3.1. Analysis 3.1.1. Use Case Model 3.1.2 Use Case Diagrams

3.1.3. Analysis Model 3.1.3.1. Analysis Class 3.2. Design 3.2.1. Design Class Diagram 4. Conclusion and Future scope

5.

Bibliography

H N L

Modern America has a severe weight problem. About 35% of all Americans are obese with an even larger percentage of Americans who are overweight. Many Americans resort to crash and fad diets that can be unhealthy and detrimental to your health. 1.2. Existing Problem Weight loss products are extremely marketable due to the weight problem in America. Everybody is looking for the next best thing that will help them reach their weight loss goals, however many people go about it the wrong way. People need to understand the importance of eating right, exercising, and portion control rather than trends and fad diets that don't work or have lasting results. 1.3. Statement of Problem Calocount is an application that we are building to aid people with a BMI calculation, food log, a schedule, and provide useful health tips to our users. The application tracks weight loss progress and graphs individual progress in a simple way that users will enjoy.

Introduction 1.1. Background

The main focus of our project is to help maintain todays overweight society. We are aware that peoples health is based on a personal choice, what we are doing is offering a tool for those who do need help in logging their progress and view their weight loss effectively. Calocount will attempt to solve many Americans' weight problems through several different features. One of these features is the weight loss tracker. The weight loss tracker will keep track of daily weight progress and graph weight loss over a period of time so that the person can see his/her weight loss progress. In addition to the weight loss tracker, Calocount will feature a food log for users to keep track of their portions and eating habits on a day-to-day and meal-to-meal basis. This is essential for proper nutrition and portion control. Also, Calocount will implement a health tips feature in which it provides the user with useful health tips to assist them in achieving their weight loss goals.

1.4.

Significance of the Project

Software Requirement Specification 2.1. Introduction

H N L The proposed implementation for the application is Google Web Toolkit with Eclipse as the chosen IDE. Google Web Toolkit is an extension of Java, which allows for increased accessibility due to Java's portability and cross-platform capabilities. Google Web Toolkit automatically translates Java code into JavaScript, HTML, and XML so that a user can access all of the content of the software as long as they have a JavaScript compatible browser. 2.1.1. Definition, Acronyms, and Abbreviations AJAX Acronym for Asynchronous JavaScript And XML that is used to create dynamic content on web pages.
Calocount A software application that functions as a food log and provides useful health tips. The application tracks monthly weight loss progress and graphs individual progress on a monthly basis. Eclipse An IDE, Integrated Development Environment, used for programming. Food-Log A record of an individual users meals on a daily basis. GWT Abbreviation for Google Web Toolkit. Google Web Toolkit A Java framework created and supported by Google that is used for writing Java code that is automatically converted into AJAX for dynamic web applications. Health Tips Nutrition and exercise tips provided to the user at random upon request. JavaScript A client-side scripting language that is used to add dynamic content and interactivity to web pages. RPC Google Web Toolkits method of communicating between the server and the client sides of a web application.

The application will utilize a graphical interface that includes a panel with several tabs for different functions of the software. Part of the interface will include: monthly progress reports including a graph of weight change, a food log, a weight log, and a tab for nutrition including health tips. 2.2.2. User Interfaces

2.2. Overall Description 2.2.1. Product Perspective

H N L

H N L

Methodology 3.1. Analysis 3.1.1. Use Case Model

C Team Use Case 1: Keep Food-Log Written By: Gabe Tafoya

Introduction: Keep Food-Log discusses the implementation and uses of keeping a daily food-log for a user's daily meals. Actors: Primary Actor: User, person who logs into the website

H N L Supporting Actor(s): Database used for storing food-log information Pre-Conditions: -User has account on the website -User is logged-in and authenticated
Post-Conditions: -User entered information into food-log fields -Food-log associated with current user -Food-log saved -Food-log stored in database for further analysis Basic Flow: 1. User arrives at website 2. User logs into the website with their user information 3. User proceeds to food-log tab 4. User enters last meal entered into food-log 5. System saves food-log to database for further analysis Alternative Flow(s): 1. User wants to enter more than one meal into food-log: a. Repeat steps 4 through 5 of Basic Flow. Special Requirements: Google Web Toolkit supported by user's browser Google Web Toolkit plug-in installed on user's browser User has access to the internet Use Case Relationships: Keep Food-Log is dependent upon System Log-In.

C Team Use Case 2: Keep Weight-Log Written By: Gabe Tafoya

Introduction: Keep Weight-Log discusses the implementation and uses of keeping a daily weight log for a user. Actors: Primary Actor: User, person who logs into the website Supporting Actor(s): Database used for storing weight-log information Pre-Conditions: -User has account on the website -User is logged-in and authenticated Post-Conditions: -User entered information into weight-log field -Weight-log is associated with current user -Weight-log is saved -Weight-log is stored in database for further analysis Basic Flow: 1. User arrives at website

2. User logs into the website with their user information 3. User proceeds to weight-log tab 4. User enters current weight 5. System saves weight-log to database for further analysis Alternative Flow(s): 1. User wants to enter more than one weight into weight-log: a. Repeat steps 4 through 5 of Basic Flow. Special Requirements: -Google Web Toolkit supported by user's browser -Google Web Toolkit plug-in installed on user's browser -User has access to the internet Use Case Relationships: Keep Weight-Log is dependent upon System Log-In.

H N L

C Team Use Case 3: Graph Weight Loss Written By: Gabe Tafoya
Introduction: Graph Weight Loss discusses the implementation of graphing weight loss data for a user. Actors: Primary Actor: User, person who logs into the website Supporting Actor(s): Database used for storing weight-log information Pre-Conditions: User has account on the website User is logged-in and authenticated User has entered previous weight-log information for tracking progress Post-Conditions: -Weight-log read from database -Weight loss progress graphed Basic Flow: 1. User arrives at website 2. User logs into the website with their user information 3. User proceeds to progress tab 4. Weight-log is read from database 5. System graphs user weight loss progress Alternative Flow(s): 1. User has no previous weight-log data: a. Print error message to indicate that there is no weight-log data. 2. Weight-log data cannot be read from database: b. Print error message to indicate that the data cannot be read. Special Requirements: -Google Web Toolkit supported by user's browser -Google Web Toolkit plug-in installed on user's browser

-User has access to the internet

H N L

Use Case Relationships: Graph Weight Loss is dependent upon Keep Weight-Log and System Log-In.

C Team Use Case 4: Provide Health Tips Written By: Gabe Tafoya
Introduction: Provide Health Tips discusses the process of retrieving random health tips for users from a database. Actors: Primary Actor: User, person who logs into the website Supporting Actor(s): Database used for storing user log-in information Pre-Conditions: -Health tips stored in database -User is logged-in and authenticated Post-Conditions: -None Basic Flow: 1. User arrives at website 2. User logs into the website with their user information 3. User proceeds to nutrition tab 4. User requests tips from the system 5. System retrieves health tips from database 6. System displays health tips to user Alternative Flow(s): 1. Health tips cannot be read from database: a. Print error message that database access failed b. Repeat steps 4-6 of Basic Flow. Special Requirements: Google Web Toolkit supported by user's browser Google Web Toolkit plug-in installed on user's browser User has access to the internet Use Case Relationships: None

C Team Use Case 5: System Log-In Written By: Gabe Tafoya

Introduction: System Log-In discusses the implementation of a user logging-in to the website. Actors: Primary Actor: User, person who logs into the website

H N L Supporting Actor(s): Database used for storing user log-in information Pre-Conditions: -User has account on the website
Post-Conditions: -User log-in information read from database -User logged-in to the website Basic Flow: 1. User arrives at website 2. User enters log-in information 3. Log-in information checked against database 4. System authenticates user Alternative Flow(s): 1. User does not have account on the website: a. Print message that user does not have an account b. See "New User Registration". 2. User enters incorrect log-in information: a. Print error message to indicate invalid log-in information. b. Repeat steps 2-4 of Basic Flow. Special Requirements: -Google Web Toolkit supported by user's browser -Google Web Toolkit plug-in installed on user's browser -User has access to the internet Use Case Relationships: System Log-In is dependent upon New User Registration.

C Team Use Case 6: New User Registration Written By: Gabe Tafoya
Introduction: New User Registration discusses the implementation of registering a new user on the website. Actors: Primary Actor: User, person who logs into the website Supporting Actor(s): Database used for storing user log-in information Pre-Conditions: -None Post-Conditions: -User information stored in database Basic Flow:

1. User arrives at website 2. User proceeds to new user registration 3. User enters information into registration fields 4. System stores information in database Alternative Flow(s): 1. User log-in information already exists: a. Print message that user log-in information is invalid b. Repeat steps 3-4 of Basic Flow. 2. User enters invalid information: a. Print error message to indicate invalid information. b. Repeat steps 3-4 of Basic Flow. 3. User does not enter all required information: a. Print error message to indicate missing information. b. Repeat steps 3-4 of Basic Flow. Special Requirements: -Google Web Toolkit supported by user's browser -Google Web Toolkit plug-in installed on user's browser -User has access to the internet Use Case Relationships: None

H N L

3.1.2 Use Case Diagrams

H N L

3.1.3. Analysis Model 3.1.3.1. Analysis Class

H N L

H N L

3.2. Design 3.2.1. Design Class

H N L

H N L

H N L

We were all GWT beginners in our group, the only one who had experience with this was Jared. We have all learned a lot on how to make RPC and Ajax calls to transfer data from the server to the client. We conclude that the following project is very user friendly, fast, and effective. We hope to make this code available online in the future. We had issues dealing with our schedule due to difficulty with emails and authenticating users with their own personal Google Calendar, as well as out progress chart. So that is still a work in progress. We hope to use this software in a professional setting one day, we also plan to improve some more weight loss features and add strength to our methods and design patterns.

4.

Conclusion and Future scope

http://www.eclipse.org/downloads/ http://code.google.com/eclipse/docs/download.html http://www.objectaid.com/ http://www.rubiconred.com/blog/gwt/ http://code.google.com/p/gwt-cal/wiki/Introduction?tm=6 http://www.zackgrossbart.com/hackito/antiptrn-gwt/ http://code.google.com/webtoolkit/ http://zion.nmhu.edu/tahani/courses/webprog/notes/gwt/ http://en.wikipedia.org/wiki/Learning_curve http://en.wikipedia.org/wiki/Guillemets http://agile.csc.ncsu.edu/SEMaterials/tutorials/import_export/ http://zion.nmhu.edu/tahani/courses/webprog/video/deploy-gwt-project-on-cypress/deploy-gwtproject-on-cypress.html http://groups.google.com/group/Google-WebToolkit/browse_thread/thread/9950a66ed15ced22

5.

Bibliography

 http://www.mysql.com/downloads/ http://google-webtoolkit.googlecode.com/svn/javadoc/1.4/com/google/gwt/user/client/Timer.html http://stackoverflow.com/questions/2256494/how-to-reload-web-page-in-gwt http://www.mysql.com/downloads/connector/j/ http://zion.nmhu.edu/tahani/courses/webprog/video/tomcat_setup/tomcat_setup.html http://zion.nmhu.edu/tahani/courses/webprog/video/webserver-port_number/webserverport_number.html

H N L

H N L