Handling UML profile attribute access & partit

[Hermes]

Dear All,

I'm working to a UML profile to be managed by my Add-in.

But I have two doubts about EA support to UML profiles:

--------------------------------
1. Is possible to handle access privileges to tagged values?

I.E. I would like to include some taggedValues not manually updable by users, but updable only by my Addin. Users can only read this taggedvalues. Is it possible?

I need this feature to handle attributes like requirement metrics.

--------------------------------
2. I'd like to model a <<Myrequirement>> sterotype.
This stereotype have two sets of attributes:
   - static attributes: that will not change in the model during its lifetime;
   - dynamic attributes: that will often change during time.

For design & Clarity reasons I would like (if possible) to have a sort of logical division beetween this two attribute sets (for example, by assigning a different stereotype to them).

How can I do this?

Thank you!

/D

[g.makulik]

1. Is possible to handle access privileges to tagged values?

No that's not possible AFAIK ...

2.  <snip>
For design & Clarity reasons I would like (if possible) to have a sort of logical division beetween this two attribute sets (for example, by assigning a different stereotype to them).

Yes, I think this is feasible somehow. It's possible to e.g. let these stereotypes derive (generalize) from different (abstract) base stereotypes, that you can distinguish them (as far it's possible to retrieve this information from the AddIn API, or a SQL-query).
It's not possible to group them in the 'Tagged Values' view by category or such AFAIK.

HTH
Günther

[Hermes]

2. Yes, That work!

1. It is as I supposed to be.
Actually I've developed a "Sync" function that works  asynchronously to restore the model coherence,
but in this manner i think that end-users will have some troubles to understand wich tags thay can modify and wich tag they do not.

Any idea to how manage "user read only" tagged-values?


Thank You Günther,

/D

[Paolo F Cantoni]

[size=18]...[/size]
Any idea to how manage "user read only" tagged-values?
[size=18]...[/size]

We use "special characters" such as:

[size=16]æ[/size], [size=16]¬[/size], [size=16]©[/size], [size=16]§[/size]

To indicate "special" tags - such as those maintained by automation.

HTH,
Paolo

[Hermes]

Yes! It could be a good tradeoff.

Thanks Paolo,

/Daniele

[Paul Murphy]

You can create read-only and read/write tagged values for steretypes by creating the read-only ones as const type pre-defined tagged values;
i.e.
  Tag Name: rootPath
  Detail: Type=Const;

These are added to the stereotype as described in the "Define Stereotype Tagged Values" section of the user guide.

Create a const predefined tag for each of your read-only tagged value types and make sure that they are exported to your stereotype profile.

When an element is created with the stereotype, its read-only tagged values will display greyed out in the UI and thus be uneditable. However, they can be modified by your addin as required.

HTH

Paul

[Makulik]

Hi Paul,

Interesting aspect. But I'm afraid that would not solve Hermes' problem. Because tagged values defined like you proposed will be read only in general, and not only for particular users, as I have understood Hermes want's to behave them.
Anyway, interesting aspect, as mentioned.

[edit]OK, the AddIn could manage user priviledged access ...[/edit]

WBR
Günther

[Oliver F.]

1. Is possible to handle access privileges to tagged values?

I.E. I would like to include some taggedValues not manually updable by users, but updable only by my Addin. Users can only read this taggedvalues. Is it possible?

I need this feature to handle attributes like requirement metrics.

On the element level you could apply a user lock by a special user (eg. "add-in"), then your add-in accesses the repository with that account, resets the lock, changes the tagged value, and sets the lock again.

Unfortunately this only works on the element level so your element is not accessable by anyone else.

So the only option is to capture the change of the tagged value in your add-in and punch the user for doing so (while resetting the tag afterwards).

Oliver

[Hermes]

You can create read-only and read/write tagged values for steretypes by creating the read-only ones as const type pre-defined tagged values;
i.e.
  Tag Name: rootPath
  Detail: Type=Const;

That's GREAT  

I really needed it!
(sorry I've not seen your posts before   )

I will implement this feature ASAP!
 
Thankyou all...

/D