Software operation maintenance agreement

Most importantly, the client should always get a copy of the fully executed contract. Locating a lawyer to check your contract might take longer than you think if you attempt to do it by yourself. Rocket Lawyer members are able to ask for advice from an experienced lawyer or ask additional questions. How It Works Create your document Answer a few simple questions to make your document in minutes.

Making a Software Maintenance Agreement. What is a Software Maintenance Agreement? The specific details that you should plan to cover are: Contact information for your client How much it will cost and when payment is due What the start and end dates are What tasks you will be doing once hired As expected, your agreement from Rocket Lawyer also contains the typical language with regard to the non-employment relationship, the protection of confidential information, the method s of dispute resolution, and finally, indemnity.

Share this. Advertising Agency Agreement. Communication Plan. Grant Proposal. Verification and Validation Plan. Concept of Operations. Implementation Plan. Concept Proposal. Installation Plan. Work Instructions. Configuration Management Plan. Interface Control Document. Maintenance Plan. Market Research. Marketing Plan. Needs Statement. Operations Guide. Project Plan. Proposal Manager Templates. Proposal Template. Quality Assurance Plan.

Release Notes. Request for Proposal. Risk Management Plan. Scope of Work. Security Plan. Setup Guide. Social Media Policy. Klariti Technical Writing Technical Writing tips and tools. Software Maintenance planing includes ten activities: Preparation — Describe software preparation and transition activities including the conception and creation of the maintenance plan; describe how to handle problems identified during development and configuration management. Modification — After the application has become the responsibility of the maintenance team, explain how to analyze each request; confirm and check validity; investigate and propose solutions; document the proposal and get the required authorizations to apply the modifications.

Implementation — Describe the process for considering the implementation of the modification itself. Acceptance — Describe how the modification is accepted by the maintenance team. The Software shall function in accordance with the Specifications on or before the Delivery Date. If the Software as delivered does not conform with the Specifications, the Client shall within [Time frame] of the Delivery Date notify the Developer in writing of the ways on which it does not conform with the Specifications.

The Developer agrees that upon receiving such notice, it shall make reasonable efforts to correct any non-conformity. Fees billed under the Hourly Rate shall be due and payable upon the Developer providing the Client with an invoice.

Invoices for work completed by the developer will be provided once every [Pay period]. The Parties acknowledge and agree that the Client will hold all intellectual property rights to the Software including, but not limited to, copyright and trademark rights. The Client may request that reasonable changes be made to the Specifications and tasks associated with the implementation of the Specifications. If the Client requests such a change, the Developer will use its best efforts to implement the requested change at no additional expense to the Client and without delaying delivery of the Software.

The Client agrees and acknowledges that the judgment regarding any delay or additional expense shall be made solely by the Developer. Development and delivery of the Software under this Agreement are not in violation of any other agreement that the Developer has with another party. The Software will not violate the intellectual property rights of any other party.