54204_PP06_Chap06PPT_Modified

54204_PP06_Chap06PPT_Modified - Chapter 6 DATA CENTERED...

Info iconThis preview shows pages 1–13. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 6 DATA CENTERED SOFTWARE ARCHITECTURE
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Objectives Introduce the concepts of data centered software architecture Describe the repository and blackboard architectures Discuss applicable domains for data centered software architecture Discuss the benefits and limitations of data centered software architecture Discuss the data centered architecture when incorporated with other architectures
Background image of page 2
Overview The data centered software architecture is characterized by a centralized data store which is shared by all surrounding software components . The software system is decomposed into two major partitions : data store and independent software component or agents. The connections between the data module and the software components are implemented either by explicit method invocation or by implicit method invocation .
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
There are two categories of data centered architecture: repository and blackboard . These are differentiated by the flow control strategy . The data store in the repository architecture is passive and clients of the data store are active ; that is, clients (software components or agents ) control the logic flow . Clients may access the repository interactively or by a batch transaction request .
Background image of page 4
The data store in the blackboard architecture option is active and its clients are passive ; thus, the flow of logic is determined by the current data status in the data store. The clients of a blackboard are called knowledge sources, listeners or subscribers .
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 6
Repository Architecture Style The repository architecture style is a data centered architecture that supports user interaction for data processing (as opposed to the batch sequential transaction processing discussed earlier). The software component agents of the data store control the computation and flow of logic of the system.
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 8
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 10
Background image of page 11

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Applicable Domain of Repository Architecture Suitable for large complex information systems where many software component clients need to access it in different ways . Data transactions to drive the control flow of computation . Benefits:
Background image of page 12
Image of page 13
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 09/14/2010 for the course SAD 333 taught by Professor Luis during the Summer '10 term at St. Louis CC.

Page1 / 31

54204_PP06_Chap06PPT_Modified - Chapter 6 DATA CENTERED...

This preview shows document pages 1 - 13. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online