Food Delivery Mobile App

Proposal

Version 1.0

For

World Wellness

No. 21, Jalan PJS 5/28B,

Petaling Jaya Commercial Centre (PJCC),
46150, Petaling Jaya, Selangor Malaysia.

1
 Document History

Prepared By: Reviewed By: Approved By: Effective

Version Reason of Change
Date: Date: Date: Date:
Siti Fadilah Rakesh Roushan
1.0 Initial Creation Nirbhay Kumar 21-Dec-2019
21-Dec-2019 21-Dec-2019
19-Dec-2019

This document is the property of SMD Webtech (M) Sdn Bhd. The information contained herein is PRIVATE & CONFIDENTIAL. Neither
the whole document, nor any part can be reproduced, disclosed to other parties, nor used for purposes other than for which it has
been supplied unless prior written permission is obtained from SMD Webtech (M) Sdn Bhd.

Page 2 of 33

2
 Table of Contents

1 EXECUTIVE SUMMARY…............................................................................................................... 5
2 BUSINESS PROPOSAL…................................................................................................................ 6
2.1 Features …........................................................................................................................... 6
2.1.1 Content Management and Content Publishing ….................................................................. 6
2.1.2 Admin Analytical Dashboard …............................................................................................ 6
2.2 Key Users Roles …................................................................................................................ 7
2.3 UI/UX Design ….................................................................................................................... 8
2.3.1 Emerging Visual and UX Design Trends …......................................................................... 10
2.3.2 Emerging Web & Mobile Technology Trends ….................................................................. 11
2.3.3 Approach ….................................................................................................................... 12
3 IDEATION FOR FUTURE EXPANSION…........................................................................................ 14
3.1.1 Phase II – Dynamic Visualization, Virtual Assistance and Outreach Program ….................... 14
3.1.2 Phase III – Business Process Automation …...................................................................... 15
4 TECHNICAL PROPOSAL…............................................................................................................ 16
4.1 Digital Experience Admin Platform: Laravel …......................................................................... 16
4.1.1 Background …................................................................................................................. 17
4.1.2 Platform Key features ….................................................................................................. 17
4.1.3 User Account Management …........................................................................................... 17
4.1.4 System Architecture …..................................................................................................... 18
4.2 Server Hosting …................................................................................................................ 19
5 PROJECT AND VENDORS REQUIREMENTS …................................................................................ 20
5.1 Project Scope ….................................................................................................................. 20
5.2 Project Management and Governance …............................................................................... 20
5.3 Delivery and Methodology …................................................................................................ 21
5.4 Project Services …............................................................................................................... 21
5.4.1 Requirements Gathering and Analysis …........................................................................... 21
5.4.2 Prototyping and Development …...................................................................................... 22
5.4.2.1 Design …................................................................................................................. 22
5.4.2.2 Development …....................................................................................................... 22
5.4.3 SIT, UAT and Remediation Works …................................................................................. 22
5.4.4 Training …...................................................................................................................... 23
5.4.5 Deployment and Go-Live Switch-Over …........................................................................... 23
5.4.6 Warranty Support …........................................................................................................ 23
5.5 Quality Assurance Management…........................................................................................ 23
5.5.1 Quality Assurance Methodologies ….................................................................................. 24
5.5.2 Bug Life Cycle …............................................................................................................. 25
5.5.3 Security Testing …........................................................................................................... 25
5.5.4 Code Review …............................................................................................................... 26
5.6 Risk Assessment ….............................................................................................................. 27

3
5.7 Project Assumptions …........................................................................................................ 28
5.8 Project Organization …........................................................................................................ 29
5.8.1 Team Structure …........................................................................................................... 29
5.8.2 Roles and Responsibilities …............................................................................................ 30
5.9 Project Timeline ….............................................................................................................. 32
5.10 Manage Services – Support and Maintenance Services …....................................................... 33
5.11 Release Management …...................................................................................................... 33
5.11.1 Application ….............................................................................................................. 33
6 COMMERCIAL PROPOSAL …........................................................................................................ 34
6.1 Cost …............................................................................................................................... 34
6.2 Payment Schedule …........................................................................................................... 34
6.2.1 Project Implementation Services …................................................................................... 34
6.2.2 Hosting …....................................................................................................................... 34
6.2.3 Annual Application Maintenance Services …...................................................................... 34
6.3 Payment Terms …............................................................................................................... 34
6.4 Sales and Services Tax (SST) …........................................................................................... 34
6.5 Assumptions …................................................................................................................... 35
7 AGREEMENT & CONFIRMATION.................................................................................................. 35

