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
The actual document is delivered in the retail products as an editable template.
Produced by:
Proposal Kit
Category:
Software > Computer Software > Business & Productivity Software
Price:
$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:
Schedule B (Specifications) (Can/UK/Aus)
Disclaimers: Proposal Kit, Inc. makes no warranty and accepts no responsibility for suitability of any materials to licensees business. Proposal Kit, 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.

How to write my Schedule B (Specifications) (Can/UK/Aus) document

SCHEDULE B SPECIFICATIONS The project will contain the following components and or services. A. Describe each deliverable to be included in the project per the terms of the contract and proposal

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

Writing the Schedule F (Project Change Form) (Can/UK/Aus) document (example of another included contract document)

SCHEDULE F CONTRACT ADDENDUM THIS AGREEMENT is made this current day day of current month current year by and between company name Company and company name Customer The following requirements are made and are to be included as part of the attached contract. ADDENDUM A. Project Change Request Insert Addendum A. Information Here

ADDENDUM B. Financial Impact and Schedule Impact Insert Addendum B. Information Here Each party represents and warrants that on the date first written above they are authorized to enter into this Agreement in entirety and duly bind their respective principals by their signature below. EXECUTED as of the date first written above. company name

By signator authorized signature or signer. Job title of signator authorized signature or signer. Date when the contact was signed company name By signator authorized signature or signer. Job title of signator authorized signature or signer. Date when the contact was signed

Customer Initials Company Initials

How to write my Exhibit F (Project Change Form) document (example of another included contract document)

EXHIBIT F CONTRACT ADDENDUM THIS AGREEMENT is made this current day day of current month current year by and between company name Company and company name Customer The following requirements are made and are to be included as part of the attached contract.

ADDENDUM A. Project Change Request Insert Addendum A. Information Here ADDENDUM B. Financial Impact and Schedule Impact Insert Addendum B. Information Here Each party represents and warrants that on the date first written above they are authorized to enter into this Agreement in entirety and duly bind their respective principals by their signature below. EXECUTED as of the date first written above. company name

By signator authorized signature or signer. Job title of signator authorized signature or signer. Date when the contact was signed company name By signator authorized signature or signer. Job title of signator authorized signature or signer. Date when the contact was signed

Customer Initials Company Initials

Writing the Exhibit G (Business Requirements) document (example of another included contract document)

EXHIBIT G BUSINESS REQUIREMENTS Priority Legend. M. Mandatory O. Optional N. Not Required E. External Mandatory. This is required deliverable. Optional. This is an optional requirement and not deliverable. Not Required. This is not required deliverable it is listed for reference.

External. This is an external or third party deliverable or dependency. BUSINESS REQUIREMENTS Business Requirement Comments Priority B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 B12 B13 B14 B15 FUNCTIONAL REQUIREMENTS System Requirement Comments Priority F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 F13 F14 F15 Administration Roles and Tasks F16 F17 F18 F19 F20 F21 F22 F23 F24 F25 F26 Project Deployment F27 F28 F29 F30 Presentation and User Interface F31 F32 F33 F34 Site Architecture and Management F35 F36 F37 F38 F39 F40 Process and Workflow Management F41 F42 F43 F44 F45 F46 F47 F48 F49 F50 Systems and Hardware Integration F51 Data driven Functions F52 F53 F54

Writing the Exhibit D (Addresses) document (example of another included contract document)

EXHIBIT D ADDRESSES Client. company name Address. address address City. city State. state or province

Zip Code. zip or postal code Developer. company name Address. address address City. city State. state or province

Zip Code. zip or postal code

How do you write a Schedule E (Additional Services) (Can/UK/Aus) document? (example of another included contract document)

SCHEDULE 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

Writing the Schedule C (Developer Materials) (Can/UK/Aus) document (example of another included contract document)

SCHEDULE C DEVELOPER OWNED MATERIALS The following is list of pre existing materials owned by Developer which will be used in the project. A. Describe each item to be included in the project owned by the Developer THIRD PARTY OWNED MATERIALS The following is list of pre existing materials owned by third parties which will be used in the project. K. Describe each item to be included in the project owned by the third party

How to write my Schedule D (Addresses) (Can/UK/Aus) document (example of another included contract document)

