This contract document is also included in the discounted Proposal Kit Professional bundle. Order and download for $199.
Use this template when designing a complex software project. The SDP worksheet will help you develop a comprehensive development plan to ensure the project conforms to your client's specifications and contractual obligations.
Document Length: 14 Pages
Business proposal example I was extremely

pleased with the multiple number of contracts for different scenarios and I also liked the advice given throughout the different manuals. You turned what would usually be a time-consuming, expensive process into an easy and affordable one that gives professional results."

Luke Boerdam
Lb Web Design
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
Software Development Plan
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 do you write a Software Development Plan document?

Software Development Plan SDP THE SDP PROJECT DOCUMENT TITLE Author Title company name current date Document Version Control Information V 1. 0 1. Introduction

1 Purpose of this Document Objectives Insert the purpose of this document its objectives and its intended audience. 1 Scope of Document Insert description of the scope of this Software Development Plan. 1. Scope Constraints Insert constraints such as schedules costs interactions overview or any other information relevant to the testing of the development requirements.

1 Overview Insert an overview or brief description of the product software or other desired end result that is being tested under this Software Development Plan. 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. Note. If you have already completed Software Requirements Specification the majority of this material is copied verbatim from that document. The purpose of this preamble is to familiarize staff recently attached to the testing portion of project who may not have been present or involved with earlier stages of the project. 1 Definitions Terms Acronyms or Abbreviations Insert definitions of any terms used throughout this Software Development Plan. Be sure to define specific acronyms or abbreviations used in your project. 1 References and Reference Material Insert list of all reference documents and other materials related to the Software Development Plan. References will often include but are not limited to. * Requirements Management Plan RQMP

* Risk Management Plan RMP * Business Modeling Guidelines * Development Case * Software Requirements Specifications SRS * Design Specifications * Programming Guidelines * User Interface UI Guidelines * Human Interface HI Guidelines * Test Guidelines and Test Measurement Plan

* Software Quality Assurance Plan * Software Management Plan * Project Outline and Management Plan * Project Acceptance Plan 1 Documentation Items Insert references to documentation. 2. Overview of Project 2 Purpose of Project Insert description of the purpose of the project and expected outcome.

2 Scope of Project Insert description of the scope of the project including the departments it may affect or include vendors it may impact business processes it may enhance or replace or anything else relating to or regarding the scope of the project that this Software Development Plan may include. 2 Project Objectives Insert description of the objectives that are to be met by the project itself and not necessarily by the Software Development Plan. 2 Assumptions and Constraints of the Project

Insert list and descriptions of all assumptions that the Software Development Plan is based upon. Constraints may also be detailed in this section including any variable or conditional constraints that may exist. 2 Software Development Plan History Insert references or table of prior versions of the Project Software Development Plan or any other information detailing revisions edits or changes to this Software Development Plan or Project as whole. 2 Specific Objectives and Requirements Not to be Met Insert any objectives and requirements for this project that are not to be met. This section is used to better clarify areas that you would like to be made clear are not the intended goals of this Software Development Plan. 3. Organization of Project Insert description of how the project and its components are to be organized including hierarchical organization chart or diagram of entities that details authorities. This includes project teams third party vendors third party contractors management duties report to lists and any group that is to be included into the overall organizational structure of the project. 3 Internal Interfaces Insert all information pertaining to how the project interfaces with internal groups in the Company. This includes all direct team members involved with the development. however this may also include departments that may have little or no say in the development of the project yet have roles as end users.

3 External Interfaces Insert all information pertaining to how the project interfaces with external groups in the Company. This includes all vendors and contractors involved with the development including those with testing or end user responsibilities. 3 Roles and Responsibilities Insert the organizational units that are responsible for determining or supporting processes. Include all points of contact for these organizational units. 4. Project Management

This section describes the management processes that oversee the costs timeline schedules decision making and evaluation points in the project. 4 Estimates This section will provide the estimated costs for project including schedule for all payments. Include detailed basis for all costs and description of the point at which re evaluation of those costs should take place. Thresholds should be detailed even if they are conditional or variable costs. 4 Project Plan Detail This section will describe the project plan in detail. This section will often span multiple pages. Criteria for developing project plan include but are not limited to. * The phases that the project plan will be broken into including any friendly names you may use for them such as Prototype Core Development Production etc. * breakdown of the work structure and assignments of responsibilities.

* Timelines Schedules or Gantt Charts that show the amount of time allotted to each phase of the project or to specific tasks. * Specific project milestones and deliverables including specific release dates for prototypes drafts demos or releases. * Specific criteria for project milestones and deliverables. * Identification of the internal or external achievements that must be met for each milestone or deliverable. 4. Project Plan Detail. Iteration Objectives

