Yoga and Travel Proposal - 2023-03-19 10-12-18

PROPOSAL
YOGA AND MEDITATION

AWARENESS
FITNESS AND MINDFUL LIVING
Contact: SARAH REVOCATUS KAPAMA
Reference: S16-9642
Version: 1.0
Status: ISSUED
Release Date: Jan 2022
Approved by: CTO
Solution Description
Solution Description Version: 1.0

Security: Commercial in Confidence Status: ISSUED
Copyright © Quantrica 2022 Page 1 of 23
APPROVAL FOR THIS DOCUMENT
Authors: SARAH REVOCATUS KAPAMA
Approved By For
Yes Sarah Fitness insctructor

Table of Contents
1. Executive Summary ..............................................................................................................................................
5
2. Introduction ..........................................................................................................................................................
6
2.1. ...................................................................................................................................
6
2.2. Project Objectives ................................................................................................................................
6
2.2.1. General Objectives. .................................................................................................................
6
2.2.2. Specific Objectives. ..................................................................................................................
6
2.3. ....................................................................................
7
2.3. Quantrica’s Proposal .............................................................................................................................
7
2.3.1. Overview ..................................................................................................................................
7
2.3.2. ......................................................................................
8
3. About Quantrica ..................................................................................................................................................

9
3.1. Why Quantrica ......................................................................................................................................

9
3.2. Our experience.....................................................................................................................................
9
4. Functional Solution Overview ..............................................................................................................................

10
4.1. Overview ..............................................................................................................................................

10
4.1.1. Web application / Content Management System. ...................................................................
10
4.1.3. Mobile applications ..................................................................................................................
10
5. Functional Solution Details ..................................................................................................................................

11
5.1. Overview ..............................................................................................................................................

11
5.1.4. High level solution architecture................................................................................................
11
5.1.4. Solution details.........................................................................................................................
11
5.1.4.1.System Database ..................................................................................................
12

5.1.4.2.Backend and API server ........................................................................................

12
5.1.4.3.System API ............................................................................................................
12
5.1.4.4.WebApp ................................................................................................................
13
5.1.4.5.Mobile applications...............................................................................................
14
5.1.4.6.Training portal and content ...................................................................................
14
5.1.4.7.Business Intelligence & Analytics ..........................................................................
14
6. Project implementation ........................................................................................................................................

16
6.1. Overview ..............................................................................................................................................

16
6.1.5. Project Phase I ..........................................................................................................................
16
6.1.6. Project Phase 2 .........................................................................................................................
18
6.2. Project technologies .............................................................................................................................
18
6.2.1. MobWapp Server infrastructure ...............................................................................................
18
6.2.2. MobWapp Database ................................................................................................................
19
6.2.3. MobWapp mobile applications ................................................................................................
19
6.2.4. MobWapp Web application .....................................................................................................
19
6.2.5. MobWapp E-learning portal ....................................................................................................
19
6.2.6. MobWapp BI & Analytics .........................................................................................................
19
7. Project costing .....................................................................................................................................................

20
7.1. Pricing overview ...................................................................................................................................

20
7.2. Pricing table .........................................................................................................................................
21
A. ................................................................................................................................
22
D. Document Version History ..................................................................................................................................

23

1. Executive Summary
Organization today exist in fast changing environment, a situation primarily driven by
changing users’ and stakeholders’ expectation, rapidly evolving technology and generally
changing societal dynamics.
The aforementioned circumstances can be elaborated as follows:
Changing user expectations:
With ubiquity of mobile communication technologies, increasing availability of data services

and general competence in mobile device usage, the preferred mode of service interaction
for most people is one where they can efficiently and quickly access services.
Organization and stakeholder expectations:
The modern organization sees the opportunity for enhanced service delivery, with
technology as the underlying platform that enables increased operational efficiency, better
decision making using insights, and to support growth and scalability.
Societal dynamics
Amongst other things, population growth, changing societal structures and behaviour
require that organizations adapt in order to be more responsive and effective at their mission
execution.
The above mentioned circumstance present both a challenge and opportunity. Technology
provides one the best opportunities for organization to address these challenges and turn
them into real opportunities. A well implemented digital service can tremendously increase
the rate and scale at which an organization meets their desired objectives.
The aspirations of ADSOCK are properly articulated in the provided terms of reference for
MobWapp system.
With all the above considerations to make, it’s important that ADSOCK selects the right
technology partner to work with in this initiative.
Quantrica is nimble software and data technology company with offices in Nairobi. Our aim
is to help build data driven organization and foster greater innovation within organizations by
providing users with tools that empower them to work better.
We have combined experience of over 50 years working on various complex technology

