Hello EPF Dev,

I am constructing a lifecycle process in much the same way as OpenUP
have done with activities inherited from reference workflow capability
patterns.

Having added tasks to the reference capability patterns and extended
them into a lifecycle, the resultant team allocation tab displays all of
the roles assigned to those tasks, and all of the work products that the
role relates to.

I understand that this is because a Role Descriptor is added along with
the task descriptor to the process. Is the purpose of the team
allocation tab to demonstrate what work products the role is involved
with in context of that activity? If so, why is the default behaviour to
inherit all of the products into the role descriptor?

Also, if the source role changes or the products that they interact with
changes, are these changes reflected in the role descriptors?

Thanks for your help in advance,

Jeff

Please consider the environment before printing this email.

This message should be regarded as confidential. If you have received this 
email in error please notify the sender and destroy it immediately.
Statements of intent shall only become binding when confirmed in hard copy by 
an authorised signatory.  The contents of this email may relate to dealings 
with other companies within the Detica Limited group of companies.

Detica Limited is registered in England under No: 1337451.

Registered offices: Surrey Research Park, Guildford, Surrey, GU2 7YP, England.

_______________________________________________
epf-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/epf-dev

Reply via email to