Online Dietician
Overview
The application is a Food/Menu request
system
which will enable users to find different food
values
as per their health
goals
and body type. The user can
receivevaluable information by selecting the food items and quantity, and access this information via text message.
Users can get
dietary suggestions on their mobile phones
as per their
requests.
Calories calculator allows them to calculate the actual calories in each food.
The application can be divided into the
following two subsystems:
- Presentation Layer
- Administrative Subsystem
The Presentation Layer
will allow users to register themselves and send their request for
calorie
information via text messages. Users can also track
their dietary choices and check their daily caloric intake. Healthy alternatives are available by selecting specific food preparations, and consulting the healthy lifestyle suggestions and recommendations found on the website.
The Administrative Subsystem
will allow the administrator of the portal to manage various aspects of the website, including managing users, food/menu, categories, request messages, and other content of the website. Administrative subsystem will also enable administrators to generate various reports to analyze usage of the website.
Key Requirements
The business requirement of the project was to develop an enterprise application “Telephone Food System” for the users who are interested in suggestions for specific diets, have weight management targets, or wish to access suggested food menus & calorie counts. Software also allows users to receive health check reminders, lab results notification and weight management guidance.
Technology Used
- ASP.Net
- C#
- MS SQL 2005
- XML
- SMS Gateway
- Compact Framework 2.0
Key Features
- Calorie Calculator
- Healthy food menu
- Request for consultancy
- Special diet requests
- An alert message on patient’s mobile phone
-
Track by
customer, request & other details.
- Detailed reporting
- Searchable database with very high end presentation
- Easy manageable for end-user and administrator
- Email notifications whenever possible to users
Challenges
- HIPPA Compliance
- Encryption of user’s data in the database
- Alerts messages on user’s mobile phone
- Development and testing on mobile device
- SMS gateway integration
Our Role
We follow the basic rooted mantras of software engineering practices - Analysis, Planning, Design, Development, Testing and Deployment.
Define: -
First is to define detailed scope of the requirements. This is done through a detailed study by the project manager to know the requirements. This process starts even before the project is awarded to us as our estimates are based on the amount of work involved and technological challenges. To estimate these we keenly study the project and the application scenario in real world before giving a quote
Plan and design: -
Once the project is awarded to us, a SRS (Software Requirements Specifications), Prototype with supporting High Level Designs (HLD), User Interface, Class Diagram and Database Diagrams are prepared. These design documents and the prototype are sent to clients for approval.
Develop: -
Upon approval, we start coding. All our codes are well commented and follow naming conventions. We have a well defined multi-tier architecture and each developer adheres to it.
Test: -
Testing phase begins with the planning. As soon as HLD is frozen, we prepare test plans and cases. Application is tested parallel to development making sure that there are no errors. Once the development is completed, the application is tested from scratch to make sure all modules are well integrated.
Debug: -
The testing results are then converted in actions for debugging and
resolving any concerns.
Once all the bugs are fixed by the developers
the quality team re-examines the software and verifies the debugging.
This process continues until all bugs are fixed.
Deployment: -
The project leader reviews the application and makes sure that the application fulfils the Service Level Agreement (SLA) and is in line with other functional and
non-functional
requirements. Upon
approval, the
application is deployed to the production server.