2012
DOI: 10.1007/978-3-642-29133-3_1
|View full text |Cite
|
Sign up to set email alerts
|

The Subject-Oriented Approach to Software Design and the Abstract State Machines Method

Abstract: Abstract. In [33, Appendix] we have shown that the system which implements the Subject-oriented approach to Business Process Modeling (S-BPM) has a precise semantical foundation in terms of Abstract State Machines (ASMs). The construction of an ASM model for the basic S-BPM concepts revealed a strong relation between S-BPM and the ASM method for software design and analysis. In this paper we investigate this relation more closely. We use the analysis to evaluate S-BPM as an approach to business process modeli… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2013
2013
2019
2019

Publication Types

Select...
3
2

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(2 citation statements)
references
References 43 publications
(58 reference statements)
0
2
0
Order By: Relevance
“…A subject-oriented-or resource-based-modeling language for business processes is S-BPM [28] [29], which is discussed later. As the modeling language is based on process-calculus, it can be easily defined via an ASM ground model [28], and models can be executed on a corresponding ASM interpreter [30].…”
Section: Abstract State Machine (Asm)mentioning
confidence: 99%
“…A subject-oriented-or resource-based-modeling language for business processes is S-BPM [28] [29], which is discussed later. As the modeling language is based on process-calculus, it can be easily defined via an ASM ground model [28], and models can be executed on a corresponding ASM interpreter [30].…”
Section: Abstract State Machine (Asm)mentioning
confidence: 99%
“…Processes are hosted on an instance of the Workflow Manager (WFM), which is responsible for the hosting, administration and configuration of the subjects based on scopes, such as a Company Scope (1), Process Scopes (2) and a Management Scope (3). Each company has its own Process Store (4) and Subject Store (5); the same for Message Store (6) and Task Store (7). Each company has Task Handler (9) instances to generate new tasks and each process has Message Handler (8) instances to manage message exchange.…”
Section: Architecturementioning
confidence: 99%