[news.eclipse.tools.hyades] Hyades Vision?

["westes" <DELETE_westes@xxxxxxxxx>]

I have read through the Hyades Vision document "Automated Software Quality
for Eclipse".  While I understand the generalization that it is attractive
for different test tools to share a common infrastructure, I did not
perceive a clear vision for how that will look and feel under Hyades.   To
put this into the framework of a design process, I read business
requirements, and I read what seemed like high level systems diagrams, but I
did not see clear use cases nor did I see user interface (UI) design.

As a result I have problems imagining where Hyades will end and where a
third-party plug-in to Hyades will begin.   Is the intent to have a "Hyades
Perspective" in which tools are integrated in a common look and feel?
This seems a logical conclusion from the project's goals to have tools share
infrastructure, but the one prototype tool I could find was a Java profiler
that implements its own Eclipse Perspective and does not seem to have any
common UI elements that would be shared by other tools.   Without a
compelling user interface for integration, I think it will be hard to get
tools developers to commit.   The vision is compelling, but the
implementation has to be compelling as well.

We have developed a performance-oriented load testing tool, written
primarily in Java, but able to interact with other languages within the
client agent environment.    We are anxious to understand how we might add
value under Eclipse in general, and now also under Hyades.  Is Hyades being
driven primarily by Rational's internal needs to integrate its own toolset?

--
Will Estes                                         U.S. Computer Software,
Inc.

NOTE:   To reply, send mail to westes AT uscsw.com.