problem. Our expertise in data-drive applications enables us to bring a unique perspective in
solution design, allowing customers to take full advantage of the insight-centred design
philosophy.
Above all, we are customer obsessed organization with an unwavering dedication to our
mission: To make our customer succeed.

2. Introduction
2.1. ADSOCKs goals

ADCOCK have listed their goals and functional requirements in the TOR document
through an email to Quantrica. The high level goals of this project are: can be
summarized as follows:
- Make ADSOCK a future-ready organization through digitization of outreach

operations
- Build a resource centre for ADSOCK’s programs for ease of access and
dissemination
- Automate SGBV incidence reporting and management work ows
More detailed requirements are addressed in subsequent sections of this document within
our response to those requirements.
2.2. Project Objectives

Based on ADSOCK’s goals in section 2.1 above, we have broken down the projective as
follows:
2.2.1. General Objectives.
• Facilitate access accurate information related to raising awareness on SGBV prevention

and response services including how to confront COVID-19 virus.
• Enhance access to accurate information about SGBV services in different contexts.
• Simplify reporting mechanisms and thus ensure support services and access to justice.
2.2.2. Speci c Objectives.
• To design, build, test and deploy a fully featured mobile application for both iOS nad
Android System for MobWapp.
• To design, build, test and deploy a fully featured, cloud content management system.
• To design, build, test and deploy a fully featured SGBV incidence reporting and
management system
• To design, build, test and deploy an analytic and report generation cloud based
application
• To design, build, test and deploy an e-learning portal for training and digital course
management on SGBV
• To use an E-Learning platform to deliver training to stakeholders across board.

fi
fl
2.3. General speci cations of ADSOCK MobWapp

In this section, we provide the general requirements for ADSOCK’s MobWapp. These
requirements together with the detail SRS are the basis for our functional and technical
proposal.
1. All-in-one content manager– Allow for the management of the mobile application
and resources from a single web application
2. Collaborative tools and activities – Allow users and supervisors to interact and
collaborate on content through comments, shares, likes, impressions and forums
3. Convenient file management – Allow the storage of files and documents supporting
as part of content.
4. Detailed reporting and logs – Allow different levels of reporting such as logins,
content interactions and impressions, incidences, regional data and parameterize
existing data.
5. Embed external resources – Allow for the embedding of external resources such as
YouTube videos from within the system
6. Manage user roles and permissions – Allow for different account types such as
Admins, Content Moderators and other user defined roles.
7. Multilingual capability – Allow the translation of resources into any language.
8. Multimedia integration – Allow graphics to be embedded into mobile application
contents
9. Notifications and Automatic Alerts – Allow the sending and receiving of messages
within the system and communication via email to external communication channels
10. Secure authentication and mass enrollment – Allow Admins to mass enroll and
authenticate users
11. Incident reporting and management: allow for recording of incidents by users and
admins and management of incidence workflow such as updating status, tagging,
sharing, escalating and closure
12. Bulk SMS: allow for bulk SMS to be sent from the control panel to predefined user
contact list
13. Allow for User Survey: allow for creation and sharing of surveys and the analysis and
reporting on these survey.
2.3. Quantrica’s Proposal
2.3.1. Overview
In order to meet ADSOCK’s requirements, Quantrica proposes to build a bespoke

solution from ground up. The solution will be completely web based and will be
developed using modern software development tools and techniques. In particular, a
modular design approach and APIs will be used to allow extensibility, scalability and
maintainability of the system.

fi
Quantrica will also develop a mobile application for both iOS and Google Android
platforms
The proposed solution will be fully cloud and web based, and can be deployed on either
an ADSOCK managed or Quantrica managed cloud computing platform.
2.3.2. .

3. About
3.1. Why yogalifestyle

