A refinement-based approach for building valid SOA design patterns (original) (raw)

An Approach for Modeling and Formalizing SOA Design Patterns

2013 Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2013

Although design patterns has become increasingly popular, most of them are presented in an informal way, which can give rise to ambiguity and may lead to their incorrect usage. Patterns proposed by the SOA design pattern community are described with informal visual notations. Modeling SOA design patterns with a standard formal notation contributes to avoid misunderstanding by software architects and helps endowing design methods with refinement approaches for mastering system architectures complexity. In this paper, we present a formal architecture-centric approach that aims, first, to model message-oriented SOA design patterns with the SoaML standard language, and second to formally specify these patterns at a high level of abstraction using the Event-B method. These two steps are performed before undertaking the effective coding of a design pattern providing correct by construction patternbased software architectures. Our approach is experimented through an example we present in this paper. We implemented our approach under the Rodin platform, which we use to prove model consistency.

Towards an approach for modeling and formalizing SOA design patterns with Event-B

Proceedings of the 28th Annual ACM Symposium on Applied Computing - SAC '13, 2013

This paper introduces a formal architecture-centric approach, which allows first to model message-oriented SOA design patterns with the SoaML standard language, and second to formally specify these patterns at a high level of abstraction using the Event-B method. These two steps are performed before undertaking the effective coding of a design pattern providing correct by construction pattern-based software architectures. We implement our approach under the Rodin platform which we use to prove model consistency.

Using SoaML Models and Event-B Specifications for Modeling SOA Design Patterns

Although design patterns have become increasingly popular, most of them are presented in an informal way. Patterns, proposed by the SOA design pattern community, are described with a proprietary informal notation, which can raise ambiguity and may lead to their incorrect usage. Modeling SOA design patterns with a standard formal notation avoids misunderstanding by software architects and helps endow design methods. In this paper, we present an approach that aims, first, to model message-oriented SOA design patterns with the SoaML language, and second to transform them to Event-B specifications. These two steps are performed before undertaking the effective coding of a design pattern providing correct by construction pattern-based software architectures. Our approach is enhanced with a tool supporting it. Specification results are imported under the Rodin platform which we use to prove model consistency.

Modeling and refinement SOA design patterns with Event-B method

2012

Using design patterns has become increasingly popular. Most design patterns are proposed in an informal way, which can give rise to ambiguity and may lead to incorrect usage. Patterns, proposed by the SOA design pattern community, are described with an appropriate notation. So they require modeling with a standard notation and then formalization. In this paper, we propose a formal architecture-centric approach that aims rst to model message-oriented SOA design patterns with the SoaML standard language and second to formally specify these patterns at a high level of abstraction using the Event-B language. These two steps are performed before undertaking the eective coding of a design pattern providing correct by design solutions. Our approach is experimented through an example we present in this paper. We implemented our approach under the Rodin platform which we use to prove model consistency.

Modeling and renement SOA design patterns with Event-B method

2015

Abstract. Using design patterns has become increasingly popular. Most design patterns are proposed in an informal way, which can give rise to ambiguity and may lead to incorrect usage. Patterns, proposed by the SOA design pattern community, are described with an appropriate nota-tion. So they require modeling with a standard notation and then formal-ization. In this paper, we propose a formal architecture-centric approach that aims rst to model message-oriented SOA design patterns with the SoaML standard language and second to formally specify these patterns at a high level of abstraction using the Event-B language. These two steps are performed before undertaking the eective coding of a design pattern providing correct by design solutions. Our approach is experi-mented through an example we present in this paper. We implemented our approach under the Rodin platform which we use to prove model consistency. 1

One approach to partial formalization of SOA design patterns using production rules

2012 Federated Conference on Computer Science and Information Systems, 2012

Service oriented architecture (SOA) is nowadays one of the dominant styles in developing new information systems. These information systems often have complex models, which can contain mistakes, or are described by informally. In order to minimize mistakes and to create formal models, patterns as components of software development could be used-according to Model driven development (MDD) principles. Design patterns in SOA have been identified by T. Erl [1]. However, they are represented in form which is suitable for humans, but not for computers. In context of machine processing formal representation of patterns would be advantageous. In this paper we present our approach to partial formal representation of SOA design patterns using production rules. This partial formal representation is useful in searching for mistakes (antipatterns) in models and will enable creating formal models (with patterns) from informal documents.

Transformation of compound SOA Design Patterns

Procedia Computer Science, 2017

Software Design Patterns provide architects and developers with reusable software elements helping them to master building complex software systems. In real applications, problems are complex and their solutions can be represented by compound patterns that require the combination and reuse of two or more design patterns. In this paper, we propose a transformation approach of compound SOA design patterns based on two types of transformations. The first type, is an M2M (Model to Model) transformation. It allows to transform SOA design patterns modeled with the semi-formal SoaML language and linked together with composition operators to a compound pattern. The second type, is an M2T (Model to Text) transformation. It allows to transform compound pattern model to Event-B specifications. So, the compound pattern will have a graphic representation and a formal description.

A Formal Approach to Design Pattern Definition & Application

1995

In this paper we present a formal approach to de ne and apply design patterns that is both process-and reuse-oriented. Initially we use a process program based on design pattern primitive tasks or constructors to describe how to instantiate a pattern. As we develop the patterns we introduce a formal model for the interconnected objects that constitute the instantiation. The formal model which is based on Abstract Data Views divides designs into both objects and views in order to maintain a separation of concerns. We have chosen a formal model for pattern de nition and application since it allows us to specify the steps in pattern instantiation unambiguously and to reason about the completed design. Furthermore, a formal statement of the application of a design pattern can provide the foundation on which to build tools to assist the programmer in code generation.

Design Patterns Formal Composition and Analysis

International Journal of Information Technologies and Systems Approach

Informal description of design patterns was adopted to facilitate their understanding by software developers. However, these descriptions lead to ambiguities limiting their successful use in real applications. Recently, several formal methods have been employed to guarantee precise specification of design pattern elements without insisting on their behavior. The main goal of this article is to propose a rewriting logic-based framework for enhancing formal description and reasoning on design patterns composition. The proposed model is integrated and executed under Maude using K-Maude tool. It allows first to associate a meta model notation, according to MDA approach, to all design patterns elements and then, a Maude semantic basis for specifying both their structural and dynamic aspects, is given. In particular, it will be shown how the…

Modest Formalization of Software Design Patterns

Formalization is the document form of formalism, where the practical compositional elements are represented by the symbols and variables. The Software Requirement Specification is documented in such a way that it breaks the deliverables into smaller components. Design patterns are among the most powerful methods for building large software systems. Patterns provide well-known solutions to recurring problems that developers face. Predicate logic is used for describing the formal specification of the design patterns. In this paper we urge to explain that formal specification of design patterns is very essential before they are implemented in any platform, further the formal specification of the design pattern is derived into a formula with respect to the application of the domain. In this paper we state some of the illustration to understand the concept of the formal specification and formula and we call this Modest Formalization of Software Design Patterns.