pleased with the multiple number of contracts for different scenarios and I also liked the advice given throughout the different manuals. You turned what would usually be a time-consuming, expensive process into an easy and affordable one that gives professional results."
PRODUCT CO DEVELOPMENT AND PROMOTION AGREEMENT THIS AGREEMENT is made this current day day of current month current year by and between company name Company and company name Customer Recitals Customer and Company desire to co produce new product the Software Product or the Co produced Product using combination of existing software products created or owned by each respective party and in adherence with the proposed development plan the Specifications as set forth in Exhibit B. Customer and Company desire to exchange advertising and links and cross promote one another using variety of marketing and advertising services the Services as set forth in Exhibit B. Agreements In consideration of the mutual covenants set forth in this Agreement Company and Customer hereby agree as follows.
1. Creation of New Software Product. Company shall make available select content documents templates and other source or object code the Content for inclusion into new Software Product using Customers Insert Customers contribution to the Co development project Customer shall provide technical assistance in the use of the product as well as specific support in aiding Company in the development of the Software Product. 1 Advertising and Promotion. Customer shall arrange for the placement of advertising and promotion of Company and agrees to fulfill the following duties. 1. Customer will offer the product on all point of sales or any other outlet agreed upon under this agreement. 1. Company will offer the product on their point of sales and any other outlet agreed upon under this agreement. 1. Compensation rates will vary according to Exhibit A. 2. Specification and Services Completion.
Advertising and Marketing Material shall mean any programming coding graphic design linking or other collateral required by either party to fulfill its obligations under the Specifications. Both parties will use reasonable diligence in any development and promotion Advertising and Marketing Material and endeavor to complete all agreed upon materials in timely manner. Both parties acknowledge that any delivery deadline communicated between parties shall be an estimate and is not required delivery date. Both Customer and Company shall retain all intellectual property rights in any logos graphics text images or other components owned and transmitted to either party for use in fulfillment or creation of Advertising and Marketing Material. Each party shall develop the Advertising and Marketing Material according to and in adherence to any guidelines styles or style guides that each party makes use of. 2 Survivability of Products and Compensation. In the event that either party decides to terminate this agreement each party shall continue to have the right to distribute the existing product through their normal sales channels and according to the compensation provisions set forth in Exhibit A. Neither party will have any right to decompile copy reverse engineer or otherwise continue development on the Co produced Product. 2 Notification of Termination. In the event that either party decides to terminate this agreement the terminating party shall give sixty days prior written notification via registered mail of their intent to terminate this agreement. 3. Compensation. For all Services under this Agreement Customer and Company shall compensate one another in cash pursuant to the terms of Exhibit attached hereto. In the event either party fails to make any of the payments referenced in Exhibit by the deadline set forth in Exhibit either party reserves the right but is not obligated to pursue any or all of the following remedies. terminate the Agreement; withhold all materials Services or content from the other party; bring legal action. 4. Confidentiality.
Customer and Company acknowledge and agree that any Specifications and all other documents and information related to the engagement of marketing or advertisement development of products or practices the Confidential Information will constitute valuable trade secrets of each party. Both parties shall keep the Confidential Information in confidence and shall not at any time during or after the term of this Agreement without the others prior written consent disclose or otherwise make available to anyone either directly or indirectly all or any part of the Confidential Information. Excluded from the Confidential Information definition is anything that can be seen by the public in any advertising medium or channel. 5. General Provisions. 5 Entire Agreement. This Agreement contains the entire agreement between the parties relating to the subject matter hereof and supersedes any and all prior agreements or understandings written or oral between the parties related to the subject matter hereof. No modification of this Agreement shall be valid unless made in writing and signed by both parties hereto. 5 Governing Law. This Agreement shall be governed by and construed in accordance with the laws of the State of state or province. Exclusive jurisdiction and venue shall be in the county County state or province Superior Court. 5 Binding Effect. This Agreement shall be binding upon and inure to the benefit of both parties and their respective successors and assigns provided that neither party assigns any of its obligations under this Agreement without the others prior written consent.
5 Waiver. The waiver by either party of any breach or failure to enforce any of the terms and conditions of this Agreement at any time shall not in any way affect limit or waive such partys right thereafter to enforce and compel strict compliance with every term and condition of this Agreement. 5 Good Faith. Each party represents and warrants to the other that such party has acted in good faith and agrees to continue to so act in the negotiation execution delivery performance and any termination of this Agreement. 5 Right to Withhold Content and Creative Services.
In the event that single party fails in its obligations as set forth on Exhibit within the time prescribed in Exhibit the other party has the right to withhold further promotion content and Services performed for or on behalf of the other party until such obligations are met. 5 Indemnification. Both parties warrant that everything they give one another to use in fulfillment of Specifications is legally owned or licensed. Both parties agree to indemnify and hold harmless one another from any and all claims brought by any third party relating to any aspect of the content and Services including but without limitation any and all demands liabilities losses costs and claims including attorneys fees arising out of injury caused by either partys products services material supplied copyright infringement and or defective products sold via the advertising or Services of either party. 5 Use of Services and Creative Content for Promotional Purposes. Both parties may advertise use or otherwise promote the creative content description of Services performed results of Services and campaign data as they see fit for promotional purposes.
5 Placement of Tracking Codes. Both parties may use tracking codes URLs or other IDs to evaluate the effectiveness of any and all advertising. 5. 10 Attorneys Fees. In the event any party to this Agreement employs an attorney to enforce any of the terms of the Agreement the prevailing party shall be entitled to recover its actual attorneys fees and costs including expert witness fees. 5. 11 Term of Agreement. This agreement shall begin on start date and shall continue in full force until terminated by either party upon at least thirty days prior written notice. The parties represent and warrant that on the date first written above they are authorized to enter into this Agreement in its entirety and duly bind their respective principals by their signatures 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
Company Initials Customer Initials
company name Change Order company name address address city state or province zip or postal code
Phone phone number Fax fax number DATE. current date Order contract reference number Bill To. company name address address city state or province zip or postal code Phone phone number Fax fax number For.
Invoice. Product and or Service Billing. Hourly. hourly rate Fixed Rate. fixed rate Other.
Please provide detailed description of the changes that you would like made to your project. Be as specific as possible. Provide the exact page frame location on the page frame and what corrections need to be made. To avoid duplication and confusion please list all of your corrections on this form. You may attach additional forms as necessary. Agreements PAYMENT TERMS. Net days. 1. 5% Interest monthly on accounts past due days. ACCEPTANCE OF AGREEMENT. The above prices specifications and conditions are hereby accepted. The designer is authorized to execute the project or provide software as outlined in this Agreement. Payment will be made as proposed above. Clients signature Title
EXHIBIT E ADDITIONAL SERVICES The project will contain the following additional services. A. Describe each additional service to be included in the project per the terms of the contract and proposal
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 Contract Addendum company name address address city state or province zip or postal code Phone phone number Fax fax number DATE. current date
Order contract reference number Bill To. company name address address city state or province zip or postal code Phone phone number Fax fax number For. Invoice. Product and or Service
Addendum. Contract #contract reference number Additional Services The following is request to amend the previous established and contracted relationship between company name and company name and is to act as an addendum to any existing contract or relationship established between the two parties. Authorized changes may also impact delivery dates and milestones. The undersigned party desires company name to provide the following additional goods and services. Total. Delivery Date Milestone Impact. Entire Agreement. This Agreement contains the entire Agreement between the parties relating to the subject matter hereof and supersedes any and all prior agreements or understandings written or oral between the parties related to the subject matter hereof. No modification of this Agreement shall be valid unless made in writing and signed by both of the parties hereto. Binding Effect. This Agreement shall be binding upon and inure to the benefit of Customer and Developers and their respective successors and assigns provided that Developers may not assign any of his obligations under this Agreement without Customers prior written consent. PAYMENT TERMS. Net days. 1. 5% Interest monthly on accounts past due days. ACCEPTANCE OF AGREEMENT. The above prices specifications and conditions are hereby accepted. The designer is authorized to execute the project or provide software as outlined in this Agreement. Payment will be made as proposed above.
Customers signature Title Date Developers signature Title Date
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