Mission of HOPE
We aim at narrowing the semantic gap by adding richer features to process modeling. Top-down meets bottom-up.
The jABC4 GUI
The browser area (top left) shows the projects, the process models (SLGs) , and services/components. In the inspector area (bottom left) information for the selected activity or SLG is shown and may be edited. The graph canvas (right) is the modeling area.
Create, store, pass and plug’n’play higher-order processes.
Processes support Generics (i.e. parametric polymorphy), so that the same process may be reused in different scenarios.
In order to shield the application expert from the complexity of advanced modeling features (e.g. generics, types, data-flow) it is possible to create new components (classes of activities) via preconfiguration of existing ones.
Unpredicted hurdles in dealing with integration, variability, and interoperability in software development can be overcome via higher-order process engineering. Even in its simplicity-oriented, tamed form, this approach fosters a powerful plug&play discipline, where processes and services are created, stored, passed,
Modern object-oriented programming languages like Java, C#, and Scala have a feature known as parametric polymorphy in type theory. In all three languages this feature is called generics. The HOPE approach interprets processes as a special form of functions reminiscent
In order to shield the modeler from the complexity of features like higher-order, static typing, and generics we provide a preconfiguration feature. Nearly everything (except the control-flow of a process) can be configured, including names, generics, types, context variables, the
jABC4 is the incarnation of HOPE and is available for download.
The modeling environment comes with an entry level project in the Chainreaction domain!
jABC3 and before…
The jABC framework and its ancestor Agent Building Center (ABC) have a long and successful history. The button will lead you to the project page of the predecessor jABC3