proposals a few years back and it was great to have a template to remind me of the critical components that needed to be included. The kit helps to win business, but at the same time it helps to protect my business by including the critical contractual components of the proposal."
PERMISSION TO LINK company name Grantor has Web site located at web site domain URL Grantors Web site web site URL Grantee has Web site located at Grantees Web site Agreements 1 Grantor hereby grants Grantee permission to provide hypertext link from Grantees Web site to the home page of Grantors Web site. 2 Neither party shall be liable to the other party for the content of its Web site or links on its Web site to other Web sites. 3 Grantee acknowledges that Grantor may terminate this Permission at any time with or without cause by giving notice to Grantee. Grantee must remove the hypertext link to Grantees Web site within days days of receiving such notice.
4 This Agreement is governed by the laws of the State of state or province excluding its conflict of laws principles. 5 This Agreement is the entire understanding between the parties relating to the link referenced here and supersedes all prior or contemporaneous understandings whether written or oral. In witness whereof the parties have executed this Agreement this current day day of current month current year. Grantor Job title of signator authorized signature or signer. Grantee
Job title of signator authorized signature or signer.
GIVING NOTICE OF BREACH OF AGREEMENT DEMANDING CORRECTIVE ACTION current date company name address address
city state or province zip or postal code Phone phone number Fax fax number Re. Our Agreement Dear salutation last name The purpose of this letter is to give formal notice of your breach of our Agreement Insert the title of the contract or agreement which was breached dated start date. Specifically you are in breach of paragraph Insert Paragraph Breached here of the Agreement which provides that Insert description of what was breached Please be advised that if Insert corrective action that must be done will have no choice but to refer this matter to legal counsel for appropriate action.
Thank you in advance for your immediate attention to this matter. Sincerely first name last name job title
CEASE AND DESIST LETTER Dear contract first name contract last name It has come to our attention that you have made an unauthorized use of our copyrighted work entitled Insert the name of the infringed work the Work in the preparation of work derived therefrom. have reserved all rights in the Work which was first published in Insert the publication date of the infringed work on Insert the URL of original work and have registered the copyright. Your work entitled Insert the name of the infringing work and which appears on your web site at Insert the URL of infringing site is essentially identical to the Work and clearly used the Work as its basis. Give few examples that illustrate direct copying and or unfair use. You neither asked for nor received permission to use the Work as the basis for Insert the name of the infringing work nor to make or distribute copies of it. Therefore believe you have willfully infringed my rights under USC §101 et seq. and could be liable for statutory damages as high as 100 000.
I demand that you immediately cease the use and distribution of all infringing works derived from the Work and all copies of it and that you deliver to me all unused undistributed copies of it or destroy such copies immediately and that you desist from this or any other infringement of my rights in the future. If have not received an affirmative response from you by date indicating that you have fully complied with these requirements shall consider taking the full legal remedies available to rectify this situation. Sincerely first name last name e mail address Phone. phone number Fax. fax number
job title company name
SOFTWARE TEST USE CASE TEMPLATE Master Project Plan HOW TO USE THIS CASE SYSTEM BOUNDARY WHEN TO USE WHEN TO START
STAKEHOLDER WHAT HAS TO HAPPEN FIRST BASIC FLOW ALTERNATIVE FLOW SPECIAL REQUIREMENTS WHO IS INTERESTED IN THIS INFORMATION PRE ARRANGMENT POST ARRANGEMENT ORDER OF EVENTS RESPONSIBLE PARTY SYSTEM ISSUE N A
SOFTWARE TEST USE CASE TEMPLATE Individual Test DESCRIPTION PRIMARY ACTOR SECONDARY ACTOR ASSUMPTIONS
STEPS TO TAKE IF this THEN interaction etc INTERACTION VARIATIONS IN STEPS AND INTERACTIONS NON FUNCTIONAL REQUIREMENTS SPECIAL REQUIREMENTS
KNOWN ISSUES ORDER OF EVENTS SYSTEM ISSUE N A
Audit Material Procedure Insert Description Here Insert Procedure Here Insert Description Here Insert Procedure Here Insert Description Here Insert Procedure Here Insert Description Here Insert Procedure Here address address city state or province zip or postal code Phone phone number
REPRINT RIGHTS AGREEMENT DATE. current date Order #. WorkOrder Job Job title of signator authorized signature or signer. Insert the Job Description Here I the undersigned being duly authorized and having the right to grant reproduction rights to company name do hereby request that company name reprint the following materials as described below. In consideration of the agreement by company name to reproduce or reprint the materials agree to the following terms and conditions. Nothing in the works and materials listed above and or submitted to company name for reprint contains any content that infringes or violates any intellectual property rights of any third party or author. Further nothing contained within the work or materials or any part or operation of the materials will cause the use reproduction resale or transfer of the rights to the materials to infringe upon the intellectual property rights of any third party. Nothing in the works and materials will result in the violation of any local state federal international or any other jurisdiction under which the reproduction or reprinting of such materials would constitute an unlawful civil or criminal offense. company name has no obligation to review edit censor or otherwise certify the materials to ensure they comply with applicable law. I hereby release and discharge company name and its agents representatives and assigns from any and all claims and demands arising out of or in connection with the reprint of the materials including without limitation any and all claims for copyright or trademark violation invasion of privacy right of publicity slander libel or defamation. further agree to defend company name for all liabilities damages judgments costs or expenses arising out of company name being made part of any claim arising out of the reproduction and reprinting of the materials listed above.
Signature. Printed Name. Company. Job title of signator authorized signature or signer. Dated. Note all fields are required to be completed.
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