At Quantrica, we offer our customers a pathway to rapid ROI realization by offering next
generation data innovation solutions that help them unlock the potential of their data assets.
Since every customer’s journey is unique, the data technology company of today must
work closely with the customer to provide tailored solutions for actual problems that
customers face as opposed to dropping in more generic one-off solutions that often fail to
scale with emerging business requirements. Doing this requires a different kind of
technology company.
Quantrica is a mission driven company. Our aim is to help build data driven enterprises.
A completely agile organization, we fully integrate our customers into our project
delivery framework to ensure that we leverage the customer’s knowledge of their business.
3.2. Our experience

Between us, we have over five decades of experience tackling the most challenging
technology problems in the world.
Building platforms for large scale data processing

at the World’s Number 1 cloud computing
company
Deploying the largest telecommunications

systems in the world
Developing and managing 50 + high

performance database systems
Developing financial analytics models used to

oversee risk for over $14 Trillion of financial assets
in the worlds largest Asset Manager

4. Functional Solution Overview
4.1. Overview
Our proposed solution is highly modular and designed for extendibility as well as
incremental addition of system capabilities. This is important consideration as it allows
platform owners to imagine new innovation without worrying about the implementation
complexity. The following sections describes the functional capabilities of our proposed
solution.
4.1.1. Web application / Content Management System.
This is an internal module will enable ADSOCK staff to publish content that can then be
viewed on a public portal by ADSOCK’s intended audience. The CMS module is a multi-
user application that will enable among other internal collaboration, notifications as well as
well as analytics and reporting.
The following are the main functional capabilities of this module.

• Internal user management
• External user management
• In-platform collaboration workflows
• Case/incident management
• Notifications and alerts
• Dashboards, reports and analytics.
• Content management
4.1.3. Mobile applications

This is a public facing web application, and will be the point of interaction between the
general public (ADSOCK’s audience) and ADSOCK’s staff.
The application will be easy to use and will provide user with ease of access of key services,
e.g incident reporting.
While the specific software requirement of this module have not been provided yet, our
proposed solution would included services such as:
• User self registration and account management
• Incident reporting workflows, with location based (GPS maps) support.
• Search and information discovery

5. Functional Solution Details
5.1. Overview
In this section we provide a high level solution architecture and additional technical details
that the system will implement.
5.1.4. High level solution architecture
The solution is based on a server-client model. In this model, a central server holds all the
application logic and clients provide end user experience. We implement a communication
interface between the two using REST API framework. A central database store all the
application data, and only the logic server has direct access to this database.
5.1.4. Solution details

In this section, we outline at high level the various components of the system, their
implementation and the services they provide.

5.1.4.1. System Database
This is the central repository of all application data. The logic (backend) server will access
the database using native database drivers (e.g ODBC) for both provisioning and data
retrieval request.
We will use a relational, fully normalized database model for this layer to ensure atomicity
of transactions and overall data integrity. Other technical considerations to make for this
layer include:
Database security
• Configured for access through non-standard ports
• Only logic server will have access to the database to prevent manual retrieval/
update of system records.
• Encryption using SSL
Redundancy and replication

• A standby database server for either online database replication.
Partitioning & indexing for OLAP services

• A specialized database replica for use with third party data analytics and
visualization tools.
We propose to use a enterprise-grade database engine for this layer, e.g PostgreSQL
5.1.4.2.Backend and API server

This is the core of the system and will be responsible for implementation of all the system
logic. It will be responsible for marshaling application request for delivery to clients or
persistence to the database.
We will use a modular, micro-services architecture to implement this layer. A micro-services

architecture ensures simplification through specialization of service end-points. The
separation of services also provides a pathway to easy scalability, e.g a service with high I/
O requirements can be moved to a separate server without affecting the operation of the
system.
All request to this layer will use authorization to ensure that only registered services can
post and retrieve data from the system.
We propose to use Python3 to implement the system backend.
5.1.4.3.System API
This is a system interface layer and the primary data interchange layer between the server
(Backend) and client (Web /Mobile frontend).
We will use REST as the framework for implementing this layer, and JSON as the data
interchange format.
An online documentation of the APIs will be provided for ease of implementation and
extension of the service.

