Legal Contract Templates How to Write the CD-ROM Development Agreement (UK)

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

CD ROM 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 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. 3 Developer Notices. Unless otherwise agreed to in writing by the Parties Developer shall have the right to place proprietary notices and logos of Developer and its suppliers on the Developer Materials and on the Presentation including developer attribution to Developers Presentations. In no event may Client remove or alter any Developer proprietary notice from the Developer Materials or the Presentation without Developers prior written consent. 4. Licence. 4 Grant of Licence Client. Client hereby grants to Developer non exclusive worldwide royalty free licence to edit modify adapt translate schedule publish transmit participate in the transfer of reproduce create derivative works from distribute perform display and otherwise use Client Content as necessary to render the Services to Client under this Agreement. 4 Grant of Licence Developer.

How do you write a General Project Work Order (No Deposit) document? (alternate or related contract document)

WORK ORDER company name address address city state or province zip or postal code Phone phone number DATE. current date Order WorkOrder Bill To. company name city state or province zip or postal code

Phone phone number For. Insert what you are doing for the customer here DESCRIPTION* HOURS RATE AMOUNT TOTAL Agreements In consideration of the mutual covenants set forth in this Agreement Customer and Company hereby agree as follows. 1. Development of Project or Services. Customer agrees to engage Company to develop the Project as described above*. 2. Delivery of Project or Services. Company will use reasonable diligence in the development of the project and endeavor to deliver to Customer an operational project no later than delivery date. Customer acknowledges however that this delivery deadline is an estimate and not required delivery date. 3. Ownership Rights. Company shall hold all right title and interest in and to all copyrights patents trade secrets and other intellectual or industrial property rights in the project or any component or characteristic thereof which are proprietary to the Company. Customer shall not do anything that may infringe upon or in any way undermine Companys right title and interest in the project as described in this paragraph 3. Notwithstanding the above Customer shall retain all of its intellectual property rights in any components it owns and transmits to Company for use in the project. 4. Compensation. For all of Companys services under this Agreement Customer shall compensate the Company in cash the amount specified in the total above. In the event Customer fails to make any of the payments referenced by the deadline set forth as invoiced Company has the right but is not obligated to pursue any or all of the following remedies. terminate the Agreement remove the project from public access bring legal action. 5. Limited Warranty and Limitation on Damages. Developers warrant the project will conform to the Specifications. If the project does not conform to the Specifications the Company shall be responsible to correct the project without unreasonable delay at the Companys sole expense and without charge to Customer to bring the project into conformance with the Specifications. This warranty shall be the exclusive warranty available to the Customer. Customer waives any other warranty express or implied. Customer acknowledges that the Company does not warrant that the project will work on all platforms. Customer acknowledges that the Company is not responsible for the results obtained by the Customer. Customer waives any claim for damages direct or indirect and agrees that its sole and exclusive remedy for damages either in contract or tort is the return of the consideration paid to the Company. 6. Binding Effect. This Agreement shall be binding upon and inure to the benefit of Customer and the Company and their respective successors and assigns provided that the Company may not assign any of its obligations under this Agreement without prior written consent of Customer. ACCEPTANCE OF AGREEMENT. The above prices specifications and conditions are hereby accepted. The Company is authorized to execute the project as outlined in this Agreement. Payment will be made as proposed 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

How do you write a Software Requirements Specifications document? (alternate or related contract document)

Software Requirements Specification SRS THE SRS PROJECT DOCUMENT TITLE Author Title company name

current date Document Version Control Information V 1. 0 1. Introduction. 1 Purpose of This Document. Insert the purpose of this document and its intended audience. 1 Scope of Document. Insert description of the scope of this Software Requirement Specification

1. 21 Scope Constraints. Insert constraints such as schedules costs interactions overview or any other information relevant to the construction of the development requirements. 1 Overview. Insert an overview or brief description of the product software or other desired end result. 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. 2. General Description. 2 Product Functions.

Insert description of the functionality of the product. 2 Similar System Information. Insert description of the relationship between this product and any other product or product ; whether the product shall be stand alone product or whether the product shall be used as component or to support another program or programs. This section is intended to discuss the relationships between the above mentioned items. 2 User Characteristics. Insert description of the characteristics of the typical user or user community that this product serves or will serve. Include features that the user or user community currently uses or expects. Include current relevant features and describe the expected experience level and familiarity with similar software systems applications or other programs and program use. 2 User Problem Statement.

Insert user problem statement that describes the essential problem currently being faced by the intended user community. 2 User Objectives. Insert the objectives and requirements for the product from the users perspective. The user objectives section may also include wish list of features or functionality that the user want and how that relates to the business context 2 General Constraints. Insert the general constraints placed upon the developers including hardware requirements schedule requirements industry protocols or standards to be met or any other constraint placed upon the development of the product. 3. Functional Requirements. This section describes the functional requirements ranked in order of importance. Here you will describe what the product must accomplish; what other component requirements must accomplish; the requirements for Interface Scalability Performance Compatibility or other components of the product; and how the product fulfills these requirements. Each functional requirement should be specified in format similar to the following. Functional Requirement #1 Name

