Introduction

This page describes what the developer of apps on the Kwantu platform needs to do, to develop a typical "business process management app". All Kwantu apps are essentially "process management apps", though the platform can be applied to other problems that lend themselves to the Kwantu platform solution anatomy as well.

Prerequisites for developing an app

(ie. what must be in place first before an app development begins)

The development process or SDLC (systems development life cycle) begins when the following list of things is in place:

1. The business uses the Kwantu platform as part of its solution architecture.
2. The Kwantu platform software is installed on a server belonging to the organisation or enterprise.
3. The business has a problem which needs to be solved with a computerised solution, and fits the Kwantu platform app template.
4. Analysis of the business problem must be done and a specification for the app development must be written.
5. There is at least one developer / administrator available to do the configuration work.
6. The developer / administrator is familiar with the configuration of files required for the development.

The Kwantu platform application development-process User Guide

The following table lists the steps involved in creating a Kwantu platform app.

Process steps	What's new	Examples
1) Create a community	Build XXX	Example apps
2) Create an app		Templates
3) Create a DO		Templates
4) Create a Taxonomy		Templates
5) Create a Search		Templates
6) Create a Workflow		Templates
7) Create a Server based actions		Templates
8) Test the app
9) Versioning the next generation		Templates
10) Adopting an app		Core apps
11) Creating an activity		Core apps

• Introduction to the concept of developing Apps on the Kwantu platform
• Establishing a server environment for: (development, testing and production)
• The stack
• Installing the stack from scratch
• Testing the stack
• Development tools
• What core data must exist before an app can be developed?
• What is a complete App configuration composed of?
• What is the most basic "hello world" app that can be developed?
• How do I test a new app?
• Can sub-components of the app be tested to ensure that they are working?
• What does an example app specification look like?
• How does an app specification translate into app configuration?
• How does a App configuration transform into a working App?
• Where will the data, that is processed by the app, be stored?
• How can I see the app's data?
• Transporting a working app from the dev environment into test and from test into prod?
• The example reference implementation: the Knowledge Management App
• What about backing up my environments?
• Getting help and support
• What about the next version of my app and what happens to the old version and its data?
• How do I integrate my app with other apps Kwantu platform apps?
• How do I integrate my app with other systems internal and external to my organisation?
• How can other people use and change my application to suit their needs?
• Is there a path for me to benefit from enhancements and improvements that have been made to my app by others?
• How can I keep my data private from others who use my apps?
• What are the licensing implications of using apps developed by other people?
• How am I protected from changes that other people make to apps that I develop?
• How do I cope with performance and scaleability issues?
• How do I ensure availability of my apps to my organisation?
• How am I protected from large workload impact of other users, or peak load usage?
• How do I calculate the relative cost to benefit ratio of using the Kwantu platform?
• How am I protected from redevelopment shock caused by obsolescence of components of the stack?