Quality models to design software architectures

Losavio, Francisca; Chirinos, Ledis; Pérez, María A.

doi:10.1109/tools.2001.911761

Cited by 13 publications

(11 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We defined these attributes as non-functional attributes in this paper. These non-functional attributes may appear and be discussed in other software applications [11]. And we believe that they can improve the usefulness of parallel components software.…”

Section: Introductionmentioning

confidence: 82%

Management of Non-functional Attributes of Parallel Components

Peng

Zhao

et al. 2011

Procedia Computer Science

View full text Add to dashboard Cite

In this paper, we present an extension to the CCA component architecture. The extension defined a minimal set of non-functional attributes of parallel components. We have a implemented the common CCA components for the management of these attributes. Parallel components can provide some non-functional interfaces optionally. And they provide related information to the common components through these interfaces. For the optimization of parallel components implementations, the component developer should implement the attributes management parts specific to certain parallel components. The tests of the management of six of them show that our management mechanism can improves the performance of parallel components. And the test of management of the other three shows that this is an easy way of controlling parallel component execution. And it is very efficient. A real application test shows the practicability of our proposal.

show abstract

Section: Introductionmentioning

confidence: 82%

Management of Non-functional Attributes of Parallel Components

Peng

Zhao

et al. 2011

Procedia Computer Science

View full text Add to dashboard Cite

show abstract

“…In order to reduce the complexity and the success rate of ETL systems implementation, we can use models to describe all system's tasks at early design stages, revealing at a primary development stage the most elementary needs of an ETL system in a very clear and precise way [4]. Models provide high-levels of systems abstraction regardless the technology used for final implementation, which can be useful for system requirements analysis and communication with non-technical users.…”

Section: Related Workmentioning

confidence: 99%

Using REO on ETL conceptual modelling

Oliveira

Belo

2013

Proceedings of the Sixteenth International Workshop on Data Warehousing and OLAP

View full text Add to dashboard Cite

The formalization of software patterns has proven to be very useful in software developing, improving systems communication, data interchange across platforms, and simplifying the integration of processes and data flows. Populating a data warehouse (ETL) is often a very complex task demanding significant computational resources, involving not only large volumes of data that must be processed but also undesirable change of business requirements. All of this leads frequently to reuse significant parts of other ETL implementations, adapting data structures and processes to comply with new requirements. Additionally, we believe that it's necessary a more simply and reliable approach for ETL conceptual modelling covering the "lack of mature" of this important part of ETL development. In this paper we explored a new approach to ETL conceptual modelling using the Reo coordination language, trying to evaluate its adequacy and expressiveness on the coordination of ETL tasks. A pattern-based approach was designed to map typical operations used in real world ETL scenarios from an initial Reo specification. For demonstration purposes, we present and discuss as two case studies, a slowly changing dimension and a surrogated key pipelining processes.

show abstract

“…In a software project, the architecture is determined in the early design phase [23,33,48], where the cost to fix an error is orders of magnitude less than in later development phases [54]. An architecture validation process [21] evaluates design decisions with respect to possibly prioritized and conflicting quality requirements.…”

Section: Architecture Tradeoff Analysis and Related Workmentioning

confidence: 99%