Hi,
I have a system with several classes and several packages. I want to do an Overview pyramid visualization. I select them all and when I do the pyramid it says NOP = 1 (number of packages equals 1), then I have a high NOC.
Why is this happening? Is it correct?
Thanks
I have the same result. Importing many packages results in NOP=1
Alexandre
On Mar 3, 2015, at 7:41 AM, Sebastian Tleye sebastian.tleye@gmail.com wrote:
Hi,
I have a system with several classes and several packages. I want to do an Overview pyramid visualization. I select them all and when I do the pyramid it says NOP = 1 (number of packages equals 1), then I have a high NOC.
Why is this happening? Is it correct?
Thanks
-- Sebastián Tleye _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
But is this correct or there is a problem?
2015-03-03 15:03 GMT+01:00 Alexandre Bergel alexandre.bergel@me.com:
I have the same result. Importing many packages results in NOP=1
Alexandre
On Mar 3, 2015, at 7:41 AM, Sebastian Tleye sebastian.tleye@gmail.com
wrote:
Hi,
I have a system with several classes and several packages. I want to do
an Overview pyramid visualization. I select them all and when I do the pyramid it says NOP = 1 (number of packages equals 1), then I have a high NOC.
Why is this happening? Is it correct?
Thanks
-- Sebastián Tleye _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
That makes sense, as the OverviewPyramidMetrics use nop := aMooseModel allModelNamespaces size.
There is no test in Famix-Tests-Extensions that tells me what to expect. It is something I noticed when migrating it.
Stephan
http://forum.world.st/OverviewPyramid-metrics-td4782812.html
On 03-03-15 15:03, Alexandre Bergel wrote:
I have the same result. Importing many packages results in NOP=1
Alexandre
On Mar 3, 2015, at 7:41 AM, Sebastian Tleye sebastian.tleye@gmail.com wrote:
Hi,
I have a system with several classes and several packages. I want to do an Overview pyramid visualization. I select them all and when I do the pyramid it says NOP = 1 (number of packages equals 1), then I have a high NOC.
Why is this happening? Is it correct?
Thanks
-- Sebastián Tleye _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Name: Famix-Extensions-StephanEggermont.283 Author: StephanEggermont Time: 3 March 2015, 3:39:46.019928 pm UUID: 727a4f0e-c96c-43c6-8903-6ca15bc76c7a Ancestors: Famix-Extensions-TudorGirba.282
Use pacakges instead of namespaces for nop OverviewPyramidMetrics
On 03-03-15 15:29, stephan wrote:
That makes sense, as the OverviewPyramidMetrics use nop := aMooseModel allModelNamespaces size.
There is no test in Famix-Tests-Extensions that tells me what to expect. It is something I noticed when migrating it.
Stephan
http://forum.world.st/OverviewPyramid-metrics-td4782812.html
On 03-03-15 15:03, Alexandre Bergel wrote:
I have the same result. Importing many packages results in NOP=1
Alexandre
On Mar 3, 2015, at 7:41 AM, Sebastian Tleye sebastian.tleye@gmail.com wrote:
Hi,
I have a system with several classes and several packages. I want to do an Overview pyramid visualization. I select them all and when I do the pyramid it says NOP = 1 (number of packages equals 1), then I have a high NOC.
Why is this happening? Is it correct?
Thanks
-- Sebastián Tleye _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes, but that will break the Overview Pyramid for Java systems.
We need to find a solution that deals with this variation if we want to keep the Overview Pyramid at all.
Doru
On Tue, Mar 3, 2015 at 3:40 PM, stephan stephan@stack.nl wrote:
Name: Famix-Extensions-StephanEggermont.283 Author: StephanEggermont Time: 3 March 2015, 3:39:46.019928 pm UUID: 727a4f0e-c96c-43c6-8903-6ca15bc76c7a Ancestors: Famix-Extensions-TudorGirba.282
Use pacakges instead of namespaces for nop OverviewPyramidMetrics
On 03-03-15 15:29, stephan wrote:
That makes sense, as the OverviewPyramidMetrics use nop := aMooseModel allModelNamespaces size.
There is no test in Famix-Tests-Extensions that tells me what to expect. It is something I noticed when migrating it.
Stephan
http://forum.world.st/OverviewPyramid-metrics-td4782812.html
On 03-03-15 15:03, Alexandre Bergel wrote:
I have the same result. Importing many packages results in NOP=1
Alexandre
On Mar 3, 2015, at 7:41 AM, Sebastian Tleye sebastian.tleye@gmail.com
wrote:
Hi,
I have a system with several classes and several packages. I want to do an Overview pyramid visualization. I select them all and when I do the pyramid it says NOP = 1 (number of packages equals 1), then I have a high NOC.
Why is this happening? Is it correct?
Thanks
-- Sebastián Tleye _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
You can check the source language of the model to know which are the metric to use by doing “self sourceLanguage“ on the model ?
Vincent
De : moose-dev-bounces@iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] De la part de Tudor Girba Envoyé : mardi 3 mars 2015 15:43 À : Moose-related development Objet : [Moose-dev] Re: Little question about visualization in Moose
Yes, but that will break the Overview Pyramid for Java systems.
We need to find a solution that deals with this variation if we want to keep the Overview Pyramid at all.
Doru
On Tue, Mar 3, 2015 at 3:40 PM, stephan <stephan@stack.nlmailto:stephan@stack.nl> wrote: Name: Famix-Extensions-StephanEggermont.283 Author: StephanEggermont Time: 3 March 2015, 3:39:46.019928 pm UUID: 727a4f0e-c96c-43c6-8903-6ca15bc76c7a Ancestors: Famix-Extensions-TudorGirba.282
Use pacakges instead of namespaces for nop OverviewPyramidMetrics
On 03-03-15 15:29, stephan wrote: That makes sense, as the OverviewPyramidMetrics use nop := aMooseModel allModelNamespaces size.
There is no test in Famix-Tests-Extensions that tells me what to expect. It is something I noticed when migrating it.
Stephan
http://forum.world.st/OverviewPyramid-metrics-td4782812.html
On 03-03-15 15:03, Alexandre Bergel wrote: I have the same result. Importing many packages results in NOP=1
Alexandre
On Mar 3, 2015, at 7:41 AM, Sebastian Tleye <sebastian.tleye@gmail.commailto:sebastian.tleye@gmail.com> wrote:
Hi,
I have a system with several classes and several packages. I want to do an Overview pyramid visualization. I select them all and when I do the pyramid it says NOP = 1 (number of packages equals 1), then I have a high NOC.
Why is this happening? Is it correct?
Thanks
-- Sebastián Tleye _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.chmailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.chmailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.chmailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.comhttp://www.tudorgirba.com
"Every thing has its own flow"
________________________________
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.