Mass.ive's Customer Experience Mass.ive's RESTful Architecture

Slides:



Advertisements
Similar presentations
JavaScript FaaDoOEngineers.com FaaDoOEngineers.com.
Advertisements

JPManager: A J2EE PERFORMANCE MANAGEMENT SYSTEM Jiang Guo Department of Computer Science California State University Los Angeles March 24, 2010.
Integration of Hand-Held Devices into Collaboration Environments IC’02 Las Vegas, NV June June Geoffrey Fox, Sung-Hoon Ko, Kangseok Kim,
Introduction to Backend James Kahng. Install Node.js.
Fuel Cell Modeling Team Members: Albert Wong Faculty Advisor: Dr. Blekhman Department of Computer Science and Technology College of Engineering, Computer.
INTRODUCTION The Group WEB BROWSER FOR RELATION Goals.
Cross Platform Web Based Home Inventory System Project Team: Jon Garibay, Firas Assaad Faculty Advisor: Dr. Lawrence Thomas.
Computer Science 101 Web Access to Databases Overview of Web Access to Databases.
UNIT-V The MVC architecture and Struts Framework.
NCAA Student Athlete Compliance System May
Fall, Privacy&Security - Virginia Tech – Computer Science Click to edit Master title style Design Extensions to Google+ CS6204 Privacy and Security.
E-Learning Material Web Application Design 3. Web Application Design Architecture Which objects go where? The final model notation Summary.
** NOTICE! These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Case study concerning architecture development Emil Doychev, Georgi Cholakov, University of.
WEP Presentation for non-IT Steps and roles in software development 2. Skills developed in 1 st year 3. What can do a student in 1 st internship.
Secure Systems Research Group - FAU SW Development methodology using patterns and model checking 8/13/2009 Maha B Abbey PhD Candidate.
GOAL User Interactive Web Interface Update Pages by Club Officers Two Level of Authentication.
AFTERCOLLEGE SELF- SERVICE SCRAPE CONFIGURATION AND POSTING UTILITY Kai Hu Haiyan Wu March 17, Cowell 416 Midterm Presentation.
Lightweight construction of rich scientific applications Daniel Harężlak(1), Marek Kasztelnik(1), Maciej Pawlik(1), Bartosz Wilk(1) and Marian Bubak(1,
Presentation Title Subtitle DSpace UI Prototype 7 Spring, Angular.js, and the DSpace REST API.
ISYS 350 Building Business Applications David Chao.
DAT602 Database Application Development Lecture 1 Course Structure & Background knowledge.
ECpE Student Database Team 21 Adviser: Tien Nguyen ECpE and Tony Moore.
Overview Web Technologies Computing Science Thompson Rivers University.
Web Services. Web Service: Simple definition : “ Service Offered On the Web “ Technically : “ A Web Service is a programmable application component that.
PROWIND (Positioning Relay over Wirelessly Networked Devices) Team Members: Mark Buising, Douglas Chow, Nazeni Mkrtchyan, Jesus Rodriguez, Jennifer Webb.
1 LM 6 Database Applications Dr. Lei Li. Learning Objectives Explain three components of a client-server system Describe differences between a 2-tiered.
 Why “By the way”?  DSD environment  About us  Requirements  Architecture design  Results.
Your Best Friend Cooking Assistant and Educational Resource Learner: Tim Bair Advisor: Dr. Hazem Said a time-saving tool for meal planning, grocery shopping,
Web Development. Agenda Web History Network Architecture Types of Server The languages of the web Protocols API 2.
TechIT: A Work Order System Team Members: Marjorie Zalaya, Duc Le, Kevin Castillo, Minh Ha, Brandon Ung Faculty Advisor: Dr. Chengyu Sun ECST Liaison:
Lesson 11: Web Services and API's
Configuration Item Page
ISYS 350 Building Business Applications
Goats And Tigers John Hurley, MS Faculty Advisor: Russell Abbott Graduate Project - Spring, 2012 Department of Computer Science California State University,
Landfill e-Forms Application
Web Technologies Computing Science Thompson Rivers University
Brice Copy, Mirjam Labrenz
REST: Web Services Abel Sanchez.
Mobile Navigation Control for Planetary Web Portals Team Members: John Calilung, Miguel Martinez, Frank Navarrete, Kevin Parton, Max Ru, Catherine Suh.
DCR ARB Presentation Team 5: Tour Conductor.
Stock Analysis Tool (SAT) Lalantha Sathkumara Faculty Advisor: Dr
IT.CAS.Web2.0 Kyle Erickson
Weapon Impact Scoring System Application Architecture
CONCUR Project Tactical Approach
Server Concepts Dr. Charles W. Kann.
CMPE 280 Web UI Design and Development October 26 Class Meeting
EcoCAR3 Year 2 Team Members: Edwin Quintanilla, Varunya Nimnualrat, Ryan Wong, David Perez Faculty Advisor: Dr. Yuqing Zhu Liaison: Dustin York |
Sarang Nazari California State University, Los Angeles
Distributed web based systems
By Janet Crawford and Dam Luong Submitted to the Faculty of
CMPE 280 Web UI Design and Development October 24 Class Meeting
ISYS 350 Building Business Applications
ISYS 350 Building Business Applications
Modern web applications
ISYS 350 Building Business Applications
ISYS 350 Building Business Applications
ISYS 350 Building Business Applications
Proposal Presentation
Modern web applications
Secure Web Programming
ISYS 350 Building Business Applications
Introduction of Week 11 Return assignment 9-1 Collect assignment 10-1
Lesson 11: Web Services and API's
ISYS 350 Building Business Applications
Team 13 The Los Angeles Community Garden Inventory and Locator
BOF #1 – Fundamentals of the Web
Web Technologies Computing Science Thompson Rivers University
Knowledge Sharing Mechanism in Social Networking for Learning
A RESTful Approach to XML Integration
Presentation transcript:

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.