Please enable JavaScript.
Coggle requires JavaScript to display documents.
Data-Centered Software Architecture (Blackboard (Domain (solving immature …
Data-Centered Software Architecture
Variants
Distributed repository system
(distributed database system)
Data are replicated ---> Improve reliability and local accessibility
All data are distributed over all sites linked by network
Virtural Repository
On top of physical repository
== view in DB -> Simplify DB structure
Security management
Blackboard
.....
Client: inactive/passive
Datastore: active
Consist of
Blackboard -> store data
Knowledge Source -> stores domain specific knowledge
Controller -> init above
Flow of logic
New data -> trigger event -> knowledge source take action -> response to event -> new data -> change logic flow
Determined by current data status -----> Data driven
Domain
solving immature - complex AI problems
The problem spans multiple disciplines
Optimal, partial, or approximate solution is acceptable
Exhausted searching is impossible.
Pros
Concurrency
Scalability
Cons
Repository
Control flow logic
Access Repository via
Public Diagram
Interactively
By client
Domain
Data transactions drive the control flow
large complex information system
Pros
Scalability + Reusability
Integrity: easy to backup/restore
Cons
Reliability + Availibility
High dependency
Cost
...
Data store: passive
Client: active
Overview
A centralized data store that is shared by all surrounding software components
Components
Data Store
Software Component Agents