Changes between Version 8 and Version 9 of LEGACY - LAMP proposal


Ignore:
Timestamp:
11/16/10 16:13:18 (14 years ago)
Author:
jeff.lusted
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LEGACY - LAMP proposal

    v8 v9  
    1414    1. Speed of restore after failure
    1515    1. Can we afford to lose transactions?
    16     1. Turn around time for a support request
    17   * Type of data stored and usage
    18  
     16    1. Turn around time for a support request. Advice please on this one.
     17  * Type of data stored and usage. I'm not sure how to characterize this. What about:
     18    1. Transactional
     19    1. Research
     20
     21==== Labels Webapp: ====
     22  * Number of users: 1 at any one time
     23  * Hours of use during the day: 8:00 to 17:00
     24  * Peak or sensitive periods: None.
     25  * Level of activity. Fifty transactions per week if recruiting 50 participants per week,
     26  * Quality of service:
     27    1. Speed of response: within 10 seconds.
     28    1. Speed of restore after a failure: ?
     29    1. We cannot afford to lose transactions, which would give rise to the possibility of duplicate id's.
     30  * Type of data: Transactional.
     31
     32==== caTissue: ====
     33
     34==== i2b2: ====
     35
    1936=== VM's and Applications ===
    2037To keep applications separate, it would be a good idea to have one application per VM.