Activity Graphs and Processes

Bolton, Christie; Davies, Jim

doi:10.1007/3-540-40911-4_6

Cited by 17 publications

(17 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Similar work has been undertaken by others (see e.g., [NB02,BD00]) by integrating parts of UML and CSP. Although the integration step is different, the motivation is quite similar: CSP serves as formal semantics to a non-formal graphical notation, and the graphical notation provides a user-friendly front-end for CSP.…”

Section: Introductionmentioning

confidence: 72%

Formalising Behaviour Trees with CSP

Winter

2004

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Behaviour Trees is a novel approach for requirements engineering. It advocates a graphical tree notation that is easy to use and to understand. Individual requirements are modelled as single trees which later on are integrated into a model of the system as a whole. We develop a formal semantics for a subset of Behaviour Trees using CSP. This work, on one hand, provides tool support for Behaviour Trees. On the other hand, it builds a front-end to a subset of the CSP notation and gives CSP users a new modelling strategy which is well suited to the challenges of requirements engineering.

show abstract

Section: Introductionmentioning

confidence: 72%

Formalising Behaviour Trees with CSP

Winter

2004

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…A branching activity model is a tree or graph (Bolton and Davies 2000) where nodes are activities (also known as routines, business processes, or projects) and the edges represent an existential causal relationship between activities: e.g. A 2 is initiated-by…”

Section: Branching Activity Modelsmentioning

confidence: 99%

How Bad is it? – A Branching Activity Model to Estimate the Impact of Information Security Breaches

Thomas¹,

Antkiewicz²,

Florer³

et al. 2013

SSRN Journal

View full text Add to dashboard Cite

“…E.g., the research by Börger et al [BCR00c] defines a semantics by translating activity diagrams to abstract state machines. Bolton and Davies [BoD00] provide a formalization of activity diagrams using CSP.…”

Section: Related Workmentioning

confidence: 99%

Partial order semantics for use case and task models

2011

View full text Add to dashboard Cite

Abstract. Use case models are the specification medium of choice for functional requirements, while task models are employed to capture User Interface (UI) requirements and design information. In current practice, both entities are treated independently and are often developed by different teams, which have their own philosophies and lifecycles. This lack of integration is problematic and often results in inconsistent functional and UI design specifications causing duplication of effort while increasing the maintenance overhead. To address these shortcomings, we propose a formal semantic framework for the integrated development of use case and task models. The semantic mapping is defined in a two step manner from a particular use case or task model notation to the common semantic domain of sets of partially ordered sets. This two-step mapping results in a semantic framework that can be more easily reused and extended. The intermediate semantic domains have been carefully chosen by taking into consideration the intrinsic characteristics of use case and task models. As a concrete example, we provide a semantics for our own DSRG use case formalism and an extended version of ConcurTaskTrees, one of the most popular task model notations. Furthermore, we use the common semantic model to formally define a set of refinement relations for use case and task models.

show abstract

Activity Graphs and Processes

Cited by 17 publications

References 11 publications

Formalising Behaviour Trees with CSP

Formalising Behaviour Trees with CSP

How Bad is it? – A Branching Activity Model to Estimate the Impact of Information Security Breaches

Partial order semantics for use case and task models

Contact Info

Product

Resources

About