| Task and their descriptors [message #3429] |
Sat, 25 February 2006 12:07  |
Eclipse User |
|
|
|
Originally posted by: rich.weiskopf.anvi.com
When a descriptor for a task is generated (using capability patterns),
elements (ex. purpose, main desc.) that are part of the original task
definition are not carried forward into the Task Descriptor definition.
After publishing, the data is available; although necessitating an awkward
approach (applet tree: delivery process->capability pattern->Work
Breakdown(Breakdown element) -> Task->Based on Method. .......This brings up
the original Task definition.
Is there some way of carrying forward into the Task Descriptor all of the
elements? Or does one have to cut and paste from the task definition into
the task descriptor?
|
|
|
| Re: Task and their descriptors [message #3562 is a reply to message #3429] |
Mon, 27 February 2006 22:05  |
| Eclipse User |
|
|
|
The idea is that you not publish the same information over and over again.
Image defining a process in which the same task is performed twenty times.
You would define twenty descriptors each with all the descriptions
duplicated. By keep the general descriptions factored into the task you
avoid a maintenance problem. Descriptors should only contain the
information which is different from the original task, e.g. they could have
different input/outputs, different performers, they selected a sub-set of
the steps defined for the task as well as can contain additional text
describing how the task is performed differently at that particular point in
the lifecycle.
However, it has been suggested to work with iframes to display the task
information inside the descriptor page or to use more frames in general or
to actually provide a publication option to redundantly publish the
information. We are looking into all of these possibilities in the future.
--
Thanks and best regards,
Peter Haumer.
____________________________________________________________ __
PETER HAUMER
IBM | Eclipse Process Framework Committer
____________________________________________________________ __
"Rich Weiskopf" <rich.weiskopf@anvi.com> wrote in message
news:dtq2ro$aeh$1@utils.eclipse.org...
> When a descriptor for a task is generated (using capability patterns),
> elements (ex. purpose, main desc.) that are part of the original task
> definition are not carried forward into the Task Descriptor definition.
>
> After publishing, the data is available; although necessitating an awkward
> approach (applet tree: delivery process->capability pattern->Work
> Breakdown(Breakdown element) -> Task->Based on Method. .......This brings
> up the original Task definition.
>
> Is there some way of carrying forward into the Task Descriptor all of the
> elements? Or does one have to cut and paste from the task definition into
> the task descriptor?
>
>
|
|
|
| Re: Task and their descriptors [message #561644 is a reply to message #3429] |
Mon, 27 February 2006 22:05 |
| Eclipse User |
|
|
|
The idea is that you not publish the same information over and over again.
Image defining a process in which the same task is performed twenty times.
You would define twenty descriptors each with all the descriptions
duplicated. By keep the general descriptions factored into the task you
avoid a maintenance problem. Descriptors should only contain the
information which is different from the original task, e.g. they could have
different input/outputs, different performers, they selected a sub-set of
the steps defined for the task as well as can contain additional text
describing how the task is performed differently at that particular point in
the lifecycle.
However, it has been suggested to work with iframes to display the task
information inside the descriptor page or to use more frames in general or
to actually provide a publication option to redundantly publish the
information. We are looking into all of these possibilities in the future.
--
Thanks and best regards,
Peter Haumer.
____________________________________________________________ __
PETER HAUMER
IBM | Eclipse Process Framework Committer
____________________________________________________________ __
"Rich Weiskopf" <rich.weiskopf@anvi.com> wrote in message
news:dtq2ro$aeh$1@utils.eclipse.org...
> When a descriptor for a task is generated (using capability patterns),
> elements (ex. purpose, main desc.) that are part of the original task
> definition are not carried forward into the Task Descriptor definition.
>
> After publishing, the data is available; although necessitating an awkward
> approach (applet tree: delivery process->capability pattern->Work
> Breakdown(Breakdown element) -> Task->Based on Method. .......This brings
> up the original Task definition.
>
> Is there some way of carrying forward into the Task Descriptor all of the
> elements? Or does one have to cut and paste from the task definition into
> the task descriptor?
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04160 seconds
Home