Legal Contract Templates CD-ROM Development Agreement (Australia)

How to write my CD-ROM Development Agreement (Australia) document

CD ROM DEVELOPMENT AGREEMENT THIS AGREEMENT is made this current day day of current month current year by and between Commencement Date between company name address city state or province zip or postal code country Developer and company name Client and collectively referred to as the Parties. WITNESS Whereas Developer is in the business of offering Internet services relating to development of multimedia Digital media graphic design computer programming web sites and CD Rom presentations and is willing to provide services to Client on the terms and subject to the conditions set forth below; and Whereas Client desires to engage Developer and Developer desires to be engaged by Client to provide CD Rom presentation services on the terms and subject to the conditions set forth below. Now therefore the Parties hereby agree as follows. 1. Developer Services. 1. 1CD Rom. CD Rom means such of CD Rom DVD PAL video and any other media format to which the parties elect to apply this Agreement.

1 Services. Developer agrees to provide Client with services for development of CD Rom presentation Presentation as set forth or described in Schedule hereto the Presentation Services and to provide Client 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 Presentation Services and the Additional Services are hereinafter referred to collectively as the Services. Client 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. Presentation Development and Transfer. 2 Specifications and Client Content. Developer in consultation with Client shall prepare detailed written specifications for the Presentation the Specifications The Specifications shall consist of among other things design for the Presentation flow chart of the pages for the Presentation programming and interactive feature requirements and the placement of any content or other materials which are to be incorporated into the Presentation. The Specifications shall be subject to any restrictions or limitations set forth in Schedule or Schedule F. The Specifications which have been mutually agreed upon by the Parties in writing shall be attached hereto as Schedule and Schedule F. 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 Client from the obligation of paying Developer for all fees due and owing to Developer as of the date of such termination. 2 Delivery of Client Content. Client Content shall mean any materials provided by Client for incorporation in the Presentation including but not limited to any images photographs illustrations graphics audio clips video clips or text. Client shall deliver the Client 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 Client Content not set forth in the Specifications shall be charged as Additional Services. Client shall promptly deliver all Client Content to Developer as required by Developer.

2 Initial Version. Upon Specifications being mutually agreed and upon Developers receipt of the Client Content and any fees called for in Schedule hereto Developer shall commence tasks associated with the development of the initial version of the Presentation Initial Version and notify the Client of the URL Uniform Resource Locator if any or other address of the Initial Version. If Client fails upon request or by the deadline set forth if any in Schedule to make the payment of any fees set forth in Schedule Developer may by written notice terminate this Agreement immediately keep Clients deposit if any and apply it towards any losses incurred by the Developer i discontinue all or any Services rendered by the Developer under this or any other Agreement up to that point in time including disabling any tracking hosting or other services and removing al web site resources if any. Developer shall use combinations of technology as Developer in consultation with the Client deems appropriate to develop the Presentation. 2 Revisions. 2. Client shall have 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. 2. If Client wishes to implement any revisions to the Presentation that deviate in any material respect from the Specifications Client 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 Client for its written acceptance proposal for undertaking the applicable tasks and price quote reflecting all associated fees associated with Clients Change Order. Client shall have business days from receipt of such proposal to accept or reject Developers proposal in writing. If Client 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. 2. If Client has not made any requests for revisions by the end of 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 within business days from receipt of the Developers proposal contemplated in clause 2. then the Developers proposal shall be deemed accepted by Client Acceptance 2. Final Approval. final proof will be provided to Client prior to mass production or replication and or release of the CD Rom and identified to the Client as such. Client assumes full responsibility to make sure that the final proof is correct in all capacities including but not limited to. grammar spelling information content artwork copyright and functionality. Developer shall not be held responsible for errors or omissions. 2 Replication. 2. Upon Acceptance of the Presentation or Developers proposal as the case requires and payment of all fees called for in Schedule hereto Developer shall commence replication of the Presentation and endeavour to deliver to the Client an operational Presentation no later than days after acceptance.

2. Client must use Developer to replicate any additional Presentations produced on CD Roms and may not replicate the Presentation on or through any other medium. 2. Client may not replicate any of the multimedia or artwork owned by the Developer without the prior written permission of Developer. 2. Client agrees that there may be differences between printed artwork and screen proofs of artwork and artwork appearing on final mass duplicated CD Roms replicated under clause 2. hereof. 2. Reverse Engineering. Client may not decompile deconstruct or otherwise reverse engineer the Presentation whether in whole or in part without the Developers prior approval 2. Project Backups Copies or Source Maintenance. Developer shall only be responsible for maintaining backups copies or other versions of any source or master files whether developed by the Developer or not for period of one year from the date of this Agreement. Client agrees to hold the Developer harmless from any damage loss of data theft or other event that may occur to any photographs source code master or other digital files digital media print outs documents or other Client Content given to Developer during the course of this Agreement. Client may arrange in writing for Developer to have copies to be maintained in escrow in the event Developer goes out of business cannot maintain copies of source or master files or as otherwise required by the Client. 2 Work Order Forms. Subsequent to the execution of this Agreement by the Parties in the event that Developer and Client 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 at which time its terms 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 Client. As between Client and Developer Client Content shall remain the sole and exclusive property of Client 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 Client Content except as provided in Clause of this Agreement. 3 Proprietary Rights of Developer. Subject to Clients ownership interest in Client 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 or created by Developer or its suppliers under this Agreement with the exception of original elements of audiovisual displays created hereunder specifically for Client which shall be deemed to be part of Client 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 Client hereby transfers and assigns to Developer all rights title and interest which Client may have in and to the Developer Materials. Client acknowledges and agrees that Developer is in the business of designing and developing Presentations and that Developer shall have the right to provide to third parties services which are the same or similar to the Services provided hereunder 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.

How do you write a 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