Order today for free lifetime support & 2 years upgrades - Limited Time Offer
This contract document is also included in the discounted Proposal Kit Professional bundle. Order and download for $199.
Use the Error Code Mapping Worksheet to keep track of software errors for testing and debugging.
Document Length: 1 Page
Business proposal example Time and time

again the most minor of normally overlooked clauses have saved our collectives asses when things turn rough with a particular client. Proposal Kit IS the reason we are still in business; a PROFITABLE BUSINESS after all these years."

Tom Granger
Florentine Design Group
The actual document is delivered in the retail products as an editable template.
Produced by:
Proposal Kit
Category:
Software > Computer Software > Business & Productivity Software
Price:
$199 USD
 
 
Proposal Kit reviews4.9 stars, based on over 700 reviews
Related documents may be used in conjunction with this document depending on your situation. Many related documents are intended for use as part of a contract management system.

Related Documents:
Error Code Mapping Worksheet
Disclaimers: Proposal Kit, Inc. makes no warranty and accepts no responsibility for suitability of any materials to licensees business. Proposal Kit, Inc. assumes no responsibility or liability for errors or inaccuracies. Licensee accepts all responsibility for results obtained. Information included is not legal advice. Use of any supplied materials constitutes acceptance and understanding of these disclaimers.

Writing the Error Code Mapping Worksheet document

IT,web,Internet,software,hardware,media,multimedia,photography,tech,information,technology,computer,business,company,pre-written,legal,contract,agreement,documents,templates,boilerplate,form,outline,text,terms,recitals problem,notification,breach

Writing the Software Development Plan document (alternate or related contract document)

Software Development Plan SDP THE SDP PROJECT DOCUMENT TITLE Author Title company name current date Document Version Control Information V 1. 0 1. Introduction

1 Purpose of this Document Objectives Insert the purpose of this document its objectives and its intended audience. 1 Scope of Document Insert description of the scope of this Software Development Plan. 1. Scope Constraints Insert constraints such as schedules costs interactions overview or any other information relevant to the testing of the development requirements.

1 Overview Insert an overview or brief description of the product software or other desired end result that is being tested under this Software Development Plan. 1 Business Context Insert an overview of the business or organization desiring the development of this project. Include the business or organizations mission statement and its organizational goals and objectives. Note. If you have already completed Software Requirements Specification the majority of this material is copied verbatim from that document. The purpose of this preamble is to familiarize staff recently attached to the testing portion of project who may not have been present or involved with earlier stages of the project. 1 Definitions Terms Acronyms or Abbreviations Insert definitions of any terms used throughout this Software Development Plan. Be sure to define specific acronyms or abbreviations used in your project. 1 References and Reference Material Insert list of all reference documents and other materials related to the Software Development Plan. References will often include but are not limited to. * Requirements Management Plan RQMP

* Risk Management Plan RMP * Business Modeling Guidelines * Development Case * Software Requirements Specifications SRS * Design Specifications * Programming Guidelines * User Interface UI Guidelines * Human Interface HI Guidelines * Test Guidelines and Test Measurement Plan

* Software Quality Assurance Plan * Software Management Plan * Project Outline and Management Plan * Project Acceptance Plan 1 Documentation Items Insert references to documentation. 2. Overview of Project 2 Purpose of Project Insert description of the purpose of the project and expected outcome.

2 Scope of Project Insert description of the scope of the project including the departments it may affect or include vendors it may impact business processes it may enhance or replace or anything else relating to or regarding the scope of the project that this Software Development Plan may include. 2 Project Objectives Insert description of the objectives that are to be met by the project itself and not necessarily by the Software Development Plan. 2 Assumptions and Constraints of the Project

