You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by BW <b....@gmail.com> on 2012/01/23 16:28:34 UTC

Re: Quality-Risk-Trade-off

> 
> 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 costs.

Re: Quality-Risk-Trade-off

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi BW,

Looks good to me, +1.

Cheers,
Chris

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 costs.


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++