HeaderSIS.jpg

IS480 Team wiki: 2015T1 Vooze Project Overview

From IS480
Revision as of 02:09, 6 July 2015 by Vnhphan.2013 (talk | contribs) (Added Comparison with Traditional CMS)
Jump to navigation Jump to search
Vooze logo.jpg


Vooze-house.png Home Vooze-info.png About Us Vooze-Eye.png Project Overview Vooze-To-do-list.png Project Management Vooze-Document.png Documentation
Description Motivation Stakeholders Deliverables Scope

Project Description

Traditional Web/Mobile Development Process vs Web/Mobile Developed using SymplCMS


Vooze PD 1.png


Focus on engaging user’s experience and forgo any troubles in infrastructure, database design, our SymplCMS takes care of everything to maintain your application’s optimal performance. Our target applications are lightweight back end or heavily involved CRUD applications that are designed in OOP. Not only experienced users can take advantage of our REST API to manage apps’ resource, even inexperienced users who only has basic knowledge on javascript can also rely on our interactive UI for resource manipulations. Easily monitoring and gaining visibility on app’s performance in real time as soon as data/request is being sent to our system which in turn helps our clients to analyse any data point in real time.

Comparing to the current popular CMS system in the market (WordPress, Joomla, Drupal), our SymplCMS serves different purposes. This will be highlighted via 5 main key listed as below

1. Content Management

Conventional CMS system provides a full-fledge solution for anyone who wants to create the website. Which means, they only need to worry about the content (post, page, media library, etc.), back-end implementation is provided by default and front-end is offered by theme or template. Our CMS only manage files (video, image, music, etc.) and non-file resource (object with keys and values). In a nutshell, we manage web resources in the forms of objects which means all resources (files or non-files) being uploaded or added into our system must belong to a class (user-defined).

2. Security

For security purpose, all conventional CMS systems needed to be applied some layers of protection via customized plugins. This requires a certain knowledge in the system itself. However with our system, there is no need to have any background about the security or a specific programming language. All security relating to the object management will be taken care by us.

3. Centrality 

Each instance of CMS only caters of one web application and their resources are separated let say an IT development house keeps multiple websites. Our CMS allows users manage all web/mobile applications ‘resource at one place. Their resources can be reused across multiple applications. At the same time, having all application resources at one place allowing us to keep track of their applications API resource request and provide meaningful insights regarding to “object” access performance which directly impact to website performance.

4. Simplicity

There is no need for configure or maintain database – Object management is just simply upload/create/edit resources (file or object entity) via our friendly UI and API call

5. Flexibility

Conventional CMS are distributed as framework and requires intensive knowledge of the framework itself for customization. While our CMS doesn’t require any knowledge at back-end, front-end could be any language up to developer’s preference (angular, ember, backbone, etc.) to consume our API for object retrieval or manipulation.

From that perspective, our main target audience is not for mass users (unlike WordPress or other CMS). Our solution is mainly for lightweight back-end CRUD Web/mobile application and IT development house who wants to leverage benefits provided by our system which not being offered by most of traditional CMS in the market.