| Re: [epf-dev] EPF Composer vs EPF Wiki ? |
Cristiano Gavião wrote:
So I could conclude that we still need EPF Composer to create our initial processes artifacts and after export it as web we can use with the EPFwiki.Pretty much yes. You could start with one of the already published processes (http://eclipse.org/epf/downloads/configurations/pubconfig_downloads.php) and modify it in EPF Wiki but I would not recommend this (you loose the advantages of formal process modeling)
But I think there is no way to get both synchronized after update them at wiki. Am I right ?Well actually there is a support mechanism in the EPF wiki called 'harvesting'. It allows you to mark changes as you manually copy/consolidate them to the EPF composer, so these get discarded once you republish the process.
There is no automatism, but I would not see the value of one either. EPF Wiki allows anybody to do ANY changes on the process, but the process engineer decides which changes make sense and add them to the common software engineering model in EPF composer supported by the tools meta model and consistency enforcement.
Rgds. GES