4
1 EXECUTIVE SUMMARY
This proposal intended to present the implementation strategy approach for the below:
• Rebrand World Wellness image towards public
• Implementation of Mobile App infrastructure platform using IONIC
• Modernize World Wellness Mobile App content strategies in terms of
o App performance
o App analytic
o User Experience on Design works
o Content branding and promotions
o User Friendly Mobile App

In this project, SMD Webtech (M) Sdn Bhd will play a role of project management, implementation and
system integration. SMD Webtech (M) Sdn Bhd will use PHP-Laravel for admin infrastructure technologies.

We provide IT solutions and services in Enterprise Content Management, Business Process Automation,
Application Development & Maintenance across various industries. Our engagement exposure spreads from
domestic enterprises to global businesses.

SMD Webtech (M) Sdn Bhd will establish a digital content journey to conceptualize, design, develop and
implement a unique user experience on the Mobile App & Admin Portal.

5
2 BUSINESS PROPOSAL
2.1 Features
2.1.1 Content Management and Content Publishing
In this project, the merging of our technical software team and UI/UX team to rebrand and setup the
design framework for the new Food Delivery Mobile App Backend Admin in PHP-Laravel platform. PHP-
Laravel serves as a CMS (Content Management System) which streamlines the creation, publishing and
management of content on Food Delivery Mobile App. User has the ownership of the content, which means
user has the ability to post new content, update current content, and archive outdated content from the
portal. In another words, content requires frequent updates can be easily handled by World Wellness
users in future. Such as:
• News & Announcement
• Latest Product
• Categories
• Store Location
• Manufacturers
• Product Variant
• Stock Management
• Order Summary
• Departments info, organization hierarchy and contact information

2.1.2 Admin Analytical Dashboard

To better understand the visitors of the Mobile App, a simple profiling will be introduced, to collect personal
data such as gender, age range and location for analysis purposes. These personal data can be collected
via quick questionnaire, or social media logins. With this information available, we can show browsing
guides or suggest related contents to the site visitors.
A traffic analysis dashboard will be implemented in the new Food Delivery Admin portal, which can assist
World Wellness Admins to identify the trends and traffic in the Food delivery Mobile App. Information on
number of visitors, traffic sources, user segments and navigation behavior will help World Wellness to
evaluate the type of information the visitors are engaged to and interested in.

6
2.2 Key Users Roles
Food Delivery Mobile App Admin Portal built in PHP-Laravel will have 2 major user roles:
• Content Contributor
o For content owner such as HR and marketing team to contribute the Mobile App content
(such as news & announcement, vacancies, project details, training details etc) in real-time,
with intuitive interfaces and drag-and-drop content authoring and layout capabilities
designed for the non-technical users
• Administrator
o Analyzes visitor traffic, and measures website effectiveness.
o To perform analysis and fine tuning on the targeting segments
o Manage and assign content contributors

2.3 UI/UX Design

The design solution shall encompass the delivery of a brand-new digital user experience across all digital
channels (such as web / mobile and tablets).
7
For the customer, the outcome will be an easy to navigate, read, find, transact, and apply intuitive design
which is accessible from various digital channels – desktop, tablets and smartphones. The digital channels
will provide a superior user experience that is available anytime, anywhere; a source of customer acquisition
and activation, with clear call-to-actions. Superior user experience could be, but not necessarily limited to,
shortened or simplified processes and steps.

SMD Webtech (M) Sdn Bhd will work with the product managers and stakeholders to ensure a timely
delivery and whilst meeting all business requirements.

8
Expected design outcomes:

• Fully responsive design across all modern devices

