Defect Data (D&E - Projects and Releases)
You can record metrics data either :
A defect is a problem, which if not corrected, could cause an application to either fail or to produce incorrect results. Defects are collected the same way for Count Session, Project or Release.
SCOPE enables you to record the number of defects detected (found) in a particular Project Phase or found within the first month of use of the software after implementation. You can record defects at the detailed level of Phase and Severity or just enter the Total values, depending on how you collect defect data in your organization.
Defects are categorized into 3 levels of severity:
- Minor defect: does not make the software unusable in any way (e.g. a modification required to a report). A defect that may or has resulted in low-key disruption to business operations, causing for example, user inefficiency. The software suffers a failure, but it is still operable. For example: data values may be wrong or corrupted in a way that is tolerable for a limited period, or some minor aspect of functionality is unavailable. Business operations can continue with little degradation and any degradation is not evident to the businesses customers (see also UKSMA Defect Measurement Standard). Note: for the purposes of this ISBSG Data Collection standards, cosmetic defects are combined with minor defects to form a single value.
- Major defect: causes part of the software to become unusable. A severe defect that may seriously or has seriously degraded but not disabled some business function, amounting to failure. The business operation can continue at a lower rate of activity or only a portion of a business function is disabled. For example: customer details can still be entered but credit information cannot be confirmed; the customer facing operation is impacted, but this may not be evident to the customer (see also UKSMA Defect Measurement Standard).
- Extreme defect: failure causing the software to become totally unusable. A very severe defect that may render or has rendered the system inoperable -that is some business function is now no longer possible -manual procedures if they exist may have to be brought into operation. Examples could be: the software will not run or stops during operation; there is seriously wrong or corrupted data; the incident seriously impacts upon customer-facing operations and customers are aware of the incident (see also UKSMA Defect Measurement Standard).
If you check:
- Sum all From Count Sessions - then SCOPE will sum all the defects for all the Count Sessions assigned to the Release or Project and automatically load the cells.
- Derived - then SCOPE will total the defects in that same row of adjacent cells.
If you wish to override the derived results then un-check the box and manually enter the number of defects.