This section describes each version or iteration of specific deliverable or objectives and what the criteria shall be for approval. If project deliverables include iterations of deliverables that are experimental or exploratory in nature then specific criteria may include Iteration Objectives that merely state what was learned or discovered. 4. Release Dates This section will describe any release dates for project milestones or deliverables. 4. Project Schedule and Schedule of Phases This section will describe the complete schedule for completion of the project including individual breakdowns of each individual phase. Phases that run concurrent should be detailed using proper project management charts and diagrams. Target dates should be fixed in this section for each deliverable or milestone even if they are estimates. 4. Acquisition of Resources This section will describe how the Company will acquire the necessary resources to fulfill the project and which budgets will be tapped to do so. The section may also detail the approach that the Company will take to acquire resources. 4. Project Staffing Plan This section will describe the projects staffing requirement and how the Company will meet those requirements from within the Company or whether additional staff will be required. Detail whether external resources will be utilized to meet the Project Staff Plan and any constraints that may be imposed upon budgets and cost estimates for the project.

4. Project Training Plan This section will describe the projects staff requirement for training and whether external resources will be utilized to meet the Project Staffs Training requirements. Detail any constraints that may be imposed upon budgets and cost estimates for the project. Include time constraints and requirements to train staff. 4. Project Budget This section will describe in detail the costs and their allocation across the entire Software Development Plan. This section may span multiple pages or addenda if necessary. 4 Project Monitoring and Oversight This section will detail the requirements for controlling the projects its costs and adherence to the delivery schedule and phases for the management of the project. Include any schedules required to monitor the progress of the project and its individual milestones and deliverables to ensure that the project adheres to its proposed schedule. 4. Budget Control

This section details any budgetary controls that will be in place for the project. 4. Quality Assurance QA Control This section details any quality assurance controls that will be in place for the project. 4. Measurement Control This section details any measurements and standards that will be used to quantify benchmarks deliverables objectives methods or any other component of the project that requires the definition of specific measurements. 4. Reporting Control This section details all reporting requirements for the project including the frequency and formats of reports for the project.

4 Post Project Responsibilities This section details the responsibilities of individual organization units teams or staff after achieving completion of the project. Include all post project debriefings reports accounting of project resources and materials and staff re assignments and responsibilities. 5. Technical Process Plans and Methods Insert the specific technical process standards and methods to be used during the development of the project. In this section you will describe and define each plan that the Software Development Plan relies upon or includes. You may attach additional exhibits to this section if your testing plan requires them. This section may include excerpts or plan attachments from Sec. and Sec. 1. 7. At minimum most Software Development Plans will include. * Software Development Case * Business Process and Modeling Guidelines

* Design Style and Programming Guidelines and Standards * User Interface UI Guidelines and Standards * Risk Assessment Reduction and Management Plans * Testing Guidelines and Standards * Use Case Standards * Hardware and Resource Infrastructure Plan * Project Acceptance Plan * Configuration Management Plan

* Documentation Guidelines and Standards * Vendor Management Guidelines and Standards * Support Management Plan * Additional Plans or Guidelines 6. Project Deliverables Insert the specific milestones and deliverables that are to be delivered under this plan. Deliverables may also include iterative versions drafts demos prototypes and release versions of Software.

7. Deliverable and Milestone Objective Testing A description of individual milestones and deliverables and the requirements for acceptance. Examples. 7 Milestone or Deliverable Name Insert description here. 7 Milestone or Deliverable Name Insert description here.

7 Milestone or Deliverable Name Insert description here. 7 Milestone or Deliverable Name Insert description here. 8. Hardware and Resource Requirements List A description of the hardware and resource requirements.

Examples. 8 Hardware Requirement Name Insert description here. 8 Software Requirement Name Insert description here. 8 Security Resources Requirement Name

Insert description here. 8 Specific Tools Requirement Name Insert description here. 8 Specific Documentation Requirement Name Insert description here. 9. Change Request and Management A description of the Software Development Plan change request and change management procedures. Describe the process that must be followed for submission review and authorization for all requests for change to the Software Development Plan or any change to any part of the deliverables. 10. Approval for Software Development Plan

A description of the personnel authorized to approve the Software Development Plan. Their names titles and signatures must accompany this document. approved approver Title Date when the contact was signed approved approver Title

Date when the contact was signed approved approver Title Date when the contact was signed approved approver

How do you write a Software Build Requirements document? (alternate or related contract document)

