SourceForge : Post

Project: Editor Discussion > INFO:GridCPR Architecture, API > Various comments... > List of Posts

Forum Topic - Various comments...: (2 Items)

View: as

10/31/2005 12:29 AM

post4732

Various comments...

Some comments:

A summary of requirements as drawn from the Use Case document would be useful (in intro or so).  Also, you actually 
promise that in the use case docuemnt ;-)

To fig. 1:
  "Lines connecting components represent transactions."
  Real transactions, or just interactions?

  Why has EHdetect two errors?  Does it really invoke significant 
  amount of data transferred in both directions?

Wouldn't it be useful to also specify (maybe in a differnt doc) the wire protocols used for notification etc? That would
 allow for interoperability of various implementations of this architecture.  If this is not in your groups scope, you 
should state that explicitely I think (with reason?).

Until the scenario section, it was unclear to me what some of the 'transactions' from fig.1 meant.  A complete list of 
them with an explanation would be useful somewhere close to fig.1.

Cheers, Andre.

Andre Merzky

03/15/2007 10:07 AM

post5775

Re: Various comments...

> Some comments:
> 
> A summary of requirements as drawn from the Use Case document would be useful 
> (in intro or so).  Also, you actually promise that in the use case docuemnt ;-)

NOT addressed, yet.


> To fig. 1:
>   "Lines connecting components represent transactions."
>   Real transactions, or just interactions?

NOT addressed, yet.
 
>   Why has EHdetect two arrows (!)?  Does it really invoke significant 
>   amount of data transferred in both directions?

NOT addressed, yet.  Also, arrow presence/directions are unclear on most interactions.

> Wouldn't it be useful to also specify (maybe in a different doc) the wire 
> protocols used for notification etc? That would allow for interoperability of 
> various implementations of this architecture.  If this is not in your groups 
> scope, you should state that explicitly I think (with reason?).

NOT addressed, yet.

> Until the scenario section, it was unclear to me what some of the 
> 'transactions' from fig.1 meant.  A complete list of them with an explanation 
> would be useful somewhere close to fig.1. 

NOT addressed, yet.  That is, I think, the same proposal as Thilos.

Return