| Aggregation of concepts [message #39710] |
Thu, 06 September 2007 05:58  |
Eclipse User |
|
|
|
Hi,
I'm considering the best approach where to link a particular concept;
let's have a concept How to plan a project in tool X. I can definitely link
it to the task Plan the project, however, it makes sense to make it
available via PM Role and PM Discipline.
What is your recommendation? link it to as many places as possible? Or does
MC aggregates the concepts automatically on dicipline or role level?
Thanks,
Roman
|
|
|
|
| Re: Aggregation of concepts [message #40087 is a reply to message #39710] |
Fri, 07 September 2007 01:25  |
| Eclipse User |
|
|
|
Hello Roman.
This is a good question. One consideration you should keep in mind is that
you might want to reuse your method elements in various contexts. Hence,
you might not want to 'hard-wire' your PM role with a specific way of doing
project management, but keep that guidance close to the tasks and activities
that model this specific way. This would allow you to use that role as well
when you decide to create a plugin that defines a different management
approach. To support you with this separation we provide different guidance
kinds to should be used to focus on different aspects. For example, we
separate concepts from guidelines. The concept would provide more static
information describing 'what things are' that can be related to work
products or roles. Guideline describe 'how to' giving background on how to
perform specific tasks or guidelines. The guidance types help to keep
focused on such separations of concerns to decouple your method and process
elements from each other to increase reuse.
If reuse and scale is not a design goal of yours, you could surely also link
as many elements to each other to ensure that information is readily
available wherever users look. It is a trade-off.
Peter.
"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:fboj0s$fe3$1@build.eclipse.org...
> Hi,
>
> I'm considering the best approach where to link a particular concept;
> let's have a concept How to plan a project in tool X. I can definitely
> link it to the task Plan the project, however, it makes sense to make it
> available via PM Role and PM Discipline.
>
> What is your recommendation? link it to as many places as possible? Or
> does MC aggregates the concepts automatically on dicipline or role level?
>
> Thanks,
>
> Roman
>
|
|
|
| Re: Aggregation of concepts [message #582927 is a reply to message #39710] |
Thu, 06 September 2007 18:48 |
| Eclipse User |
|
|
|
Roman,
There's no automatic aggregation of guidance types (concepts, etc.) on a
discipline or role level.
The suggestion is to attach the guidance to the elements where you would
like to see the guidance referenced.
Regards,
Ricardo Balduino.
"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:fboj0s$fe3$1@build.eclipse.org...
> Hi,
>
> I'm considering the best approach where to link a particular concept;
> let's have a concept How to plan a project in tool X. I can definitely
> link it to the task Plan the project, however, it makes sense to make it
> available via PM Role and PM Discipline.
>
> What is your recommendation? link it to as many places as possible? Or
> does MC aggregates the concepts automatically on dicipline or role level?
>
> Thanks,
>
> Roman
>
|
|
|
| Re: Aggregation of concepts [message #582958 is a reply to message #39710] |
Fri, 07 September 2007 01:25 |
| Eclipse User |
|
|
|
Hello Roman.
This is a good question. One consideration you should keep in mind is that
you might want to reuse your method elements in various contexts. Hence,
you might not want to 'hard-wire' your PM role with a specific way of doing
project management, but keep that guidance close to the tasks and activities
that model this specific way. This would allow you to use that role as well
when you decide to create a plugin that defines a different management
approach. To support you with this separation we provide different guidance
kinds to should be used to focus on different aspects. For example, we
separate concepts from guidelines. The concept would provide more static
information describing 'what things are' that can be related to work
products or roles. Guideline describe 'how to' giving background on how to
perform specific tasks or guidelines. The guidance types help to keep
focused on such separations of concerns to decouple your method and process
elements from each other to increase reuse.
If reuse and scale is not a design goal of yours, you could surely also link
as many elements to each other to ensure that information is readily
available wherever users look. It is a trade-off.
Peter.
"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:fboj0s$fe3$1@build.eclipse.org...
> Hi,
>
> I'm considering the best approach where to link a particular concept;
> let's have a concept How to plan a project in tool X. I can definitely
> link it to the task Plan the project, however, it makes sense to make it
> available via PM Role and PM Discipline.
>
> What is your recommendation? link it to as many places as possible? Or
> does MC aggregates the concepts automatically on dicipline or role level?
>
> Thanks,
>
> Roman
>
|
|
|
Powered by
FUDForum. Page generated in 0.05126 seconds
Home