Creating a Cloud system in one hour using Google DOCS spreadsheets

Creating a Harmony system in one hour

Demonstrating the power ofHarmony

Delivering a Proof-of-Concept (PoC)

Our (new) customer created a flowchart

We converted this to a Lucid Chart flowchart

We generated the Harmony application

• Importing the LucidChart flowchart• The application/system was generated– In 1 minute

And• a Harmony configuation (the “source”

file) was shared via Google DOCS

• Next step: – running the application

About the generated application

• It generated all process (workflow) steps• Using decisions

– controlling the workflow• It generated two database files

– Customer & Product• Using the definition in the flowchart

– One sample entry (record) in each file

• With Harmony comes pre-defined & auto generated:– User groups/authorization [sheets]– Decision support [user interface (UI)– History overview (UI showing all completed steps)

Running the generated application 1st stepCustomer registration

Step 2Product specification

Etc, etc

• It will run all process (workflow) steps – We check with customer– and change the configuration

• About the modified configuration– because this is stored in Google DOCS spreadsheet

format• it’s easy to understand, hence easy to change• It’s shared with the customer

– We created structures– Customer added data

– We added extra fields (data input) to the screens• Doesn’t make sense to specify this in flowchart (or other

diagramming tools)– etc

Modifying dialogs: how to• add more details to dialogs– is very simple to do

Defining the workflowcontrolling the dialog flow (sequence)

Create two expressions

• Expressions can be– Computation– Concatenations– etc

re-generate the application

• Application is generated – in one minute

• Check by running the application again

No changes in this user interface/dialog

If product exists -> create quote

• All decisions are displayed in decision support

Product does not exist -> different dialog & workflow step

• Determine product is required

forgot something ?

• The new version:

The workflow continues

Standard with Google maps integration

Added “conditionally displayed” fields

• Add rules that control which dialog items are displayed– If not satisfied: prompt “notes”

How to conditionally display fields

• Initially hide a dialog

• Create a rule

Some Notes

• Creating the flowchart was done by the customer– This gave us a pretty good idea of what he wanted (he also

shared some of his quote samples (i.e. “data”)• After creating a high-level flowchart we continued with

Harmony– Creating process details is much easier with Harmony …

using data to verify if the correct actions are taken!• Next steps involved:

– Verify with customer– Add Harmony building blocks (like generating and sharing

order quotes)– Create Testimony test.sheet (which is 5 min job)– Asking customer to enter test data and start testing

• Which is fully automated with Testimony

Some more info

• Lucidchart– flowchart (used in this PoC)– Lucidchart event driven modeling

• Get started– Creating Harmony applications• Step-by-step explanation

• YouTube Samples of Testing with Testimony