We do things different, deliberately.
We believe there’s power in a long-term solution versus a short-term fix.
Healthy habits versus unrealistic expectations.
Overall well-being versus the amount you weigh.
Ours is a tailored approach rather than a one size fits all mentality.
We think food should be enjoyed. Not avoided.
Fresh and fabulous. Not frozen. Simple. Not overly complex.
The Challenge for The Fresh Diet (TFD) project was to streamline the business process for ERP and to make provisions to improve the current implementation with improved UI and workflows for performance optimization and operational excellence and to build on the improvements to cater for The Fresh Diet’s global expansion.
To achieve this, a detailed insight and understanding of The Fresh Diet’s current business process and implementation was required. Business Technologies team travelled to The Fresh Diet’s head office in Miami, USA to acquire the necessary domain knowledge and to discuss the underlying architecture for the new system in order to establish the improvements required for optimization. After gaining the required domain knowledge and familiarizing itself with the technical and operational workflows of The Fresh Diet, Business Technologies team returned to its base office in Lahore, Pakistan to kick-start the offshore development to revamp the existing application with an improved UI and optimize the existing workflows in the current system for efficiency and user friendliness. In addition to these improvements, the revamped application would also incorporate new functional requirements raised by various TFD departments such as Kitchen, Operations, Logistics, and Customer Services. Business Technologies technical team in collaboration with The Fresh Diet’s technical team finalized the application-architecture as well as the database for the revamped application.
In this approach proposed and used by The Fresh Diet technical team in its existing system, the architecture of the TFD Revamp Application would be an MVC (Model-View-Controller) architecture with View (Presentation layer) physically separate from the Model (Data Layer) and Controller (Business Logic Layer) as illustrated by the diagram below:
The PROS & CONS of the above architecture are as follows:
The Fresh Diet technical team insisted on using the MVC architecture in Approach 1 to be the architecture for the TFD revamp application because, despite its CONS, they were adamant on keeping the View physically separate from the Model and Controller.
The front end (TFD Website and client-side website) and member’s section were unchanged for the revamp stage. Thus, the features/functionality currently in the front end and member’s section were more or less the same with modifications to only those parts where necessary/required.
Functionality for handling the content and features used in front end and member’s section were added to their relative sections i.e., admin and member’s section. For example, gallery slider, pages content, testimonials, FAQ etc.to admin section and Profile Edit, Billing information, Food Profile update etc. to member’s section.
A Twitter Bootstrap Theme was setup for the back end (admin panel).
A. Member Login/Logout
B. Member Password Recovery Forms
C. Account Overview/Dashboard
D. Billing Management
E. Schedule & Day Meal Management
A. ACL Management (Module+ Controller+ Action based)
B. Employee Management
C. Department Management
D. Role Management
E. Resource Management
H. Tasks Management - Internal Ticketing System
I. Site Operations
J. Culinary and Kitchen Operations
L. API/Library Integration
N. CRON Jobs