5.1.4.4. WebApp
WebApp is the primary interface that user (internal ADSOCK user) will interact with the
system. It is an abstraction layer for all the underlying system capabilities. The following
modules will be available for use by the end users
5.1.4.4.1. User management
This module will be responsible for managing all user (internal and external).
Some of the services provided by this module include user registration, group
and role management among others.
5.1.4.4.2. Content Management
This module will enable ADSOCK staff to publish content for consumption by
ADSOCKs external users. This content my include, bulletins, contact information
on response centre, etc. We consider every public user resource (e.g new
location, contact information, etc to be content)
5.1.4.4.3. Collaboration
This is a productivity module that will make it easy for internal ADSCOK users to
effectively resolve issues without leaving the system. As as example, a user can
quickly tag a reported incident, provide additional context and assign or to
another user/group for follow-up. The other users will receive and in-platform as
well as a email notification for follow-up.
5.1.4.4.4. Incident management
This module will provide a repository of all incidents reported, as well as the
workflows for resolution. ADSOCK will be able to define incident severity types
so that all incidents are automatically tagged for prioritization purposes.
5.1.4.4.5. Notification services
This module will allow ADSOCK staff to define various notification services for
either internal or external service consumption. For instance, a notification
service may be defined to alert (via email, SMS or in-platform) a specific group of
ADSOCK staff about certain priority level incidents reported by the public.
Another use case would to automatically send a public messages to users in a
location with a mass public action. E.g “There are ongoing demonstrations in
your location. In case of an incident, please report to this number: XXX. Keep
safe.”
5.1.4.4.6. Analytics and reports
This reporting module will be responsible for providing metrics and reports for all
system module. We will use various data presentation options e.g, charts, data
tables, summarized report. In addition, user will be able to apply and use filters.

E.g to see the number of incidents reported in a certain area in a given period.
etc.
5.1.4.5.Mobile applications
WebApp The mobile applications will the primary interface with which the general public
will interact with the system. The application will be available on app store (Google and
Apple) and users will be able to download and register to use the service. The mobile app
will have GPS maps capability, and easy to access “incident reporting” functionality. Other
sections of the app will have information portal, options to invite other users, among
others.
5.1.4.6. Training portal and content

While user training will occur throughout the project, it is imperative that this knowledge be
persisted as an organizational asset. For this reason, we are providing a competence based
e-learning portal as part of this solution.
Our e-learning solution is one of the only Learning Management Systems designed
specifically to handle competency based education. It allows you to set competencies,
perform diagnostic assessments, and personalize learning paths. It supports various modes
of content delivery, e.f video, text, slide-shows among other.
It is completely web based and can be accessed from anywhere. It is therefore a suitable
solution for scaling knowledge both internally as well as externally, e.g
• Can be used by internal ADSOCK staff to enhance system competence, as well as to

help new staff onboard more effectively.
• Can be used to train ADSOCK’s staff or outreach partners who work directly with
ADSOCK’s community
• Can be used by ADSOCK field staff to directly educated ADSOCK community
5.1.4.7.Business Intelligence & Analytics
We understand that one of the key goals of this project is to surface insights from data in
order to be more responsive and generally effective at executing their mission.
While dashboards and reports will be available in the core MobWapp system by default, it
is objectively better to have a specialized tool for advanced reporting and analytics.
Our proposed solution is a general purposes data analytics tools designed for rapid data
modeling and insight generation.
It has been designed purposely for business users, and therefore has been simplified data
modeling and analytics workflows; minimal training is required for effective use of this
system.
Other features of the system include:
• Support for various data source types, e.g databases, Excel, external applications, etc.
• Reusable data models

• Support for unlimited models, reports and dashboards.
• A robust data visualization library including bar charts, pie chart, stacked charts, line
charts, grouped charts, data tables, etc.
• Multiple user support.
• Data governance and security through fine-grained security control
• Data download and sharing
• Configurable data filters.
Quantrica will implement the analytics module including designing end-to-end (from data
to dashboards) data workflows as part of this project.

6. Project implementation
6.1. Overview
Our project delivery and implementation are based on key assumption provided in earlier
section of this document and may change based on the detailed software requirement
specification. We have further broken down the project delivery into iterative phases to
ensure feedback is continuously implemented.
In Phase I (21 project days), we will provide the basic functionality of both the mobile and
web application.
In phase II (+60 project days), we will extend the system for more functionality as well
incorporate feed back from the MVP into the solution. Subsequent phases will include
other system enhancements and changes from continuous feedback.
6.1.5. Project Phase I
System Name Task Name Deliverable Days
ADSOCK Commissioning of The Project Contract 1

