testing - is it necessary to use Microsoft approach in every class for finding software maintainability? -


for finding software maintainability using microsoft approach, have use following method

mi = max(0, (171 — 5.2 * ln(hv) — 0.23 * cc — 16.2 * ln(loc)) * 100 / 171),

where,

hv – halstead volume,

cc – cyclomatic complexity;

loc – lines of code.

in program have few different type of classes .as example "finding area "__problem have ----"circle", "triangle","quadrilateral", "abstract","choice" classes .

do have use approach every individual class finding software maintainability ?

the simples answer no. heuristic formula created assess code , drive code refactoring in order achieving maintainability. can find many other interesting heuristics if code smells (aka anti-patterns).

in real world, face challenges, resource constraints (e.g. time, legacy, design options), leads decisions create technical debt. so, not worry strictly following these formulas. guidelines in making decisions while designing software architecture.


Comments

Popular posts from this blog

php - cannot display multiple markers in google maps v3 from traceroute result -

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -

javascript - firefox memory leak -