0% found this document useful (0 votes)
26 views14 pages

Orca Share Media1603024649711 6723572700385554981

This document provides an overview of XXX's proposal for developing a mobile application for YYY's sales force automation. It outlines the project scope, architecture, delivery timeline, roles and costs. Key aspects include developing requirements with the client, designing UI/UX, implementing core functional modules for recruitment, learning, sales and more. It also introduces XXX, its mobile solutions expertise, and sample finance/insurance projects.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
26 views14 pages

Orca Share Media1603024649711 6723572700385554981

This document provides an overview of XXX's proposal for developing a mobile application for YYY's sales force automation. It outlines the project scope, architecture, delivery timeline, roles and costs. Key aspects include developing requirements with the client, designing UI/UX, implementing core functional modules for recruitment, learning, sales and more. It also introduces XXX, its mobile solutions expertise, and sample finance/insurance projects.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

YOUR ENTERPRISE SOFTWARE DEVELOPER

XXXs Proposal & Quotation

I. Introduction .......................................................................................................................................... 3
1. Purpose ............................................................................................................................................. 3
2. Project Scope..................................................................................................................................... 3
3. Assumption ....................................................................................................................................... 5
II. Architecture Overview .......................................................................................................................... 6
1. Mobile Architecture .......................................................................................................................... 6
2. Mobile Gateway ................................................................................................................................ 9
III. Delivery Timeline............................................................................................................................. 13
IV. Proposed Roles and Team Size ....................................................................................................... 13
V. Quotation ............................................................................................................................................ 14
VI. XXX Introduction ............................................................................................................................. 14
1. Company Overview ......................................................................................................................... 14
2. Why XXX? ........................................................................................................................................ 14
3. XXX Mobile Solutions ...................................................................................................................... 15
4. Sample Insurance/Finance Projects ................................................................................................ 15
5. UI/UX Design ................................................................................................................................... 16
6. Quality Foundation ......................................................................................................................... 17

XXX CONFIDENTIAL 2
XXX’s Proposal & Quotation

I. Introduction
1. Purpose
The purpose of this document is to describe XXX’s proposal for YYY SFA Mobile Application
project.

2. Project Scope
1. Business Analysis Activities

No Activity
1 Develop Project Requirements with Client
2 Define Business Requirement Document
- Project scope
- Assumptions and dependencies
- Functional requirements
+ Business Flows
+ Module Description
3 Transfer requirements to UI/UX Designer

2. UI/UX Design Activities

No Description
1 UI Design Effort
2 Wireframe Design Effort
3 Effort for Updating Wireframe/UI based on customer feedback
4 Effort for Reviewing/Checking UI during implementation phase
5 Effort for Communication (Q&A from the team during development phase) and
designing UI specification

3. Functional

No Module Description
Recruitment
1 Company Information Allow users to view information about HLV by many
dynamic formats (clip, infographic…), link to website,
fanpage
2 Career Orientation Show career information by dynamic formats (slide, clips or
combine using story telling)
Combine career presentation with lead gen
Connect with E-recruiment portal
3 Job Submission Register to become new FCs of HLV. They can login to the
system with their personal account to tracking the
application status
Learning Management System

XXX CONFIDENTIAL 3
XXX’s Proposal & Quotation

4 Learning Status Allow User to view current Learning status


5 Courses Allow User to view all available Courses and register to join
6 Exams Allow user to view all available exams and register to join.
They can also have a trial on an exam with explanation
7 Certificates Allow user to view their certificates and upload a new one
User Profile
8 Authentication and Allow user to active their account and login to system with
Authorization YYY account
9 User Info View all user information and update them if need
10 Recognition Help user to know current level and the next level
11 Sale Report Allow user to track their sale result.
Revenue report by day
Revenue estimated (basing on number of lead data)
12 Income Allow user to view their income status and its details
Notification
13 Notification Management Allow user to review all their notifications and remove
them
14 Push Notification Help user receive all latest information via Push
Notification
Customer Relationship Management
15 Customer Management User can add and view existing potential customers.
16 Customer Approach Plan Set goal and plan to contact/meet with customers
17 Customer Care Customer birthday information
Input/edit other information: wife/husband/son/daughter
information (if any), hobby...
Policy anniversary
Send eCard to customer
18 Notification Receive notifications related to customers
Claim Request
19 Claim Request Document Listing essential document (for claim)
20 Claim Request Status Claiming status (by policy)
Product Collateral
21 Product Information Show list of product and its information
22 Product Illustration Demonstrate the product using clip, story
Sale Presentation
23 Product Suggestion Allow sale can input customer info and receive a list of
suitable product
24 Product Presentation Allow to view a product details
25 Benefit Schedule Allow user to create a new Benefit Schedule or edit an
existing Benefit Schedule
Calendar and Meeting
26 Offline Meetings Allow user to create an offline meeting and send the
invitation. User can view their meeting in Calendar
27 Online Meetings Allow user to create an online meeting with zoom. They can
interact with trainer for Q&A
28 Calendar View personal Calendar
Online Payment
29 Payment Integration Integrate with current payment gateway of YYY

