Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CCM metric realization issue #517

Open
User123363 opened this issue Apr 22, 2021 · 0 comments
Open

CCM metric realization issue #517

User123363 opened this issue Apr 22, 2021 · 0 comments

Comments

@User123363
Copy link

The upper bound of the CCM metric is at 0.5 level. In our opinion, this is not due to a low metric value, but to an error in an implementation of the metric, in the formula CCM(C)=NC(C)/(NMP(C) NCC(C))
where NC – the number of connections, NCC – the number of connection components, NMP – the number of maximum possible connections. However, jPeek for the NCC counts the number of related methods, which is why a maximum score will be 0.5, in this case.
For an example, to test the hypothesis, let us implement a class Class with three interconnected methods. According to the CCM definition, this class has one connectivity component, but jPeek supposed that there are three ones.
Result

@User123363 User123363 changed the title CCM problem CCM metric realization issue Apr 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants