Celebrating 20 Years of Helping Businesses Win Business
This contract document is also included in the discounted Proposal Kit Professional bundle. Order and download for $199.
The Specifications is a basic fill-in-the-blank form for you to specify all of the components of the project. This document is used as an attachment to the contract.
Document Length: 1 Page
Business proposal example Our best response

to your tools, is when a client comments on how unique our proposal or contract document looked to them from the competition, especially when we win the contract."

Dr. Allison Frazier Jackson
This 'flip-book' sample is for our web site illustration purposes only. The actual document is delivered in the retail products as an editable template. Proposal Kit products do not include this 'flip-book' style presentation.
Produced by:
Proposal Kit
Software > Computer Software > Business & Productivity Software
$199 USD
Proposal Kit reviews4.9 stars, based on over 700 reviews
Related documents may be used in conjunction with this document depending on your situation. Many related documents are intended for use as part of a contract management system.

Related Documents:
Exhibit B (Specifications)
Disclaimers: Cyber Sea, Inc. makes no warranty and accepts no responsibility for suitability of any materials to licensees business. Cyber Sea, Inc. assumes no responsibility or liability for errors or inaccuracies. Licensee accepts all responsibility for results obtained. Information included is not legal advice. Use of any supplied materials constitutes acceptance and understanding of these disclaimers.

Writing the Exhibit B (Specifications) document

EXHIBIT 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

How to write my 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

How do you write a Contract Specifications Definitions document? (alternate or related contract document)

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.

Writing the Works for Hire Agreement document (example of another included contract document)

WORKS FOR HIRE AGREEMENT THIS AGREEMENT is made this current day day of current month current year by and between company name Company and company name Contractor Declarations Pre existing Works shall mean any method practice source code object code graphics or other resource incorporated into any deliverable that contains Contractors Proprietary Rights. Contractors Proprietary Rights shall mean anything in which Contractor has rightful copyright trademark patent or other intellectual property interest.

Moral Rights shall mean the right to the integrity of the work specifically the right to preserve works for hire from alteration distortion or mutilation. Deliverables shall mean the software provided in object and or source format and subject to Contractors Proprietary Rights documentation or other materials required to be delivered by Contractor to Company or Companys Client as set forth in any Specification s. Source Code shall mean all of the readable forms of code documentation or any combination thereof that go together to make and build files or Deliverables. Services shall mean any programming training customization enhancement or other labor performed by the Contractor as required by the Specifications which may or may not have an associated Deliverable. Specifications shall mean the specifications for the Deliverables as reasonably communicated and agreed to by Contractor which include detailed specifications and instructions for all required Deliverables features and functionality and complete production schedule for each Deliverable. Recitals A. Contractor has experience and expertise in the development and formation of original written works Materials or Project B. Company desires to have Contractor develop Materials for Company.

C. Contractor desires to develop Companys Materials on the terms and conditions set forth in Exhibit attached hereto the Specifications Agreements In consideration of the mutual covenants set forth in this Agreement Company and Contractor hereby agree as follows. 1. Term of Agreement. The term of the agreement shall be for years years from the date signed. 2. Development of Materials. Contractor agrees to the documentation and development of the Materials according to the compensation terms listed on Exhibit attached hereto. All work performed by Contractor shall be considered Works for Hire and Contractor shall be compensated to grant all rights including Moral Rights to the Materials to Company.

3. Specifications. Contractor agrees to develop the Project pursuant to the Specifications set forth in Exhibit B. 4. Delivery Dates and Milestones. Contractor will use reasonable diligence in the development of the Materials and endeavor to deliver to Company all operational Materials and files no later than delivery date. Company acknowledges however that this delivery deadline and the other payment milestones listed in Exhibit are estimates and are not required delivery dates unless otherwise noted in the Specifications. Deliverables defined as Critical Deliverables shall be outlined in Exhibit and shall contain the delivery date and the terms of delivery of the Critical Deliverable. Contractor shall deliver at all times any and all material required to complete the Project. 5. Ownership Rights.