Work with the team to arrive at a responsive design strategy/approach including how the content will
behave on different screen sizes. The minimum and maximum screen resolutions will be provided. The
design should start with the small screen and then progressive scale up to larger screens and enhance the
experience.

• Simplified user journeys

Relook at the existing user flows and find opportunities to reduce all possible frictions and the time taken
to complete the journeys.

• Retain our conceptual IA/Navigation model

We would like to continue to use the successful high level IA (Information Architecture). Most (if not all)
functions in scope should be categorized under these existing categories.

• Align with World Wellness Brand guidelines.

For things like the main navigation bar and the way information in presented should all align to the global
World Wellness Brand guidelines.

• Scalability and reusability of designs

We need the designs to scale up and adapt for additional new products and features in the near future.

9
2.3.1 Emerging Visual and UX Design Trends

10
2.3.2 Emerging Web & Mobile Technology Trends

11
2.3.3 Approach
We aim to put users at the center of everything and create brand experience, which connects, engages,
promotes dialogue and delivers tangible benefits to World Wellness. The success of this project lies in
agile methodology. Our think, create, release and engage strategy will be the pillars of this engagement
blending various components for a holistic solution

As explained in the above diagram we will set clear objective for business, will understand the needs and
wants of the end customer alongside ensuring World Wellness brand is highly reflected in the work we
produce.

We will follow agile methodology and refined experience to ensure the shortest design cycle with quality
outcome. We will provide user journeys for defined platforms to demonstrate the treatment and
adaptability on different platforms.

Guiding principles for the Project

We have been working in past and keeping up with the pace and need of users that eliminates the need
of designing multiple apps for different platforms. Responsive Design is the approach that suggests that
design and development should respond to the user’s behavior and environment based on screen size,
platform and orientation. As the user switches from their Tablets to Mobile, the application should
automatically switch to accommodate for resolution, image size and scripting abilities. In other words, the
application should have the technology to automatically respond to the user’s preferences. This would
eliminate the need for a different design and development phase for each new gadget on the market.

12
We have identified high-level principles for the project as below.

For this project, we will create a design, which portrays the dominant following terms:

• Simplicity
• Minimalism
• Clear Layouts
• App-style Interfaces
• Simplification of UI, and
• Focusing on typography

Design principals will also help to enforce that we should be adding personal touches wherever possible
and creating an impact through typography.

While working on user journey’s we will look through some signature interactions with the choreography
definition. At all these thought processes user will be at the heart of design thinking.

As a part of initial workshop we will identify all basic flows and will create the layout structure to be followed
across the similar user journeys. The separate layout will be created for tablet and smartphones to ensure
the client is present with the information in most effective manner.

Various alterations will be defined for master layout – even for landscape vs. portrait.

Since we will be dealing with customer data and real money we will work very closely to ensure how the
data is shown on the various screen sizes and switch from the portrait to landscape. We will work with the
client project team to define the content structure long with the flexible adjusting layouts using responsive
web design techniques.

We will possibly categorize the content type and create the rules for content display according to devices.

13
3 IDEATIONS FOR FUTURE EXPANSION

3.1.1 Phase II – Dynamic Visualization, Virtual Assistance and Outreach Program

Dynamic Visualization
Interactive content rich dashboard, where the portal admins can filter, drill down, slice and dice the data
collected according to needs via the dynamic dashboard.

14
Outreach Program
To engage with Entrepreneur with e-Campaign program, we can extend the Food Delivery App to create
space for Entrepreneur to advertise, perform business matching and promotion via World Wellness.

To outreach to public users, the site visitors can give comments, suggestions and feedbacks to World
Wellness via the App.

15
4 TECHNICAL PROPOSAL
4.1 Digital Experience Portal Platform: PHP-Laravel

4.1.1 Background
Laravel is a web application framework with expressive, elegant syntax. We’ve already laid the foundation
— freeing you to create without sweating the small things.

More info on Laravel can be found at https://laravel.com

16
4.1.2 Platform Key features
The key features of PHP-Laravel below can be utilized to create World Wellness Admin Panel for Mobile
App in Phase I, and for future expansion for subsequent phases.

