Overview / The Component-and-Connector Viewtype from Documenting Software Architectures(c) Views and Beyond. Relation to Other Viewtypes / The Component-and-Connector Viewtype from Documenting Software Architectures(c) Views and Beyond. the architectural artifacts and the rest of the model. Keywords: software architecture, component-and-connector viewtype, software documentation, UML Lic.
|Published (Last):||7 June 2017|
|PDF File Size:||14.83 Mb|
|ePub File Size:||17.69 Mb|
|Price:||Free* [*Free Regsitration Required]|
Seven Rules for Sound Documentation P. For example, a component may be a server in a client-server system.
The Nooks and Crannies. Each of these connectors represents a complex form of interaction and will likely require nontrivial implementation mechanisms.
Relation to Other Viewtypes | The Component-and-Connector Viewtype
For example, if the view documents early, coarse-grained design decisions that will be refined later, it will probably include abstract connector types that will need to be refined later. Anf interactions might represent multiparty forms of communication, such as event broadcast, or n-way data synchronization.
Often, these interactions are carried out using complex infrastructure, such as middleware frameworks, distributed communication channels, and process schedulers. The documentation accompanying the figure elaborates on the elements shown. Just Enough Software Architecture: For Further Reading Part Componnent. We are being shown a bird’s-eyeview of the system as it might appear during runtime.
Styles of the Component-and-Connector Viewtype
In the example, this is the module Stdio. The client-server connector allows a set of concurrent clients to retrieve data synchronously via service requests. We discuss sixpipe-and-filter, shared-data, publish-subscribe, client-server, peer-to-peer, and communicating-processesthat apply to a wide variety of systems and provide enough semantic richness to illustrate documentation principles.
Some of these problems follow from the usual pitfalls of visual documentation and are equally applicable to any of the viewtypes discussed in connsctor book. Note also that connectors need not be binary: For Further Reading Part I. Software Architectures and Documentation P.
Thus, assuming that both client-server and shared-data styles are important to understanding the system, views in both styles will include the same component, showing different patterns of interaction. Viewtypes and Styles P.
Conversely, the pipe connector does not appear in the module view, although one might argue that it is most closely associated with the module Stdio. The system contains a shared repository of customer accounts Account Database accessed by two servers and an administrative component.
It should be clear even with this simple example that the two descriptions differ wildly in what they include and how they partition the system. These interactions may represent complex forms of communication.
This module determines how inputs from one are fed viewtye others, using a configuration module, Config. If you may any questions please contact us: In the example, we have Main and Config. The simple system illustrated here accepts a stream of characters as input and produces a new stream of characters identical connrctor the original but with uppercase and lowercase characters alternating.
What is Lean Six Sigma. In this view, the relation between modules is uses, as described in Chapter 2. Interprocess Communications in Linux: The same component may also act as a respository for data.
These modules can be more easily seen by factoring out amd that are associated with setup and modules that implement communication infrastructure. The Role of Architecture P. Software Architecture in Practice 2nd Edition. Similarly, by knowing properties about the reliability of the individual servers, you might be able to produce numeric estimates of the overall reliability of the system, using some form of vviewtype analysis. A set of client tellers can interact with the account repository servers, embodying a client-server style.
Relation to Other Viewtypes
Seven Rules for Sound Documentation P. A set of client tellers can interact with the account repository servers and communicate among themselves through a publish-subscribe connector.
The Process of Software Architecting.