|
Data is shared between components through shared storage. The computational
components are coordinated, with subroutines to a main program sequences through
them. Data is then communicated between the components through shared storage.
Communication between the computational components and shared data is an
unconstrained read-write protocol.
Data is shared, common storage this can be plus and a minus.
![](graphics/shareddata.bmp)
Software
Architecture, by Mary Shaw and David Garlin Page 36
Advantages:
![bullet](graphics/check.bmp) |
The system is space efficient. |
![bullet](graphics/check.bmp) |
The system is time efficient. |
![bullet](graphics/check.bmp) |
Since computational aspects are in different modules the design is easier to
understand.
|
Disadvantages:
![bullet](graphics/check.bmp) |
Changes in data storage format affects all modules, for example if the data
structure is changed, then all the modules have to be modified to adjust to that
change. |
![bullet](graphics/check.bmp) |
Changes in algorithm not well supported
|
![bullet](graphics/check.bmp) |
Poor stability if access to the shard data is not handled appropriately. |
![bullet](graphics/check.bmp) |
Not supportive of reuse due to the dependency on the shared data. |
![bullet](graphics/check.bmp) |
Enhancements not easily incorporated because of the above reasons. |
|
|