Eclipse Community Forums: EPF » EPF Composer X EPF Wiki

Help

Home

Home » Archived » EPF » EPF Composer X EPF Wiki

Show: Today's Messages :: Show Polls :: Message Navigator

EPF Composer X EPF Wiki [message #55492]

Wed, 11 February 2009 19:52

Fernanda Oliveira

Messages: 21
Registered: July 2009

Junior Member

Hi,
I´d like to know, to understand better, what EPF Composer tool has that
EPF Wiki doesn´t have (features).
Maybe a comparison with when I should use one and when I should use another.

I have been using EPF Composer for 2 years, and usually I have problems
with “non-technical” users, because these users that don´t know eclipse
framework/tools in general think it´s complex to use EPF Composer, and
now I think the wiki it is the solution to incentive the processes
documentation by “non-technical” users, because wiki format seems to be
easier to understand.

What I understood until the moment that is the correct way of working:
1) Create the Library: We should create all process structure in EPF
Composer, creating the “Library”, then publish the site.
2) Generate the Wiki: then we should generate the EPF Wiki based on the
generated site.
3) Process Maintanance/Evolution: all users can edit the process and
approve it ni EPF Wiki.
4) Final Release Publish: Then we should “re-generate” the “Library”
(harvesting) to be opened in EPF Composer to execute some structure
changes, if necessary, and publish the final release (EPF Site or Wiki)
with all users modifications.

Is it correct?

Thank you in advance,

Fernanda

Report message to a moderator

Re: EPF Composer X EPF Wiki [message #55600 is a reply to message #55492]

Thu, 19 February 2009 00:36

Ricardo Balduino

Messages: 191
Registered: July 2009

Senior Member

Fernanda,

At this time, there isn't a comparison table between EPF Composer and EPF
Wiki (not that I know of). However, your assumptions below (in terms of
usage model) are correct. The EPF Wiki opens the door for non-technical
users (non-technical in the sense they don't need to know the process
metamodel) to collaborate and improve their process descriptions. However, a
more robust environment to capture, author, extend, configure and publish a
process is EPF Composer.

Ricardo.

"Fernanda Oliveira" <fernanda.stringassi@venturus.org.br> wrote in message
news:gmvabd$hi9$1@build.eclipse.org...
> Hi,
> I

Report message to a moderator

Re: EPF Composer X EPF Wiki [message #55776 is a reply to message #55600]

Tue, 03 March 2009 12:39

Fernanda Oliveira

Messages: 21
Registered: July 2009

Junior Member

Hi Ricardo,
Thank you your information. I think I´m in the right way.
I installed and tested the Wiki and worked fine.
But until the moment I couldn´t discover HOW to transform a wiki in a
EPFC Library. I selected my changes as "Review Completed (harvesting)"
but now I´d like to see how my changes impacted the Library to generate
a release.

Thank you,
Fernanda

Ricardo Balduino escreveu:
> Fernanda,
>
> At this time, there isn't a comparison table between EPF Composer and EPF
> Wiki (not that I know of). However, your assumptions below (in terms of
> usage model) are correct. The EPF Wiki opens the door for non-technical
> users (non-technical in the sense they don't need to know the process
> metamodel) to collaborate and improve their process descriptions. However, a
> more robust environment to capture, author, extend, configure and publish a
> process is EPF Composer.
>
> Ricardo.
>
> "Fernanda Oliveira" <fernanda.stringassi@venturus.org.br> wrote in message
> news:gmvabd$hi9$1@build.eclipse.org...
>> Hi,
>> I´d like to know, to understand better, what EPF Composer tool has that
>> EPF Wiki doesn´t have (features).
>> Maybe a comparison with when I should use one and when I should use
>> another.
>>
>> I have been using EPF Composer for 2 years, and usually I have problems
>> with “non-technical” users, because these users that don´t know eclipse
>> framework/tools in general think it´s complex to use EPF Composer, and now
>> I think the wiki it is the solution to incentive the processes
>> documentation by “non-technical” users, because wiki format seems to be
>> easier to understand.
>>
>> What I understood until the moment that is the correct way of working:
>> 1) Create the Library: We should create all process structure in EPF
>> Composer, creating the “Library”, then publish the site.
>> 2) Generate the Wiki: then we should generate the EPF Wiki based on the
>> generated site.
>> 3) Process Maintanance/Evolution: all users can edit the process and
>> approve it ni EPF Wiki.
>> 4) Final Release Publish: Then we should “re-generate” the “Library”
>> (harvesting) to be opened in EPF Composer to execute some structure
>> changes, if necessary, and publish the final release (EPF Site or Wiki)
>> with all users modifications.
>>
>> Is it correct?
>>
>> Thank you in advance,
>>
>> Fernanda
>
>

Report message to a moderator

Re: EPF Composer X EPF Wiki [message #56180 is a reply to message #55776]

Wed, 18 March 2009 15:41

Ricardo Balduino

Messages: 191
Registered: July 2009

Senior Member

Fernanda,

There is no automated harvesting from the Wiki to EPF Composer at this time.
You want to manually copy the text from the Wiki, to EPFC or manually add
new text to EPFC based on comments users put in the Wiki.
You mark the page as "harvested" in the Wiki so when you upload a new
baseline process, the Wiki will override that page. If you don't mark the
page as harvested, then the new upload will keep the commented/altered
version of the page even though a new baseline process is being uploaded
(that's what I understand about this functionality - others, please correct
me if that's not how it goes).

Ricardo.

"Fernanda Oliveira" <fernanda.stringassi@venturus.org.br> wrote in message
news:goj8ef$786$1@build.eclipse.org...
> Hi Ricardo,
> Thank you your information. I think I

Report message to a moderator