| An End-to-End Solution |
Digital Harbor represents a sophisticated platform that took over five years to develop,
is comprised of over three million lines of code and has evolved through
the proving ground of a demanding customer base. From a technology
standpoint, Digital Harbor has made the following innovations with
regard to component-based software and semantic modeling:
|
 |
 |
|
Component-Based Interface
|
The interface moves beyond HTML to XML and Java by providing a set of components that are
aware of each other, and can "talk" using a common infrastructure. This awareness of
their surrounding context and their ability to communicate within it makes them "smart".
Components also enable interfaces to be extended to incorporate existing enterprise functionality
and web services.
The result is that components enable applications with all the benefits of the web (wide deployment, intuitive navigation, rich formatting) and all the benefits of client/server technology (interactivity, speed, desktop-level behavior).
|
|
|
 |
|
|
Application Linking and Embedding (ALE™)
|
Using a drag-and-drop paradigm, any end-user or application developer can graphically link,
attach or embed one application inside another. For example, a map can be linked or
embedded within the "router" object on a network diagram, so that the next actor in the
collaborative process of "customer service" (e.g. a provisioning agent) can see the same
information in the context that makes sense - inside the application. |
|
|
 |
|
|
Business Ontology™ |
Different systems are tied together by logically mapping information
and describing the interaction of data, processes, rules and messages
across systems in a "schema across systems", much like a database ties
together discrete pieces of data.
The business ontology hides complexity by moving assumptions out of
the code and into a higher-level model, making it easy enough for
business analysts to construct integrated applications.
- Logically map to data
- Use assets you have
- Correlate information
- Collaborate in long-duration processes
- Two way application
|
|
|
 |
|
|
Rich Semantics
|
In databases, we define that a relationship exists, and we write code to specify how
it fits together with processes, rules, events or applications. Semantic
definitions allow us to specify what kind of relationship exists, how it is
related to other elements of the architecture (e.g. a web service), and to exploit
those relationships to save development time and capture more business meaning
from our data. For example, an item may not have a location, but is contained
in a warehouse that has a location or is provided by a supplier that has a location. The data in these scenarios may be different. Semantics enable users to capture meaning from data without writing code.
- Correlation across heterogeneous information sources
- Business logic by business analysts
- Smarts for coordination (future), traceability (past), collaboration (present)
|
|
|
|
