1. Mass.ive's Customer Experience Mass.ive's RESTful Architecture
Mass.ive Team Members: Hsiang-Yu Liao, Richard Cross, Jason Kelsey, Kazuya Namba, Gabriela Monroy, Ummata Thangvijit, Kai Perng Faculty Advisor: Dr. Russ Abbott Liaison: Devin Lee Department of Computer Science - College of Engineering, Computer Science, and Technology California State University, Los Angeles
Background: The conceptual design and artistic vision of the Mass.ive shopping web site project was already well developed when it was first brought to us. Our mission was to lay the groundwork for a commercial version of this web project as well as to produce a demonstration web site. Using agile development methods we worked closely with our client to help realize his vision.
Have students check that the logo is the appropriate one to use.
Project background/context
Objectives
Deliverables (what you built, how you solved the problem, etc.)
Results (performance, testing, etc.)
Conclusions
Objectives:
Architect a client/server interface using the RESTful architecture design pattern using the HTTP protocol
Build a highly-integrated web-based client application that focuses on view logic, such as templates and interactivity, using modern browser technologies such as AngularJS, PubSub and HTML5
Construct a RESTful server API that focuses on business logic, such as validating and store data
Map a flexible, embedded/reference-based data model scheme and persist it using a document-orientated NoSQL database 1 1
Mass.ive's Customer Experience
To Individual Products, Chat, and Chains
From Stores to Product Selection
Mass.ive's RESTful Architecture
Client
Server
JavaScript
AngularJS
Java 7
Tomcat/Jersey T H E I N R
JSON
User's Browser (Firefox, Chrome, Safari)
Message Provider
serialize/de-serialize JSON to Java Objects
Java Objects
HTML-based Templates
Models
Resources
Stores,
Products,
Inventory,
Racks,
Customers,
Vendors, Chains,
etc...
GET
POST
PUT
DELETE
Utility
methods
Directives (View logic)
PubSub
Chat API
Drag and
Drop
Controllers (Business logic)
Login
Store List
DataStore Interface (using morphia)
Services (Communication)
Shared Services
Resources
Document-orientated NoSQL
Database (MongoDB)
Results:
Successfully accomplished a functional prototype allowing users to create customer or vendor accounts and interact live
Vendors can create stores, pick a store-front image (called a faceplate), assign a store name, create product profiles and populate racks with those products
Customers can browse stores and look through vendors' racks to check out products; then, they can chat live with Vendors and other Mass.ive users and form social chains with each other to help drive down the cost of a product.
Conclusions:
Having the desktop client/server applications client handle views and interactivity while letting the server act as a wrapper to provide data access worked well.
Communications was the key to this project. Though some isolated development of component elements was possible for short periods of time, the overall scope of the project required close coordination between the team members to meet our goals.
Using frameworks that follow industry standards and have clear APIs helped to prevent problems at the interfaces.