Page 233 - DCAP307_PLANNING_AND_MANAGING_IT_INFRASTRUCTURE
P. 233
Unit 14: Enterprise Architecture
14.2.4 Implicit Invocation Notes
This style suits applications that involve coupled collection of components, each of which carries
out some operation and may in the process enable other operations. These are often reactive
systems.
Figure 14.2: Representation for Implicit Invocation
Object or Process
Implicit Invocation
Source: http://etd.lsu.edu/docs/available/etd-07082004-152330/unrestricted/Banerjee_thesis.pdf
Task Make distinction between data abstraction style and implicit invocation style.
14.2.5 Repository
This style is suitable for applications in which the central issue is establishing, augmenting, and
maintaining a complex central body of information. Typically the information must be
manipulated in a wide variety of ways.
Example: An example of a repository or blackboard architecture may be the management
of work allocation process in a company.
Figure 14.3: Repository or Blackboard Architecture
Process 1 Process 2
Direct Access Computations
Blackboard
Process 6 (shared Data) Process 3
Memory
Process 5 Process 4
Source: http://etd.lsu.edu/docs/available/etd-07082004-152330/unrestricted/Banerjee_thesis.pdf
LOVELY PROFESSIONAL UNIVERSITY 227
