You should look at the implementation of Andre Hora of some various metrics here: http://smalltalkhub.com/#!/~
It was working on Moose5.0, so it is possible that there is some adaptations to make for the latest version of Moose.
De : Moose-dev [firstname.lastname@example.org.
unibe.ch] de la part de Cris Fuhrman [email@example.com]
Date d'envoi : lundi 20 février 2017 21:30
À : Moose-related development
Objet : [Moose-dev] Re: CK metrics from Moose? (was Re: Publications of projects using Moose?)
The CK Metric I am looking for is CBO (Coupling Between Object Classes) for a class. The entire CK metrics suite was proposed in 1994 and several measures are controversial in OO software (read more here: http://www.virtualmachinery.
com/sidebar3.htm). So, thinking about my first request for "CK metrics", it might be hard to decide how to implement all of these for a general case that is FAMIX.
Looking more into what's in MOOSE, I see that CBO for a class can be estimated as CBO <= fanIn + fanOut. The "true" CK CBO value should not count an afferent and efferent link twice if it is to/from the same class (it's why I use <= in the estimation). See more at http://stackoverflow.com/a/
29877357/1168342-- I think CBO defined this way would be easy to calculate for a FAMIX class, but I didn't look at fanIn and fanOut yet to see when/how/where they're calculated.
I'm not sure how many people would want to see CBO in MOOSE. We're doing studies involving fault/change proneness, and CBO has been used as a measure quite often in published research in that area. It's why it would be useful to us.
On Mon, Feb 20, 2017 at 2:04 PM, Alexandre Bergel <firstname.lastname@example.org<
mailto:email@example.com[cid:F0DE6FBF-C7D5-45CB-8A19- >> wrote:
Indeed, CK Metrics should be one-click away from a Moose Model.
I have just implemented many of the CK metrics in the latest version of Moose (I updated Famix-Extensions in fact).
Is this what you had in Mind?
On Feb 20, 2017, at 1:48 PM, Cris Fuhrman <firstname.lastname@example.org<mailto:
I'm wondering if it's in the scope of Moose to get to the standard CK metrics for a model? It seems it's been done experimentally (https://pdfs.semanticscholar.
org/0eb2/) and I also found the momfe paper from 2002 (http://scg.unibe.ch/archive/ 14ec7c6288dc13564580beafc2609b 09118b.pdf projects/Bute02a.pdf) but appeared not to have all the CK metrics.
I also found the right-click on a Moose Model -> Export -> Export model to MSE, but there was nothing that looked like standard CK metrics in the exported file.
We are particularly trying to generate CBO (for a research comparison) for a few classes and would like to be able to do all our work in Moose if possible (especially with the visualizations in a RTView).
On Wed, Oct 5, 2016 at 11:58 AM, Hernán Morales Durand <email@example.com<
mailto:hernan.morales@gmail.Moosefirstname.lastname@example.org< com>> wrote:
Do you have good reference links to publications (yours or from other people) which uses Moose metrics for example in a "Material and Methods" section?
I mean *not* Moose projects publications (projects derived from Moose), but those projects which uses Moose analysis to report Cyclomatic Complexity, Halstead Length, WMC, DIT, CBO, etc . I want to see what and how people reports metrics for a software project using Moose. If publication is in a Journal outside of the field of Software Engineering field that would be better.
Moose-dev mailing list
Moose-dev mailing list
Alexandre Bergel http://www.bergel.eu
Moose-dev mailing list
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"