Changes between Version 7 and Version 8 of LEGACY - CaTissueClientAPI


Ignore:
Timestamp:
11/26/10 12:09:57 (14 years ago)
Author:
jeff.lusted
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • LEGACY - CaTissueClientAPI

    v7 v8  
    1616
    1717=== The Client and The User ===
    18 The client API is invoked within an application entirely separate from the caTissue application. '''They are both separate applications'''. The client will need to be written in Java if it is to use serialized Java domain objects. The client application has a user. How does the user interact with it:
     18The client API is invoked within an application entirely separate from the caTissue application. '''They are both separate applications that happen to talk to one another'''. The client will need to be written in Java if it is to use serialized Java domain objects. The client application has a user. How does the user interact with it:
    1919  * Web browser?
    2020  * Desktop gui?
    2121  * Command line?
    22 This user interface will need designing and programming. (Also see next point below, which is also relevant).
     22  * Two-d barcode reader?
     23This user interface will need designing and programming.[[BR]]
     24(Also see next point below, which is also relevant).
     25
     26=== Domain Objects ===
     27This concerns point 4 in the pseudo code example. The use cases we need to cover will involve business objects (domain objects) like Participant, Collection Protocol, Collection, Specimen Collection Group, Specimen, and so on. We will need to understand how these relate to one another. The code that supports the use cases must support the relationship between these objects. It is possible the integrity of the objects will be checked by the caTissue application when the client finally interacts with it. But:
     28  * If it does, we need to handle error conditions. The examples I've seen are very rudimentary in dealing with errors.
     29  * If it does not, we risk data corruption unless our understanding is good and we programme defensively.
     30
     31=== Transactions ===
     32This is partly an extension of the above points on Domain Objects.[[BR]]
     33Normally, a business action within an application is defined by one or more transactions. I cannot see a clear transaction boundary yet in the API.