@conference {12801,
	title = {Architectural Interaction Diagrams: AIDs for System Modeling},
	booktitle = {Software Engineering, International Conference on},
	year = {2003},
	month = {2003///},
	pages = {396 - 396},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {This paper develops a modeling paradigm called Architectural Interaction Diagrams, or AIDs, for the high-level design of systems containing concurrent, interacting components. The novelty of AIDs is that they introduce interaction mechanisms, or buses, as first-class entities into the modeling vocabulary. Users then have the capability, in their modeling, of using buses whose behavior captures interaction at a higher level of abstraction than that afforded by modeling notations such as Message Sequence Charts or process algebra, which typically provide only one fixed interaction mechanism. This paper defines AIDs formally by giving them an operational semantics that describes how buses combine subsystem transitions into system-level transitions. This semantics enables AIDs to be simulated; to incorporate subsystems given in different modeling notations into a single system model; and to use testing, debugging and model checking early in the system design cycle in order to catch design errors before they are implemented.},
	doi = {http://doi.ieeecomputersociety.org/10.1109/ICSE.2003.1201218},
	author = {Ray,Arnab and Cleaveland, Rance}
}
