Executable Specifications for Real-Time Distributed Systems

Authors:
Arnab Ray;Rance Cleaveland
Affiliations:
Fraunhofer USA Center for Experimental Software Engineering, University of Maryland at College Park, 4321 Hartwick Road Suite 500, College Park MD 20742-3290;Department of Computer Science, University of Maryland at College Park, AV Williams Building, College Park MD 20742
Venue:
Electronic Notes in Theoretical Computer Science (ENTCS)
Year:
2008

Citing 8
Cited 0

Foundations for the study of software architecture

ACM SIGSOFT Software Engineering Notes
A process algebra for timed systems

Information and Computation
Experience assessing an architectural approach to large-scale systematic reuse

Proceedings of the 18th international conference on Software engineering
Formalizing architectural connection

ICSE '94 Proceedings of the 16th international conference on Software engineering
A formal basis for architectural connection

ACM Transactions on Software Engineering and Methodology (TOSEM)
Real-Time UML: Developing Efficient Objects for Embedded Systems

Real-Time UML: Developing Efficient Objects for Embedded Systems
An Event-Based Architecture Definition Language

IEEE Transactions on Software Engineering
Architectural Interaction Diagrams: AIDs for system modeling

Proceedings of the 25th International Conference on Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

One of the challenges in designing distributed, embedded systems is the paucity of formal, executable specification notations that provide support for both real-time and asynchronous communication. This paper describes a timed architecture design language (Timed Architecture Interaction Diagrams or TAID) that, by virtue of its formal, executable semantics, combines the benefits of synchronous specification notations with the advantages of traditional architecture description languages. In addition, TAID provides support for a variety of temporal inter-process communication (IPC) primitives as a native feature of the language, so that the encapsulated communication behavior (captured by real-time ''buses'' in TAID) may be re-used across designs and serve as specifications for more detailed model implementations.