Metrics: Software Development Performance Index (SDPI)

Software Development Performance Index (SDPI) for measuring Agile Teams performance.
The concept and principle is described in this whitepaper of "The impact of Agile Quantified" (from the Software Engineering Institute, the organization managing the CMMI model:

• https://www.ca.com/content/dam/ca/us/files/white-paper/the-impact-of-agile-quantified.pdf
• https://www.agilealliance.org/resources/sessions/the-impact-of-agile-quantified-a-de-mystery-thriller/

Get Ready for CMMI V2.0!

And CMMI V2.0 launches today... Eager to hear the news? Yes and no...

Preparation for Launch – Getting Ready for CMMI V2.0

Automated Quality Characteristic Measures (AQCM from CISQ - Consortium for IT Software Quality)

Complementing the AFP and AEP standards from CISQ, the Automated Quality Characteristic Measures (AQCM) is also worth mentioning:

• Automated Quality Characteristic Measures | CISQ - Consortium for IT Software Quality

Quoting:
"CISQ has developed Automated Quality Characteristic Measures to measure and manage the structural quality of IT application software. The automated measures for Security, Reliability, Performance Efficiency, and Maintainability are now OMG® approved standards making them global standards for use by IT organizations.

These measures were developed from coding rules covering some of the most serious violations of good architectural and coding practices that should be avoided and can be detected through static code analysis. Each measure counts the number of violations of the architectural and coding rules related to that quality characteristic and then can be used in creating metrics for defect density, etc.

Security	Critical security violations in the source code drawn from the Top 25 security weaknesses in the Common Weakness Enumeration (CWE) repository
Reliability	Critical violations of availability, fault tolerance, and recoverability of software
Performance Efficiency	Critical violations of response time, as well as processor, memory, and utilization of other resources by the software
Maintainability	Critical violations of modularity, architectural compliance, reusability, analyzability, and changeability in software (...)"

Standards: Automated Enhancement Points (AEP) standard (CISQ)

The Automated Enhancement Points (AEP) Standard details and uses:
http://it-cisq.org/standards/automated-enhancement-points/

Quoting:
"Automated Enhancement Points is a standard measure of software size to be used in productivity analysis and the sizing of software maintenance activities. As of October 2016, the specification is an official standard of the Object Management Group® (OMG®).

The Automated Enhancement Points specification was published after the Automated Function Point (AFP)standard written by CISQ in 2013. Automated Enhancement Points improves the measurement of software size for use in productivity analysis by measuring both the functional and non-functional size of software. This is a significant advance in automated software sizing that solves problems that functional size measures have experienced in analyzing productivity during maintenance and enhancement activities.

With these two standards [AFP and AEP] for function point analysis and software sizing, organizations can:

- perform software quality and productivity analysis
- enable users to determine the ROI of an application by sizing the functionality that specifically matches the requirements of their organizations
- calibrate estimating methods against the results of past estimates
- measure and manage contracts and agreements with system integrators and outsourcers
- normalize data used in software benchmarks
- determine the size of a purchased application package (COTS or customized system) by sizing all the code included in the package"

The standard can found here: http://www.omg.org/spec/AEP/

Also make sure to read about the AFP and AQCS standards (also from CISQ).

Standard: Automated Quality Characteristic Measures

http://it-cisq.org/standards/automated-quality-characteristic-measures/

Quoting:
"Automated Quality Characteristic Measures for measuring the Security, Reliability, Performance Efficiency, and Maintainability of software"

Standards: Code Quality Standards (CISQ)

Ways of measuring objectively (and automatically) Software quality (measuring things related to non-functional quality attributes such as Maintainability) and knowing if you should act or not. Very interesting indeed:

Quoting:
"Code Quality Standards

IT organizations can use code quality standards to detect critical violations of good coding and architectural practice in software. Measure software against code quality standards at every release, e.g., measure code compliance to secure architectures, and put CISQ software quality measures into contracts with outside developers or software vendors to track to established outcomes.

Published Standards (Available for Use)

Automated Function Points (AFP) and Automated Enhancement Points (AEP) for software sizing
Automated Quality Characteristic Measures for measuring the Security, Reliability, Performance Efficiency, and Maintainability of software

Automated Quality Characteristic Measures in Detail

The nonfunctional requirements of software (Security, Reliability, Performance Efficiency, and Maintainability) can be traced to the most damaging of security breaches and system failures and are at the core of code quality standards and recommendations. CISQ Quality Characteristic Measures are consistent with ISO/IEC 25010 definition. The measures are designed to be automated on source code to identify critical vulnerabilities in the software that are severe enough that they need to be fixed. Combined with a sizing measure, a density metric is produced for each quality characteristic. Thresholds can be set for each characteristic.

The CISQ Quality Characteristic Measures cover eighty-six well-established software engineering rules to ensure secure, reliable, efficient and easy to maintain software. The following table shows a snapshot of software engineering rules contained in the measurement of each quality characteristic at the unit level and system level."

More details (and source): http://it-cisq.org/standards/

Standards: Automated Function Point (AFP) Specification (from CISQ)

The beauty of standards continues: Now (some years ago, in fact), a standard for counting function points (which is a measure of "size" of software source code):

"AFP provides a standard for automating the popular Function Point measure according to the counting guidelines of the International Function Point User Group (IFPUG). AFP provides a standard for automating the popular Function Point measure according to the counting guidelines of the International Function Point User Group (IFPUG). While there are several automated counters available in the market, there has never been a standard that ensures they are all counting the same way."

OMG has adopted it (in 2013 ;):

"The announcement by OMG of a specification for [AFP] counting should dramatically expand the use of Function Points for sizing IT applications," stated Dr. Bill Curtis, Director, CISQ. "By dramatically reducing the cost of counting and eliminating the problem of inconsistency among manual counters, automated Function Point measurement can become a standard component of the software development and maintenance process."

Source: http://www.omg.org/news/releases/pr2013/01-17-13.htm

The standard can be found here: http://www.omg.org/spec/AFP/

Also be sure to check the AEP and the ACQS (also from CISQ)

Standards: Code Quality driven by a Consortium (CISQ)?

Interesting consortium joining SEI (that developed the CMMI model) and OMG (UML and some related standards):

"Consortium of IT Software Quality (CISQ). CISQ brings together industry executives from Global 2000 IT organizations, system integrators, outsourcers, and package vendors to jointly address the challenge of standardizing the measurement of IT software quality and to promote a market-based ecosystem to support its deployments.
(...)
Jointly organized by the Software Engineering Institute (SEI) at Carnegie Mellon University and the Object Management Group (OMG), CISQ is designed to be a neutral forum in which customers and suppliers of IT application software can develop an industry-wide agenda of actions for defining, measuring, and improving IT software quality."

Source: Wikipedia

Additional info:
http://www.sei.cmu.edu/newsitems/cisq.cfm
http://www.eweek.com/development/software-quality-has-a-new-name-cisq