oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: Quality-Risk-Trade-off
Date Mon, 23 Jan 2012 18:41:31 GMT
Hi BW,

Looks good to me, +1.


On Jan 23, 2012, at 7:28 AM, BW wrote:

>> Quality: Usability : High Priority
>> Architectural aspect supporting Usability:
>> Components and the data flow related to servicing the user needs:
>> Client/Server components wrapped in a web app that is deployed to a tomcat server
>> where REST services are provided through an end point.
>> Performance wise, the communications are synchronous where blocking on the user
>> client side occurs until the thread of the service invocation completes.
>> Associated Risk:
>> Extremely large data transfers will force the user to wait until thread involved
>> in servicing user completed resulting in user dissatisfaction and a decrease in performance.
>> Approach Trade Off:
>> Synchronous blocking communications are more manageable and are not as complex as
>> asynchronous communications resulting an increase in maintainability and development

Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA

View raw message