Appl/A

Abstract

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Formalizing Rework in Software Processes

“…Many process languages and workflow languages offer some form of control abstraction with invocation semantics. Some of these are drawn directly from conventional programming languages, for example, HFSP [27], which is based on a functional computational model, and APPL/A [40], which incorporates and extends Ada control abstractions and invocation semantics.…”

“…This can be interpreted as a kind of rework, even if the transaction is atomic and the results of the earlier execution are obviated. Apart from the languages that support work contexts, several others have transactional notions, including AP5 [16], Marvel [26], and APPL/A [40]. HFSP [42] supports rework directly with a redo clause which can be used to indicate reinstantiation of a step with different parameters.…”

“…4 With Little-JIL, for example, a step introduces pre-and postrequisites, substeps and their control flow, reactions and exception handlers, and resource and data parameters. A language like APPL/A [40], which is based closely on a general-purpose programming language, has the sorts of scoping constructs that one would expect in a general-purpose programming language, such as packages and subprograms.…”

“…In Little-JIL, steps define a strictly local scope for data and a hierarchical scope for exception handlers and execution agents. Languages based directly on general-purpose programming languages or paradigms, such as APPL/A [40] and HFSP [27], can adopt scoping rules from those approaches. Many flow-graph and Petri-net based languages allow for hierarchical scoping of contexts by nesting [7,18,31,12].…”

“…These can be used to reflect the "state" of the artifact, including its state with respect to rework (for example, whether it is "complete", "outdated", "under revision", and so on). A few languages offer full data modeling capabilities (for example, APPL/A [40] and FUNSOFT Nets [18]), thus allowing the definition of rework processes based on details of the data affected.…”