• Content Publishing
o User friendly What-You-See-Is-What-You-Get (WYSIWYG) content
authoring and designing tools for World Wellness team.
o Approval workflow for content authorization before publishing to productive World
Wellness Admin Panel & Mobile App

• Engage
o Demographic feature for marketers to gather and evaluate information about website
visitors, define segments, and create personalized recommendations and promotions.
o Sophisticated customer-segment-based targeting, personalizing & promotions, to display
the recommended contents to end user.
o Supports implicit (without the need of the visitor’s decision, such as geo-location, time,
search engine referrals for keywords) and / or explicit (visitor’s data that the visitor has
decided to share with, such as age, gender, religion, etc) segmentation

• Multi Device
o Centralized management and delivery of Websites to desktop browser, and various types
of mobile device types, including iPhone, iPad, Android phones
o Support optimal viewing experience with responsive design.

4.1.3 User Account Management

Laravel admin portal connects to an authentication system through the Directory Services API. This API
provides out-of-the-box support for two types of authentication systems: Native Authentication System,
and External Directory Server (LDAP). Hence user accounts can be created through Laravel native user
manager, or through external user managers such as LDAP, provided the LDAP services is accessible for
integration.

Once users are created and configured, they must be associated, by means of roles, with the sites they are
to work in.

17
4.1.4 System Architecture
At its base, Laravel is a web application framework with
expressive, elegant syntax. We’ve already laid the
foundation — freeing you to create without sweating
the small things.

Laravel is a web application framework with

expressive, elegant syntax. We believe development
must be an enjoyable and creative experience to be
truly fulfilling. Laravel attempts to take the pain out of
development by easing common tasks used in most
web projects.

On the front-end, Laravel can jive with popular front-

end technologies such as:
• Bootstrap
• SaSS
• JavaScript 2019
• jQuery (included)
• Angular 4
• Ionic

18
4.2 Server Hosting
SMD Webtech (M) Sdn Bhd will work with our hosting partner: AMAZON to provide the hosting services.

Virtual Private Server Minimum Specification:

• 200 GB SSD Disk Space
• 16 GB Memory
• 14 vCPU
• 1 Dedicated IP
• 16 TB Monthly Data Transfer
• 100 Mbps Bandwidth
• Free SSL/HTTPS
• Tomcat / WebLogic
• MySQL Database

19
 5 PROJECT AND VENDORS REQUIREMENTS
5.1 Project Scope
SMD Webtech (M) Sdn Bhd is responsible for define, design, development, host and maintain Food Delivery
Mobile App that meets all the requirements and functionalities specified by our Business Analyst (B.A). The
scope of work includes

• Implementation of infrastructure platform

• Developing new content
• Designing Mobile App content framework and structure (Design stage)
• Hosting
• Maintenance and Support – Managed Services

Customer Application features:

• Restaurant list nearby with open or close status

• Restaurant list by user rating
• Restaurant list on map
• Sort restaurant list by radius
• Sort restaurant list by City
• Search restaurant
• Search restaurant list by cuisine type
• restaurant information,
• Restaurant Name,
• Restaurant Image
• Restaurant ratings by user
• Restaurant address
• Restaurant contact number
• Opening and closing time
• Food type served by restaurant
• Map location
• Home delivery time
• delivery type: Cash on delivery or Card on delivery
• Restaurant description
• Set as favorite restaurant
• Categorized restaurant menu
• Add to cart menu items
• Place order from cart
• Also change quantity from cart
• Use google map to share your location while place order, you don’t need to type address.
• but you can edit location retrieve from google map
• Complete detail of order
• Order time & delivery time
• Order amount & restaurant detail
• Ordered item details
• Total 5 Order status
• Add Review to restaurant
• User order history.
• Order detail with status & item details
• Favorite list of restaurants
• Share app.
• Terms & Condition
• About us page
• Register user with profile picture
• User login
• Facebook login
• Google plus login

20
• Push notification with firebase
• Order status push notification

Delivery Boy Features:

• Login from Delivery app

• Set presence
• Check new Orders
• Order History
• Order detail with name, address, contact no & item detail
• Call customer or show route on map
• Picked order & deliver order
• Get notified on new order assigned

