Skip to main content

Overview

The RASP-Platform serves two primary functions: it generates boiler-plate code based on provided JSON specs and acts as a library offering useful classes to help get custom code up and running.

Workflow​

The following diagram provides a high-level overview of the general workflow used when developing application using the RASP-Platform :

Workflow

The diagram highlights four steps :

  1. Creation : The first step in the workflow is creating a set of JSON files detailing the required attributes and methods of the of data classes in the application. These files can be easily created based on the diagrams drawn during the design phase.
  2. Generation : Given the JSON specs, the generator class written using components from the platform spits out boiler-plate code - comprising of, but not limited to controllers, messages, services, helpers and some UI elements.
  3. Supplying Implementation : Once the boiler-plate is generated, the application developer needs to supply implementations of a few classes on which the generated code is dependent on. These classes need to be written keeping certain things in mind and they may utilize handy components made available by the platform.
  4. Augmentation : If the application developer wishes to add their custom business logic to the application, they can do so by using Decorators. In this case too, components provided by the platform come in handy.

Guide​

This documentation aims to guide application developers through the above steps in detail and enable them to utilize the RASP-Platform to get their own application up-and-running.