Hi Peter,
 
You’re correct that the purpose of
the method library is to allow people to make changes to the OpenUP process. Specifically,
the method library is the “source code” for OpenUP. The tool to
make these changes is the EPF Composer, which you can download from the EPF
website (www.eclipse.com/epf). EPF
Composer can publish the method library to create a website of software process
information.
 
The tool you desire, which sounds like kind
of a process mentor, doesn’t exist in EPF. But it’s a great idea
and there’s no reason it can’t be considered. You can enter a
Bugzilla change request against EPF (report it against the Tool) if you’d
like to participate in making such a tool come true.
 
Regarding the differences between Eclipse
and EPF, there are two answers:
 
 - Eclipse
     (www.eclipse.org) is an open source
     community for creating development tools. There are many different
     projects within the Eclipse organization, the most prominent being the one
     that builds the Eclipse tool. The Eclipse Process Framework (EPF) is one
     of the projects within Eclipse. Our job is to provide an extensible set of
     tools for authoring software development processes, and to actually author
     processes across a range of domains.
 
 - Eclipse
     is an open source tool that is an IDE, but also serves as an extensible
     platform for building other types of applications. The EPF Composer is an
     open source process authoring tool built on top of Eclipse. It’s
     used by the EPF project to author processes such as OpenUP. It’s also
     used by organizations and companies to extend EPF processes and even build
     their own processes from scratch.
 
 
Feel free to contact me if you have any
other questions.
 
- Jim
 
____________________
Jim Ruehlin, IBM
Rational
RUP Content
Developer
Eclipse Process
Framework (EPF) Committer
email:  
jruehlin@xxxxxxxxxx
phone: 
760.505.3232
fax:     
949.369.0720
 
 
 
 
From:
epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Peter Scott
<Peter@xxxxxxxx>
Sent: Friday, September 15, 2006
10:08 AM
To: epf-dev@xxxxxxxxxxx
Subject: [epf-dev] Executing
OpenUP in IDE
 
 
I am embarrassed to be asking this question, but after a reasonable 
amount of digging I am not sure of the answer. 
I believe I have made a large mistake in understanding the OpenUP 
method library. I am currently involved in selecting and evaluating an 
enterprise methodology. OpenUP looks attractive not least because of 
the software support. I came to this site and saw the two OpenUP 
products: a web site and a method library. I had formed the impression 
that the purpose of the method library was for members of a project to 
execute OpenUP in an IDE and that as they selected various steps it 
would tell them what artifacts to create, track where they were, 
remember role assignments, etc. 
I am now pretty sure I was wrong. After a lot of head scratching I now 
believe the purpose of the method library is to be able to make changes 
to the OpenUP process so that one can export a revised web site. Is 
that right? 
That function is useful to me, but nowhere near as useful as what I had 
imagined it was: an Eclipse plugin to guide team members through the 
stages of a project and track the products specifically required by 
OpenUP (vision document, etc). If such a tool existed it would 
immeasurably assist the adoption of OpenUP within our enterprise. Does 
it exist anywhere? 
And while I'm here can someone please explain to me the difference 
between Eclipse and EPF? Sorry to ask such a dumb question but after 
prowling around the web site for a few hours I'm still not sure. Or 
point me to a better place to ask this kind of question. Thanks. 
_______________________________________________ 
epf-dev mailing list 
epf-dev@xxxxxxxxxxx 
https://dev.eclipse.org/mailman/listinfo/epf-dev