Admin Panel Features:

• Check list of restaurants – Add, Edit,

• Add cuisine type
• Check Menu
• Add New city
• Check no of orders for restaurant
• Moderate app user
• Moderate User reviews
• Setup push notification from admin
• send push notification

Restaurant owner admin features:

• Separate admin panel for restaurant owner

• Add restaurant details
• add menu and menu items
• Check new orders and order details
• Add delivery boy
• Assign order to delivery boy
• on dashboard check order report

5.2 Project Management and Governance

Since year 2012, We have defined a set of policy as below for each process area as below.
• Organization Process Management
• Organization Training
• Project Management
• Risk Management
• Supplier Agreement Management
• Requirements Development & Management
• Technical Analysis & Design, Technical Development, and Release Management
• Validation
• Verification

21
 • Configuration Management and Change Management
• Decision Analysis and Resolution
• Measurement and Analysis
• Product and Process Quality Assurance

5.3 Delivery and Methodology

The delivery of the project shall be based on a hybrid of both Prototyping and Agile development strategy.

The Prototyping Model is a systems development method (SDM) in which a prototype (an early approximation
of a final system or product) is built, tested, and then reworked as necessary until an acceptable prototype is
finally achieved from which the complete system or product can now be developed. This model works best in
scenarios where not all the project requirements are known in detail ahead of time. It is an iterative, trial-and-
error process that takes place between the developers and the users.

22
5.4 Project Services
5.4.1 Requirements Gathering and Analysis

Task

(a) Conduct user requirements gathering workshops

(b) Identify and document all business requirements and functionalities to assist users in performing
their duties

(c) Analyse and optimise the business and functional requirements

(d) Review and assess the functionalities and technical requirements, including suggestion of optimised
options for both functionalities and technical requirements.

(e) Prepare and develop the documentations as set out in the Deliverables of Requirements Analysis.

• Business Requirement Specification (BRS)

• Requirements Traceability Matrix (RTM)

5.4.2 Prototyping and Development

5.4.2.1 Design

Task
(a) Conduct system design workshops
(b) Identify and document the solution’s integration, interfaces and compatibility with other systems
which the solution is required to integrate
(c) Identify all reusable component/services provided and used by the solution
(d) Develop the documentation as set out in the Deliverables of Design.
- Software Design Specification

5.4.2.2 Development

Task
(a) Develop the relevant modules and interface
- Page / Portlet / Form Creation
- Search
(b) Ensure compliance to security control requirements throughout the system development process;
(c) Ensure the solution is in line with the design specifications;
(d) Ensure the workability within the Programs and interoperability between Programs and Developed
Programs;

5.4.3 SIT, UAT and Remediation Works

Task
(a) Prepare and develop the documentations as set out in the Deliverables of Requirements Analysis.
23
 (i) Test plan, approach and strategy
(ii) Test case and test scripts (SIT and UAT)

(e) Perform system integration test on the solution components.

(i) Execute system integration test and user acceptance test
(ii) Evaluate test results and remediation works to meet expected solution quality
(a) Prepare the detailed test artefacts that contains but not limited to the following information:
(i) Test results, analysis and recommendation for defect / bug resolution
(ii) Evidence of test coverage level based on requirements matrix
(b) Coordination with SMD Webtech (M) Sdn Bhd Project Team throughout Test and Remediation
activities.
(c) Execute remediation works to resolve defects identified throughout CMS test processes including its
integration with other systems, to achieve acceptable threshold of passed test result

5.4.4 Training

Task

(a) Assess training infrastructure, facilities, equipment and training culture

(b) Define Training Facilities Requirements

(c) Prepare detailed Training Plan during UAT Stage
(d) Develop Training Materials
- Functional
- Technical
(e) Conduct Train the Trainer sessions based on the agreed session by SMD Webtech (M) Sdn Bhd
Project Team
- Functional
- Technical

5.4.5 Deployment and Go-Live Switch-Over

Task

(a) Execution of deployment and go-live works