3 Description. complete description of the functional requirement. 3 Criticality. description of how critical this functional requirement is to the overall product. 3 Technical Issues. description of issues related to the design development or integration of this functional requirement. 3 Cost Summary and Schedules. description of the costs and timelines associated with this functional requirement.

3 Risks. description of the risks and possible circumstances under which this functional requirement may not be able to be met. Include provisions the developers must take in order to overcome this risk. 3 Dependencies with other requirements. description of the various interactions between this requirement and other functional requirements. Here you will insert statements concerning the impact of these dependencies and the impact on the ranking of requirements. Functional Requirement #2 Name Repeat the section above for more requirements. 4. Interface Requirements. This section describes both how the product will interface with other software products or dependencies or with end users for input and output.

4 User Interfaces. Describes how this the end user interfaces with the product. 4. Graphical User Interface GUI. Describes the graphical user interface or whether another system is required to provide the GUI. Include mock ups or screenshots of the user interface features. Describe all navigation systems hierarchy of menus sub menus buttons and all other relevant GUI features of the product. 4. Command Line Interface CLI. Describes the command line interface if present. For each command description of all arguments and example values and invocations should be provided. 4. Application Programming Interface API. Describes the application programming interface if present. For each public interface function the name arguments return values examples of invocation and interactions with other functions should be provided.

4. Debugging and Diagnostics. Describes the process required for the product to return troubleshooting debugging or other diagnostic data and feedback. 4 Hardware Interfaces. description of all interfaces to hardware or hardware devices. 4 Communications Interfaces.

description of all communication and network interfaces. 4 Software Interfaces. description of all software interfaces. 5. Performance Requirements. Insert specific performance requirements. 6. Design Constraints. Insert specific design constraints including compliance with specific standards and constraints on design due to hardware limitations.

7. Other Non Functional Attributes. A description of other non functional attributes required by the product. Examples. 7 Security. Insert the attributes description here. 7 Binary Compatibility. Insert the attributes description here.

7 Reliability. Insert the attributes description here. 7 Maintainability. Insert the attributes description here. 7 Portability. Insert the attributes description here.

7 Extensibility. Insert the attributes description here. 7 Reusability. Insert the attributes description here. 7 Application Compatibility. Insert the attributes description here.

7 Resource Utilization. Insert the attributes description here. 7. 10 Serviceability. Insert the attributes description here. 8. Preliminary Object Oriented Domain Analysis. A description or list of the fundamental objects required to be modeled within the product in order to satisfy its requirements. The goal is to create structural view on the requirements and how they may be satisfied. This section deals primarily with higher level programming and functional requirements AND may be safely omitted for projects not concerned with Object Oriented Domain Analysis OODA. This section should not be removed from your SRS Document. Instead you should include an entry such as. No Object Oriented Domain Analysis Requirement. 8 Inheritance Relationships.

description of primary inheritance hierarchy. Include diagrams graphs or other UML examples to further illustrate such relationships. 8 Class descriptions. description of each class identified during the OODA. Include more detailed description of each class. The description of each class should be organized as follows. 8. Insert the Class name identifier 8. 2. Abstract or Concrete. Indicates whether this class is abstract designed only as parent from which subclasses may be derived or concrete suitable to be instantiated.

8. 2. List of Superclasses. Lists the class from which another class subclass inherits. 8. 2. List of Subclasses. Lists the class that is derived from base class by inheritance. The new class contains all the features of the base class but may have new features added or existing features redefined. 8. 2. Purpose. Lists the purpose of the class. 8. 2. Collaborations. Lists the names of each class that this class must interact with and how it must interact in order to accomplish its purpose. 8. 2. Attributes.

Lists each attribute associated with each instance of this class and indicates examples of possible values or range of values. 8. 2. Operations. Lists each operation able to be invoked upon instances of this class. 8. 2. Constraints. Lists the constraints and restrictions upon the behavior of instances of this class. 9. Operational Scenarios. description of the various scenarios that an end user may experience when using the product under certain conditions or situations. Scenarios are not considered to be functional requirements rather they are used to help set parameters and expectations for the use of the product under these conditions or situations. 10. Preliminary Schedule.

description of the project schedule and timeline for completion. The project plan should include all major tasks who is responsible for the completion of such tasks what the interdependencies of each task are and what the start and completion of each task will be. You should also include vendor information and requirements of such that affect the schedule and timeline. 11. Preliminary Budget. description of the cost summary and an attachment of the initial line item and itemized budget for the project. 12. Appendices. A description of all other supporting information for understanding these requirements. All SRS documents require the following two appendices. 12 Definitions Acronyms Abbreviations.

description of the definitions of important terms abbreviations and acronyms. May also include Glossary. 12 References. listing of all citations to all documents and meetings referenced or used in the preparation of this requirements document. Customer Initials Developers Initials