Company shall retain all ownership title and interest in all Materials including all Moral Rights delivered under this Agreement. All subject matter created as part of the Materials shall be considered works made for hire and Company shall own all copyrights. To the extent that any rights in the Materials vest initially with Contractor for any reason Contractor hereby irrevocably assigns and quitclaims any such rights to Company. Contractor acknowledges that the materials contributed and work performed are being commissioned for Insert Project or Materials Name and shall be used in connection with Insert brief usage description All work performed and or contributed by Contractor shall be considered Works for Hire as defined by the copyright laws of the United States of America. Company shall be the exclusive owner of such works and retain all rights and title in and to the results and proceeds of the Contractors work regardless of its level of completion or whether the work is used in part or as whole. Contractor shall not have any Moral Rights to the Materials or Pre existing Works incorporated into the Materials or Project or any right to direct or approve their usage in part or in whole. Contractor hereby grants to Company non exclusive royalty free nontransferable worldwide right and license to use reproduce modify and distribute any Pre existing Works incorporated into the Materials in connection with Companys use of the Materials. Rights and license shall include but is not limited to rights to modify any Pre existing Works to adapt or incorporate the Pre existing Works into the Materials and to modify the Pre existing Works to correct errors add features or functionality to the Materials and to make the Materials compatible with other hardware or software. 6. Project Development. 6 Contractor Warranties.

Contractor certifies and warrants that the following is true and valid. 6. No Conflict. By entering into this Agreement Contractor certifies that Contractor does not and will not violate conflict with or result in material default under any other contract agreement indenture decree judgment undertaking conveyance lien or encumbrance to which Contractor or any of Contractors affiliates is party or by which Contractor or any of Contractors property is or may become subject or bound. Contractor will not grant any rights under any future agreement and will not permit or suffer any lien obligation or encumbrances that will conflict with the full enjoyment by Company of Companys rights under this Agreement. 6. Right to Make Full Grant. Contractor has all required ownership rights and license to grant Company all necessary rights with respect to the Materials free and clear of any and all agreements liens and interests of any person or party including without limitation Contractors employees contractors agents artists or any such employees contractors agents and artists who have provided are providing or will provide services with respect to the development of the Materials.

6. Non infringement. Nothing contained in the Materials or required as any part or operation of the Materials or required to deliver the Materials under this Agreement does or will infringe upon or violate any intellectual property rights of any third party. Further nothing contained within the Materials or any part or operation of the Materials will cause the use reproduction resale or transfer of the rights to the Materials to infringe upon the intellectual property rights of any third party. 6. Pre existing Works and Third party Materials. Contractor has the right to assign and transfer rights to such Pre existing Works and third party materials as specified in this Agreement. 6 No Reliance on Third party Software or Technology.

Unless otherwise agreed to by Company Project files shall not require any additional software third party resources plug ins or other technologies not listed in the Specifications. Any additional software required to run the deliverables shall be construed as non conformance to the Specifications. 7. Specific Enhancements. Contractor and Company acknowledge that at some time during the Term of this Agreement either Contractor or Company may propose enhancements to the Project that fall outside of the scope of the Specifications. Upon such proposal Contractor shall confer in good faith with Company concerning the feasibility of developing such enhancements and the time frame for developing testing and incorporating such enhancements. Contractor and Company shall mutually agree in writing as to whether Contractor shall pursue the development of such enhancements and if so which party will fund such development. The Specifications will be amended to include such enhancements. 8. Compensation. For all of Contractors services under this Agreement Company shall compensate Contractor in cash pursuant to the terms of Exhibit attached hereto. In the event Company fails to make any of the payments referenced in Exhibit by the deadline set forth in Exhibit Contractor has the right but is not obligated to pursue any or all of the following remedies. terminate the Agreement; remove equipment owned by Contractor whether leased to Company by Contractor or not and remove any Contractor personnel or Staff from Company location ; bring legal action; or Contractor may suspend development of the Project and is responsible for any schedule changes required and additional financial impact. 9. Confidentiality. Company and Contractor acknowledge and agree that the Specifications and all other documents and information related to the development of the Materials the Confidential Information will constitute valuable trade secrets of Contractor. Company shall keep the Confidential Information in confidence and shall not at any time during or after the term of this Agreement without Contractors prior written consent disclose or otherwise make available to anyone either directly or indirectly all or any part of the Confidential Information.

