The FlexoBPM analysis and documentation path is dedicated to business users and managers. The FlexoBPM rapid prototyping provides the structure and tools to define, optimize and reengineer business processes. This can be a goal in itself (e.g. compliance or IT governance requirements) or this analysis can be used as a base. for application development with or without the FlexoBPM Tools.

A short initial training is sufficient for Business analysts to become fully autonomous.

Needed tools : FlexoBPM Business - FlexoBPM Server

STEP 1 Scope and architecture definition

The very first action of any process modelling requires defining its scope with the people involved and all significant aspects such as security, control, IT infrastructure and planning.

Depending on the objective of the project a system architect may be involved to provide guidelines on the associated IT architecture.

STEP 2 Iterative process analysis and prototyping

This analysis phase starts by modelling the process and its interaction with the various actors whether human or existing IT solutions. Screens may be added specifying the users interactions, generating a first functional prototype with its associated documentation for validation. Every object in the model can indeed be documented in different ways for various specification types.

Each iteration generates a new prototype and a new documentation as a basis for the next meeting possibly involving newcomers to validate the latest requests. This concrete way of proceeding keeps the team highly motivated and productive. Furthermore, this collaborative effort naturally leads to rapid improvements of the process.

STEP 3 Business data flow definition

If the process interacts with existing or new data flows and the skills are available to define a basic data access model, then it can already be inserted into the project and connected to the screen layer.

It is also possible to import existing data model and web services definition.

STEP 4 Prototype and documentation delivery

After successive iterations and meetings where the participants remain motivated and actively involved, a dynamic prototype is delivered with different specific customized documentation (e.g. Business, Functional or Technical).

These deliverables can be used to go on with the FlexoBPM approach or they can be transferred to a non-FlexoBPM development team. They will be amazed by the precision and the utility of the FlexoBPM deliverables.