UML 1.4 versus UML 2.0 as Languages to Describe Software Architectures

Pérez, José Pedro López; Sierra-Alonso, Almudena

doi:10.1007/978-3-540-24769-2_7

Cited by 15 publications

(9 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Adaptations are defined by stereotypes that are grouped in a profile. • The 'heavyweight' extension [1,26,27] allows modifications on the existing meta-models and creates new ones or replaces existing semantics by modifying the metamodel of UML.…”

Section: Umlmentioning

confidence: 99%

MeidyaCoM‐policy: Approach for modelling and checking repair policies for self‐healing systems

2021

View full text Add to dashboard Cite

The architecture of distributed systems is subject to certain failures: component failure, downed connections etc. These failures come from the dynamicity and complexity of these systems. As a solution to cure this weakness, adaptation plans can be added. However, the main difficulty of self-adaptation emerges while considering the soundness of the adaptation and preservation of stylistic constraints of the system. The MeidyaCoM-Policy, an architecture-centric approach for modelling and checking repair policies to guarantee the success of the adaptation, is presented. This approach is a solution for applying self-healing. A new unified modelling language (UML) profile that provides a visual notation for modelling repair policies is proposed to automatically transform UML models to Z notation using transformation rules coded in eXtensible styles language transformation (XSLT) language. These specifications are implemented under the Z/ EVES theorem prover to prove specification soundness and consistency to guarantee the success of the adaptation. MeidyaCoM-Policy applies to all architectural styles. It is instantiated for the publish/subscribe style and illustrated with a case study. An outline of the developed software environment is provided.This is an open access article under the terms of the Creative Commons Attribution License, which permits use, distribution and reproduction in any medium, provided the original work is properly cited.

show abstract

Section: Umlmentioning

confidence: 99%

MeidyaCoM‐policy: Approach for modelling and checking repair policies for self‐healing systems

2021

View full text Add to dashboard Cite

show abstract

“…Researches that focus on UML architecture modeling [39] can be divided into two classes. The first called As Is [40].…”

Section: Related Workmentioning

confidence: 99%

“…The adaptations are defined by stereotypes which are grouped in a profile. The heavyweight extensibility [39,42], is handled through the MOF (Meta Object Facility). This approach allows modifications on the existing meta-models and creates new ones with no restrictions.…”

Section: Related Workmentioning

confidence: 99%

Modeling and enforcing invariants of dynamic software architectures

2010

View full text Add to dashboard Cite

In this paper, we propose an "end-to-end" approach that supports dynamic reconfiguration of software architectures taking advantage of graphical modeling, formal methods and aspect-oriented programming. There are three ingredients of the proposal. The specification end of the solution is covered by a new UML profile enabling to specify the desired architectural style (model), its invariants and the intended reconfiguration operations. In order to verify the consistency of the model and the preservation of the invariants after every reconfiguration, we automatically generate formal specifications in Z notation from the defined model. At the runtime enforcing end of the solution, we propose to encode the enforcement logic as aspect in the AspectJ language. The third important ingredient that makes our approach end-toend is the automatic translation of formal specifications into aspect-based enforcement code.

show abstract

“…One of the difficulties in using UML to model the architecture of large systems is the fact that the links in connection, activity, or sequence diagrams are regarded as representing message passing or method calls. Although UML 2.0 makes it easier to adopt an architectural style using UML, this is still a problem (Perez-Martinez and Sierra-Alonso, 2004). An alternative to POSD could be Jackson's Frame Diagrams (Jackson, 2001), although these are designed for the modelling of a problem domain rather than the structure of a solution.…”

Section: Modellingmentioning

confidence: 99%

On the architecture and form of flexible process support

Snowdon

Warboys

Greenwood

et al. 2006

Softw Process Imprv Pract

View full text Add to dashboard Cite

The ability of businesses to develop is frequently hampered by difficulties in changing underlying software systems. An example is the need to change when business partnerships are formed, or dissolved. This article is concerned with the architecture of business process support systems in the context of change, and particularly with the need for such systems to facilitate software change. The viable system model (VSM) is a cybernetic model of organisations that change. It provides an inclusive architecture in which both operational and development components are described within an organisation. This article illustrates, through a business supply chain example, the use of the VSM as an architecture for flexible process support systems. This architecture is systemic and inclusive: it incorporates the ongoing development of both the business and its underlying software.

show abstract

UML 1.4 versus UML 2.0 as Languages to Describe Software Architectures

Cited by 15 publications

References 10 publications

MeidyaCoM‐policy: Approach for modelling and checking repair policies for self‐healing systems

MeidyaCoM‐policy: Approach for modelling and checking repair policies for self‐healing systems

Modeling and enforcing invariants of dynamic software architectures

On the architecture and form of flexible process support

Contact Info

Product

Resources

About