| 176 |
@InProceedings{Allen98FASE,
AUTHOR = {Allen, Robert and Douence, Remi and Garlan, David},
TITLE = {Specifying and Analyzing Dynamic Software Architectures},
YEAR = {1998},
MONTH = {March},
BOOKTITLE = {Proceedings of the 1998 Conference on Fundamental Approaches to Software Engineering (FASE'98)},
KEY = {Allen},
VOLUME = {1382},
SERIES = {Lecture Notes in Computer Science},
ADDRESS = {Lisbon, Portugal},
PUBLISHER = {Springer},
PDF = {http://www.cs.cmu.edu/afs/cs/project/able/ftp/wright-fase98/wright-fase98.pdf},
PS = {http://www.cs.cmu.edu/afs/cs/project/able/ftp/wright-fase98/wright-fase98.ps},
ABSTRACT = {A critical issue for complex component-based systems design is the modeling and analysis of architecture. One of the complicating factors in developing architectural models is accounting for systems whose architecture changes dynamically (during run time). This is because dynamic changes to architectural structure may interact in subtle ways with on-going computations of the system.
In this paper we argue that it is possible and valuable to provide a modeling approach that accounts for the interactions between architectural reconfiguration and non-reconfiguration system functionality, while maintaining a separation of concerns between these two aspects of a system. The key to the approach is to use a uniform notation and semantic base for both reconfiguration and steady-state behavior, while at the same time providing syntactic separation between the two. As we will show, this permits us to view the architecture in terms of a set of possible architectural snapshots, each with its own steady-state behavior. Transitions between these snapshots are accounted for by special reconfiguration-triggering events.
},
NOTE = {An expanded version of the paper Specifying Dynamism in Software Architectures, which appeared in the Proceedings of the Workshop on Foundations of Component-Based Software Engineering, September 1997.},
ANNOTE = {CONFERENCE-URL : http://www.di.fc.ul.pt:80/~llf/etaps98/},
KEYWORDS = {Dynamism, Formal Methods, Software Architecture, Wright}
}
|
|
