[One-project-devel] dynamic issues

[Pierfranco F. <pfe...@so...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

another issue relevant and found in D1.2 is related to the management of
"dynamic issues" (it's a new definition I have introduced for this purpose).
The requirement is that in both the setup and the runtime the
participant must be able to create new issues that where not specified
in the model.

There are two type of dynamic issues:
1. setup time
2. run-time

Setup-time
- ----------
the owner be able to choose from a list one or more issue about an item
at set-up time. The list of allowable issues can defined at modelling
time: a proper model in the MM, so do a mechanism in Editor, has yet to
be defined and implemented.
A a suggestion: "Setup-time" might be an attribute of one or more issues
in the information model, if true it can be added or removed at set-up
time. Setup-time issue can not be referenced in the action language
since they might not be available at run-time.
- From the implementation viewpoint the decision at setup will not affect
the model, but rather the instance (M0) as if the issues chosen were not
present in the original XMI model (M1).

Run-time
- --------
the participant can create an issue on the fly in the negotiation
console. This can be implemented by creating a  "Run-time Issue Allowed"
attribute (Yes/No ,Changeable: yes: allowed. No: not allowed, is also
Changeable = tre then the Setup can modify these values otherwise not)
of the information model and be set in the editor as well as in the setup.
The engine will allow the creation of a new issue at any tine while in
the Negotiating Stage. This issue might be as an object (M0) in the
instance model of the negotiation, an instance of entity "run-time
issue" (M1). The original model stored in the KDB has not to be
affected, so do the instance model in the XMI model (in the DKB), the
fact that this object was created in memory at run-time will be stored
in the log/history for possible post-processing purposes: this
information is indeed valuable.
NS: a negotiation model can have only one type of dynamic issue.

considerations
- --------------
Using dynamic issues has some negative congruences:
- - If over-used they will badly affect the reuse of models and even
reduce the use of the Editor:
- - It does not allow the use of the action language.
- - The recommender will have no clause about this issue and be unable to
make valuable recommendation.
Even if I understand the value of this requirement from a user
perspective, dynamic issue might de-structure the life-cycle of the
negotiation and the strategy we set for the architecture. I suggest a
very cautious approach.

best regards
Pierfranco

- --
Soluta.net

Pierfranco Ferronato
CIO and Founder
Soluta.Net,Italy
Innovation in Action
http://www.soluta.net

Tel: +39-0423-915547
Fax: +39-0423-915547
ICQ: 297565827
Skype: pferronato

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHaUQks+zjG7yrDdQRAiwbAJ91gQmwXW7OlpQCQ/5nqW4tjkN6JwCgph4s
s7vIQCqYAk8eU/6+YF8NwIQ=
=fGA0
-----END PGP SIGNATURE-----