(b) Documentation of:
(i) Deployment plan and checklist
(ii) Contingency plan if go-live is not successful
(c) Resolve issues during preparation and go-live activities system deployment planning

5.4.6 Warranty Support

Task

(a) Fix identified Level 3 Defects for the in-scope Applications

(b) Perform Root Cause Analysis (RCA) on Severity 1 and 2 defects for the in-scope Applications

5.5 Quality Assurance Management

Software and application development, managing data, in a secure, controlled environment is a top-level
objective. For this we made sure our processes are secure. Security is a requirement that must be included

24
within every phase of a system development life cycle. The Agile software development life cycle is followed for
the development model which is a combination of repetitive and incremental model of multiple processes. The
model 100% focuses on delivering a working software product that provides complete customer satisfaction and
adaptability.

5.5.1 Quality Assurance Methodologies

Methodologies are strategies and approaches used to test product to ensure it meets the purpose.
Following are the various functional and non-functional tests performed to ensure quality goals are achieved.

Functional Testing

Unit Testing System Integration Testing Acceptance Testing

Non-Functional Testing

Security Testing Performance & Load Testing Compatibility Testing

5.5.2 Bug Life Cycle

5.5.3 Security Testing

A pass in security testing is a must for certification to UAT. Security test planning and identification for a feature
begins with the feature discussion and detailing. Test cases are developed with this goal in mind and have to
be passed.
We will ensure that the design and implementation of the application shall not be affected by at least the
following vulnerabilities:

Vulnerability Counter-measure

• Input sanitization: Implement whitelisting approach at server side

1 Injection for what all can be accepted.
• Use of safe API’s and parametrized queries.

25
 • Use of multifactor authentication
• Session isolation
2 Broken Authentication
• Idle session timeouts
• Using secured cookies

• Encrypt all data in transit and at rest.

• Use secure protocols and algorithms.
3 Sensitive data exposure
• Disable caching of responses with sensitive data. Hackers might
get the cached copies and steal the information from them.

• Avoid serialization of sensitive data

• Implement whitelisting approach at server side to prevent
XML External Entities
4 malicious XML upload.
(XXE)
• Use of WAF to detect and block XXE.
• Code review

• Invalidate tokens and cookies after logout.

• Forced login/logout after a password change.
5 Broken Access control
• Server-side resource restriction e.g. directories.
• Restrict access to all resources basis roles.

• Have a hardening process in place for both hardware and

Security
applications. Do ensure that defaults are changed.
6 misconfigurations
• Install only the required features from a framework.
• Review the security of the configurations at fixed intervals.

Cross Site Scripting

• Output encoding and escaping untrusted characters.
7 (XSS) • Enabling Content-Security-policy (CSP)

• 24x7 monitoring of application traffic and log analysis.

Insufficient logging and
10 • Effective Security Incident and response procedures to be in place
monitoring
and practice.

Best practices- technology driven

Best practices are prepared and followed within the team based on technology level at:
▪ Server side
▪ Client side

5.5.4 Code Review

For all important changes and bug fixes, Tech Lead/ Architect needs to review the code and give appropriate
comments.

26
5.6 Risk Assessment
The unpredictable and dynamic nature of software development poses numerous risks and challenges to
the organizations. We consider a project to be successful if it meets all three to the following requirements.
• Completed On-time
• Completed within budget
• Completed within required functionality
Based on our experience delivering numerous IT related projects throughout various industries, At this early
stage we could perceived that there are three main factors that might contribute to be the most riskiest for
this project.
• Unrealistic schedules and budget
• More functionality than required
• Continuing requirement changes

Below table indicate the risk assessment for this project.

ID Risk Event Probability Impact Mitigation / Response

• Ensure that the requirements

specifications have been internally
reviewed by all concerned parties and is
Time, cost and scope deviation to
internally agreed as complete and
1. be expected if the requirement
LOW HIGH feasible.
will not be finalized at project
• Agreed with customer that all issues not
kick-off.
clarified until project kick-off will be
treated as change requests with possible
impacts on time and cost.

Inadequate funding to complete • Re-scope project by focusing on time and

2. LOW HIGH
the project identified. resources.

• Increased collaboration and information

