your contracts very useful and have used them as part of doing business. The web site contracts worked really great as I had to present them to a clients attorney and he found them to be very concise and accurate."
WEB SITE DEVELOPMENT AGREEMENT THIS AGREEMENT is made this current day day of current month current year Commencement Date between company name address city state or province zip or postal code country Developer and company name Customer and collectively referred to as the Parties. WITNESSETH Whereas Developer is in the business of offering Internet services relating to development of sites on the World Wide Web portion of the Internet and is willing to provide services to Customer on the terms and subject to the conditions set forth below; and Whereas Customer desires to engage Developer and Developer desires to be engaged by Customer to provide Internet services on the terms and subject to the conditions set forth below. Now therefore the Parties hereby agree as follows. 1. Developer Services. Developer agrees to provide Customer with services for development of Web site on the World Wide Web portion of the Internet the Web Site as set forth or described in Schedule hereto the Web Site Services and to provide Customer with additional services if any set forth or described in Schedule hereto and mutually agreed upon in writing by the Parties the Additional Services. The obligations of Developer if any to provide ongoing maintenance tasks for the Web Site shall be set forth and included as part of Additional Services on Schedule hereto Maintenance The Web Site Services and the Additional Services are hereinafter referred to collectively as the Services. Customer agrees that Developer is responsible only for providing the Services and Developer is not responsible for providing any services or performing any tasks not specifically set forth in Schedule or Schedule hereto. 2. Web Site Development and Transfer.
2 Specifications and Customer Content. Developer in consultation with Customer shall prepare detailed written specifications for the Web Site the Specifications. The Specifications shall consist of among other things design for the Web Site flow chart of the pages for the Web Site programming and interactive feature requirements and the placement of any content or other materials which are to be incorporated into the Web Site. The Specifications shall be subject to any restrictions or limitations set forth in Schedule or Schedule E. The Specifications which have been mutually agreed upon by the Parties in writing shall be attached hereto as Schedule and Schedule E. If the Parties are unable to agree in writing to mutually acceptable Specifications after using good faith efforts on or before days after the Commencement Date either party may terminate this Agreement by providing written notice to the other party. Such termination shall not relieve Customer from the obligation of paying Developer for all fees due and owing Developer as of the date of such termination. 2 Delivery of Customer Content. Customer Content shall mean any materials provided by Customer for incorporation in the Web Site including but not limited to any images photographs illustrations graphics audio clips video clips or text. Customer shall deliver the Customer Content to Developer in an electronic file format specified and accessible by Developer e. g. txt gif or as otherwise specified in the Specifications. Any services required to convert or input Customer Content not set forth in the Specifications shall be charged as Additional Services. Customer shall promptly deliver all Customer Content to Developer as required by Developer. 2 Initial Version.
Upon Specifications being mutually agreed and upon Developers receipt of the Customer Content and any fees called for in Schedule hereto Developer shall commence tasks associated with the development of the initial version of the Web Site Initial Version and notify the Customer of the URL Uniform Resource Locator or other address of the Initial Version. Developer shall use combinations of technology as Developer in consultation with the Customer deems appropriate to develop the Web Site. 2 Revisions. Customer shall have days days or such time as otherwise agreed by the Parties in writing from the date of written notice of completion of the Initial Version from Developer to review and request in writing from Developer revisions to the Initial Version. Upon receipt of such requests Developer shall use commercially reasonable efforts to implement such revision requests that are within the scope of and consistent with the Specifications. If Customer wishes to implement any revisions to the Web Site that deviate in any material respect from the Specifications Customer shall submit to Developer written change order containing such revisions in detail and request for price quote for each change collectively the Change Order. Developer shall promptly evaluate the Change Order and submit to Customer for its written acceptance proposal for undertaking the applicable tasks and price quote reflecting all associated fees associated with Customers Change Order. Customer shall have days business days from receipt of such proposal to accept or reject Developers proposal in writing. If Customer accepts Developers proposal to undertake the work necessitated by the Change Order then the Change Order as supplemented and or modified by Developers proposal shall amend and become part of the Specifications in Schedule and Schedule as appropriate and Schedule hereto Fee and Payment Schedule and Developer shall proceed to implement such revisions in accordance with the Specifications and Schedule and Schedule as so modified. If Customer has not made any requests for revisions by the end of days days from the date of written notice of completion of the Initial Version from Developer or by such time as otherwise agreed by the Parties in writing or upon completion of implementation of such requests which were mutually agreed upon by the Parties under the revised Specifications the Web Site shall be deemed accepted by Customer Acceptance 2 Transfer. Upon Acceptance of the Web Site and payment of all fees called for in Schedule hereto Developer shall transfer the Web Site to the computer system owned and operated by Customer and or its designated third party contractor identified on Schedule hereto through which the Web Site may be accessed via the World Wide Web portion of the Internet the Host Server. 2 Work Order Forms.
Subsequent to the execution of this Agreement by the Parties in the event Developer and Customer agree that Developer is to perform additional tasks not in the original scope of Services hereunder then the Parties shall execute work order form each an Order Form in the form attached hereto as Schedule upon which each such Schedule shall be incorporated into and shall become part of this Agreement and shall be subject to the terms and conditions hereof. 3. Proprietary Rights. 3 Proprietary Rights of Customer. As between Customer and Developer Customer Content shall remain the sole and exclusive property of Customer including without limitation all copyrights trademarks patents trade secrets and any other proprietary rights. Nothing in this Agreement shall be construed to grant Developer any ownership right in or license to the Customer Content except as provided in Section of this Agreement. 3 Proprietary Rights of Developer. Subject to Customers ownership interest in Customer Content all materials including but not limited to any computer software in object code and source code form script programming code data information or HTML script developed or provided by Developer or its suppliers under this Agreement with the exception of original elements of audiovisual displays created hereunder specifically for Customer which shall be deemed to be part of Customer Content and any trade secrets know how methodologies and processes related to Developers products or services shall remain the sole and exclusive property of Developer or its suppliers including without limitation all copyrights trademarks patents database rights trade secrets and any other proprietary rights inherent therein and appurtenant thereto collectively Developer Materials. To the extent if any that ownership of the Developer Materials does not automatically vest in Developer by virtue of this Agreement or otherwise Customer hereby transfers and assigns to Developer all rights title and interest which Customer may have in and to the Developer Materials. Customer acknowledges and agrees that Developer is in the business of designing and hosting Web sites and that Developer shall have the right to provide to third parties services which are the same or similar to the Services and to use or otherwise exploit any Developer Materials in providing such services. 3 Confidentiality. Each party agrees that during the course of this Agreement information that is confidential or proprietary may be disclosed to the other party including but not limited to software technical processes and formulas source codes product designs sales cost and other unpublished financial information product and business plans advertising revenues usage rates advertising relationships projections and marketing data Confidential Information Confidential Information shall not include information that the receiving party can demonstrate is as of the time of its disclosure or thereafter becomes part of the public domain through source other than the receiving party was known to the receiving party as of the time of its disclosure is independently developed by the receiving party or is subsequently learned from third party not under confidentiality obligation to the providing party. Except as provided for in this Agreement each party shall not make any disclosure of the Confidential Information to anyone other than its employees who have need to know in connection with this Agreement. Each party shall notify its employees of their confidentiality obligations with respect to the Confidential Information and shall require its employees to comply with these obligations. The confidentiality obligations of each party and its employees shall survive the expiration or termination of this Agreement.
3 Developer Notices. Unless otherwise agreed to in writing by the Parties Developer shall have the right to place proprietary notices of Developer and its suppliers including hypertext links related thereto on the Developer Materials and on the Web Site including developer attribution and hypertext links to Developers web sites and to change or update such notices from time to time upon notice to Customer. In no event may Customer remove or alter any Developer proprietary notice from the Developer Materials or the Web Site without Developers prior written consent. 4. License. 4 Grant of License Customer. Customer hereby grants to Developer non exclusive worldwide royalty free license to edit modify adapt translate Schedule publish transmit participate in the transfer of reproduce create derivative works from distribute perform display and otherwise use Customer Content as necessary to render the Services to Customer under this Agreement. 4 Grant of License Developer.
Developer hereby grants to Customer limited non exclusive non transferable royalty free license solely to make use of Developer Materials which are incorporated in the Web Site and which are required for the operation of the Web Site solely to operate the Web Site on the Host Server. Developer hereby reserves for itself all rights in and to the Developer Materials not expressly granted to Customer in the immediately foregoing sentence. In no event shall Customer use any trademarks or service marks of Developer without Developers prior written consent. Unless otherwise agreed to in writing by Developer the transfer or attempted transfer of the Web Site to any host server other than the Host Server shall automatically terminate the foregoing license. 5. Customer Content. 5 Accuracy and Review of Customer Content. Customer assumes sole responsibility for. acquiring any authorization necessary for hypertext links to third party Web sites; and the accuracy of materials provided to Developer including without limitation Customer Content descriptive claims warranties guarantees nature of business and address where business is conducted; and ensuring that the Customer Content does not infringe or violate any right of any third party including without limitation intellectual property rights and without violating any law. 5 Limitations on Customer Content.
Specification Definitions Example attachment defining specification definitions for web site project Standard Page. * Uses our pre existing page templates completely custom pages will require more time. * Page body contains up to unique static GIF or JPG images requiring minimal work including but not limited to. scanning sizing cropping editing compressing. * to browser screens of text when viewed at 640x480 screen resolution. * Up to hyperlinks not including the page header and trailer site navigation hyperlinks * Includes the addition of basic navigation systems built into each page. Creation of the graphical menu bar with image slicing and rollovers is rolled into the base price per page. Keyword Splash Page.
* copy of the primary splash page that is tailored to specific key word of phrase. E commerce Solutions. * Level 1. Flat text file non interactive. * Level 2. page interactive form using email. * Level 3. Multi page interactive forms using email and or data files * Level 4. Multi page interactive forms using real time credit card processing. Level and allow for shopping cart product purchasing on any pages. Common Navigation Systems.
1. Graphical navigation bar with rollovers at head of each page. 2. Page header text navigation bar under the graphical navigation bar. 3. Text navigation bar at bottom of each page. 4. Site map page. 5. Help page. 6. Quick guide page.
7. Automated search component. 8. Index pages page of simple links to sub pages within the site 9. List traversal of series pages pages designed to be read one after the other 10. Hyperlinks to other pages. 11. Shallow tree 4 clicks max. 12. Consistent navigation across all pages.
company name Project Acceptance Signoff address address city state or province zip or postal code Phone phone number DATE. current date Order WorkOrder
Client. company name city state or province zip or postal code Phone phone number For. General Description of Project Deliverables Please initial the following sections which detail the projects deliverables contracted between company name and company name and sign the Acceptance of Agreement at the bottom of this document. Initials Description of Completed Milestone
Acceptance of Milestone #1 description here Acceptance of Milestone #2 description here Acceptance of Milestone #3 description here Acceptance of Milestone #n description here Acceptance of Project per Contract Specifications. ACCEPTANCE OF AGREEMENT. I certify that have received the above project deliverables from company name and that the deliverables listed above have been demonstrated delivered or otherwise completed to my satisfaction. Best Practice Note. If billing by credit card the above line should include permission to charge their credit card. This helps reduce your chargeback exposure. Example. Florentine Design Group LLC may now charge the final installment of 390 to AMEX ************345 for completion of the project. Clients signature
company name Milestone Acceptance Signoff address address city state or province zip or postal code Phone phone number DATE. current date
Order WorkOrder Client. company name city state or province zip or postal code Phone phone number For. General Description of Project Deliverable Please initial the following sections which detail the project deliverable contracted between company name and company name and sign the Acceptance of Agreement at the bottom of this page.
Initials Description of Completed Milestone Acceptance of Milestone Insert Milestone number here Milestone description here ACCEPTANCE OF AGREEMENT. I certify that have received the above project deliverable from company name and that the deliverable listed above has been demonstrated delivered or otherwise completed to my satisfaction. Clients signature
SOFTWARE PROBLEM REPORT If you think you have encountered problem in our product. confirm that you have the latest version of the product you are reporting on; and complete the following form. Reported By signator authorized signature or signer. Date. Phone. Email. Software Version Environment Operating System Y N. Windows Release Y N. Macintosh Release Y N. Linux Release Other. Problem Description Please describe the problem in as much detail as possible. Make note of any behaviors you observe whether you can reproduce the problem and any observations of system behavior slowdown or other events taking place prior to the instance of the problem encountered.
Describe any specific actions you were performing prior to the problem. Frequency Y N. Problem occurs each time Y N. Problem occurs occasionally performing specific action Describe action. Y N. Problem occurs randomly Reproduction Y N. Problem can be reproduced Y N. Problem cannot be reproduced Describe any specific steps or actions to take to reproduce the problem.
Severity Y N. Does not affect usability Y N. Minor requires some extra work to get around Y N. Major requires significant extra work to get around Y N. Critical software is unusable in current state Additional Comments Developer Assigned To
Developer Notes Resolution
SCHEDULE F CONTRACT ADDENDUM THIS AGREEMENT is made this current day day of current month current year by and between company name Company and company name Customer The following requirements are made and are to be included as part of the attached contract. ADDENDUM A. Project Change Request Insert Addendum A. Information Here
ADDENDUM B. Financial Impact and Schedule Impact Insert Addendum B. Information Here Each party represents and warrants that on the date first written above they are authorized to enter into this Agreement in entirety and duly bind their respective principals by their signature below. EXECUTED as of the date first written above. company name
By signator authorized signature or signer. Job title of signator authorized signature or signer. Date when the contact was signed company name By signator authorized signature or signer. Job title of signator authorized signature or signer. Date when the contact was signed
Customer Initials Company Initials
SCHEDULE B SPECIFICATIONS The project will contain the following components and or services. A. Describe each deliverable to be included in the project per the terms of the contract and proposal
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