Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Corona » Tool X: Exemplary Corona Candidate
Tool X: Exemplary Corona Candidate [message #1108] Wed, 29 March 2006 22:42 Go to next message
Bob Brady is currently offline Bob Brady
Messages: 7
Registered: July 2009
Junior Member
Hello Corona Team,

I'm interested in integrating one of several ALM tools into the Corona
framework. However, I'm not clear on which tools at my disposal would be
best suited as a candidate for Corona.

Can somebody please recommend a list of characteristics that would make a
"Tool X" an exemplary candidate for integration into Corona vs. say, a
good candidate for integration into the ALF project?

I think a server-side tool which already has a web services interface but
no eclipse client (plugin or rcp) are some characteristics a good ALF
candidate.

Thank you,
Bob
Re: Tool X: Exemplary Corona Candidate [message #1135 is a reply to message #1108] Fri, 31 March 2006 13:02 Go to previous message
Dennis O'Flynn is currently offline Dennis O'Flynn
Messages: 73
Registered: July 2009
Member
Bob,

Corona is about tool integration. To achieve this, Corona will enable
Eclipse constructs, such as a "project", to be shared in a distributed
environment. This requires Corona to have an Eclipse based server-side
runtime environment that can manage these common constructs.



With that brief explanation, an exemplary (RCP based) Tool X candidate for
Corona would be any tool that would benefit from collaboration involving
human interaction.



Consider how the JDT is used. Each developer has its own Eclipse workbench
using the JDT. Each developer has its own definition of a "project" that
has been mapped to a CVS repository. Currently these are manually
synchronized with CVS. Developers are not aware of changes being done by
their peers without any manual intervention.



Corona will enable the concept of a shared "project" across multiple RCP
instances (aka workgroup). Corona will tap into the Eclipse event model and
listen for resource change events within the RCP. Any of these events that
are considered a collaboration type event will be posted to the shared
"project" definition managed by Corona. These collaboration events will
also be distributed to any other RCP that has the same shared "project"
open. This will enable the workgroup to have a shared view of project
related activity.



This scenario for an exemplary Tool X candidate could be used for
requirements tools, development tools, testing tools, etc. The value that
Corona brings is the shared context of a "project". This context can be
shared by tools within the same workgroup (ie: development tools) as well as
tools that span ALM steps. Corona's ability to manage the shared context of
a "project" enables a historical perspective of each "project" and its
artifacts as they travel across the ALM.


-Dennis

"Bob Brady" <rbrady@segue.com> wrote in message
news:1992413b88a45e1436b232217b1b610b$1@www.eclipse.org...
> Hello Corona Team,
>
> I'm interested in integrating one of several ALM tools into the Corona
> framework. However, I'm not clear on which tools at my disposal would be
> best suited as a candidate for Corona.
> Can somebody please recommend a list of characteristics that would make a
> "Tool X" an exemplary candidate for integration into Corona vs. say, a
> good candidate for integration into the ALF project?
>
> I think a server-side tool which already has a web services interface but
> no eclipse client (plugin or rcp) are some characteristics a good ALF
> candidate.
>
> Thank you,
> Bob
>
Previous Topic:Knowledge Collection in Corona Workbench
Next Topic:VCS collaboration events
Goto Forum:
  


Current Time: Wed Oct 22 09:37:35 GMT 2014

Powered by FUDForum. Page generated in 0.01586 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software