Interactive Behavior-driven Development: a Low-code Perspective

This file contains instructions for launching the demo from the paper:

Interactive Behavior-driven Development: a Low-code Perspective. Nitish Patkar, Andrei Chiş, Nataliia Stulova, Oscar Nierstrasz. In 2nd LowCode Workshop of the MODELS'21 conference, focusing on Modeling in Low-Code Development Platforms

Publication access: see it on IEEE, download an author's copy as a PDF, or cite as .bib

Original instuctions source: figshare

Step 1

Download and open the latest image of the Glamorous toolkit from their official homepage. Open a Playground and execute the following script.

Metacello new
    baseline: 'MyMoldableRequirements';
    repository: 'github://nitishspatkar/moldable-requirements:scheduling’;
    load 

Step 2:

To verify the average number of lines of code to define a view in an image: open a Playground and execute

#gtView gtPragmas.

The returned object has a “Metrics” view that shows the average number of lines of code of view methods.

Step 3

To verify Figure 3 in the paper, you need to run a specific example. There are two ways to run that example:

• Alternative 1: Open another Playground and type:

MyProject

and click on the inspect button.
An object inspector window will open.
Navigate to the tab “Examples map” and run the example:

gtParseJSONExample

• Alternative 2: type:

gtParseJSONExample

in Spotter and run the example from there.

This would load a list of four sample projects, the last being “Hospital management system.”
When you double-click on it, it will open corresponding epics.
When you double-click one of the epics, it should open corresponding user stories.

Step 4:

To verify Figure 4 in the paper, kindly type brows the class "RMInvoice" and navigate to the tab "Parameterized examples". Click on "Order item with price and tax". After filling all the required details, kindly click "Run".

Similarly, to verify Figure 5, click on "Create an invoice with order items with regular or reduced tax rates". After filling all the required details, kindly click "Run".

Finally, to verify Figure 7, simply navigate to the tab "Path" from the previous step.