company name Software Build Requirements Documentation current date To. company contract with Re. Insert Project Title Statement of Work ID#. contract reference number Beneficiary. Insert Beneficiary Depositor. Insert Depositor Purpose. Insert Short Description Contact. contract first name contract last name Deposit Schedule. Insert Timeframe or Schedule for Build Deposits Due Date date Software Build Requirements. Assembly Build Deposit Description E. g. PHP HTML JQuery and JavaScript Build Processes Required E. g. None Hardware Requirements E. g. None Operating System Requirements Insert Description Here Total Deliverable Components E. g. Required Compilers Tools Third Party Tools E. g. PHP Database Requirements Insert Description Here Additional Requirements not Listed Insert Description Here Software Build Requirements. Execution Hardware or Peripheral Devices Required for Execution Insert Description Here Minimum Number of Machines for Testing include OS requirements Insert Description Here Third party Software Required for Operation Insert Description Here Database Required for Operational Testing. If so does the build contain the necessary SQL or scripts to create the database Insert Description Here Total Estimated Time to Install and Configure all Required Software Tools Insert Description Here Total Estimated Time to Conduct Limited Testing Insert Description Here Test Plans Included in Deposit Insert Description Here Connections to third party systems web service or other resource required. Insert Description Here Software Build Requirements. Audit Procedures Note. Upon the delivery of any of the build deposits to Beneficiary by Depositor the following procedures shall be conducted prior to the acceptance of each deposit. Depositor shall provide to Beneficiary or Beneficiarys Agent any additional access required including access to all source and build instructions in order to create test or otherwise execute the build of the following fully functional software application s.

Audit Material Procedure Insert Description Here Insert Procedure Here Insert Description Here Insert Procedure Here Insert Description Here Insert Procedure Here Insert Description Here Insert Procedure Here address address city state or province zip or postal code Phone phone number

Writing the CD-ROM Development Contract (Quebec) document (alternate or related contract document)

CD ROM DEVELOPMENT AGREEMENT the Agreement THIS AGREEMENT is made this current day day of current month current year by and between company name Developers and company name Customer Recitals A. Developers have experience and expertise in the development of multimedia digital media graphic design computer programming web sites and CD ROM presentations. B. Multimedia created by Developers includes. CD ROMs web sites computer programming flash animations graphics and other multimedia created or licensed by Developers. C. Customer desires to have Developers develop multimedia for them.

D. Developers desire to develop Customers Presentation on the terms and conditions set forth herein the Presentation Definitions As used herein the following terms shall have the following meanings; A. Customer shall mean company name B. Developers shall mean company name C. Presentation shall mean the project according to the terms and specifications as set out in the schedules to this contract as agreed and amended by the parties hereto.

D. Specifications shall mean for the purpose of each separate contract the specifications as set out and agreed to by the parties and any amendments thereto as attached hereto as Schedule B. E. Dollars All amounts referenced herein shall mean currency of Canada. F. Material shall mean all of Developers and third parties material described in Schedule C. G. Schedules The following are the Schedules attached hereto and are incorporated by reference into this agreement. a Schedule Terms and other conditions for the development of the Presentation. b Schedule Specifications that are applicable to Customers Presentation. c Schedule List of Material owned by Developer and third parties. d Schedule Addresses specified for the parties to this Agreement.

Agreements In consideration of the mutual covenants set forth in this Agreement Customer and Developers hereby agree as follows. 1. Development of Presentation. Developers agree to develop the Presentation according to the terms and specifications set forth in Schedule attached hereto. 2. Specifications. Developers agree to develop the Presentation pursuant to the specifications set forth in Schedule attached hereto the Specifications 3. Delivery of Presentation.