10. Limited Warranty and Limitation on Damages. Contractor warrants that the Materials will conform to the Specifications. If the Materials do not conform to the Specifications Contractor shall be responsible for correcting the Materials without unreasonable delay at Contractors sole expense and without charge to Company to bring the Materials into conformance with the Specifications. This warranty shall be the exclusive warranty available to Company. Company waives any other warranty express or implied. Company acknowledges that Contractor does not warrant that the Materials will work on all platforms. Company acknowledges that Contractor will not be responsible for the results productivity or any other measurable metric not specified in Exhibit obtained by Company on the Materials. Company 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 Contractor as set forth in Exhibit attached hereto. Contractor will monitor the reliability and stability of the Materials for period of up to days days to ensure that they perform in accordance with the Specifications. If modifications are required at any time Contractor will confer in good faith with Company concerning the appropriateness of any modifications and mutually agree whether or not to make such modifications; provided however that such agreement will not be deemed to relieve Contractor from Contractors obligations to ensure that the Project continues to conform to the Specifications and compensation estimates as set forth in Exhibit A. 11. Independent Contractor. Contractor shall be retained as an independent contractor. Contractor will be fully responsible for payment of income taxes on all compensation earned under this Agreement. Company will not withhold or pay any income tax social security tax or any other payroll taxes on Contractors behalf. Contractor understands Contractor will not be entitled to any fringe benefits that Company generally provides for Companys employees or to any statutory employment benefits including without limitation workers compensation or unemployment insurance. 12. Equipment.

Company agrees to make available to Contractor for Contractors use in performing the services required by this Agreement such items of hardware and Materials as Company and Contractor may agree are reasonably necessary for such purpose. 13. General Provisions. 13 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. 13 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. 13 Binding Effect. This Agreement shall be binding upon and inure to the benefit of Company and Contractor and their respective successors and assigns provided that Contractor may not assign any obligations under this Agreement without Companys prior written consent.

13 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. 13 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. 13 No Right to Assign. Contractor has no right to assign sell modify or otherwise alter the Materials except upon the express written advance approval of Company which consent can be withheld for any reason.

13 Indemnification. Contractor warrants that the Project will conform to the Specifications or such other specifications as are agreed to in writing by Contractor for period of one year from the date of completion of the Project. If the Project does not conform to the Specifications as Companys sole remedy Contractor shall be responsible for correcting the Project without unreasonable delay at Contractors sole expense and without charge to Company to bring the Project into conformance with the Specifications set forth in Exhibit B. This warranty shall be the exclusive warranty available to Company. Company waives any other warranty express or implied. Company acknowledges that Contractor is not responsible for the results obtained by Company on the Project. Company acknowledges that Contractor is not responsible for fixing any problems errors or omissions on the Project after Company has tested proofed and approved the Project and either written approval has been given to Contractor or the Project has been mass produced or transmitted in the Public Domain in any way. Company waives any claim for damages direct or indirect and agrees that Companys sole and exclusive remedy for damages either in contract or tort is the return of the consideration paid to Contractor as set forth in Exhibit attached hereto. No action regardless of form arising out of any claimed breach of this Agreement or transactions under this Agreement may be brought by either party more than one year after the cause of action has occurred. 13 Right to Make Derivative Works. Contractor will have no rights in making any derivative works from any of its work practices coding programming or other work on the Materials as outlined in the Specifications. 13 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. 13. 10 Identification of Contractor. Contractor identification may not be annotated within any of the code or on the web site as the author. Contractor also agrees not to use copyright notices on Materials and the relevant content therein. Insert even stricter usage requirements if you wish. If your Company or project has an interest in not disclosing that your product project or other relevant work has been provided by Contractor use this section to restrict such rights. Otherwise your project may wind up in the Contractors portfolio blog etc.

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 Contractor Initials

A Document from Contract Pack

The editable Exhibit B (Specifications) template - complete with the actual formatting and layout is available in the retail Contract Packs.
Proposal Kit on BBB
Proposal Kit
Create winning business proposals & contracts with minimal effort and cost. Downloadable proposal software, proposal templates, legal contracts and sample proposals.
© 1997 - 2016, Cyber Sea, Inc. All rights reserved.
Proposal Kit on BBB Proposal Kit

Create winning business proposals & contracts with minimal effort and cost. Proposal software, proposal templates, legal contracts and sample proposals.