Date: Name/Address: Project: Details: Estimated length: Completion by: Price: <$X> Requirements: Customer hereafter referred to as 'The customer' .. Standard business conditions: 1. Completed work produced in the project remains the property of the customer, unless otherwise negoiated. 1a. The use of other, freely available software modules is allowed (these will not be the property of the customer, but remain the property of the community). 1b. Any existing or newly created generic reusable software modules will remain the property of the contractor. 2. Estimated time and price include the following: 2a. Creation of software to fulfill the project goals. 2b. Documentation of software, both user and admin manuals, unless stated otherwise. 2c. Clearly defined milestones (project tasks), and up-to-date informationabout the progress of each task. 2d. Meeting/Discussion time to clarify project goals. Using Instant Messaging / EMail methods. Email and IM exchanges will be retained for reference, with 'meeting minutes' summary docments created as appropriate. 2e. Installation and user support for 14 days after completion of project. 2f. Project testing in an environment as near to the deployment environment as possible. Test results will be available. 2g. Defect fixing after installation. (Subject to defect being confirmed as such by the development team) 3. Estimates do *not* include: 3a. Change requests - wanted features which are outside the scope of the original project specification, after the specification has been agreed upon and signed. These will be evaluated and added as appendices to the specification, with new deadline and price estimates. 3b. Cost for changes: See hourly/daily rates. 4. Requirements: 4a. Appropriate access to any existing solution with which the project solution must work. 4b. Access to persons needed to clarify any goals etc. Delays in this access will result in delays to the completion of the project. 4c. Project specification detailing exactly which deliverables will result from the project and what they will do. 4c. Project specification must be agreed and signed by the customer before development can commence. 4d. Specific details to be set down in the Specification, of the environment in which the project will be used. (To ease local testing). #5. We will not be liable for any disruption of work or loss of income due to #the use or installation of the completed solution. #5a. The customer will help in defining tests to prove the solution works as #requested, and will sign off the project upon completion. 5. Tests, work completion document 5a. A set of tests to prove the software works as required will be defined. 5b. The customer will help design and approve the test suite. 5c. When the software has been tested according to the predefined tests, and the results are deamed a pass, a document will be signed by the customer to acknowledge that the work is complete and functional. 6. Current specifics: 6a. Specification documentation will be delivered in MS Word format. 6b. User documentation will be delivered as HTML. 6c. Milestone reporting: Depends on project length, at least daily. 6d. Response time to problems with the installed solution: 'Urgent' problems occuring within 14 days of installation, 2 hours, daytimes(8:00-22:00 CET timezone). 6e. Problems occuring after 14 days will be treated as change requests, see above.