Developers will use reasonable diligence in the development of the Presentation and endeavour to deliver to Customer Presentation based on the Specifications no later than days after all required media has been received from Customer. Customer acknowledges however that this delivery deadline and the other milestones listed in Schedule are estimates and are not required delivery dates. 4. Ownership Rights. Except for any exclusive rights titles interests into any and all trade marks logos intellectual properties and Confidential Information which Customer may have at any time adopted used registered or intended to use during the term of this Agreement in Canada USA or in any other country and provided by Customer Developers shall hold all right title and interest in and to the Presentation. Specifically but without limitation Developer shall hold all right title and interest in and to all text graphics animation audio components and digital components of the Presentation the Content all interfaces navigational devices menus menu structures or arrangements icons help and other operational instructions and all other components of any source or object computer code that comprises the Presentation all literal and nonliteral expressions of ideas that operate cause create direct manipulate access or otherwise affect the Content and all copyrights patents trade secrets and other intellectual or industrial property rights in the Presentation or any component or characteristic thereof. Customer shall not do anything that may infringe upon or in any way undermine or challenge any of Developers right title and interest in the Presentation as described in this paragraph 4. Notwithstanding the above Customer shall retain all of its intellectual property rights in any text images or other components it owns and provides to Developers for use in the Presentation. 5. Compensation. For all of Developers services under this Agreement Customer shall compensate Developers in cash pursuant to the terms of Schedule attached hereto. In the event Customer fails to make any of the payments referenced in Schedule by the deadline set forth in Schedule Developers have the right but are not obligated to pursue any or all of the following remedies. terminate the Agreement remove all web sites hosting and tracking resources for Presentation avail itself of any other right available at law equity or otherwise bring legal action keep Customers deposit and credit it towards development time and costs already incurred for the Presentation. The rights and remedies set out in this Agreement are cumulative and the exercise of any right shall not exhaust all rights or preclude Developers from exercising any one or more right or remedy. 6. Confidentiality. Customer and Developers acknowledge and agree that the Specifications and all other documents and information related to the development of the Presentation provided by Developers the Confidential Information are confidential and constitute valuable trade secrets of Developers. Customer shall keep the Confidential Information in confidence and shall not at any time during or after the term of this Agreement without Developers prior written consent disclose or otherwise make available to anyone either directly or indirectly all or any part of the Confidential Information. Excluded from the Confidential Information definition is anything that can be seen by the public on the Presentation when each page of the Presentation is first accessed. 7. Limited Warranty and Limitation on Damages. Developers warrant the Presentation will conform to the Specifications for period of days from the date of shipment by Developers. If the Presentation does not materially conform to the Specifications Developers shall be responsible to correct the Presentation without unreasonable delay at Developers sole expense and without charge to Customer to bring the Presentation into material conformance with the Specifications. This warranty shall be the exclusive warranty available to Customer. Except as expressly set out herein Customer waives any other warranty condition or representation express or implied. Customer acknowledges that Developers do not warrant that the Presentation will work on all platforms. Customer acknowledges that Developers are not responsible for the results obtained by Customer on the Presentation. Customer acknowledges that Developers are not responsible for fixing problems on Presentations once mass produced after Customer has tested proofed and approved their Presentation. Under no circumstances will Developers be liable to Customer for any claim for damages direct indirect incidental consequential or special howsoever caused or arising even if such damages are reasonably foreseeable. Customer agrees that its sole and exclusive remedy for damages either in contract or tort is the return of the consideration paid to Developers as set forth in Schedule attached hereto.

8. Independent Contractor. Developers agree that they are retained as independent contractors and not as employees associates joint venture partners or legal representatives of Customer. It is the intention of the parties that Developers will be fully responsible for payment of all withholding taxes including but not limited to; their own provincial and federal income taxes paid under this Agreement. The parties agree that Customer will not withhold or pay any income tax Workers Compensation Board Assessments contributions or any other similar charges in respect of Developers personnel and any other payroll taxes on Developers behalf. Developers understand and agree that they will not be entitled to any employee benefits that Customer provides for its employees generally or to any statutory employment benefits including without limitation company pension plans profit sharing plans workers compensation or employment insurance. Developers agree to indemnify Customer for any and all claims made by any lawful government authority for all statutory withholding taxes and deductions not paid by Developers and claimed against Customer for monies paid pursuant to this Agreement and remitted thereto by Customer to such authority or claims against Customer from Developers partners associates and employees. 9. Equipment. Customer agrees to make available to Developers for Developers use in performing the services required by this Agreement such items of hardware and software as Customer and Developers may agree are reasonably necessary for such purpose. 10. General Provisions. 10 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 all of the parties hereto. 10 Proper Law of Contract. This agreement shall be governed by the Laws of the Province of Quebec and the laws of Canada applicable therein without regard to choice of law principles. The parties further agree and understand that notwithstanding any regulations rulings or conventions under any conflict of laws in any jurisdiction that regardless of where the contract is executed and entered into the parties have agreed that the laws of the province of Quebec and Canada as applicable shall govern this contract. The parties hereby agree to attorn to the exclusive jurisdiction of the courts of the Province of Quebec for the commencement of any action hereunder other than applications for injunctive relief. 10 Binding Effect. This Agreement shall be binding upon and enure to the benefit of Customer and Developers and their respective successors and assigns provided that Developers may not assign any of their obligations under this Agreement without Customers prior written consent. 10 Waiver. The waiver by either party or its employees officers directors agents or representatives 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. 10 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.

