Modeling and Verifying Timed Compensable Workflows and an Application to Health Care

Mashiyat, Ahmed Shah; Rabbi, Fazle; MacCaull, Wendy

doi:10.1007/978-3-642-24431-5_18

Cited by 5 publications

(2 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As Figure 5A depicts, the methods use 14 different languages to represent the processes. In particular, S15, S27, and S32 use Abstract State Machines (ASM); 125 S13 uses Answer Set Programming (ASP); 121 S14 uses Composition Tree (CT) notation; 126 S9 uses Time Compensable Workflow Modeling Language (CWMLT); 127 S12 uses Foundational Subset for Executable UML Models (fUML); 128 S22 uses MSC; 93 S21, S24, S26, S30, S31, and S34 use Web Ontology Language (OWL); 129 S17 uses Petri net; S16 uses Business Process Management Notation (BPMN); 116 S20 uses Satisfiability Modulo Theories (SMT); 130 S1 uses Process Programming & Tailoring (ProcePT); 72 S6, S7, S19, S23, S25, S28, S29, S33, S37, S38, S39, and S40 use SPEM 2.0; 115 S2, S3, S4, S5, S8, S10, S11, S18, S35, and S41 use UML; 131 and finally, S36 uses OASIS eXtensible Access Control Markup Language (XACML) 132 . It is important to note that models created in OWL and UML could also be considered as new languages.…”

Section: Resultsmentioning

confidence: 99%

Compliance checking of software processes: A systematic literature review

Ardila

Gallina

Muram

2022

J Software Evolu Process

View full text Add to dashboard Cite

The processes used to develop software need to comply with normative requirements (e.g., standards and regulations) to align with the market and the law. Manual compliance checking is challenging because there are numerous requirements with changing nature and different purposes. Despite the importance of automated techniques, there is not any systematic study in this field. This lack may hinder organizations from moving toward automated compliance checking practices. In this paper, we characterize the methods for automatic compliance checking of software processes, including used techniques, potential impacts, and challenges. For this, we undertake a systematic literature review (SLR) of studies reporting methods in this field. As a result, we identify solutions that use different techniques (e.g., anthologies and metamodels) to represent processes and their artifacts (e.g., tasks and roles). Various languages, which have diverse capabilities for managing competing and changing norms, and agile strategies, are also used to represent normative requirements. Most solutions require tool‐support concretization and enhanced capabilities to handle processes and normative diversity. Our findings outline compelling areas for future research. In particular, there is a need to select suitable languages for consolidating a generic and normative‐agnostic solution, increase automation levels, tool support, and boost the application in practice by improving usability aspects.

show abstract

Section: Resultsmentioning

confidence: 99%

Compliance checking of software processes: A systematic literature review

Ardila

Gallina

Muram

2022

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…Duration is the time span required to finish a task. In [18] we incorporated time in Nova Workflow and presented the formal semantics of Timed Compensable WorkFlow Nets. The workflow in Fig.…”

Section: Dynamic Task Schedulingmentioning

confidence: 99%

T □: A Domain Specific Language for Rapid Workflow Development

Rabbi

MacCaull

2012

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. In MDE, software systems are always synchronized with their models since changes are made first to the model whenever there are changes in the requirement specifications. While MDE has a lot of potential, it requires maturity and tool support. In this research we present a framework for a workflow management system based on the MDE approach. We propose a domain specific language, T (T-Square) for rapidly specifying details of (workflow) tasks and their associated user interfaces which may be used with the NOVA Workflow, an executable workflow management system. T includes syntax for writing procedural statements, for querying an ontology, for declaring user interfaces, for applying access control policy, and for scheduling tasks, using Xtext to write the grammar. We apply transformation methods, based on Xtend, to generate executable software from the abstract task specifications. A running example from health services delivery illustrates the usefulness of this approach.

show abstract

NOVA Workflow: A Workflow Management Tool Targeting Health Services Delivery

MacCaull

Rabbi

2012

Foundations of Health Informatics Engineering and Systems

View full text Add to dashboard Cite

Modeling and Verifying Timed Compensable Workflows and an Application to Health Care

Cited by 5 publications

References 15 publications

Compliance checking of software processes: A systematic literature review

Compliance checking of software processes: A systematic literature review

T □: A Domain Specific Language for Rapid Workflow Development

NOVA Workflow: A Workflow Management Tool Targeting Health Services Delivery

Contact Info

Product

Resources

About