 DAROC Introduction.

 Blackboards.
 Importance Of Blackboard.
 DAROC External Architecture .
 DAROC Implementation.
 Goals of DAROC
 DAROC Tool Kit (DTK).
 DAROC is a middleware architectural model,
which is loosely based upon on the blackboard
model. This architecture will decrease distributed
software development time by abstracting away
much of the communication overhead and
scheduling, which most software developers are
burdened with in their application.
 The combination of reduced communication and
synchronization overhead and flexibility will reduce
software development time, which has a direct
impact on the over all cost of development and
testing.
 The short-term goal of DAROC is to provide a
programming environment that will allow both
undergraduate and graduate students the ability
to gain some exposure and experience in
programming distributed applications.
 The long-term goal is a bit more ambitious. The
DAROC architecture will address problems such as
distributed simulation and battle management
scenarios
 The blackboard model is an opportunistic and
incremental problem- solving model that defines
how to organize the sources of knowledge, along
with the reasoning steps and the domain
knowledge needed to build a solution to a
problem.
 The blackboard model consists of three major
components:
 Knowledge source.
 Blackboard structure.
 Control component.
 The blackboard style has a big advantage when it
comes to simplicity. The blackboard style consists of
one connector that all components use, which of
course is the blackboard itself. Another big
advantage is evolve ability, because new types of
components can be easily written.
 The blackboard style naturally lends itself to
increased concurrency. Multiple components can
read and write blackboard data and perform their
assigned computations concurrently if possible.
 Data Objects.
 Functional Elements.
 Constraints.
 Single Writer Rule (SWR).
 DAROC’s Error Manager.
 Garbage Collection.
 Data Objects
DAROC currently supports data objects defined
as any standard ANSI/ISO C++ data type such as
integers, floats, doubles, characters, and arrays.
 Functional Elements
Functional elements are always created as an
abstract data type. In their simplest form, they
consist of a “build” function to create and
instantiate the DAROC components around
the functional element .
 Constraints
functional element and data object consists of a
name and an ID field. The name field is any unique
generic name that the user calls the object. The ID field
consists of three parts. It always starts with a ‘/DO’ or a
‘/FE’ to discern between a data object and a
functional element.
 Single Writer Rule (SWR)
DAROC is implemented with a single-writer rule as
part of the application implementation. This simple
means that only one functional element may write
to a particular data object at all times
 DAROC’s Error Manager
The error manager is an attempt to provide a
consolidated error messaging system for future
DAROC developers and application programmers.
 Garbage Collection
DAROC currently deal locates any memory that was
dynamicallyallocated for a functional element or data
object along with all threadmurexes if the program exits
cleanly. The linked lists that make up the DONAR and FEBAR
managers are also properly deal located when the program
exits cleanly.
 DONAR
The DONAR acts as a local name services manager.
All data objects that are created on a node register
themselves with the DONAR. When a functional
element needs to find the address of data object it
sends its request to the DONAR.
 FEBAR
the FEBAR is not a global name services
manager. Every functional element has its own
FEBAR, which it uses to store copies of the data
objects that it needs to read from to perform its
computation.
 Reduce software development costs, error-
proneness and inflexibility associated with
distributed systems applications.
 Reduce code complexity so that the “average”
programmer is able to build distributed systems.
 Provide a tool to better prepare students for the
ever-growing need in the job market for
experienced distributed systems programmers
 A tool kit is currently under
development to further increase the
programmer’s ability to rapidly program
data objects and functional elements.
The tool kit will not be static and will
continue to grow to meet the needs of
the users as time progresses.
 Blackboard Parser
The user runs their source code through this utility to wrap their
code around the appropriate DAROC functions and cast the
data objects to their respected type.
 Single Writer Rule (SWR) Checker
Within DAROC, data objects can only be written by a single
functional element at all times. The user runs their source
code through the SWR checker to verify the integrity of this
rule.
 Code Nuggets
Skeleton code of data object’s and functional elements can
be created on the fly and be free of syntactical errors by
simply filling out a specifications form.
THANK YOU