10 Ownership of Photographs and Media. Developers may use some of their own photographs and other media for the Presentation. Developers retain all right title and interest in such photographs and other media other than hereby granting Customer non exclusive right to use those photographs and media and only on the Presentation. Customers right to use of Materials will be revoked if the Agreement is breached. 10 No Right to Assign. Customer has no right to assign sell modify or otherwise alter the Presentation except upon the express written advance approval of Developers which consent can be withheld for any reason. 10 Indemnification.

Customer warrants that everything it provides Developers to put on the Presentation is legally owned or licensed to Customer. Customer agrees to indemnify and hold Developers harmless from any and all claims brought by any third party relating to any aspect of the Presentation including but without limitation any and all demands liabilities losses costs and claims including attorneys fees arising out of injury caused by Customers products services material supplied by Customer copyright infringement and defective products sold via the Presentation. 10 Use of Presentation for Promotional Purposes. Customer grants Developers the right to use the Presentation for promotional purposes including public display inclusion in Developers marketing material and programs and or to cross link it with other marketing venues developed by Developers now or in the future. 10. 10 No Responsibility for Theft. Developers have no responsibility for any third party copying reverse engineering or improper use of any or all of the Presentation. 10. 11 Right to Make Derivative Works.

Developers have the exclusive rights in making any derivative works or modifications of the Presentation source code or other methods or practices developed and employed by Developers. 10. 12 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. 10. 13 Identification of Developers. Customer agrees that Developers trademarks logos and web links will be placed and remain on the credits page of the Presentation. Customer also agrees to put Developers copyright notices on the Presentation and the relevant content therein and maintain such proprietary notices at all times. 10. 14 No Responsibility for Loss. Including Hardware or Software Compatibility Issues or User Behaviour. Developers make no representations or warranties whatsoever express or implied statutory or otherwise including without limitation fitness of purpose custom or usage or merchantability regarding hardware or software compatibility Y2K issues Operating System compatibility and or any and all improper use of the Presentation by an end user individual or other third party. 10. 15 Transfer of Rights.

In the event Developers are unable to continue maintenance of the Presentation non exclusive rights to the object code version of the Presentation will be granted to Customer. Transfer of Rights does not apply to non transferable third party licenses and proprietary Material owned by Developers. 10. 16 Replication of CD ROMs or other Digital Format. Customer must use Developers to replicate or copy any additional Presentations produced on CD ROM or other Digital Format DVD PAL Video or otherwise. 10. 17 Replication of Multimedia. Customer may not replicate or copy any of the multimedia or artwork owned by Developers without the express written permission of Developers. 10. 18 Cover Art. Customer agrees there may be differences in printed and screen proofs of artwork and screened artwork on final mass duplicated CD ROMs. 10. 19 Reverse Engineering.

Customer may not decompile deconstruct or otherwise reverse engineer the Presentation whether in whole or in part without Developers prior approval. 10. 20 Final Approval. A final proof will be provided to Customer prior to mass production or replication and or release of the Presentation and identified to Customer as such. Customer assumes full responsibility to make sure that the final proof is correct in all capacities including but not limited to. grammar spelling information content artwork copyright and functionality. Developers shall not be held responsible for errors and omissions. 10. 21 Project Backups Copies or Source Maintenance. Developers shall only be responsible for maintaining backups copies or other versions of any source or master files whether developed by Developers or not for period of one year from the date of this agreement. Customer agrees to hold Developers harmless from any damage loss of data theft or other event that may occur to any photographs source code master or other digital files digital media print outs documents or other Customer owned material given to Developers during the course of this agreement. Customer may arrange in writing for Developers copies to be maintained in escrow in the event Developers go out of business cannot maintain copies of source or master files or as otherwise required by Customer. 10. 22 Expiration of Services Related to Project. Any externally linked services provided by Developers that the CD ROM may require including but not limited to. tracking features email hosting forwarding autoresponders submission forms and general web hosting will expire one year from the date of this agreement. External services related to CD ROMs and Presentations created by Developers are not guaranteed to be fully functional in areas requiring access to Internet services after this date and may require an updated version be created at extra cost for updates and reduplication. Developers are not liable or responsible at any time for any damages resulting from any third party services the CD ROM or Presentation may use or changes made to externally linked services that are not provided directly by Developers. Developers will make every effort to test any third party or externally linked resources that Customer requires and will present to Customer proof that all externally linked services are present and in working condition prior to signoff and replication. Developers are not responsible for maintaining any of the data features or reports that third party services may provide.

10. 23 Language. The parties hereto acknowledge that they have requested and are satisfied that the present agreement be drawn up in English. Les parties reconnaissent quelles ont exigé que la présente convention soit rédigée en anglais et sen déclarent satisfaites. 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 Developers Initials

A Document from Contract Pack

The editable Software Development Plan 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.