What fUML can bring to MBSE?

Loïc Fejoz

4th february 2011 Loïc Fejoz 2/19

More model semantics checking is needed.

Real models are complex.Syntactical verifications are nice but not enough.

4th february 2011 Loïc Fejoz 3/19

Ok those are simple examples but you can imagine others...

4th february 2011 Loïc Fejoz 4/19

This one could be very tricky as the Generalization is not drawn on the diagram.

4th february 2011 Loïc Fejoz 5/19

Activities verification is the #1 priority of the group that has written the report

called "Executable UML/SysML

semantics project report"

4th february 2011 Loïc Fejoz 6/19

Your models certainly contain less obvious

examples(especially for cross-diagram

elements)Remember that not all elements are visible on diagram. Moreover they are cross-cutting concerns of diagrams.

4th february 2011 Loïc Fejoz 7/19

fUML brings semantic checking possibility.

4th february 2011 Loïc Fejoz 8/19

(buml:Classifier “ZooPackage::SelfContentBlock“)(buml:Property “ZooPackage::SelfContentBlock::subpart“)(buml:ownedAttribute

“ZooPackage::SelfContentBlock““ZooPackage::SelfContentBlock::subpart“)

(buml:aggregation “ZooPackage::SelfContentBlock::subpart“ buml:composite)…(forall (o v f) (if (and (form:classifies “ZooPackage::SelfContentBlock“ o f) (form:property-value o “ZooPackage::SelfContentBlock::subpart“ v f)) (= o v)))

Those formulae are written in Common Logic Format (CLIF) with Process Specification Language (PSL).

FUML does not axiomatize all UML. It does not axiomatize SysML, nor OCL. But it can be trivialy extended for those examples.

4th february 2011 Loïc Fejoz 9/19

Boolean primitive types axiomatization:(forall (x) (if (buml:Boolean x) (or (= x form:true) (= x form:false))))

(not (= form:true form:false))…

Classification and generalization:(forall (csub csuper o f) (iff (buml:general csub csuper) (if (form:classifies csub o f) (form:classifies csuper o f))))

fULM Axiomatization

Obviously fUML provides axiomatization for primitive types, Classification, activity, etc.

4th february 2011 Loïc Fejoz 10/19

Those formulae may be verified automatically by some provers.Thus models can be formally

verified(and shall be).

4th february 2011 Loïc Fejoz 11/19

Time for a plugin !

Following slides will list tools and difficulty we have to develop an fUML plugin for Topcased.

4th february 2011 Loïc Fejoz 12/19

[template class2clif(clz : Class)](buml:Classifier [clz.clifName()/])[for (gen : Generalization | clz.generalization)](buml:general [gen.specific.clifName()/] [gen.general.clifName()/])[/for][for (prop : Property | clz.ownedAttribute)][property2clif(prop, clz)/][/for][/template]

Acceleo MTLThe generated Java is nor easy to (unit)test nor easy to call. To few documentations for programmatic use.

4th february 2011 Loïc Fejoz 13/19

ATLvs

QVT

We would prefer to use QVT but the ATL implementation is more advance.Not easy to write unit-tests especially when comparing with QVT.Usually we run ATL then MTL but it is not that easy to chain both tool without creating intermediate files.

4th february 2011 Loïc Fejoz 14/19

Warnings and errorsas feedbacks

This are getting better and easier from version to version.No documentation (again!) but the code of the simple verification made by TopCased editor is easy to read and reproduce.

4th february 2011 Loïc Fejoz 15/19

Quickfix?Which quickfix?

If we generate warnings it would be nice to propose quickfixes. We were not able to program some! There are stuff missing to do that... Moreover there are no documentation nor existing code.

4th february 2011 Loïc Fejoz 16/19

Diagram extension

A little bit of topic but... At one point we tried to extends the SysML activity diagram editor so as to present (some) activities with a different looking.We manage to do it but we violate some access restriction. The code is not written for that purpose and reuse is not made easy. Lots of copy'n paste.No documentation nor existing code.

4th february 2011 Loïc Fejoz 17/19

ResourceSet,Builder

andmodel updates

As we generate files for external programs, we have build a special builder to generate files on model modification but we also tried to update the model from files content.It is a real nightmare...

4th february 2011 Loïc Fejoz 18/19

Fast!Too fast?

Topcased evolves quite quickly so bugs are quickly corrected. BUT plugins also change to quickly and sometime (most of the time?) it involves incompatible changes.I have code from last summer that do not work anymore.Moreover the freeze period is to short for us to react and test our plugin.

4th february 2011 Loïc Fejoz 19/19

Conclusion● Interesting platform● Lots of plugins

● Models need more semantic checking

● To few documentation● Not stable enough● NIH syndrom (between EMF and core)