Software engineering institute maintainability index

The code quality standards from CISQ are comprised of software weaknesses CWEs that can be detected in source code through static code analysis.

CAST and Synopsys tool vendors contributed to development of the standards and support the standards in their tools. Most static analysis tools identify some, if not all, critical CWEs. Are you a tool vendor that supports CWEs and code quality standards? To be listed for reference, contact us.

Corrective maintenance is defined as maintenance of bugs or errors. It means when the error is detected in the software then the corrective maintenance is required to fix it.

These bugs or errors are responsible for the faults which may appear in the code, design or logic of the software. Sometimes the user asks for the enhancements of the software and not about fixing the bugs.

Corrective maintenance requires the correction of existing faults in the software. Sometimes a change in hardware also cause bugs or errors. Adaptive maintenance includes the environmental changes where your software is living. Changes to the hardware, operating system, software dependencies, and organizational business rules and policies are handled in adaptive maintenance. By these modifications to the environment, changes can occur in the other parts of the software.

The authors describe how they used machine learning ML modeling to create decision-making preferences for non-player characters NPCs. The SEI led the community in creating this multi-year research and development vision and roadmap for engineering next-generation software-reliant systems. Alberts discusses the results of a study to identify a prototype set of risk factors for adopting cloud technologies.

View More Publications. At the Software Engineering Institute SEI , we research complex software engineering, cybersecurity, and artificial intelligence engineering problems; create and test innovative technologies; and transition maturing solutions into practice.

The U. Department of Defense, as well as other public agencies and private businesses, can meet mission goals and gain strategic advantage by using tools, technologies, and practices developed or matured by the SEI. Attendees of the January event will learn a broad range of the latest techniques for applying data and analytic methods. My favorite part is the sine of the square root of comments — why would there be a periodic raise and fall of maintain ability?

A fantastic post and great read. I am doing my MEng in Software Engineering and im looking at introducing a different way of writing endpoints on server side code. Every new feature request ends in a new endpoint. I was hoping to stumble onto a formula i could use to measure maintainability in these systems, vs the new approach, but alas no luck so far.

At least i found a way not measure it! Intuitively, a combination of simple linear length lines of code with cyclomatic complexity and the vocabularly required for reasoning Halstead Volume seems reasonable.

Pragmatically, having the metric constantly visible while working via Code Lens is a great reminder to keep things managable as I go. Of course the thresholds are arbitary — they would be arbitary at any level. Great article! Good insight into how these scores are calculated but most importantly how reliable they are. Thank you. We have:. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account.

You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. Based on this, my key concerns about the Maintainability Index are: There is no clear explanation for the specific derived formula.