Lecture 4 Software Connectors

CS 3212
Software Architecture & Design
Dr. Chinthana Wimalasuriya
Lecture 4
Software Connectors
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved.
Software Architecture: Foundations, Theory, and Practice
Overview
 Introduction
 Connector Roles and Types
 Example Connectors
2
Introduction
3
What is a Software Connector?

 Software connectors perform transfer of control and data
among components.
 Connectors can provide services such as;
 Persistence
 Invocation
 Messaging
 Transaction
 Middleware standards like CORBA, DCOM and RMO
referred to these as “facilities components”.
 Software connectors are NOT just calls between
components like method calls.
4
Connectors in an Architecture
 Architectural elements that models

 Interactions among components
 Rules that govern these interactions
 Simple interactions
 Procedure calls
 Shared variable access
 Complex and semantically rich interactions

 Client-server protocols
 Database access protocols
 Asynchronous event multicast

5
Connectors in an Architecture
(contd.)
 Each connector provides
 Interaction duct(s)
 Transfer of control and/or data
 First class entities

 Have identity
 Describe all system interactions
 Entitled for their own specification and abstraction.
6
Connectors vs. Components
 Components provide application-specific functionality.

 Connectors provide application-independent interaction
mechanisms.
 Components design involves functionality abstraction
and/or parametrisation.
 Connectors design involves interaction abstraction
and/or parametrisation.
 Connectors are independent of components.
7
Benefits of Connectors
 Separate computation from interaction

 Minimize component interdependencies
 Support software evolution
 At component-level, connector-level, and system-level
 Potential for supporting dynamism

 Facilitate heterogeneity
 Become points of distribution
 Aid system analysis & testing
8
Simple Connector
9
Event Bus Connector
10
Connector Roles and Types
11
Connector Roles
 Classes of Services
 Communication
 Transmission of data
 Coordination
 Transfer of control
 Conversion
 Conversion of data formats
 Wrappers for legacy components
 Facilitation
 Load balancing
 Scheduling services
 Concurrency control
12
Connector Types
 Procedure Call
 Event
 Data access
 Linkage
 Stream
 Arbitrator
 Adaptor
 Distributor
13
Procedure Call Connectors

These are mainly coordination connectors
14
Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.
Event Connectors
These are mainly coordination connectors
15
Data Access Connectors

These mainly provide communication services
16
Linkage Connectors
• Provide facilitation services.
• Used by higher order connectors to enforce
interconnection unit, relationship syntax, and
interaction semantics.
17
Stream Connectors
 Stream connectors provide communication services.

 Used to transfer large amounts of data between
autonomous processes.
18
Stream Connectors (contd.)
19
Arbitrator Connectors
 Arbitrator connectors provide facilitation services and

coordination services.
 When components cannot make assumptions about their
state and needs, arbitrator;
 Streamline system operations and resolve any
conflicts. (Facilitation)
 Redirect the flow of control (Coordination)
20
Arbitrator Connectors (contd.)
21
Adaptor Connectors
• Facilitates interaction between components that have
not been designed to interoperate.
•Adaptors provide conversion services.
22
Distributor Connectors
 Performs the identification of interaction paths and

subsequent routing of communication.
 Coordination of components along these paths.
 Distributor connectors provide facilitation services.
23
Distributor Connectors (contd.)
24
Example Connectors
25
Data Distribution Connectors
26
Event-Based Data Distribution

Connectors
 Composition of four connector types
 Event
 Data access
 Stream
 Distributor
 Send and receive data through asynchronous

notifications (events)
 E.g. Publish-subscribe type middleware
27
Client-Server Based Distribution

Connectors
 Allow seamless distribution of data between distributed
systems using RPC
 Procedure call
 Data access
 Stream
 Distributor
 Invoke via a synchronous remote procedure call that

appears as if it were a local method call.
 E.g., HTTP/REST, Java RMI, CORBA, FTP, SOAP
28
P2P Based Data Distribution

Connectors
 Arbitrator
 Data access
 Stream
 Distributor
 Rely on arbitration as a means of synchronization and
invocation.
 Use rendezvous as a mechanism to achieve concurrency
and scheduling.
 Transaction support often available and invocation can
be rolled back if necessary.
 E.g., BitTorrent 29

Lecture 4 Software Connectors

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lecture 4 Software Connectors

Uploaded by

Copyright:

Available Formats

CS 3212

Software Architecture & Design

Dr. Chinthana Wimalasuriya

What is a Software Connector?

 Architectural elements that models

 Rules that govern these interactions

 Shared variable access

 Complex and semantically rich interactions

 Database access protocols

 Asynchronous event multicast

 Transfer of control and/or data

 First class entities

Connectors vs. Components

 Components provide application-specific functionality.

 Separate computation from interaction

 Potential for supporting dynamism

Event Bus Connector

Connector Roles and Types

Procedure Call Connectors

Data Access Connectors

 Stream connectors provide communication services.

Stream Connectors (contd.)

 Arbitrator connectors provide facilitation services and

Arbitrator Connectors (contd.)

 Performs the identification of interaction paths and

Distributor Connectors (contd.)

Data Distribution Connectors

Event-Based Data Distribution

 Send and receive data through asynchronous

Client-Server Based Distribution

 Invoke via a synchronous remote procedure call that

P2P Based Data Distribution

You might also like