A Use-Case Driven Approach to Formal Service-Oriented Modelling

Bocchi, Laura; Fiadeiro, José Luiz; Lopes, Antónia

doi:10.1007/978-3-540-88479-8_12

Cited by 6 publications

(10 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some of the methodological aspects concerning SRML have been discussed in previous work [BLF08], which proposes a process to arrive at (formal) service models in SRML starting from informal (or semi-formal) specifications in notations that are typically described in UML. In Section 6.1 we use the extension of UML use-case diagrams presented in [BLF08] to capture requirements in a service-oriented scenario and derive the structure of SRML models.…”

Section: Methodology By Example -A Case Study Of Using Stpowla and Srmlmentioning

confidence: 99%

“…In Section 6.1 we use the extension of UML use-case diagrams presented in [BLF08] to capture requirements in a service-oriented scenario and derive the structure of SRML models.…”

Section: Methodology By Example -A Case Study Of Using Stpowla and Srmlmentioning

confidence: 99%

“…The outcome of this phase is a Use Case diagram. By using the mapping defined in [BLF08] it is possible to derive, from the diagram, the structure for a number of SRML modules where the orchestration and the behavoural specification of the external interfaces is left unspecified. An Eclipse plugin is currently under development to automate this transformation.…”

Section: Methodology By Example -A Case Study Of Using Stpowla and Srmlmentioning

confidence: 99%

“…The requirements are expressed in Figure 8. Figure 8 uses the notation for use-case diagrams proposed in [BLF08]. The customized icons represent different types of roles that an actor can have in a service-oriented context (e.g., dynamically discovered services, statically bound persistent resources, service requester, etc.…”

Section: Use Case Driven Examplementioning

confidence: 99%

See 3 more Smart Citations

From StPowla processes to SRML models

Bocchi

Gorton²,

Reiff-Marganiec

2010

Form. Asp. Comput.

Self Cite

View full text Add to dashboard Cite

Abstract. Service Oriented Computing is a paradigm for developing software systems as the composition of a number of services. Services are loosely coupled entities, that can be dynamically published, discovered and invoked over a network. The engineering of such systems presents novel challenges, mostly due to the dynamicity and distributed nature of service-based applications. In this paper, we focus on the modelling of service orchestrations. We discuss the relationship between two languages developed under the SENSORIA project: SRML as a high level modelling language for Service Oriented Architectures, and STPOWLA as a process-oriented orchestration approach that separates core business processes from system variability at the end-user's level, where the focus is towards achieving business goals. A fundamental challenge of software engineering is to correctly align business goals with IT strategy, and as such we present an encoding of STPOWLA to SRML. This provides a formal framework for STPOWLA and also a separated view of policies representing system variability that is not present in SRML.

show abstract

Section: Methodology By Example -A Case Study Of Using Stpowla and Srmlmentioning

confidence: 99%

“…In Section 6.1 we use the extension of UML use-case diagrams presented in [BLF08] to capture requirements in a service-oriented scenario and derive the structure of SRML models.…”

Section: Methodology By Example -A Case Study Of Using Stpowla and Srmlmentioning

confidence: 99%

Section: Methodology By Example -A Case Study Of Using Stpowla and Srmlmentioning

confidence: 99%

Section: Use Case Driven Examplementioning

confidence: 99%

See 2 more Smart Citations

From StPowla processes to SRML models

Bocchi

Gorton²,

Reiff-Marganiec

2010

Form. Asp. Comput.

Self Cite

View full text Add to dashboard Cite

show abstract

“…In many places, different diagrams can be useful, and you shouldn't hesitate to use a non-UML diagram if no UML diagram suits your purpose" [6]. Motivated by the development of use-case extensions for the SENSORIA Reference Modelling Language (SRML) [2], we employ use cases to depict Cases and Actor as Role elements. A use-case diagram describes "who the relevant users will be, the services they require of the system and the services they need to provide to the system" [10].…”

Section: Modelling Notationmentioning

confidence: 99%

Formal Visual Modelling of Human Agents in Service Oriented Systems

Donyina

Heckel

2009

2009 Fourth South-East European Workshop on Formal Methods

View full text Add to dashboard Cite

When the level of granularity of services approaches that of business activities, humans become part of a serviceoriented system not just as users but as providers of services. A model of such a system has to take into account the characteristics of human actors as service providers. Conversely, in the world of agent-based systems, software components have been attributed with human properties such as reactivity, autonomy and proactivity. We believe that modelling techniques developed for software agents are a valid starting point for specifying human agents in service-oriented systems (HASOS). In particular, we extend UML use case and class diagrams by concepts of rolebased access control (RBAC) and use graph transformation (GT) rules to model changes to data as well as the dynamic (re-)assignment of roles played by human actors. From these models we can derive specifications of the services required systematically in terms of pre-and post-conditions as well as communication scenarios modelling their interactions. We use the formal framework provided by GT to formalize consistency relations between the different parts of these models. The technique will be demonstrated with the use of a pharmacy scenario.

show abstract

A Model for Dynamic Reconfiguration in Service-Oriented Architectures

Fiadeiro

Lopes

2010

Software Architecture

View full text Add to dashboard Cite

The importance of modelling the dynamic architectural characteristics of software systems has long been recognised. However, the nature of the dynamic architectural characteristics of service-oriented applications goes beyond what is currently addressed by existing architecture description languages (ADLs). At the heart of the service-oriented approach is the logical separation of service need from the need-fulfillment mechanism, i.e., the service provider: the binding between the two is deferred to runtime and established at the instance level, i.e. each time the need for the service emerges. In this paper we present an architecture-oriented model for dynamic reconfiguration that paves the way for the definition of ADLs that are able to address the specification of dynamic architectural characteristics of service-oriented applications.

show abstract

A Use-Case Driven Approach to Formal Service-Oriented Modelling

Cited by 6 publications

References 14 publications

From StPowla processes to SRML models

From StPowla processes to SRML models

Formal Visual Modelling of Human Agents in Service Oriented Systems

A Model for Dynamic Reconfiguration in Service-Oriented Architectures

Contact Info

Product

Resources

About