MobWapp Project
ADSOCK Requirements Analysis Software 2

MobWapp with the various Requirements
stakeholders Speci cations
Document
ADSOCK System Analysis and System Architecture 5

MobWapp Design Document,
Database Schema
Document,
ADSOCK Development of Application 7

MobWapp ADSOCK MobWapp Programming
Backend Infrastructure Interface Software,
Automated
Deployment/Delivery
Pipeline
DEMobWapp
Database

fi
ADSOCK Analysis of ADSOCK Mobile Application 3

MobWapp MobWapp Mobile User Interface Mock-
Application User ups /wire frames
Interface Design
ADSOCK Analysis of ADSOCK Web Application User 3

MobWapp MobWapp Web Interface Mock-ups /
Application User wire frames
Interface Design
ADSOCK Development of Minimum Viable 14

MobWapp ADSOCK MobWapp Mobile Application
Mobile Application Program
ADSOCK Development of Minimum Viable Web 14

MobWapp ADSOCK MobWapp Application Program
Web Application
ADSOCK Publishing ADSOCK Minimum Viable 1

MobWapp MobWapp Mobile Mobile Application
Application Program Program Accessible
on Google Play Store on both iOS and
and Apps Store Android stores
ADSOCK Hosting ADSOCK Minimum Viable Web 1

MobWapp MobWapp Web Application Program
Application Program Accessible via web /
on Virtual Private internet
Server Infrastructure
ADSOCK User testing User Accepted 3

MobWapp acceptance testing Minimum Viable
and full testing of Product
functional and non-
functional
requirements
ADSOCK Stakeholder Feedback Requirements 2

MobWapp & Planning of Phse2/ Document for Phase2/
Iteration number 2 Iteration Number 2

6.1.6. Project Phase 2
System Task Name Deliverables Days

Name
ADSOCK Development of ADSOCK Updated Mobile Application 21

MobWapp MobWapp Mobile Application Program (Public Version) or
Version 1 (V1)
ADSOCK Development of ADSOCK Updated Web Application 21

MobWapp MobWapp Web Application Program (Public Version) or
Version 1 (V1)
ADSOCK Publishing ADSOCK Version 1 (V1) Mobile 1

MobWapp MobWapp Mobile Application Application Program
Program on Google Play Store Accessible on both iOS and
and Apps Store Android stores
ADSOCK Hosting ADSOCK MobWapp Version 1 (V1) Web 1

MobWapp Web Application Program on Application Program
Virtual Private Server Accessible via web / internet
Infrastructure
ADSOCK Production of Training Plan Textual Tutorial Document, 4

MobWapp and Materials
Video Tutorial Files,
Hosted Training Portal (E-

Learning Resource Centre for
MobWapp)
ADSOCK Handing Over of Source Code, Source Code, Documentation 1

MobWapp Documentation and and Deployment Pipeline/
Infrastructure) Infrastructure
ADSOCK Maintenance Service Level Agreement 365

MobWapp
6.2. Project technologies

The following technologies will be used in this project.
6.2.1. MobWapp Server infrastructure
VPS running Debian Linux Operating system
NodeJS

ExpressJS
Python3
Laravel 6+
Shell scripts
Vanilla JavaScript
6.2.2. MobWapp Database
MySQL
MongoDB
PostgreSQL
6.2.3. MobWapp mobile applications
ReactJS
ReactNative
RxJS
6.2.4. MobWapp Web application
ReactJs
HTML5
CSS3
Vanilla JavaScript
Material Design
6.2.5. MobWapp E-learning portal
Moodle
Moodle Mobile
6.2.6. MobWapp BI & Analytics
Athena Analytics

7. Project costing
7.1. Pricing overview

Our proposed commercial offer based on assumptions made in sections 2 and 3 of this
document and adjustments may be required based on the detailed software requirement
specification. We have taken into consideration the human resource effort, and other
material costs required to make the project operation. Specifically, we have included the
following 3rd party resources that will be required to make the service operation. In cases
where ADSCOK may prefer to directly pay for this services, an updated commercial offer
with this consideration will be provided by Quantrica.
• Application hosting
• Email notification services
• Bulk SMS for SMS notifications