Insert list and descriptions of all assumptions that the Software Development Plan is based upon. Constraints may also be detailed in this section including any variable or conditional constraints that may exist. 2 Software Development Plan History Insert references or table of prior versions of the Project Software Development Plan or any other information detailing revisions edits or changes to this Software Development Plan or Project as whole. 2 Specific Objectives and Requirements Not to be Met Insert any objectives and requirements for this project that are not to be met. This section is used to better clarify areas that you would like to be made clear are not the intended goals of this Software Development Plan. 3. Organization of Project Insert description of how the project and its components are to be organized including hierarchical organization chart or diagram of entities that details authorities. This includes project teams third party vendors third party contractors management duties report to lists and any group that is to be included into the overall organizational structure of the project. 3 Internal Interfaces Insert all information pertaining to how the project interfaces with internal groups in the Company. This includes all direct team members involved with the development. however this may also include departments that may have little or no say in the development of the project yet have roles as end users.

3 External Interfaces Insert all information pertaining to how the project interfaces with external groups in the Company. This includes all vendors and contractors involved with the development including those with testing or end user responsibilities. 3 Roles and Responsibilities Insert the organizational units that are responsible for determining or supporting processes. Include all points of contact for these organizational units. 4. Project Management

This section describes the management processes that oversee the costs timeline schedules decision making and evaluation points in the project. 4 Estimates This section will provide the estimated costs for project including schedule for all payments. Include detailed basis for all costs and description of the point at which re evaluation of those costs should take place. Thresholds should be detailed even if they are conditional or variable costs. 4 Project Plan Detail This section will describe the project plan in detail. This section will often span multiple pages. Criteria for developing project plan include but are not limited to. * The phases that the project plan will be broken into including any friendly names you may use for them such as Prototype Core Development Production etc. * breakdown of the work structure and assignments of responsibilities.

* Timelines Schedules or Gantt Charts that show the amount of time allotted to each phase of the project or to specific tasks. * Specific project milestones and deliverables including specific release dates for prototypes drafts demos or releases. * Specific criteria for project milestones and deliverables. * Identification of the internal or external achievements that must be met for each milestone or deliverable. 4. Project Plan Detail. Iteration Objectives

This section describes each version or iteration of specific deliverable or objectives and what the criteria shall be for approval. If project deliverables include iterations of deliverables that are experimental or exploratory in nature then specific criteria may include Iteration Objectives that merely state what was learned or discovered. 4. Release Dates This section will describe any release dates for project milestones or deliverables. 4. Project Schedule and Schedule of Phases This section will describe the complete schedule for completion of the project including individual breakdowns of each individual phase. Phases that run concurrent should be detailed using proper project management charts and diagrams. Target dates should be fixed in this section for each deliverable or milestone even if they are estimates. 4. Acquisition of Resources This section will describe how the Company will acquire the necessary resources to fulfill the project and which budgets will be tapped to do so. The section may also detail the approach that the Company will take to acquire resources. 4. Project Staffing Plan This section will describe the projects staffing requirement and how the Company will meet those requirements from within the Company or whether additional staff will be required. Detail whether external resources will be utilized to meet the Project Staff Plan and any constraints that may be imposed upon budgets and cost estimates for the project.

4. Project Training Plan This section will describe the projects staff requirement for training and whether external resources will be utilized to meet the Project Staffs Training requirements. Detail any constraints that may be imposed upon budgets and cost estimates for the project. Include time constraints and requirements to train staff. 4. Project Budget This section will describe in detail the costs and their allocation across the entire Software Development Plan. This section may span multiple pages or addenda if necessary. 4 Project Monitoring and Oversight This section will detail the requirements for controlling the projects its costs and adherence to the delivery schedule and phases for the management of the project. Include any schedules required to monitor the progress of the project and its individual milestones and deliverables to ensure that the project adheres to its proposed schedule. 4. Budget Control

This section details any budgetary controls that will be in place for the project. 4. Quality Assurance QA Control This section details any quality assurance controls that will be in place for the project. 4. Measurement Control This section details any measurements and standards that will be used to quantify benchmarks deliverables objectives methods or any other component of the project that requires the definition of specific measurements. 4. Reporting Control This section details all reporting requirements for the project including the frequency and formats of reports for the project.

