Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
A Component- and Message-Based Architectural Style for GUI Software
IEEE Transactions on Software Engineering - Special issue: best papers of the 17th International Conference on Software Engineering (ICSE-17)
Acme: architectural description of component-based systems
Foundations of component-based systems
Towards a taxonomy of software connectors
Proceedings of the 22nd international conference on Software engineering
Component Software: Beyond Object-Oriented Programming
Component Software: Beyond Object-Oriented Programming
XML Schemas
ArchJava: connecting software architecture to implementation
Proceedings of the 24th International Conference on Software Engineering
The IWIM Model for Coordination of Concurrent Activities
COORDINATION '96 Proceedings of the First International Conference on Coordination Languages and Models
xADL: Enabling Architecture-Centric Tool Integration with XML
HICSS '01 Proceedings of the 34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 9 - Volume 9
Speechnet: A Network of Hyperlinked Speech-Accessible Objects
WECWIS '99 Proceedings of the International Workshop on Advance Issues of E-Commerce and Web-Based Information Systems
Exogenous connectors for software components
CBSE'05 Proceedings of the 8th international conference on Component-Based Software Engineering
Applications = Components + GLoo
Electronic Notes in Theoretical Computer Science (ENTCS)
Composite connectors for composing software components
SC'07 Proceedings of the 6th international conference on Software composition
| Hi-index | 0.00 |
In a traditional software architecture, control originates in components and flows to other components via connectors. The system's control flow is fixed at design time, when components and their inter-connections are specified. Code generated from the design inherits this control flow, and consists of component code and glue code that tightly couples connected components. This means that code generated from a given software architecture is system-specific, and is therefore neither generic nor reusable. In this paper we describe an approach which allows separate reuse of component code and connector code, and thus making it possible to build architectures from pre-existing components and generic connectors. Furthermore, we show we can implement such architectures by generating control flow at run-time automatically.