sharing on the external and internal team.
“Ad-Hoc” request for additional
• Agreed with customer that all issues not
3. features or module that not been LOW HIGH
clarified until project kick-off will be
identified during project kick-off.
treated as change requests with possible
impacts on time and cost.

27
5.7 Project Assumptions
The project assumptions are as follows
o Resource Assumptions
▪ SMD Webtech (M) Sdn Bhd have the necessary expertise to build and delivery the
proposed solution
▪ Management will ensure that project team members are available as needed to complete
project tasks and objectives.
▪ The Steering Committee and customers will participate in the timely execution of the
Project Plan
▪ Project team members will adhere to the Communications Plan.
▪ All project participants will abide by the guidelines identified within Project Plan
o Scope Assumptions
▪ The Project Plan may change as new information and issues are
revealed.
o Cost Assumptions
▪ Project is delivered timely without additional labours, extra services and indirect costs

The project dependencies are as follows

o Commitment of users in participating during requirement analysis and user acceptance test phase
in order not to delay the project plan.
o Flexibility of technology platform to cater all user requirements and needs (e.g. PHP-Laravel out
of the box features)

The project constraints are as follows

o Time
o Budget

28
5.8 Project Organization
Our Project Team is responsible for delivering this project in a way that meets your project goals and objectives.
Our team places a great deal of emphasis on strong project management, including excellent communication,
extensive planning, timely change management and a predictable overall outcome.

The key focus of the project committee will be to attend the biweekly project meeting and assist in advising if
the progress is up to par and what are the areas would both parties like the project group to improve upon.

5.8.1 Team Structure

29
5.8.2 Roles and Responsibilities

Roles Responsibilities

Project Director 1) Ensure that the appropriate resources are assigned to tasks, and that
resources are effectively utilized;
2) Monitor project’s financial status;
3) Manage project within budget limits;
4) Ensures integrity of project;
5) Provide overall direction and oversee operational aspects of the System
project; and
6) Function as point of escalation for project issues and resolutions.

Project Manager 1) Initiate the project;

2) Formulate a detailed project plan;
3) Communicate project parameters, policies and process;
4) Establish the workspace and project ecosystem;
5) Build the teams needed to complete the project;
6) Execute the project plan;
7) Monitor project progress;
8) Close the project; and

Solution Architect 1) Conduct architectural evaluation, design and analysis of solutions;

2) Responsible for the overall design of the application and mapping the
business requirements to systems/technical requirement;
3) Perform impact analysis of the architecture;
4) Add periodic review of the architecture over the change of business
requirements; and
5) Work closely with architecture team to assure compliance of blueprints
and architecture;

Business Analyst 1) Determine operational objectives by studying business functions;

gathering information; evaluating output requirements and formats;
2) Developing a clear understanding of all existing data requirements;
3) Analysing information from surveys and workshops, task analysis, and
business process description;
4) Compile Requirement Traceability Matrix and Business Requirement
Specification;
5) Supporting the development of training and implementation material;
and
6) Assisting with integration and acceptance testing.

Technical Team Leader 1) Provide technical advisory and assistance for the system development;
2) Review software coding method and standard; and
3) Coordinate/communicate with the development team for the
development works.

PHP Developer 1) Design, develop and maintain all aspects of Laravel related module;

30
 Roles Responsibilities

2) Develop Page and portlet; and

3) Perform unit test.

System Developer 1) Develop integration services program;

2) Develop reports, building and maintain reporting dashboards;
3) Perform unit test; and
4) Perform peer code review.

UX and UI Specialist 1) Create user personas and user journeys;

2) Illustrate design ideas using storyboards, process flows and sitemaps;
3) Develop UI mock-ups and prototypes that illustrate how the application
function and look like; and
4) Identify and troubleshoot UX problems.

Quality Assurance 1) Prepare Test Cases and Test Scripts;

Engineer
2) Conduct and perform quality review on system work products and
deliverables; and
3) Provide remediation recommendations on quality issues identified.

System Engineer 1) Developing, maintaining and supporting technical infrastructure,