SCHEDULE D ADDRESSES Client. company name Address. address address City. city Province. state or province

Postal Code. zip or postal code Developer. company name Address. address address City. city Province. state or province

Postal Code. zip or postal code

Writing the Schedule A (Payment Terms) (Can/UK/Aus) document (example of another included contract document)

Select an appropriate payment terms from the list of possible choices depending on the agreement being used with and delete the rest. For example if using project development contract use one of the first three milestone based payment terms. For general pricing use the payment terms pricing plan at the end of the list of plans below. SCHEDULE A PAYMENT TERMS 1. Customer agrees to pay Developers fee of Insert Total Payment Amount according to the following terms. A. 90% of the estimated price upon execution of the Agreement. 2. Customer agrees to the pay for all out of pocket expenses incurred by Developers in developing the project including but without limitation any. A. License fees

B. Outsource services billed for Customer C. Film and Developing D. Shipping E. Domain name registration F. Host costs for ISP G. Hardware and software H. Travel 3. Customer agrees to pay for the Developers fee and all expenses as set forth above within days of invoice. All unpaid balances shall accrue interest at 2% per month.

4. Customer agrees that any changes customer makes to the specification may adversely affect the original estimate. Extra time incurred above and beyond the original specification will be billed at an hourly rate of hourly rate and is not subject to the costs estimates and caps in 1. above. 5. Customer agrees that estimated yearly maintenance costs are only estimates and are not included in the quoted price. SCHEDULE A PAYMENT TERMS 1. Customer agrees to pay Developers fee of Insert Total Payment Amount according to the following terms. A. 3 of the fee upon execution of the Agreement;

B. 3 of the fee upon completion of Insert Key Payment Milestone C. The remaining upon completion of the specification. 2. Customer agrees to the pay for all out of pocket expenses incurred by Developers in developing the project including but without limitation any. A. License fees B. Outsource services billed for Customer C. Film and Developing D. Shipping E. Domain name registration F. Host costs for ISP

G. Hardware and software H. Travel 3. Customer agrees to pay for the Developers fee and all expenses as set forth above within days of invoice. All unpaid balances shall accrue interest at 2% per month. 4. Customer agrees that any changes customer makes to the specification may adversely affect the original estimate. Extra time incurred above and beyond the original specification will be billed at an hourly rate of hourly rate and is not subject to the costs estimates and caps in 1. above. 5. Customer agrees that estimated yearly maintenance costs are only estimates and are not included in the quoted price. SCHEDULE A PAYMENT TERMS 1. Customer agrees to pay Developers an hourly fee according to the following terms. A. 10% of the estimate upon execution of the Agreement of Insert Total Payment Amount B. Customer is billed at hourly rate per hour at the completion of each milestone.

C. The customer will not be liable for more than Insert the Maximum Billing Amount in hourly work. 2. Customer agrees to the pay for all out of pocket expenses incurred by Developers in developing the project including but without limitation any. A. License fees B. Outsource services billed for Customer C. Film and Developing

D. Shipping E. Domain name registration F. Host costs for ISP G. Hardware and software H. Travel 3. Customer agrees to pay for the Developers fee and all expenses as set forth above within days of invoice. All unpaid balances shall accrue interest at 2% per month. 4. Customer agrees that any changes customer makes to the specification may adversely affect the original estimate. Extra time incurred above and beyond the original specification will be billed at an hourly rate of hourly rate and is not subject to the costs estimates and caps in 1. above.

5. Customer agrees that estimated yearly maintenance costs are only estimates and are not included in the quoted price. SCHEDULE A CREDIT CARD PAYMENT PLAN Authorization for credit card payments for development per Schedule and B. Charges to be applied as Customer accepts each milestone. Customer accepts liability for all costs incurred including but not limited to chargebacks and reversals. Card Number

Expiration Date Name on Card Title Phone. phone number Fax. fax number Email. email address Company. company name Street. address address City. city

Country. country SCHEDULE A PAYMENT TERMS Pricing Plan. Insert your pricing plan here. Discounts. Insert any discounts available here.

Restrictions. Insert any restrictions here.

How to write my Exhibit E (Additional Services) document (example of another included contract document)

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

A Document from Contract Pack

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

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