Detecting architectural mismatches during systems composition
BARRY W. BOEHM, Cristina Gacek · 1998
ion for describing architectural styles and/or systems characteristics (see also section 1.0). The conceptual features he used were: 1. Dynamism. Earlier we discussed how the topology of software can be dynamic, adding and removing concurrent threads as it executes. Some styles constrain the topology to be static (i.e. the number of concurrent threads remains constant), while other styles do not. A style is dynamic if and only if it allows non-blocking control connectors (spawns). 2. Supported data transfers. Of the styles we studied, all of them achieved data transfers through one (or more) of three mechanisms: explicit data connectors, an implicit global network of data connectors, or shared data variables. “Thing” Data Control Object Data Control Port Data store Procedure Process Filter Object Socket Event queue Shared data Pipe Circuit Call Spawn