your contracts very useful and have used them as part of doing business. The web site contracts worked really great as I had to present them to a clients attorney and he found them to be very concise and accurate."
WEB SITE 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 Customer and collectively referred to as the Parties. WITNESSETH Whereas Developer is in the business of offering Internet services relating to development of sites on the World Wide Web portion of the Internet and is willing to provide services to Customer on the terms and subject to the conditions set forth below; and Whereas Customer desires to engage Developer and Developer desires to be engaged by Customer to provide Internet services on the terms and subject to the conditions set forth below. Now therefore the Parties hereby agree as follows. 1. Developer Services. Developer agrees to provide Customer with services for development of Web site on the World Wide Web portion of the Internet the Web Site as set forth or described in Schedule hereto the Web Site Services and to provide Customer 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 obligations of Developer if any to provide ongoing maintenance tasks for the Web Site shall be set forth and included as part of Additional Services on Schedule hereto Maintenance The Web Site Services and the Additional Services are hereinafter referred to collectively as the Services. Customer 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. Web Site Development and Transfer.
2 Specifications and Customer Content. Developer in consultation with Customer shall prepare detailed written specifications for the Web Site the Specifications. The Specifications shall consist of among other things design for the Web Site flow chart of the pages for the Web Site programming and interactive feature requirements and the placement of any content or other materials which are to be incorporated into the Web Site. The Specifications shall be subject to any restrictions or limitations set forth in Schedule or Schedule E. The Specifications which have been mutually agreed upon by the Parties in writing shall be attached hereto as Schedule and Schedule E. 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 Customer from the obligation of paying Developer for all fees due and owing Developer as of the date of such termination. 2 Delivery of Customer Content. Customer Content shall mean any materials provided by Customer for incorporation in the Web Site including but not limited to any images photographs illustrations graphics audio clips video clips or text. Customer shall deliver the Customer 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 Customer Content not set forth in the Specifications shall be charged as Additional Services. Customer shall promptly deliver all Customer Content to Developer as required by Developer. 2 Initial Version.
Upon Specifications being mutually agreed and upon Developers receipt of the Customer Content and any fees called for in Schedule hereto Developer shall commence tasks associated with the development of the initial version of the Web Site Initial Version and notify the Customer of the URL Uniform Resource Locator or other address of the Initial Version. Developer shall use combinations of technology as Developer in consultation with the Customer deems appropriate to develop the Web Site. 2 Revisions. Customer shall have days 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. If Customer wishes to implement any revisions to the Web Site that deviate in any material respect from the Specifications Customer 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 Customer for its written acceptance proposal for undertaking the applicable tasks and price quote reflecting all associated fees associated with Customers Change Order. Customer shall have days business days from receipt of such proposal to accept or reject Developers proposal in writing. If Customer 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. If Customer has not made any requests for revisions by the end of days 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 upon completion of implementation of such requests which were mutually agreed upon by the Parties under the revised Specifications the Web Site shall be deemed accepted by Customer Acceptance 2 Transfer. Upon Acceptance of the Web Site and payment of all fees called for in Schedule hereto Developer shall transfer the Web Site to the computer system owned and operated by Customer and or its designated third party contractor identified on Schedule hereto through which the Web Site may be accessed via the World Wide Web portion of the Internet the Host Server. 2 Work Order Forms.
Subsequent to the execution of this Agreement by the Parties in the event Developer and Customer 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 upon which each such Schedule 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 Customer. As between Customer and Developer Customer Content shall remain the sole and exclusive property of Customer 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 Customer Content except as provided in Section of this Agreement. 3 Proprietary Rights of Developer. Subject to Customers ownership interest in Customer 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 by Developer or its suppliers under this Agreement with the exception of original elements of audiovisual displays created hereunder specifically for Customer which shall be deemed to be part of Customer 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 Customer hereby transfers and assigns to Developer all rights title and interest which Customer may have in and to the Developer Materials. Customer acknowledges and agrees that Developer is in the business of designing and hosting Web sites and that Developer shall have the right to provide to third parties services which are the same or similar to the Services 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 of Developer and its suppliers including hypertext links related thereto on the Developer Materials and on the Web Site including developer attribution and hypertext links to Developers web sites and to change or update such notices from time to time upon notice to Customer. In no event may Customer remove or alter any Developer proprietary notice from the Developer Materials or the Web Site without Developers prior written consent. 4. License. 4 Grant of License Customer. Customer hereby grants to Developer non exclusive worldwide royalty free license to edit modify adapt translate Schedule publish transmit participate in the transfer of reproduce create derivative works from distribute perform display and otherwise use Customer Content as necessary to render the Services to Customer under this Agreement. 4 Grant of License Developer.
Developer hereby grants to Customer limited non exclusive non transferable royalty free license solely to make use of Developer Materials which are incorporated in the Web Site and which are required for the operation of the Web Site solely to operate the Web Site on the Host Server. Developer hereby reserves for itself all rights in and to the Developer Materials not expressly granted to Customer in the immediately foregoing sentence. In no event shall Customer use any trademarks or service marks of Developer without Developers prior written consent. Unless otherwise agreed to in writing by Developer the transfer or attempted transfer of the Web Site to any host server other than the Host Server shall automatically terminate the foregoing license. 5. Customer Content. 5 Accuracy and Review of Customer Content. Customer assumes sole responsibility for. acquiring any authorization necessary for hypertext links to third party Web sites; and the accuracy of materials provided to Developer including without limitation Customer Content descriptive claims warranties guarantees nature of business and address where business is conducted; and ensuring that the Customer Content does not infringe or violate any right of any third party including without limitation intellectual property rights and without violating any law. 5 Limitations on Customer Content.
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
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
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