15.07.2013 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Page 59 of 60<br />

Test <strong>Management</strong> Tool (TMT)<br />

<strong>Software</strong> <strong>Project</strong> <strong>Management</strong> <strong>Plan</strong> (<strong>SPMP</strong>)<br />

TMT-<strong>SPMP</strong>-1.2<br />

27-Sep-2010<br />

Code Defect Type Description<br />

definition, and termination of subprocesses. This<br />

category includes incorrect order or number of<br />

parameters passed, ambiguous termination value<br />

for a function, incorrect parameter data types,<br />

inter-process communication problems, and<br />

timing/scheduling anomalies.<br />

4e Standards Violations of programming standards, incorrect use<br />

of the programming language, typographical errors<br />

during code/text entry for source code and test<br />

procedures, etc.<br />

4f Build/Configuration Incorrect/incomplete software build/configuration,<br />

e.g., missing code, wrong version of code,<br />

incorrect placement in memory, missing test<br />

procedure, etc.<br />

4z Documentation Documentation does not accurately describe the<br />

implementation of the design, and categories 4a<br />

through 4f are not appropriate. This category also<br />

includes defects in documentation format or other<br />

documentation standards, typographical errors,<br />

understandability, etc.<br />

5z Documentation Documentation does not accurately reflect test<br />

results. Format, documentation standards,<br />

typographical errors, and understandability are<br />

included in this category. This category does not<br />

include problems with software configuration item<br />

test plans, test cases, or test procedures.<br />

6z Documentation Documentation generated to support the transition<br />

to the customer is in error. Format, documentation<br />

standards, typographical errors, and<br />

understandability are included in this category.<br />

This category does not include problems with<br />

documentation developed in prior phases that are<br />

covered by categories 1z, 2z, ... 5z.<br />

7a GFE/BFE A problem caused by GFE/BFE not operating in<br />

accordance with its specification.<br />

7b CFE/Subcontractor A problem caused by external CFE/subcontracted<br />

equipment/software not operating in accordance<br />

with its specification, e.g., host computer<br />

hardware, firmware, supplier errors, or<br />

performance problems. This does not include<br />

internally maintained reused assets.<br />

7c SEE A problem caused by the SEE not operating in<br />

accordance with its specification, e.g., compiler<br />

problems, linker problems, interface definition tool<br />

problems, etc. This does not include internally<br />

maintained reused assets.<br />

7d Other Other external problem, and no other external<br />

category is appropriate. This does not include<br />

internally maintained reused assets.<br />

7e Test The product under test is operating correctly, yet

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!