4 Post Project Responsibilities This section details the responsibilities of individual organization units teams or staff after achieving completion of the project. Include all post project debriefings reports accounting of project resources and materials and staff re assignments and responsibilities. 5. Technical Process Plans and Methods Insert the specific technical process standards and methods to be used during the development of the project. In this section you will describe and define each plan that the Software Development Plan relies upon or includes. You may attach additional exhibits to this section if your testing plan requires them. This section may include excerpts or plan attachments from Sec. and Sec. 1. 7. At minimum most Software Development Plans will include. * Software Development Case * Business Process and Modeling Guidelines

* Design Style and Programming Guidelines and Standards * User Interface UI Guidelines and Standards * Risk Assessment Reduction and Management Plans * Testing Guidelines and Standards * Use Case Standards * Hardware and Resource Infrastructure Plan * Project Acceptance Plan * Configuration Management Plan

* Documentation Guidelines and Standards * Vendor Management Guidelines and Standards * Support Management Plan * Additional Plans or Guidelines 6. Project Deliverables Insert the specific milestones and deliverables that are to be delivered under this plan. Deliverables may also include iterative versions drafts demos prototypes and release versions of Software.

7. Deliverable and Milestone Objective Testing A description of individual milestones and deliverables and the requirements for acceptance. Examples. 7 Milestone or Deliverable Name Insert description here. 7 Milestone or Deliverable Name Insert description here.

7 Milestone or Deliverable Name Insert description here. 7 Milestone or Deliverable Name Insert description here. 8. Hardware and Resource Requirements List A description of the hardware and resource requirements.

Examples. 8 Hardware Requirement Name Insert description here. 8 Software Requirement Name Insert description here. 8 Security Resources Requirement Name

Insert description here. 8 Specific Tools Requirement Name Insert description here. 8 Specific Documentation Requirement Name Insert description here. 9. Change Request and Management A description of the Software Development Plan change request and change management procedures. Describe the process that must be followed for submission review and authorization for all requests for change to the Software Development Plan or any change to any part of the deliverables. 10. Approval for Software Development Plan

A description of the personnel authorized to approve the Software Development Plan. Their names titles and signatures must accompany this document. approved approver Title Date when the contact was signed approved approver Title

Date when the contact was signed approved approver Title Date when the contact was signed approved approver

Title Date when the contact was signed 11. Appendices A description of all other supporting information required for the understanding and execution of the Software Development Plan and requirements. All Software Development Plan documents require the following two appendices. Expanded from Sec. 11 Definitions Acronyms Abbreviations A complete list of the definitions of important terms abbreviations and acronyms. This may also include Glossary of terms.

11 References A complete listing of all citations to all documents and meetings referenced or used in the preparation of this Software Development Plan and testing requirements document. Customer Initials Developer Initials

How to write my Software Testing Plan document (alternate or related contract document)

Software Testing Plan STP THE STP PROJECT DOCMENT TITLE Author Title company name current date

Document Version Control Information V 1. 0 1. Introduction 1 Purpose of this document Objectives Insert the purpose of this document its objectives and its intended audience. 1 Scope of document

Insert description of the scope of this Software Testing Plan 1. 21 Scope Constraints Insert constraints such as schedules costs interactions overview or any other information relevant to the testing of the development requirements. 1 Overview Insert an overview or brief description of the product software or other desired end result that is being tested under this Software Testing Plan. 1 Business Context Insert an overview of the business or organization desiring the development of this project. Include the business or organizations mission statement and its organizational goals and objectives. Note. If you have already completed Software Requirements Specification the majority of this material is copied verbatim from that document. The purpose of this preamble is to familiarize staff recently attached to the testing portion of project who may not have been present or involved with earlier stages of the project. 1 Testing Strategy

