TAPAS Design Document

Release Information

Project: TAPAS
Internal Release Number: $Revision: 1.5 $
Attached Worksheets:
Related Documents:

Deployment Model

The system's structural design is described in the following UML model: TAPAS-Models.

 

Deployment Diagram

deeployment diagram

The current model has five different classes of computing nodes:

  • the tapas server
  • the initiation station
  • a number of online clients
  • a number of synced (offline) clients (PDA)
  • a number of hosts for synced clients


(The same physical machine may play the role of a host for synced clients and the tapase online client. However, this is not necessarily the case, since some online clients may not be hosts for offline clients.)


There are seven software components involved in the application:

  • The NSMobile Conduit component is a plugin to the JSyncManager component. It is deployed on the Synced Client Host and the Initiation station and performs the syncronisation between synced devices and the server.
  • The Synced Client has several components. These include several custom built pieces along with several built in applications:
    • Plucker - open source eBook reader
    • Palm's built in Date Book
    • TAPAS|msg - custom messaging application
    • TAPAS|ems - custom application. Patient medical summary program for the PDA.


License terms. Retain this copyright statement whenever this file is used as a template.
0