Re: [epf-dev] Allowing late changes in published configurations

["Ricardo Martinho" <rmartin.email@xxxxxxxxx>]

I Nate,

Thanks for answering in such a short notice...

Here's
a pretty simple example: A senior software process modeler designs the
overall model of a UP-based configuration to be used in her company. As
she's not an expert in designing software, she wants to mark the
Elaboration Phase as an element that can be late-modeled (finished) by
other more skillfull process participants. However, she has some
restrictions, i.e., she wants to let know other process participants
which and how properties of the Elaboration Phase can be changed (e.g.
the "Refine System Scope and Requirements" activity behavior design can
be finished at the instance/project level, but not to be reflected at
the configuration/model level).

Resuming, she wants to publish the UP-based configuration, and
mark which and how elements are to be flexible. Thus, the published
configuration must allow these restricted changes to be made by other
process participants. In the example above, they must be able to
complete the definition/modeling of the aforementioned activity
behavior.

Mainly, we must provide a way to mark those configuration
elements as flexible (visually/through a properties' form). Then, we
must create a publishing plugin to enable those restricted changes in
the published configuration.

In one sentence: "I want to tell my software team which, where and how can they change my configuration.".

Does that make any sense to you?

Thanks in advance,

Ricardo Martinho.

On 10/19/07, Nate Oster <noster@xxxxxxxxxxxxx> wrote:

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.

_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev

-- 
Ricardo Martinho.
-------------------------------------------------------------
Departamento de Engenharia Informática
ESTG - IPLeiria
Campus 2, Morro do Lena - Alto do Vieiro
Apartado 4163, 2411-901 - Leiria, Portugal