XXX CONFIDENTIAL 4
XXX’s Proposal & Quotation

30 Policy Payment Allow user pay for a Policy


Document Management System
31 Document Viewer Allow user to view documents in popular format like Clip,
PDF, and HTML
32 Document and Form Allow user to view Document and Form provided by Ad
team
33 FAQ Allow user to view frequently asked questions
34 Other Information Allow user to view other information from legal, OP,
instruction information, memo
35 Notification Alert user when there is a new information, document and
form
Live Chat
36 Live Chat Integration Integration with current Live Chat system
37 Live Chat View User can use this view to contact with dept for clarifying
concerns
38 Chat Bot Chat Bot Integration if have
OCR
39 OCR System Provide an OCR System to YYY to help user reduce their
effort on input data
40 Training Data Training model for text recognition
41 Integration Integration with Input form

3. Assumption
Language
The application mainly supports following languages
English
Korean
Vietnamese
The default language is English. YYY provides the translation for the others
API and Test Environment
For each in scope feature: all APIs and services consumed/used by the feature must be done and
ready for test and integration by YYY at least 2 weeks earlier before the feature is getting started to
implement. Any delay in providing the APIs and services by YYY will lead to the corresponding delay
to the delivery that XXX can waive any responsibility
Test Environments are ready before starting project
Hardware Support
The project is expected to be tested on following devices:
Android
o Google Pixel 3 (Android 9)
o Samsung Galaxy S9 plus (Android 9)
o Samsung Galaxy S8 (Android 9)
iOS
o iPhone 7 (iOS 12)
o iPhone 8 plus (iOS 12)
o iPhone X (iOS 12)

XXX CONFIDENTIAL 5
XXX’s Proposal & Quotation

All Hardwares which are used for testing project will be provided by YYY

II. Architecture Overview


The purpose of this software design is to provide a high-level description of the YYY SFA
Mobile App (or also known as FC Mobile App), providing insights into the structure and
design of each component.

1. Mobile Architecture

FC Mobile App is a mobile application built with Flutter Framework in modular architectures.
There are 7 main modules in the application:

User Management: Manage User info and their status. It also aims to recruit new
agents
Customer Relationship Management: Provide features related to Customer such as
Customer Management, Customer Approach Plan and Customer Care
Product and Sale: Demonstrate and provide in details for products
Policy and Claim: Policy Management and Claim Request
DMS: Provide a quick way to access all document, form and policy
Training: Provide a modern way to register training session and manage attendees
using latest technologies
Report: Provide visually and effective report of Sale result, Income and
Compensation.

XXX CONFIDENTIAL 6
XXX’s Proposal & Quotation

These modules are developed outside of the application and communicate with the
application only via defined entry-points.

This approach gains us several advantages:

Less dependencies: The modules are more independent from the application itself. Both
modules and the application can evolve independently as they only need to make sure the
“entry points” are compatible.
Independent development: Modules can now be developed by several development
teams and can be released with independent release cycles. It increases our productivity
and flexibility can include only high quality modules into the application.
Better testability and maintainability: all modules are now self-contained. They don’t
directly depend on each other, there is no need for stepping through other parts of the
app to do test one specific function. It not only makes tests simpler and faster, but also
make them more reliable and tests can no longer be broken due to bugs in other features.

Flutter Framework

Flutter is a free and open-source framework for building cross platform apps on Android and
iOS. It provides developers an easy way to build and deploy visually attractive, fast mobile
apps.

Why choose Flutter

One code for 2 platforms: Application on Android and iOS built with Flutter uses the
same code base, there is no need to develop for one system and repeat the process for
another. Apps made in Flutter work on both Android and iOS platform seamlessly.

XXX CONFIDENTIAL 7
XXX’s Proposal & Quotation

Less testing: Because of one code base, the developers write automation tests only once.
Hence, the QA process can be faster.
The same app UI/UX on both of Android and iOS systems: Flutter apps look as good
on the up-to-date operation system as they do on older versions. Since they have one
codebase, the apps look and behave similarly across Android and iOS, imitating their
native components.
Perfect for MVP: Flutter is an open-source that has the support of a larger community. It
helps to create app faster and solves most of the complicated tasks. Following the Widget
approach, it helps building apps with faster go-to-market and record time.

