1. Ready to Go Business Kit
COMP2014 Group 10 (2013)

2. Team Jing Li (Leader/Dev) jing.li.11@ucl.ac.uk Horace Li
(Leader/Testing)
Eeren Tan
Tim Szeto
Weiwei Liang

3. Project Specification
To offer thin Web services solution for small businesses

4. Solution?
Increase efficiency (store work on cloud, various business tools etc.)
Ease daily tasks
So, why a thin web services solution to the small businesses? Do they need it? Do they want it? what do we offer?
How our service will help them? we help to improve their work efficiencies (by storing work on cloud to enable collaboration easily)
management tools to help them keep track of their transactions and documents

5. More importantly - Expand their existing market - Increase publicity
- Newsletter generator
- Social network integrator
- Sales model driven online store for retail
Location based rankings Google + does affect seo ranking
We want the business' website to show on google results as often as possible, to those potential customers
we want the businesses to stay connected, socially
The other focus is to dynamically generate webpage of the business website using the sales model based on sales analysis

6. Requirements HTML5 App panel FT (one post to all)
Inventory , sales, purchase management
Online store
POS system
HTML5 essentially the major part of the system, for employees to manage daily transaction documents, inventory and contacts management
FTG , acronym for Facebook TwitterOnline store, populated with items in inventory
POS system for in-shop purchase to synchronize stock in real time

15. Behind the Scenes JSON Feeds MTA MDA Web UI LDAP FileSys SQL ERP Mail
Cloud
WebDav
LDAP
OpenLDAP
Authentication/Authorization
Virtual Users for Mail
Address Book
SQL
MySQL & why
ERP usage
FileSys
PDF, documents, images
Servers
MDA Dovecot
LDAP password lookup
MTA Postfix
Dovecot S-A-S-L PLAIN cleartext authentication
Probe MDA for user exist
Mail
Ugly SquirrelMail
LDAP address book
Cloud
WebDav file storage
Caldav
ERP
Custom coded
JSON product listing
Web UI
ERP+Mail+Cloud Storage

16. Evaluation Meets (most) requirements Standards Control of Code
Portable
Minimal dependency on S/IaaS providers
Scalable
Volume
Modular
3rd Party
Evolve into SaaS
Most requirements met
Notable omissions, office suite, mailchimp API integration, web store - time constraints
Completed core functionality
Standards
Interoperability
Open beats Closed
Standards compliant
Industry conventions
Control of Code
FOSS
Custom codebase where possible
Know our own code
Flexibility
Portable
Self contained VM
Minimal dependency on 3rd parties
No vendor lock-in/proprietary APIs (AWS, OpenStack)
No Google Apps, Office 365, Zoho
Scalable
Volume
MySQL designed for high volume
LDAP allows replication
Modular
Internal subsystems, apps
3rd Party
Standards-compliant interfaces
Retrieve LDAP data
WebDav interface
Single Deployment to SaaS
Dynamically create/delete businesses
MS Exchange Server to MS Exchange Online

17. Tests Exploratory Unit Integration System Critical Path PHPUnit
CodeIgniter
Integration
Continual process
System
Exploratory
Not Ad-hoc
Minimal overhead
Reduce critical path drag
Unit
In progress
PHPUnit
Extensive testing
Unable to replicate CodeIgniter framework
CodeIgniter
Limited tests within framework
Integration
Just started for ERP
Continual process for different subsystems
MySQL, LDAP
Mail servers
System
Comparison with original requirements
About to start

18. Where Now... Integration SSO Mobile apps Online shopping
Web apps (SAML)
Thin client, non-HTTP (SASL/Kerberos)
Mobile apps
Online shopping
Payment methods
Calendar
Integration
Previous module project - thin client, Archlinux on RPi
Visual integration of separate subsystems - ERP, mail, cloud
SSO
Web-based, e.g. webmail, external services, Google Apps
Thin client/workstation SSO
Mobile apps
RESTful-ize JSON feeds
Online Shopping
Web store or mobile app
3rd party make use of JSON data feeds
Payment
Paypal, credit card (online)
Square (offline)
Calendar
Integration with ERP dates
Direct edits through CalDav

19. Q&A
Thank You