Comparative evaluation of dependability characteristics for peer-to-peer architectural styles by simulation

Bischofs, Ludger; Giesecke, Simon; Gottschalk, Michael G.; Hasselbring, Wilhelm; Warns, Timo; Willer, Stefan

doi:10.1016/j.jss.2006.02.063

Cited by 7 publications

(6 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…These established fundamentals helped with formalizing and comparing the architectures. In the future, we intend to apply the presented approach to less established areas, such as variability in service-centric integration architectures [61] and in peer-to-peer architectures [62].…”

Section: Discussionmentioning

confidence: 99%

Formalization of Federated Schema Architectural Style Variability

Hasselbring¹

2015

JSEA

Self Cite

View full text Add to dashboard Cite

Data integration requires managing heterogeneous schema information. A federated database system integrates heterogeneous, autonomous database systems on the schema level, whereby both local applications and global applications accessing multiple component database systems are supported. Such a federated database system is a complex system of systems which requires a well-designed organization at the system and software architecture level. A specific challenge that federated database systems face is the organization of schemas into a schema architecture. This paper provides a detailed, formal investigation of variability in the family of schema architectures, which are central components in the architecture of federated database systems. It is shown how the variability of specific architectures can be compared to the reference architecture and to each other. To achieve this, we combine the semi-formal object-oriented modeling language UML with the formal object-oriented specification language Object-Z. Appropriate use of inheritance in the formal specification, as enabled by Object-Z, greatly supports specifying and analyzing the variability among the studied schema architectures. The investigation also serves to illustrate the employed specification techniques for analyzing and comparing software architecture specifications.

show abstract

Section: Discussionmentioning

confidence: 99%

Formalization of Federated Schema Architectural Style Variability

Hasselbring¹

2015

JSEA

Self Cite

View full text Add to dashboard Cite

show abstract

“…The separation between a simulation model of a P2P system and a real P2P system that operates on a real physical network hinders the transition of simulation models to real systems. To bridge this gap, RealPeer [12,13] introduces the idea of simulation-based development of P2P systems [4]. With RealPeer, an initial simulation model of a P2P system is iteratively transformed into the intended real P2P system.…”

Section: Benchmarks Vs Simulationsmentioning

confidence: 99%

Benchmarking as Empirical Standard in Software Engineering Research

Hasselbring

2021

Evaluation and Assessment in Software Engineering

Self Cite

View full text Add to dashboard Cite

In empirical software engineering, benchmarks can be used for comparing different methods, techniques and tools. However, the recent ACM SIGSOFT Empirical Standards for Software Engineering Research do not include an explicit checklist for benchmarking. In this paper, we discuss benchmarks for software performance and scalability evaluation as example research areas in software engineering, relate benchmarks to some other empirical research methods, and discuss the requirements on benchmarks that may constitute the basis for a checklist of a benchmarking standard for empirical software engineering research.

show abstract

“…An important concern for the successful deployment of a dependable system is its quality of service (QoS), which is significantly influenced by its architectural style. Bischofs et al [30] proposed the comparative evaluation of architectural styles by simulation.…”

Section: Trustworthiness Evaluationmentioning

confidence: 99%

“…In [30] the style evaluation of a software architecture is studied, while failing to involve the concept of trustworthiness. In [20,21] the authors study the trusted modeling of a architecture while failing to involve trustworthiness evaluation and measurement.…”

Section: This Paper's Reviewsmentioning

confidence: 99%

A Trustworthiness Evaluation Method for Software Architectures Based on the Principle of Maximum Entropy (POME) and the Grey Decision-Making Method (GDMM)

Jiang

2014

Entropy

View full text Add to dashboard Cite

Abstract:As the early design decision-making structure, a software architecture plays a key role in the final software product quality and the whole project. In the software design and development process, an effective evaluation of the trustworthiness of a software architecture can help making scientific and reasonable decisions on the architecture, which are necessary for the construction of highly trustworthy software. In consideration of lacking the trustworthiness evaluation and measurement studies for software architecture, this paper provides one trustworthy attribute model of software architecture. Based on this model, the paper proposes to use the Principle of Maximum Entropy (POME) and Grey Decision-making Method (GDMM) as the trustworthiness evaluation method of a software architecture and proves the scientificity and rationality of this method, as well as verifies the feasibility through case analysis.

show abstract

Comparative evaluation of dependability characteristics for peer-to-peer architectural styles by simulation

Cited by 7 publications

References 5 publications

Formalization of Federated Schema Architectural Style Variability

Formalization of Federated Schema Architectural Style Variability

Benchmarking as Empirical Standard in Software Engineering Research

A Trustworthiness Evaluation Method for Software Architectures Based on the Principle of Maximum Entropy (POME) and the Grey Decision-Making Method (GDMM)

Contact Info

Product

Resources

About