Insert general overview of the strategy and plan for meeting the testing deliverables. Describe the levels of testing that will need to take place and the type of testing activities. more detailed outline will be provided further on in this document. If there are specific tests that need to follow their own STP you can describe them in an additional document separate from this main document. A Testing Strategy Outline will include. * The individual items to be tested * The purpose for testing those items * The individual features to be tested * The individual features NOT to be tested * The managerial and technical approach to testing * The criteria for pass and failure of testing * The individual roles or responsibilities of participants in testing

* The milestones and deliverables required for testing * The schedules and timelines for individual tests or the Software Testing Plan as whole * The risk assumptions and constraints placed upon the Software Testing Plan. 1 References and Reference Material Insert list of all reference documents and other materials related to the Software Testing Plan. References will often include but are not limited to. * Software Requirements Specifications

* Software Development Plan * Software Quality Assurance Plan * Software Management Plan * Project Outline and Management Plan 1 Documentation Items Insert references to documentation including but not limited to. * Software Requirements Specification SRS * Software Design Specification SDS

* Software Development Plan SDP * Software Installation Guide * Software Users Guide * Software Features Guide * Software Bug Error Correction or Defect Removal Guide 2. Items to be Tested 2 Program Modules Insert description of the testing to be performed for each module that the software contains.

2 Job Control Procedures Insert description of the procedures to be followed for testing the job control language JCL including scheduling for production control and all job sequencing. This section should include all the relationships between the above mentioned items in the Program Modules section. 2 User Procedures Insert description of the testing to be conducted on user documentation and support resources online or printed to ensure that they are complete and comprehensive. 2 Operator Procedures Insert description of the testing procedures to be conducted to ensure that the software can be run and supported within production environment as intended and that any Help Desk or other support services outlined in the plan can be verified as effective and meeting the intended support outcomes as outlined in the goal of the Software Testing Plan. 2 Features to be Tested

Insert the objectives and requirements for features that are being tested in this Software Testing Plan. 2 Features Not to be Tested Insert the objectives and requirements for features that are NOT being tested in this Software Testing Plan 3 Approach Insert the objectives and requirements for the overall approach to testing. The approach should cover such major tasks as the identification of time estimates for each element of the Software Testing Plan. Identify the different types of testing and describe their testing methods and the criteria for evaluating such testing. Your Software Testing Plan may contain several different approaches for certain elements. 3 Component Testing Insert the objectives and requirements to verify the implementation integrity and functionality for single unit component module or group of individual software elements or components. Component Testing is performed to verify that the individual component or group of components is complete and functioning as intended. 3 Integration Testing Insert the objectives and requirements to verify the implementation integrity and functionality for combined units such as individual software units components or group of individual software elements or components that has been combined with hardware elements. Integration testing is important to ensure that the software is functional as whole within the environment it is intended to run. The Integration Testing is performed to ensure that all operational requirements are met.

3 Conversion Testing Insert the objectives and requirements for testing that all historical data elements convert or are compatible with the new system. Conversion testing is required only if the software is an upgrade of an older system or will use or manipulate data from other systems. 3 Job Stream Testing Insert the objectives and requirements for testing that the software operates correctly in the production environment. 3 Interface Testing Insert the objectives and requirements for testing that the software operates correctly with all user interface and input systems. 3 Recovery Testing Insert the objectives and requirements for testing that the softwares recovery and restore operations function correctly and all backup systems and procedures work as intended in the production environment. 3 Performance Testing

