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

More documents

Recommendations

Info

Appendix K: Defect Severity Levels Page 56 of 60 Test Management Tool (TMT) Software Project Management Plan (SPMP) TMT-SPMP-1.2 27-Sep-2010 Code Defect Description Level 0 No defect found or comment. None 1 Prevents the accomplishment of an operational or mission essential capability Major Jeopardizes safety Causes significant technical, cost, or schedule risks to the project or to life cycle support of the system. This is a MAJOR defect. 2 Adversely affects the accomplishment of an operational or mission essential capability and no work-around solution is known Major Adversely affects technical, cost, or schedule risks to the project or to life cycle support of the system, no work-around solution is known. This is a MAJOR defect. 3 Adversely affects the accomplishment of an operational or mission essential capability, but a work-around solution is known Major Adversely affects technical, cost, or schedule risks to the project or to life cycle support of the system, but a work-around solution is known. This is a MAJOR defect. 4 Results in user/operator inconvenience or annoyance, but does not affect a required operational or mission essential capability Minor Results in inconvenience or annoyance for development or support personnel, but does not prevent the accomplishment of those responsibilities. This is a MINOR defect. 5 Any other effect not described above. Projects may define and assign sub-codes for this priority. This is a MINOR defect. Minor
Appendix L: Defect Types Page 57 of 60 Test Management Tool (TMT) Software Project Management Plan (SPMP) TMT-SPMP-1.2 27-Sep-2010 Code Defect Type Description 1a Functionality The definition of a functional capability desired by the customer was not clear and unambiguous, or was misinterpreted. 1b GFE/BFE/CFE/Subcontractor Incompatibilities or deficiencies with specificationcompliant Government Furnished Equipment (GFE), Buyer Furnished Equipment (BFE), Contractor Furnished Equipment (CFE), or subcontractor supplied products in their interaction with the system. 1c Software Engineering Environment (SEE) The SEE, as specified, is deficient in supporting the software engineering process; incompatibilities exist between SEE tools. 1d Programmatic Requirements Conflicting contractual requirements; problems relating to security requirements; problems relating to teaming with other companies. 1e Test The test equipment/environment, as specified, is Equipment/Environment deficient to support system operation. 1f Support The support equipment/environment, as specified, Equipment/Environment is deficient to support system operation. 1z Documentation Documentation does not accurately/adequately describe the planning, and categories 1a through 1f are not appropriate. 2a Subsystem/Software Requirements Incorrect/incomplete translation or specification of the lower level (subsystem/software) requirements that was not the result of category 2e. Examples include: incorrect specification at the SRS level, subsystem specification incorrect, etc. 2b Physical Interface An error in the definition or specification of a physical (hardware) interface. 2c Functional Interface Incorrect/incomplete specification of the functional interaction or communication of data with other processes or subsystems, and categories 2b and 2d are not appropriate. 2d User Interface Incorrect/incomplete specification of the software interaction with the user. 2e System Requirements Incorrect/incomplete translation or specification of the customer requirements that was not the result of category 1a. Examples include: incorrect specification at the SSS level, Air Vehicle Specification, etc. 2z Documentation Documentation does not accurately describe the intended requirements, and categories 2a through 2e are not appropriate. Format, documentation standards, typographical errors, and understandability are included in this category. 3a Physical Interface Incorrect/incomplete design of the software interaction with hardware.
Page 1 and 2:
Software Project Management Plan (S
Page 3 and 4:
SIGNATURE PAGE Page 3 of 60 Test Ma
Page 5 and 6: REVISION HISTORY Page 5 of 60 Test
Page 7 and 8: PREFACE Page 7 of 60 Test Managemen
Page 9 and 10: TABLE OF CONTENTS Page 9 of 60 Test
Page 11 and 12: Page 11 of 60 Test Management Tool
Page 13 and 14: LIST OF TABLES Page 13 of 60 Test M
Page 15 and 16: 1.1. Project Summary 1. OVERVIEW Pa
Page 17 and 18: 1.1.3. Project Deliverables The TMT
Page 19 and 20: 1.3. Document Overview This plan is
Page 21 and 22: 2. REFERENCES 2.1. Standards, Docum
Page 23 and 24: 3. DEFINITIONS Page 23 of 60 Test M
Page 25 and 26: 4.1. External Interfaces 4. PROJECT
Page 29 and 30: 5.1. Start-up Plan 5.1.1. Estimatio
Page 33 and 34: 5.3.2.3. Schedule Reviews Page 33 o
Page 37 and 38: 6.1. Process Model 6. TECHNICAL PRO
Page 39 and 40: Table 6.2-1: TMT Programming Langua
Page 41 and 42: 7. SUPPORTING PROCESS PLANS 7.1. Co
Page 45 and 46: There are no other addition plans.
Page 47 and 48: APPENDIXES Appendix A: Requirements
Page 49 and 50: Appendix C: Code Review Checklist P
Page 51 and 52: Appendix E: Defect Report Form Use
Page 53 and 54: Appendix G: Review Closeout Form Us
Page 55: Appendix I: Data Collection Point C
show all

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

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

Delete template?

Save as template?