Added support to extract orders of All stores

Membership

Added configuration for membership. Include promo and stores to membership. Create membership tiers.

Added members view

Update on Google Play Store or Apple App Store

The Model-View-View-Model (MVVM) pattern helps to cleanly separate the business and presentation logic of an application from its user interface (UI). Maintaining a clean separation between application logic and the UI helps to address numerous development issues and can make an application easier to test, maintain, and evolve. It can also greatly improve code re-use opportunities and allows developers and UI designers to more easily collaborate when developing their respective parts of an app.

We will organize our source code based on the following folders for easy management.

• Fonts – Customized fonts
• Model – Data structure classes. Mainly structure classes for holding JSON objects from APIs.
• Data – Data structure classes. Static singleton data objects. Such as user_data.
• Services – Interfaces and implementation for dependency injection of services functions to view models. Such as navigation services which allows view models to navigate to other pages. Static class tools such as random string generator can be in this folder.
• Views – Consist of all the UI Pages (View – XAML and CS) and its MVVM binding view model (CS).

Web Platforms

Our web platforms were developed using ReactJS. ReactJS solved the issue of complex HTML coding and makes it easier. It provides less coding and gives more functionality. ReactJS supports multiple components, and each component has its own logic and controls. These components are responsible for outputting a small, reusable piece of HTML code which can be reused. The reusable code helps to make development and code maintenance easier.

We will organize the source code according to the following structure:

• Pages – Main component will be returned by the Route
• Components – independent and reusable UI components
• Styles – styling files by component in SCSS format
• Assets – Local media, e.g. images
• Utils – reusable custom functions, e.g. data formatter and validation

The diagram above shows the overall high-level structure of our software application. The software design consists of 3 main layers. The application layer provides the user interfaces for user interaction with the system. The API web services forms the middle layer which exposes backend data and application functionalities for use by the application layer. The last layer consists of the database and S3 file storage which provides long term memory storage for the software application. This design provides an ecosystem of applications and web services that are modular and reusable — which is ideal for microservices.

Microservices are a style of service-oriented architecture (SOA) where the app is structured on an assembly of interconnected services. With microservices, the application architecture is built with lightweight protocols. The services are finely seeded in the architecture. Microservices disintegrate the app into smaller services and enable improved modularity. Our approach is to build the backend supporting services in microservices modules on a common database and file storage location. Although this method decreases the reliability of microservices running on individual databases. This architecture allows the microservices to be easily scaled and deployed.

Our applications are housed on Amazon Web Services (AWS) and hosted on servers located in Singapore region. The AWS cloud infrastructure has been architect-ed to be one of the most flexible and secure cloud computing environments available today. It provides a reliable, and scalable platform.

AWS infrastructure provides the following features:

• The AWS cloud infrastructure is housed in AWS’s data centers, designed to satisfy the requirements of our most security-sensitive customers. The AWS infrastructure has been designed to provide the highest availability while putting strong safeguards in place regarding customer privacy and segregation.
• The AWS infrastructure is protected by extensive network and security monitoring systems. In addition, AWS infrastructure components are continuously scanned and tested.
• AWS builds its data centers in multiple geographic regions as well as across multiple Availability Zones within each region to offer maximum resiliency against system outages. AWS designs its data centers with significant excess bandwidth connections so that if a major disruption occurs there is sufficient capacity to enable traffic to be load-balanced to the remaining sites, minimizing the impact.
• AWS provides certification reports that describe how the AWS Cloud infrastructure meets the requirements of an extensive list of global security standards, including: ISO 27001[1], SOC[2], the PCI Data Security Standard[3], FedRAMP[4], the Australian Signals Directorate (ASD) Information Security Manual[5], and the Singapore Multi-Tier Cloud Security Standard (MTCS SS 584)[6].

[1] https://aws.amazon.com/compliance/iso-27001-faqs/

[2] https://aws.amazon.com/compliance/soc-faqs/

[3] https://aws.amazon.com/compliance/pci-dss-level-1-faqs/

[4] https://aws.amazon.com/compliance/fedramp/

[5] https://aws.amazon.com/compliance/irap/

[6] https://aws.amazon.com/compliance/aws-multitiered-cloud-security-standard-certification/

Virtual Private Cloud (VPC)

VPC is a network layer that isolates other virtual networks in the AWS cloud. VPC comes with a security group that acts as a virtual firewall for the VPC to control inbound and outbound traffic into the individual servers. Network access control lists (ACL) is added as a second layer of defence by controlling traffic into the individual subnet. We create a public subnet for HTTP/HTTPS access to the web servers and a private subnet for the backend databases.

Internet Gateway

An Internet gateway is a horizontally scaled, redundant, and highly available VPC component that allows communication between servers in the VPC and the Internet.

S3 Storage

S3 is a scalable, high-speed, Web-based service designed for online backup and archiving data and application programs. S3 will be used for daily backup of application data. S3 encrypts data in transit via SSL-encrypted endpoints, and data will be encrypted at rest. S3 is designed for 99.999999999% durability and up to 99.99% availability of objects over a given year. All files and secondary artefacts such as images will be stored in S3.

Amazon RDS

Amazon Relational Database Service (Amazon RDS) provides cost-efficient and resizable capacity while automating time-consuming administration tasks such as hardware provisioning, database setup, patching and backups. MySQL database instances run in Amazon Virtual Private Cloud (Amazon VPC), enabling us to isolate the database instances from public access. RDS also replicates the data to a standby instance in a different Availability Zone (AZ).

Elastic Load Balancer

To achieve higher levels of fault tolerance, we deploy Elastic Load Balancing (ELB) to automatically route traffic across multiple servers and two different Availability Zones. ELB ensures that only healthy Web Servers receive traffic by detecting unhealthy instances and rerouting traffic to other healthy Web Servers in other Availability Zones.

ELB also provides SSL services that ensure that data sent over from client to servers are verified and encrypted. The ELB uses the certificate to terminate the connection and then decrypt requests from clients before sending them to the instances.

The SSL and TLS protocols use an X.509 certificate (SSL/TLS server certificate) to authenticate both the client and the backend application. An X.509 certificate is a digital form of identification issued by a certificate authority (CA). It contains identification information, a validity period, a public key, a serial number, and the issuer’s digital signature.

Bug fixes
Fix GST inclusive value
Added support for Table Service

Bug Fixes
Added Supplier in Item Fulfillment Report
Added Sort by Supplier
Export and Share Item Fulfillment Report

Improve Checkout process