Component Coordination组件的协调.pptVIP

Seminar on Component-based Software Engineering Component Coordination Nadia Ramjiawan LIACS - Leiden University Fall 2005 Component Every component instance contains one or more active entities (thread of control). The active entities inside a component C can communicate with the active entities in other components only through I/O operations performed on the channel ends connected to C. Channels The only primitive medium of communication between two components. A channel has exactly two ends. A channel end is either: Source: accepts data into its channel. Sink: dispenses data out of its channel. Example: ab represents the channel with source end a and sink end b. Although every channel has exactly two ends, these ends can be of the same or different types (two sources, two sinks, or one source and one sink). Various kinds of channel are possible, offering different synchronisation, buffering, lossy and even directionality policies. Channel I/O Operations Read/write data items from /to their channel ends. Abstract Behavior Type (ABT) Model An ABT defines an abstract behavior as a relation among a set of timed-data-streams, without specifying any detail about: the operations that may be used to implement such behavior or the data types it may manipulate for its realization. A timed data stream is a twin pair of streams consisting of a data stream and a time stream with the interpretation that ?i≥0, the data item appears at its corresponding time moment Used to model the data flow through channel ends. ABT Examples Basic channels Synchronous channel : Asynchronous unbounded FIFO channel : Asynchronous FIFO channel with the bounded capacity of 1: ABT Examples (II) Asynchronous FIFO channel with the bounded capacity of 1 and initially contain the data item D : Synchronous drain channel: Two source ends, cannot produc