2018
DOI: 10.17485/ijst/2018/v11i32/123093
|View full text |Cite
|
Sign up to set email alerts
|

Complexity Metrics for Component-based Software Systems: Developer Perspective

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 17 publications
0
2
0
Order By: Relevance
“…In other words, if the Mab is 1 then function b th is called by the a th function either directly or indirectly. The MMAC is given by (7). 7Where, nm, na are the number of methods and attributes in class c respectively.…”
Section: (5)mentioning
confidence: 99%
See 1 more Smart Citation
“…In other words, if the Mab is 1 then function b th is called by the a th function either directly or indirectly. The MMAC is given by (7). 7Where, nm, na are the number of methods and attributes in class c respectively.…”
Section: (5)mentioning
confidence: 99%
“…A high-quality software should produce less complexity, coupling and high cohesion as low coupling and high cohesion reduces the testing and maintainability cost [6]. Coupling, cohesion as well as the complexity of software can be measured by using the software metric [7]. Software metric plays a significant role to control the quality of software this is due to the fact that improvement needs measurement which is done through the metric.…”
Section: Introductionmentioning
confidence: 99%