hardware and system software components
2) Performing installation, maintenance and support of system
software/hardware and user support
3) Configuring, debugging and supporting multiple infrastructure
platforms.

31
5.9 Project Timeline

Milestone Estimated Efforts

Project Initiation and Planning 1 Week

Requirement Gathering and Analysis 10 weeks

Prototyping and Development

Test

Training 1 week

Production Go-live Preparation 1 week

Total 13 Weeks

• Note: Appstore can take up to 10 working days to make app Live

32
5.10 Manage Services - Support and Maintenance Services
The following services are covered in response to the specified areas:

Support hours • Business Day

o Normal Support Hours
o 9:30 am – 6:00 pm
o (Mon – Fri)
• Off Business Day/ Hours
o Standby support (On-call support)

Communication Channel • Help desk telephone support

• Email
Scope of Services • All application software, including but not limited to problem resolution,
bug fixes, and new versions
• Suggest improvements to the application and carry out the impact
analysis when necessary
• Performance tuning and optimization
• Availability management such as preventive maintenance and procedures
for daily health check
• Maintenance services to be carried out during non- business day
• Application product update if applicable
• Usage and technical advice which related activities due to infrastructure
maintenance
• Standby for any applications problems due to ad-hoc or planned business
operation
• Free development man-days to accommodate ad-hoc request for changes
to application.

5.11 Release Management

5.11.1 Application
Interim Release Scheduled Release
Description
Frequency Bi-weekly Bi-monthly
Condition Hotfix • Less critical bugs (Non show stopper
bugs)
• Enhancement

33
 6 COMMERCIAL PROPOSAL
6.1 Cost
The following details the total cost for the effort, as per the scope and implementation plan specified in the
scope of work above.

Description Amount (Exclusive SST)

Project Implementation Services – Phase I

RM 58,000.00
o Project Management Services
o Define, Design, Development, Testing & Deployment
• Professional Services
o Documentation
o Training
o Warranty: 90 days

*Annual Secure Cloud Hosting

RM 12,000.00
(RM 1000 x 12 months)
*SMS Charges (50000 SMS) RM 10,000.00

Google Map API (RM 600 x 12 Month) RM 7,200.00

Appstore Fee (Annual) RM 600.00
Google Play Store (One Time) RM 300.00
Payment Gateway Integration RM 2,500.00

Note: Item Marked in * is optional

6.2 Payment Schedule

6.2.1 Project Implementation Services
• 50% Upon signing of agreement
• 40% After UAT
• 10% After Making OnLive on Play Store & AppStore

6.2.2 Hosting
• 100% Upon signing of hosting agreement

6.3 Payment Terms

Payment period is within 10 days from the date of invoice.

6.4 Sales and Services Tax (SST)

The issued invoice shall be 6% inclusive of any tax, duty or charge which is imposed by the Government of
Malaysia pursuant to Malaysian law from the Commencement Date in respect of agreement if applicable as
imposed under the Sales and Services Tax Act.

34
6.5 Assumptions
The reimbursement of travelling expenses and allowances to Any of the Site is per diem basis.

7. Contract Terms & Condition

1. Contract is neither transferrable nor refundable during the development & yearly maintenance if any

2. General Suppor-8 x 5 support model, Working day Only. Response time: 4Hour.
(Dedicated- 24x7 Support subject to separate agreement)

3. Any third-party tools / API / Plugin / SMS Gateway Fee / Payment Gateway charge will be borne by
Customer.

4. SMD Webtech is not liable for loss of business or profit due to hardware or software related incidents.

Note* - Any additionally functionality, Onsite Support, Additional Training, Enhancement, Change Request and
customization are chargeable.

AGREEMENT & CONFIRMATION

By signing below, I/We agree to accept this proposal contract for World Wellness and any custom solution already
agreed upon with SMD Webtech (M) Sdn Bhd.

Software Provider: SMD Webtech (M) Sdn Bhd Company/Client : World Wellness

Signed by: Signed by:

Mr. Rakesh Roushan
(Sales – Project Director) Full Name:

(Director/CTO/CFO)

Sign: Sign:

………………………………………………… …………………………………………………………..



Date: Date:

35