Safarchie Studio: ArgoUML Extensions to Build Safe Architectures

Barais, Olivier; Duchien, Laurence

doi:10.1007/0-387-24590-1_6

Cited by 13 publications

(15 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The dynamic structural verification consists of checking the compatibility between the newly connected ports, according to the definition of the port compatibility of SafArchie [14]. Concretely, based on transformation rules that have been applied, the analysis builds a list containing the newly created connections as well as the connections between ports that have been modified by the transformations.…”

Section: Dynamic Checksmentioning

confidence: 99%

“…In this section, instead of providing a catalogue of ADL characteristics, we focus on three significant directions for software architecture definitions: (i) the specification and the analysis of distributed software behaviour, illustrated with Darwin [7] and Wright [8], (ii) the strong link with the implementation, that may be found in ArchJava [9], Fractal [10] and Sofa [11], and (iii) the building of architecturedriven software development environment, as promoted by ArchStudio [12], AcmeStudio [13] and SafArchie [14]. Finally, we provide a short evaluation of these works against the evolution issue.…”

Section: Component-based Software Architecture: Concepts and Lacksmentioning

confidence: 99%

“…Finally, SafArchie [14] is an abstract component model for designing a software architecture. The SafArchie component model describes the structure of a piece of software in terms of components, ports, operations and bindings.…”

Section: Architecture Centric Integrated Development Environmentsmentioning

confidence: 99%

“…The diagram specifies that some component Cm1 must be connected to two other components Cm2 and Cm3. The remaining declarations define a series of placeholders for operations (line 3), specify whether these operations must be declared as provided or as required (lines 4-11) and specify that they must be associated with the ports pm1 to pm4 (lines [12][13][14][15]. Finally, lines [16][17][18][19] ensure that the operation opm1 is the inverse of operation opm5 in the bound port, and similarly for opm2 and opm6, opm3 and opm7, and opm4 and opm8.…”

Section: The Join Point Maskmentioning

confidence: 99%

See 3 more Smart Citations

Software Architecture Evolution

et al. 2008

Self Cite

View full text Add to dashboard Cite

show abstract

Section: Dynamic Checksmentioning

confidence: 99%

Section: Component-based Software Architecture: Concepts and Lacksmentioning

confidence: 99%

Section: Architecture Centric Integrated Development Environmentsmentioning

confidence: 99%

Section: The Join Point Maskmentioning

confidence: 99%

See 2 more Smart Citations

Software Architecture Evolution

et al. 2008

Self Cite

View full text Add to dashboard Cite

show abstract

“…The Transat framework consists of a tool called SafArchie Studio [Bar04a]This tool is an extension of ArgoUML, which offers several views of the evolution process depending on the kind of user.…”

Section: Transatmentioning

confidence: 99%

Prisma: aspect-oriented software architectures

Benedí¹

View full text Add to dashboard Cite

The complexity of current software systems and the fact that their non-functional requirements have become very relevant for the end-user are challenges to be faced in software development.In the last few years, these properties have increased the time and the staff required for the development and maintenance processes of software. As a result, there is greater interest in reducing the costs of these processes in complex software systems. In order to deal with these challenges, to achieve the milestones of software products, and to overcome the competitiveness of the market, this thesis presents a novel approach for developing complex software systems. This approach is called PRISMA.PRISMA is supported by a framework that consists of a model, a language, a methodology and a Computer-Aided Software Engineering (CASE) tool prototype. The PRISMA model combines two approaches to define software architectures: the Component-Based Software Development (CBSD) and the Aspect-Oriented Software Development (AOSD). The main contributions of the model are the way that it combines both approaches to take their advantages, and its formal language. PRISMA takes into account non-functional requirements from the early stages of the software life cycle and improves the reusability and maintenance of software by decomposing software systems using two different concepts: aspects and architectural elements (components and connectors).PRISMA provides a formal Aspect-Oriented Architecture Description Language (AOADL) for specifying aspect-oriented software architectures. Its AOADL is independent of technology and is based on formal languages and formalisms to preserve non-ambiguity in order to apply code generation techniques.The methodology that PRISMA proposes for developing software systems follows the Paradigm of Automatic Programming by applying the Model-Driven Development (MDD) approach. As a result, PRISMA provides traceability from the analysis and design stages of the software life cycle to the implementation stage, and provides mechanisms to improve the time and cost invested in the development and maintenance processes.iiThe PRISMA model and its methodology are supported by a CASE tool prototype called PRISMA CASE. This tool allows the specification of PRISMA architectures using its AOADL in a textual and a graphical way, the verification of PRISMA software architectures, and the automatic C# code generation thanks to the middleware and the code generation patterns that the CASE tool prototype integrates. Finally, PRISMA CASE provides a genericGraphical User Interface to execute PRISMA applications over .NET platform and to validate them.iii RESUMENHoy en día, la complejidad de los sistemas software y la gran relevancia que han adquirido los requisitos no funcionales son retos que han de abordarse durante el proceso de desarrollo software. En los últimos años, estas propiedades han provocado un gran incremento en el tiempo y el personal necesario para llevar a cabo los procesos de desarrollo y mantenimiento del so...

show abstract

The analysis of architectural languages for the needs of practitioners

Özkaya

2018

Softw Pract Exp

View full text Add to dashboard Cite

Summary Architectural languages (ALs) have attracted much attention as the modeling notations for specifying and reasoning about important design decisions. In this study, 124 different existing ALs have been analyzed for a set of requirements that are crucial for practitioners. These requirements are concerned with language definition, language features, and tool support. Some of the important findings obtained from the analysis are as follows: (1) performance is the top popular nonfunctional requirement supported by ALs; (2) no ALs offer both textual and visual notation sets, one of which could be used independently; (3) process algebras are the top preferred formal method by formal ALs; (4) the physical, deployment, and operational viewpoints are rarely supported by ALs; (5) the top preferred extension mechanism of the extensible ALs is XML for syntax extension; (6) Java is the top preferred programming language in generating software code; (7) the exhaustive model checking is the top preferred automated analysis method; (8) the logic‐based formal techniques are so popular in specifying system requirements; (9) among the analysis properties considered, consistency is the top supported property for the automated checking; and (10) most ALs do not provide any discussion platform (eg, forums). Hence, these findings can be used by the new AL developers in addressing the needs of practitioners and bridging the gaps in the field. Practitioners can also use the findings to find out about the existing ALs and compare them to choose the one(s) that suits their needs best.

show abstract

Safarchie Studio: ArgoUML Extensions to Build Safe Architectures

Cited by 13 publications

References 16 publications

Software Architecture Evolution

Software Architecture Evolution

Prisma: aspect-oriented software architectures

The analysis of architectural languages for the needs of practitioners

Contact Info

Product

Resources

About