| Roles & Tasks in a published process [message #23606] |
Tue, 14 November 2006 12:27  |
Eclipse User |
|
|
|
Originally posted by: alexander.pehm.gmx.at
A simple example...
When I publish a process and click on a role to see the tasks that this
role performs I see every task wheter it is performed in this particular
process or not.
It's clear, that's because of the separation of content and its
application in a process.
But that's not very satisfying. I am interested in the tasks that are
performed by this role in a particular derivation of a process (only the
"role descriptor's" "task descriptors" so to speak), I'm not interested in
all the tasks that can be performed by this role.
The most elegant way would probably be to have a suitable package/plug-in
structure and to control which tasks get published or not by simply
selecting/deselecting packages in the method-configuration.
However, I can't imagine that it is realistic that I will find such a
structure as I have to support a wide range of development methods.
Is there another way to deal with that?
|
|
|
| Re: Roles & Tasks in a published process [message #23871 is a reply to message #23606] |
Thu, 16 November 2006 18:17  |
| Eclipse User |
|
|
|
Originally posted by: phaumer.xxx.com
You see this information in the Team Allocation View (TA). For example, you
can look at the TA for the whole of OpenUP Basic and see which tasks every
role performs or just one phase (or any other level of breakdown) of OpenUP
Basic and see the subset of tasks performed there. (Note, there was bug in
the TA in the official release of OpenUP Basic 0.9. Please use the latest
one or publish it yourself using 1.0.1 of the tool, which has this bug
fixed.)
--
Thanks and best regards,
Peter Haumer.
____________________________________________________________ __
PETER HAUMER
IBM | Eclipse Process Framework Committer
____________________________________________________________ __
"Alexander Pehm" <alexander.pehm@gmx.at> wrote in message
news:db79f8619c9760b03ce70f2a26bb01c9$1@www.eclipse.org...
>A simple example...
> When I publish a process and click on a role to see the tasks that this
> role performs I see every task wheter it is performed in this particular
> process or not.
> It's clear, that's because of the separation of content and its
> application in a process.
> But that's not very satisfying. I am interested in the tasks that are
> performed by this role in a particular derivation of a process (only the
> "role descriptor's" "task descriptors" so to speak), I'm not interested in
> all the tasks that can be performed by this role.
>
> The most elegant way would probably be to have a suitable package/plug-in
> structure and to control which tasks get published or not by simply
> selecting/deselecting packages in the method-configuration.
> However, I can't imagine that it is realistic that I will find such a
> structure as I have to support a wide range of development methods.
>
> Is there another way to deal with that?
>
|
|
|
| Re: Roles & Tasks in a published process [message #568658 is a reply to message #23606] |
Thu, 16 November 2006 18:17 |
| Eclipse User |
|
|
|
You see this information in the Team Allocation View (TA). For example, you
can look at the TA for the whole of OpenUP Basic and see which tasks every
role performs or just one phase (or any other level of breakdown) of OpenUP
Basic and see the subset of tasks performed there. (Note, there was bug in
the TA in the official release of OpenUP Basic 0.9. Please use the latest
one or publish it yourself using 1.0.1 of the tool, which has this bug
fixed.)
--
Thanks and best regards,
Peter Haumer.
____________________________________________________________ __
PETER HAUMER
IBM | Eclipse Process Framework Committer
____________________________________________________________ __
"Alexander Pehm" <alexander.pehm@gmx.at> wrote in message
news:db79f8619c9760b03ce70f2a26bb01c9$1@www.eclipse.org...
>A simple example...
> When I publish a process and click on a role to see the tasks that this
> role performs I see every task wheter it is performed in this particular
> process or not.
> It's clear, that's because of the separation of content and its
> application in a process.
> But that's not very satisfying. I am interested in the tasks that are
> performed by this role in a particular derivation of a process (only the
> "role descriptor's" "task descriptors" so to speak), I'm not interested in
> all the tasks that can be performed by this role.
>
> The most elegant way would probably be to have a suitable package/plug-in
> structure and to control which tasks get published or not by simply
> selecting/deselecting packages in the method-configuration.
> However, I can't imagine that it is realistic that I will find such a
> structure as I have to support a wide range of development methods.
>
> Is there another way to deal with that?
>
|
|
|
Powered by
FUDForum. Page generated in 0.03681 seconds
Home