Insert the objectives and requirements for testing that the software operates correctly in regards to normal operation response and execution times scalability portability and all other performance requirements within the production environment. 3 Regression Testing Insert the objectives and requirements for testing that any changes applied to the software do not affect functions previously tested. 3 Acceptance Testing Insert the objectives and requirements for testing that the software or system meets all criteria and deliverables. The Acceptance Testing is important to ensure that all requirements are met and that all components modules hardware requirements and recovery and restore operations function in the production environment and that plan exists to demonstrate such functionality for customer. 3. 10 Alpha Beta and Release Candidate RC Testing Insert the objectives and requirements for testing that will be done by customer to verify that the software meets all deliverables and requirements from the Software Requirements Specifications SRS or the Software Development Plan SDP and to detect any errors bugs or defects in the software.

4. Pass and Failure Criteria This section describes the criteria to determine whether specific item has passed or failed particular test. 4 Criteria for Suspension This section will describe the criteria for suspending an individual element or group of elements for particular testing activity. 4 Criteria for Resumption of Testing This section will describe the criteria for resuming testing for an individual element or group of elements that has been previously suspended. 4 Criteria for Approval of Testing This section will describe the criteria for acceptance and approval for an individual element or group of elements.

5. Testing Process and Methods Insert the specific testing process and methods to be used in performing each testing activity. In this section you will describe and define each type of test that the Software Testing Plan contains. You may attach additional exhibits to this section if your testing plan requires them. 6. Test Deliverables Insert the specific deliverables and documents that are to be delivered from the testing process. Test deliverables may include incremental data or data derived from incomplete tests. Typical test deliverables include but are not limited to. * Individual Test Element or Module Summary Reports * Group Element or Module Summary Reports * Individual and Combined Test Logs

* Test Metrics and Benchmark Reports * Test Input and Output Reports * Test Incident Reports 7. Testing Task and Requirements List A description of tasks and the skills required for performing testing as part of the deliverables.

Examples. 7 Task Name Insert description here. 7 Responsibility for Task Insert description here. 7 Resources Required for Task Insert description here. 7 Schedule or Timeline for Task Insert description here.

8. Testing Hardware and Environmental Requirements List A description of the hardware and environmental requirements for performing testing as part of the deliverables. Examples. 8 Hardware Requirement Name Insert description here. 8 Software Requirement Name Insert description here. 8 Security Resources Requirement Name Insert description here.

8 Specific Tools Requirement Name Insert description here. 8 Specific Documentation Requirement Name Insert description here. 8 Specific Risks and Assumptions Insert description here. Focus on restraints such as resource availability time constraints staff and developer availability and all other external factors that can influence testing.

8. 61 Risk and Assumption Contingency Plan Insert description of the contingency plan for each item listed above. 9. Change Request and Management A description of the Software Testing Plan change request and change management procedure. Describe the process that must be followed for submission review and authorization for all requests for change to the Software Testing Plan or any change to any part of the deliverables. 10. Approval for Software Testing Plan A description of the personnel authorized to approve the Software Testing Plan. Their Name Title and signature must accompany this document.

approved approver Title Date when the contact was signed approved approver Title Date when the contact was signed

approved approver Title Date when the contact was signed approved approver Title Date when the contact was signed 11. Appendices A description of all other supporting information required for the understanding and execution of the Software Testing plan and requirements. All Software Testing Plan documents require the following two appendices.

11 Definitions Acronyms Abbreviations A description of the definition of important terms abbreviations and acronyms. This may also include Glossary of terms. 11 References A listing of all citations to all documents and meetings referenced or used in the preparation of this Software Testing Plan and testing requirements document. Customer Initials Developer Initials

A Document from Contract Pack

The editable Error Code Mapping Worksheet template - complete with the actual formatting and layout is available in the retail Contract Packs.
Proposal Kit on BBB
Proposal Kit
Proposal Kit on FaceBook
Create winning business proposals & contracts with minimal effort and cost. Downloadable proposal software, proposal templates, legal contracts and sample proposals.
© 1997 - 2018, Proposal Kit, Inc. All rights reserved.
Proposal Kit

Create winning business proposals & contracts with minimal effort and cost. Proposal software, proposal templates, legal contracts and sample proposals.