7.2. Pricing table
Offer Description: Price (KES)
ADSCOK MobWapp
MobWapp Software development 1,665,000.00
Design, Implementation & Integration
- Web Adminstration and content management 935,000.00
- iOS and Android mobile application 530,000.00
- Training portal and content* 80,000.00
- Advanced BI and Analytics (10 seats)* 120,000.00
3rd Party Software & Services** 179,000.00
- Cloud servers / year 120,000.00
- Email notification server / year 24,000.00
- Bulk SMS (10,000) 10,000.00
- SSL certificates / year 12,000.00
- Android and iOS play store / year 13,000.00
Other services 0.00
- User training 0.00
- 1st year support and maintenance 0.00
Total 1,844,000.00
VAT (16%) 295,040.00
Total Incl VAT 2,139,040.00
Notes
Scope of offer:
This is budgetary offer. A final offer will be provided once all the requirements have
been provided and software requirement specification accepted and signed off
Invoicing terms:
20% on contract; 30% on MVP; 30% on completion; 20% final acceptance

A. Standard Glossary of Terms
API Application Programming Interface HTTP Hypertext Transfer Protocol

REST Representational state transfer SNMP Simple Network Management Protocol
BI Business Intelligence AMS Athena Management Station
ROI Return on Investment SQL Structured Query Language

D. Document Version History
Version Status Date Details of Changes Author(s)
0.1 DRAFT 07-Jan-2022 Initial version M.Aluda
0.2 ISSUED 09-Jan-2022 Implementation updated M. Aluda
1.0 ISSUED 09-Jan-2022 Final version D.Waweru
Document Version History


Yoga and Travel Proposal - 2023-03-19 10-12-18

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Yoga and Travel Proposal - 2023-03-19 10-12-18

Uploaded by

Copyright:

Available Formats

PROPOSAL

YOGA AND MEDITATION

FITNESS AND MINDFUL LIVING

Contact: SARAH REVOCATUS KAPAMA

Solution Description Version: 1.0

APPROVAL FOR THIS DOCUMENT

Authors: SARAH REVOCATUS KAPAMA

Solution Description Version: 1.0

3. About Quantrica ..................................................................................................................................................

3.1. Why Quantrica ......................................................................................................................................

4. Functional Solution Overview ..............................................................................................................................

4.1. Overview ..............................................................................................................................................

5. Functional Solution Details ..................................................................................................................................

5.1. Overview ..............................................................................................................................................

Solution Description Version: 1.0

5.1.4.2.Backend and API server ........................................................................................

6. Project implementation ........................................................................................................................................

6.1. Overview ..............................................................................................................................................

7. Project costing .....................................................................................................................................................

7.1. Pricing overview ...................................................................................................................................

D. Document Version History ..................................................................................................................................

Solution Description Version: 1.0

The aforementioned circumstances can be elaborated as follows:

Changing user expectations:

With ubiquity of mobile communication technologies, increasing availability of data services

Organization and stakeholder expectations:

We have combined experience of over 50 years working on various complex technology

Solution Description Version: 1.0

2.1. ADSOCKs goals

- Make ADSOCK a future-ready organization through digitization of outreach

2.2. Project Objectives

2.2.1. General Objectives.

• Facilitate access accurate information related to raising awareness on SGBV prevention

2.2.2. Speci c Objectives.

Solution Description Version: 1.0

2.3. General speci cations of ADSOCK MobWapp

2.3. Quantrica’s Proposal

In order to meet ADSOCK’s requirements, Quantrica proposes to build a bespoke

Solution Description Version: 1.0

Solution Description Version: 1.0

3.1. Why yogalifestyle

3.2. Our experience

Building platforms for large scale data processing

Deploying the largest telecommunications

Developing and managing 50 + high

Developing financial analytics models used to

Solution Description Version: 1.0

4. Functional Solution Overview

4.1.1. Web application / Content Management System.

The following are the main functional capabilities of this module.

4.1.3. Mobile applications

Solution Description Version: 1.0

5. Functional Solution Details

5.1.4. High level solution architecture

5.1.4. Solution details

Solution Description Version: 1.0

5.1.4.1. System Database

Redundancy and replication

Partitioning & indexing for OLAP services

5.1.4.2.Backend and API server

We will use a modular, micro-services architecture to implement this layer. A micro-services

We propose to use Python3 to implement the system backend.

Solution Description Version: 1.0