Architectural description with integrated data consistency models

The focus of typical architectural models is the description of large systems. Even though these systems are usually distributed, aspects of distributed systems are only addressed in a rudimentary way. While typical approaches pay attention to technical issues like deployment, data consistency problems are mostly ignored. We present a modeling approach which integrates assumptions about data consistency into architectural models. The concepts of abstract locations and operations play a central role in this context. They allow transactions and snapshots to be implicitly defined by mapping high-level architectural models to low-level models. The decision about the application of transactional techniques and snapshot algorithms can then be based on architectural models. Furthermore, the approach can be integrated into programming languages and platforms. In this case, a runtime environment could automatically detect and process both transactions and snapshots.

[1]  C. Petri Kommunikation mit Automaten , 1962 .

[2]  Andreas Reuter,et al.  Principles of transaction-oriented database recovery , 1983, CSUR.

[3]  Leslie Lamport,et al.  Distributed snapshots: determining global states of distributed systems , 1985, TOCS.

[4]  George Coulouris,et al.  Distributed systems - concepts and design , 1988 .

[5]  Sape Mullender,et al.  Distributed systems , 1989 .

[6]  Henri E. Bal,et al.  Orca: A Language For Parallel Programming of Distributed Systems , 1992, IEEE Trans. Software Eng..

[7]  Andreas Reuter,et al.  Transaction Processing: Concepts and Techniques , 1992 .

[8]  Gerard Tel,et al.  Introduction to Distributed Algorithms: Contents , 2000 .

[9]  Mary Shaw,et al.  Abstractions for Software Architecture and Tools to Support Them , 1995, IEEE Trans. Software Eng..

[10]  Robert L. Nord,et al.  Software Architecture in Industrial Applications , 1995, 1995 17th International Conference on Software Engineering.

[11]  Paul C. Clements,et al.  A survey of architecture description languages , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[12]  Clemens Szyperski,et al.  Component software , 1997 .

[13]  Andrei Borshchev,et al.  Systems modeling, simulation and analysis using COVERS active objects , 1997, Proceedings International Conference and Workshop on Engineering of Computer-Based Systems.

[14]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[15]  Robert L. Nord,et al.  Applied Software Architecture , 1999, Addison Wesley object technology series.

[16]  Richard N. Taylor,et al.  A Classification and Comparison Framework for Software Architecture Description Languages , 2000, IEEE Trans. Software Eng..

[17]  Frank Keller,et al.  Improving Knowledge Transfer at the Architectural Level: Concepts and Notations , 2000 .

[18]  Peter Tabeling Der Modellhierarchieansatz zur Beschreibung nebenläufiger, verteilter und transaktionsverarbeitender Systeme , 2000 .

[19]  Peter Tabeling Ein Metamodell zur architekturorientierten Beschreibung komplexer Systeme , 2002, Modellierung.

[20]  P. Tabeling Multi-Level Modeling of Concurrent and Distributed Systems , 2002 .

[21]  Ivar Jacobson,et al.  Unified Modeling Language , 2020, Definitions.

[22]  Frank Keller,et al.  FMC: an approach towards architecture-centric system development , 2003, 10th IEEE International Conference and Workshop on the Engineering of Computer-Based Systems, 2003. Proceedings..

[23]  C. A. R. Hoare,et al.  Proof of correctness of data representations , 1972, Acta Informatica.