Wow, Ricardo, that sounds pretty advanced!
I’m having a hard time imagining that in the abstract. Can you provide
some more detail?
In particular, a more complete example
might be helpful. Are you thinking of some situation in particular?
Thanks,
Nate
From:
epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Ricardo Martinho
Sent: Thursday, October 18, 2007
3:19 PM
To: epf-dev@xxxxxxxxxxx
Subject: [epf-dev] Allowing late
changes in published configurations
Dear All,
I'm working on the customization of EPF in order to allow the composition of
flexible configurations. This means that, basically, users should be allowed to
change configurations (through the publish perspective/published website?), but
only to a certain predefined degree of change. As an example, consider the
definition of a UP-based configuration, with a half-baked programming stage,
which should allow users to freely late-model the missing programming steps
according to some project specifics, but strictly requires an API reference as
a work product at the end.
This will imply extending the UMA metamodel with more specific flexibility
concepts and mechanisms to be associated with the SPEM modeling elements. It
will also imply a way to mark those elements (through stereotypes) in a
configuration that are somehow flexible. Finally, it must allow users to change
configurations in the publish perspective/published website, according to the
restricted flexible ways and mechanisms associated previously with the
configurations elements.
I'd like to have your guidelines (through the EPF code) regarding the way I can
do this. For now, I just want to be able to associate a predefined flexible
mechanism to a SPEM element (e.g. an Activity), and propagate that association
to the several views of that element, including the possibility to change it in
browsing perspectives, according to the associated flexible mechanism.
Thanks in advance,
Ricardo Martinho.