Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Evolution of the model validation solution in Papyrus
Hi,


In this specific case, I think "DSML Validation" means "Profile-/Stereotype- specific validation" (i.e. extension of default UML Validation for a specific Language/Profile)

> I don't understand not defining a stereotype.

That's a common request from users to be able to add some constraints to UML without using a Profile (i.e. a Lightweight mechanism), but it really seems to be a bad practice. What could possibly make sense is to provide a specific tool (Related to the Dynamic Profile Definition tool?) to define Stereotype Constraints without actually going through all the steps to create a Profile, Required Stereotype, ... The user could e.g. specify a new Constraint for all "uml::Class", and Papyrus would under the hoods create a new Profile, a new required Stereotype extending Class, attach the constraint to this Stereotype, then define & apply the profile on the current model. Part of this tooling already exists (I'm not sure what the status of this tool is exactly today), so it could be extended for supporting Constraints.

In addition to these new features, I think some things already exist which are not (completely/at all) integrated in Papyrus, e.g. Constraints Severity/Message/Kind..., Complete OCL Support...


Camille
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mdt-papyrus.dev-bounces@xxxxxxxxxxx] de la part de Ed Willink [ed@xxxxxxxxxxxxx]
Envoyé : mercredi 3 décembre 2014 09:02
À : mdt-papyrus.dev@xxxxxxxxxxx
Objet : Re: [mdt-papyrus.dev] Evolution of the model validation solution in Papyrus

Hi Christian

Requirements

  • extensible validation for DSMLs, contributing domain-specific constraints via profiles and/or other mechanisms
  • users should be able to select which constraints to include/exclude in the validation operation
  • it should not be necessary for a profile to define a stereotype extending a metaclass just to define constraints for that metaclass (this leads to required extensions). A profile should be able to constrain a referenced metaclass without reference to any stereotype
Beyond being obviously a good idea, I'm not sure what extensible validation for DSMLs means. AFAICS DSML is just a politically more acceptable/exciting term than the discredited UML modeling. So if UML validation works, DSML validation works too.

It would be good to allow users to have a validation configuration so that large projects can easily switch between quick / thorough / aspectX / ... validation configurations. So a model of validation configurations behind a DSL.

I don't understand not defining a stereotype. This seems to require a UML change/extension. UML supports mandatory stereotype application so constraints defined in a stereotype can be applied automatically, if their profile is applied.

===================

OCL 2.5 will probably introduce a small profile to support gaps in UML

a) Integer/Real precision/rounding/overflow

b) InstanceSpecification validation enable/disable

Perhaps something more helpful can be provided in respect of validation control.

    Regards

        Ed Willink

On 02/12/2014 20:18, Christian W. Damus wrote:
Hi, team,

Pursuant to the brief discussion that we had at the Papyrus Summit in October, I have captured some notes that are my attempt to frame the problem and provide a context for deciding as a group how we will steer Papyrus towards a coherent long-term model validation solution:

https://wiki.eclipse.org/Papyrus/Mars_Discussion/Validation

Please feel free to edit this page to fill in gaps, correct mistakes and misunderstandings, and otherwise contribute anything helpful.  We can exchange ideas here on the mailing list or in the wiki (do we use the talk pages much at Eclipse?) to come to a decision about what we should attempt to do in the Mars release and later to bring our validation pieces to a happy place.

Cheers,

Christian


_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev


No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5577 / Virus Database: 4235/8669 - Release Date: 12/02/14


Back to the top