Software Project Management Plan (SPMP) - Southern Polytechnic ...

Page 58 of 60
Test Management Tool (TMT)
Software Project Management Plan (SPMP)
TMT-SPMP-1.2
27-Sep-2010
Code Defect Type Description
3b Subsystem Interface Incorrect/incomplete design of the functional
interaction or communication of data with other
subsystems or processes, and categories 3a and 3c
are not appropriate.
3c User Interface Incorrect/incomplete design of the software
interaction with the user.
3d Inter-process
Communication
Incorrect/incomplete interfaces or communications
between processes or components within a
product. Includes timing/scheduling anomalies as
well as parameter passing/ omission and other
inter-process defects.
3e Data Definition Incorrect/incomplete design of the data structures
to be used in the product, e.g., defects associated
with data precision/accuracy and data units.
3f Unit/Procedure Design Problem with the control flow and execution within
a unit/procedure. For example, errors in
logic/computations in algorithms,
incorrect/incomplete translation of requirements,
incorrect/incomplete sequence of operations in a
test procedure or installation procedure, etc.
3g Error Handling The checks for error detection/isolation were not
adequate, or the response to detected error
conditions was not correct.
3h Standards Violations of design standards that do not cause a
defect in the functional operation of the product.
This does not include documentation standards.
3i Traceability A known requirement was missed or a non-existing
requirement was introduced into the design.
3z Documentation Documentation does not accurately describe the
design or software configuration item (product)
test plans/procedures, and categories 3a through
3i are not appropriate. Format, documentation
standards, typographical errors, and
understandability are included in this category.
4a Logic Incorrect/incomplete decision logic causes the
product not to implement the full intent of the
design, e.g., invalid "If-Then-Else," loop structures,
case statements, missing "Begin-End," wrong
execution sequence.
4b Computations Incorrect/incomplete mathematical or arithmetic
operations cause the product not to implement the
full intent of the design.
4c Data Handling Incorrect/incomplete definition or use of data
structures in accordance with the design. This
category includes data precision, improper
indexing into arrays or tables, improper scaling or
units of measure, and data incorrectly stored or
accessed.
4d Unit Interface Problems related to the calling, parameter