XXX CONFIDENTIAL 8
XXX’s Proposal & Quotation

2. Mobile Gateway

Mobile Gateway is totally secure SSL Web-Service portal being contained as a Docker image.
The Mobile Service is built with Spring Boot framework to provide RestFUL API to client. To protect
those RestFUL API, we leverage the Keycloak Solution with Oauth2 protocol.

XXX CONFIDENTIAL 9
XXX’s Proposal & Quotation

In the first step of on-boarding process, user can use their personal account to login to the system,
we use Firebase Authentication to help user easy to reuse any supported account such as Facebook,
Google and Github

This approach gives us a lot of benefits:

Mobile Service are secured with standard protocols and best practices provided by Spring
Framework and Keycloak
Easy to engage with new service as we can leverage Keycloak SSO feature
Quickly support new Social Account with Firebase Authentication
Highly maintainable and testable

Spring Boot

An open source Java -based framework used to create a micro Service. It is developed by Pivotal
Team and is used to build stand-alone and production ready spring applications.
It provides a good platform for Java developers to develop a stand-alone and production-grade
spring application that you can just run. You can get started with minimum configurations
without the need for an entire Spring configuration setup.

Benefits:

● Easy to understand and develop spring applications


● Increases productivity
● Reduces the development time

Keycloak

Keycloak is an Open Source Identity and Access Management solution for advanced
applications and services. Keycloak offers everything that a sophisticated user management
tool needs – without having to log on repeatedly with every login and into every system – as
well as system security, social logins support for mobile apps.

XXX CONFIDENTIAL 10
XXX’s Proposal & Quotation

Single Sign-On

2-factor Standard
authentication Keycloak Protocol

Social login

Single Sign-on is a property of access control of multiple related software system. Allowing
users to remember and manage less passwords and username for each application.
Standard Protocols: Provide supports for many standard protocols like OAuth2, OpenID,
and SAML. It helps us increase the security and reduce the maintenance cost
Social login: Social login allows users to access websites using their existing social
account IDs, such as Facebook, Twitter, and LinkedIn. It is not only to enhance user’s
experience on our application but also to allows us to gather more accurate data,
including verified email addresses, age, gender, etc…
2-factor authentication allows us to add an extra layer of protection for user accounts
that significantly decreases the risk of unauthorized access.

Firebase Authentication

Firebase Authentication provide a secure authentication systems to improve the sign-in and
onboarding experience of end users. It provides an end-to-end identity solution, supporting
email and password accounts, phone auth, and Google, Twitter, Facebook, and Github login,
and more.

XXX CONFIDENTIAL 11
XXX’s Proposal & Quotation

Benefit:

Easy sign-in with any platform


Flexible, drop-in UI
Comprehensive Security
Fast Implementation

XXX CONFIDENTIAL 12
XXX’s Proposal & Quotation

III. Delivery Timeline


Assuming the project will start from November 2020 early. In case of any delay to the starting day,
the timeline below has to be changed/updated accordingly.

Furthermore, as per the assumption, the timeline below would be changed/updated in case of any
delay in providing APIs and services by YYY for the in scope features.

Phase/Month Jan-2021 March-2021 Jun-2021


Recruitment User Profile CRM
LMS Notification Product Collateral
Phase 1
Sale Presentation
Live Chat
Phase/Month Aug-2021 Nov-2021
Policy Management DMS
Claim Request OCR
Phase 2
Calendar and Meeting
Online Payment

IV. Proposed Roles and Team Size


We would like to recommend the ODC model for this project so as to have a long term development
and cost effective. Here are the team size and structure that are committed for this project.

Period Team Remark


Phase 1 10 members in total: Establish core framework for the whole
(Duration: 8 - 1 Project Manager (PM) mobile system ready
months) - 1 Technical Architect (TA) Standardize UX/UI for the whole mobile
- 1 UX/UI system
- 1 Business Analyst (BA) Work on part of the functionalities.
- 4 Developers
- 2 Tester
Phase 2 7 members in total: Reduce 1 BA, 1 UI/UX, 1 TA
(Duration: 5 - 1 PM Focus on completing and delivering
months) - 4 Developers functionalities as much as possible.
- 2 Testers

PM: at least 3 years of experience in project management, and overall 9+ years of experience
in software industry.

TA: at least 3 years of experience in software architecture and design, and overall 8+ years of
experience in software development.
BA and UI/UX designer: at least 5 years of experience in their role.

Developers and Testers: at least 4 years of working experience.

XXX CONFIDENTIAL 13
XXX’s Proposal & Quotation

V. Quotation

XXX CONFIDENTIAL 17

You might also like