Formal Verification for Feature-Based Composition of Workflows

Declarative GUIs

“…The function argument determines the next step based on the inputs provided by the user. 5 Finally, the simple constructor represents a basic step in the process, which consists of a message to display and a business model that is the next step in the process. A value of type BusinessModel can be translated into a GUI using the following function.…”

“…The following three lines define the final discharge step and two of the simple steps that precede it. 5 The repository contains a more advanced variant where the input constructor also accepts an input validation function. The resulting GUI application will then validate its inputs; if validation fails, the validation function specifies an error message to display and the application will return to the input form.…”

“…Such properties include data-dependent reachability and unreachability constraints for GUIs generated from declarative business process specifications. In another paper [5], we have adapted the current framework to allow the specification and verification of feature-based composition of workflows implemented as a feature-oriented software product line [10]. The framework allows the modular definition of features and promotes the separation of concerns in workflow definitions.…”