% % GENERATED FROM http://acme.able.cs.cmu.edu % by : anonymous % IP : ec2-3-147-86-143.us-east-2.compute.amazonaws.com % at : Sun, 24 Nov 2024 23:59:12 -0500 GMT % % Selection : Publication #205 %
@InProceedings{Allen94MIL, AUTHOR = {Allen, Robert and Garlan, David}, TITLE = {Beyond Definition/Use: Architectural Interconnection}, YEAR = {1994}, MONTH = {August}, BOOKTITLE = {Proceedings of the ACM Interface Definition Language Workshop}, KEY = {Allen}, VOLUME = {29}, NUMBER = {8}, PUBLISHER = {SIGPLAN Notices}, PDF = {http://www.cs.cmu.edu/afs/cs/project/able/ftp/connectors-idl94/connectors-idl94.pdf}, PS = {http://www.cs.cmu.edu/afs/cs/project/able/ftp/connectors-idl94/connectors-idl94.ps}, ABSTRACT = {Large software systems require decompositional mechanisms in order to make them tractable. Traditionally, MILs and IDLs have played this role by providing notations based on definition/use bindings. In this paper we argue that current MIL/IDLs based on definition/use have some serious drawbacks. A significant problem is that they fail to distinguish between 'implementation' and 'interaction' relationships between modules. We propose an alternative model in which components interact along well-defined lines of communication - or connectors. Connectors are defined as protocols that capture the expected patterns of communication between modules. We show how this leads to a scheme that is much more expressive for architectural relationships, that allows the formal definition of module interaction, and that supports its own form of automated checks and formal reasoning.}, KEYWORDS = {Software Architecture, Wright} } |