2581
Assessment vendors may use this view to anticipate future changes to CWE that will help them
to better prepare customers for important changes in CWE.
Filter
/Weakness_Catalog/*/*[Notes/Note[@Type='Maintenance']]
Membership
Nature Type ID Name Page
HasMember 1081 Entries with Maintenance Notes 2580
Metrics
CWEs in this view Total CWEs
Weaknesses 143 out of 938
Categories 39 out of 374
Views 5 out of 50
Total 187 out of 1362
View-1128: CISQ Quality Measures (2016)
View ID : 1128
Type : Graph
Objective
This view outlines the most important software quality issues as identified by the Consortium for
Information & Software Quality (CISQ) Automated Quality Characteristic Measures, released in
2016. These measures are derived from Object Management Group (OMG) standards.
Audience
Software Developers
This view provides a good starting point for anyone involved in software development (including
architects, designers, coders, and testers) to ensure that code quality issues are considered
during the development process.
Product Vendors
This view can help product vendors understand code quality issues and convey an overall status
of their software.
Assessment Tool Vendors
This view provides a good starting point for assessment tool vendors (e.g., vendors selling static
analysis tools) who wish to understand what constitutes software with good code quality, and
which quality issues may be of concern.
Membership
Nature Type ID Name Page
HasMember 1129 CISQ Quality Measures (2016) - Reliability 2440
HasMember 1130 CISQ Quality Measures (2016) - Maintainability 2441
HasMember 1131 CISQ Quality Measures (2016) - Security 2442
HasMember 1132 CISQ Quality Measures (2016) - Performance Efficiency 2443
References
[REF-968]Consortium for Information & Software Quality (CISQ). "Automated Quality Characteristic
Measures". 2016. < http://it-cisq.org/standards/automated-quality-characteristic-measures/ >.
Metrics
CWE Version 4.14
CWE-1133: Weaknesses Addressed by the SEI CERT Oracle Coding Standard for Java
CWE-1133: Weaknesses Addressed by the
SEI CERT Oracle Coding Standard for Java 2582
CWEs in this view Total CWEs
Weaknesses 77 out of 938
Categories 4 out of 374
Views 0 out of 50
Total 81 out of 1362
View-1133: Weaknesses Addressed by the SEI CERT Oracle Coding Standard
for Java
View ID : 1133
Type : Graph
Objective
CWE entries in this view (graph) are fully or partially eliminated by following the guidance
presented in the online wiki that reflects that current rules and recommendations of the SEI CERT
Oracle Coding Standard for Java.
Audience
Software Developers
By following the SEI CERT Oracle Coding Standard for Java, developers will be able to fully
or partially prevent the weaknesses that are identified in this view. In addition, developers can
use a CWE coverage graph to determine which weaknesses are not directly addressed by the
standard, which will help identify and resolve remaining gaps in training, tool acquisition, or other
approaches for reducing weaknesses.
Product Customers
If a software developer claims to be following the SEI CERT Oracle Secure Coding Standard
for Java, then customers can search for the weaknesses in this view in order to formulate
independent evidence of that claim.
Educators
Educators can use this view in multiple ways. For example, if there is a focus on teaching
weaknesses, the educator could link them to the relevant Secure Coding Standard.
Membership
Nature Type ID Name Page
HasMember 1134 SEI CERT Oracle Secure Coding Standard for Java -
Guidelines 00. Input Validation and Data Sanitization (IDS)