Please enable JavaScript.
Coggle requires JavaScript to display documents.
Data-Centered Software Architecture (Repository (Examples (Database…
Data-Centered Software Architecture
Repository
Data store is passive
Clients of the data store are active
Its clients taking control of flow logic
Client may access the repository
Examples
Database management system
Library Information system
Interface repository in CORBA
UDDI registry for Web Services
CASE tools – IBM Rational Rose
IDE (Interactive Development Endowment)
Variants of Data Repository
Virtual repository
Built up on the top of multiple physical repositories
Most DB allows users to create views that are virtual repositories since they do not exist physically.
Benefits
Simplify the overall complexity of overall database structure
Security management in terms of scope of data of manipulation for different users
Data integrity:
Distributed repository system (distributed database system)
All data are distributed over all sites linked by network
Data are replicated in order to
Cons
Data store reliability and availability
High dependency between data structure of data store
Overhead cost of moving data on network
Blackboard
Properties
Each knowledge source is relatively independent
They don’t need to interact with each other
Only interact and respond to the blackboard subsystem
Pros
Scalability: easy to add new knowledge source
Concurrency: all knowledge sources can work in parallel
Reusability of knowledge source agents
Cons
Tight dependency between the blackboard and knowledge source
Synchronization of multiple agents is an issue
Testing of the system is a challenge.
Application Domain
Suitable for solving immature and complex AI problems
The problem spans multiple disciplines, each of which has complete different knowledge expertise
Optimal, partial, or approximate solution is acceptable
Exhausted searching is impossible.