LePUS3: An Object-Oriented Design Description Language

Gasparis, Epameinondas; Nicholson, Jonathan; Eden, Amnon H.

doi:10.1007/978-3-540-87730-1_37

Cited by 18 publications

(15 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There are some well-proven approaches [4] based on Gamma et al However, this kind of techniques does not allow to achieve the high degree of pattern structure flexibility which is required to reach our target. The framework promoted by LePUS [9] is interesting but the degree of expressiveness proposed to design a pattern is too restrictive. The major concern of [22] is how to exploit security analysis patterns during the security engineering analysis, an important issue but out of the scope of our paper.…”

Section: Related Workmentioning

confidence: 99%

“…In the same way, RBML(Role-Based Meta modeling Language) [18] is able to capture various design perspectives of patterns such as static structure, interactions, and state-based behavior. The framework LePUS [9] offers a formal and visual language for specifying design patterns. It defines a pattern in an accurate and complete form of formula with a graphical representation.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Enforcing S&D Pattern Design in RCES with Modeling and Formal Approaches

Hamid

Gürgens

Jouvray

et al. 2011

Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

Abstract. The requirement for higher security and dependability of systems is continuously increasing even in domains not traditionally deeply involved in such issues. Yet, evolution of embedded systems towards devices connected via Internet, wireless communication or other interfaces requires a reconsideration of secure and trusted embedded systems engineering processes. In this paper, we propose an approach that associates model driven engineering (MDE) and formal validation to build security and dependability (S&D) patterns for trusted RCES applications. The contribution of this work is twofold. On the one hand, we use model-based techniques to capture a set of artifacts to encode S&D patterns. On the other hand, we introduce a set of artifacts for the formal validation of these patterns in order to guarantee their correctness. The formal validation in turn follows the the MDE process and thus links concrete validation results to the S&D requirements identified at higher levels of abstraction.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Enforcing S&D Pattern Design in RCES with Modeling and Formal Approaches

Hamid

Gürgens

Jouvray

et al. 2011

Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

show abstract

“…However, instead of checking architecture intent, LePUS focuses on the specification of programming protocols, such as forward (that holds when the formal arguments of a method are used to call a method with the same signature) and produce (a special kind of create in which the new object is used in a return statement). The language also includes a visual version, called LePUS3 [GNE08].…”

Section: Architecture Conformance Techniques and Toolsmentioning

confidence: 99%

Architecture Conformance Checking in Dynamically Typed Languages.

Miranda¹,

Rodrigues²,

Valente³

et al. 2016

JOT

View full text Add to dashboard Cite

Architectural erosion is a recurrent problem faced by software architects, which might be even more severe in systems implemented in dynamically typed languages. The reasons are twofold: (i) some features provided by such languages make developers more propitious to break the planned architecture (e.g., dynamic invocations and buildings), and (ii) the developers' community lacks tool support for monitoring the implemented architecture. To address these shortcomings, this paper presents an architectural conformance and visualization approach based on static code analysis techniques and on a lightweight type propagation heuristic. The central idea is to provide the developers' community with means to control the architectural erosion process by reporting architectural violations and visualizing them in high-level architectural models, such as reflexion models and DSMs. This paper also describes a tool-called ArchRuby-that implements our approach. We evaluate our solution in three real-world systems identifying 48 architectural violations of which the developers had no prior knowledge. We also measure the effectiveness of our type propagation heuristic reporting that (i) the number of analyzed types raises 5% on the average and (ii) certain violations are only detected due to our heuristic.

show abstract

“…The template is augmented with UML notations for the solution and with formal artifacts for the requirement properties. Another approach [7] provides a formal and visual language for specifying design patterns called LePUS. It defines a pattern in an accurate and complete form of formula in Z, with a graphical representation.…”

Section: Related Workmentioning

confidence: 99%

A Modeling and Formal Approach for the Precise Specification of Security Patterns

Hamid

Percebois

2014

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Non-functional requirements such as Security and Dependability (S &D) become more important as well as more difficult to achieve. In fact, the integration of security features requires the availability of both application domain specific knowledge and security expertise at the same time. Hence, capturing and providing this expertise by the way of security patterns can support the integration of S&D features by design to foster reuse during the process of software system development.The solution envisaged here is based on combining metamodeling techniques and formal methods to represent security pattern at two levels of abstraction fostering reuse during the process of pattern development and during the process of pattern-based development. The contribution of this work is twofold: (1) An improvement of our previous pattern modeling language for representing security pattern in the form of a subsystem providing appropriate interfaces and targeting security properties, (2) Formal specification and validation of pattern properties, using the interactive Isabelle/HOL proof assistant. The resulting validation artifacts may mainly complete the definitions, and provide semantics for the interfaces and the properties in the context of S&D. As a result, validated patterns will be used as bricks to build applications through a Model-Driven engineering approach.Keywords: Pattern, Metamodel, Domain, Formalization, Model-Driven engineering, Security. IntroductionRecent times have seen a paradigm shift in terms of design by combining multiple software engineering paradigms, namely, Model-Driven Engineering (MDE) [20] and formal methods [25]. Such a paradigm shift is changing the way systems are developed nowadays, reducing development time significantly. Embedded systems [26] are a case where a range of development approaches have been proposed. The most popular are those using models as main artifacts to be constructed and maintained. In these approaches, software development consists of model specification and transformations. In addition to MDE, pattern-based development has gained more attention recently in software engineering by addressing new challenges that were not targeted in the past. In fact, they are applied in modern software architecture for distributed systems including middlewares, real-time embedded systems, and recently in security and dependability engineering.Unfortunately, most of security patterns are expressed as informal indications on how to solve some security problems, using template like traditional patterns [1,6]. These patterns do not include sufficient semantic descriptions, including those of security and dependability concepts, for automated processing within a tool-supported development and to extend their use. Furthermore, due to manual pattern implementation, the problem of incorrect implementation (the most important source of security problems) remains unsolved. For that, model driven software engineering can provide a solid basis for formulating design patterns that can incorp...

show abstract

LePUS3: An Object-Oriented Design Description Language

Cited by 18 publications

References 2 publications

Enforcing S&D Pattern Design in RCES with Modeling and Formal Approaches

Enforcing S&D Pattern Design in RCES with Modeling and Formal Approaches

Architecture Conformance Checking in Dynamically Typed Languages.

A Modeling and Formal Approach for the Precise Specification of Security Patterns

Contact Info

Product

Resources

About