Home » Eclipse Projects » Technology Project and PMC » EPF -- Process Aspects
| EPF -- Process Aspects [message #70221] |
Tue, 29 November 2005 14:10  |
Eclipse User |
|
|
|
Originally posted by: eclipse.ambysoft.com
I was wondering how we intended to handle what I call, for lack of a
better term, "process aspects". A process aspect is a concept woven
throughout a process. For example, Extreme Programming (XP)'s value
of Simplicity would be an example of a process aspect. Or Agile
Data's Sweet Spot philosophy. These aspects can have a huge impact on
the overall process, potentially affecting every task.
- Scott
|
|
|
| Re: EPF -- Process Aspects [message #70262 is a reply to message #70221] |
Tue, 29 November 2005 18:55  |
| Eclipse User |
|
|
|
This is a great idea. We had requests like these before, but did not have
the time to think about ways of modeling such more advanced relationships in
a simple way.
You probably know of the 'contribution', 'replace', and 'extends'
variability relationships that we currently support to define changes on
specific elements from plug-ins which can be valid in specific
configurations. One of Ricardo's demo videos on the eclipse server shows an
example of how to contribute a new work product responsibility (Service) to
a specific role (Architect) in a plug-in that extends BUP. Similarly, you
can contribute steps to a task, replace work products, contribute new roles
to a task, etc.
For "process aspects" such a variability relationships would be defined in a
way such as instead of having the currently fixed many variability elements
to one base element association, it would probably be a declarative pointcut
definition.
If you have detailed examples, ideas for how to specify pointcuts, or
perhaps suggestions for meta-model and UI extensions, please send it to us.
Best regards,
Peter Haumer.
____________________________________________________________ __
Rational Software | IBM Software Group
PETER HAUMER, Dr. rer. nat.
RUP Development, Cupertino, CA
Tel/Fax: +1 408 863-8716
Email: mailto:phaumer@us.ibm.com
____________________________________________________________ __
"Scott W. Ambler" <eclipse@ambysoft.com> wrote in message
news:lo9po15imejtsafhd8o4540toohrt3md61@4ax.com...
>I was wondering how we intended to handle what I call, for lack of a
> better term, "process aspects". A process aspect is a concept woven
> throughout a process. For example, Extreme Programming (XP)'s value
> of Simplicity would be an example of a process aspect. Or Agile
> Data's Sweet Spot philosophy. These aspects can have a huge impact on
> the overall process, potentially affecting every task.
>
> - Scott
|
|
|
| Re: EPF -- Process Aspects [message #599738 is a reply to message #70221] |
Tue, 29 November 2005 18:55 |
| Eclipse User |
|
|
|
This is a great idea. We had requests like these before, but did not have
the time to think about ways of modeling such more advanced relationships in
a simple way.
You probably know of the 'contribution', 'replace', and 'extends'
variability relationships that we currently support to define changes on
specific elements from plug-ins which can be valid in specific
configurations. One of Ricardo's demo videos on the eclipse server shows an
example of how to contribute a new work product responsibility (Service) to
a specific role (Architect) in a plug-in that extends BUP. Similarly, you
can contribute steps to a task, replace work products, contribute new roles
to a task, etc.
For "process aspects" such a variability relationships would be defined in a
way such as instead of having the currently fixed many variability elements
to one base element association, it would probably be a declarative pointcut
definition.
If you have detailed examples, ideas for how to specify pointcuts, or
perhaps suggestions for meta-model and UI extensions, please send it to us.
Best regards,
Peter Haumer.
____________________________________________________________ __
Rational Software | IBM Software Group
PETER HAUMER, Dr. rer. nat.
RUP Development, Cupertino, CA
Tel/Fax: +1 408 863-8716
Email: mailto:phaumer@us.ibm.com
____________________________________________________________ __
"Scott W. Ambler" <eclipse@ambysoft.com> wrote in message
news:lo9po15imejtsafhd8o4540toohrt3md61@4ax.com...
>I was wondering how we intended to handle what I call, for lack of a
> better term, "process aspects". A process aspect is a concept woven
> throughout a process. For example, Extreme Programming (XP)'s value
> of Simplicity would be an example of a process aspect. Or Agile
> Data's Sweet Spot philosophy. These aspects can have a huge impact on
> the overall process, potentially affecting every task.
>
> - Scott
|
|
|
Goto Forum:
Current Time: Sun Apr 27 09:11:55 EDT 2025
Powered by FUDForum. Page generated in 0.03705 seconds |
Home