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."
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
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
Title Date when the contact was signed 11. Appendices A description of all other supporting information required for the understanding and execution of the Software Development Plan and requirements. All Software Development Plan documents require the following two appendices. Expanded from Sec. 11 Definitions Acronyms Abbreviations A complete list of the definitions of important terms abbreviations and acronyms. This may also include Glossary of terms.
11 References A complete listing of all citations to all documents and meetings referenced or used in the preparation of this Software Development Plan and testing requirements document. Customer Initials Developer Initials
COMPUTER SOFTWARE DEVELOPMENT 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 Computer Software Software B. Customer desires to have Developers develop Software for them. C. Developers desire to develop Customers Software on the terms and conditions set forth in Exhibit attached hereto the Specifications Definitions Deliverables shall mean the Software provided in object and or source format as set forth in the Specifications and subject to Developers Proprietary Rights documentation or other materials required to be delivered by Developers to Customer as set forth in the Specifications.
Critical Deliverables shall mean Deliverables that have Milestone date as outlined in the Specifications that must be transmitted to Customer on or before specific date. Source Code shall mean the readable forms together with make and build files. Beta shall mean any and all Deliverables provided to Customer prior to the Launch Date. Final shall mean any and all Deliverables provided to Customer that are in accordance with the Specifications and accepted by Customer as completion of particular Deliverable. Launch Date shall mean the date that the Product is first available for use by the public. Software shall mean the computer software program described in the Specifications that is to be developed by Developers including all Enhancements made under this Agreement. Product shall mean software for computer or an end user.
Schedule shall mean the schedule for completion of the Deliverables as set forth in the Specifications. Delivery shall mean transmitted by Developers to Customers electronically and in accordance with security measures agreed upon by both parties in accordance with the Specifications. Services shall mean any training customization enhancement or other labor performed by Developers as required by the Specifications. Error shall mean malfunctions or defect within the Software or Deliverable that prevents it from conforming to the Specifications. Internet shall mean any system for distributing digital or electronic information to end users via transmission broadcast or any other form of delivery whether direct or indirect known or subsequently developed. Specifications shall mean the specifications for the Product and Services as detailed and attached to this Agreement as Exhibit that includes detailed specifications and instructions for all required Deliverables features and functionality and complete production schedule for each Deliverable and Milestone. Term shall mean the period of time commencing on the Effective Date of this Agreement and continuing indefinitely until this Agreement is terminated. User Interface shall mean all navigational devices menus menu structures or arrangements icons visual mechanisms metaphors or help and other operational instructions and all other components of any source or object computer code that comprises the Software.
Web shall mean the World Wide Web containing pages written in hypertext markup language HTML and or any similar successor technology. Web Page shall mean document that may be viewed in its entirety on the Web. Web Site shall mean collection of inter related Web pages or documents accessible through Web page browser interface or any other similar successor technology. Developers Proprietary Material shall mean all intellectual property rights in any text images or other components and or materials owned by Developers or which Developers have the legal right to use that are delivered to Customer including but not limited to software related documentation source code scripts object code logos graphics or tag lines. Customers Proprietary Material shall mean all intellectual property rights in any text images or other components and or materials owned by Customer or which Customer has the legal right to use that are delivered to Developers including but not limited to software related documentation Customer marketing material logos graphics or tag lines. Developer Code shall mean all Developers Proprietary Material or software Source Code existing as of the date of this Agreement that is to be incorporated into the Source Code of the Product. The license terms for Developer Code will be stated in the Specifications. Documentation shall mean all user guides reference integration installation or implementation manuals that describe in detail the operation of the Software that is normally provided by Developer as part of its deliveries to its customers. Development Activities shall mean any activities undertaken by Developer in the development of the Software and Documentation satisfying the Specifications pursuant to this Agreement.
Enhancements shall mean error corrections bug fixes modifications and updates not included in the Specifications with respect to the Software. Milestone shall mean each development or Deliverable reached by Developers and agreed upon in writing between Developers and Customer. Milestone Payment shall mean payment obligation related to the achievement and acceptance of particular Milestone. Acceptance shall mean completion of Deliverable that conforms to the Specifications and is mutually agreed upon in writing by both Developers and Customer. Agreements
In consideration of the mutual covenants set forth in this Agreement Customer and Developers hereby agree as follows. 1. Development of Software. Developers agree to installation management documentation and development of the Software and Software based operations according to the compensation terms listed on Exhibit attached hereto. 2. Specifications. Developers agree to develop the Software pursuant to the Specifications set forth in Exhibit attached hereto the Specifications 3. Delivery Dates and Milestones.
Developers will use reasonable diligence in the development of the Software and endeavor to deliver to Customer operational Software no later than delivery date. Customer acknowledges however that this delivery deadline and the other payment milestones listed in Exhibit are estimates and are not required delivery dates unless otherwise noted in the Specifications. Deliverables defined as Critical Deliverables shall be outlined in Exhibit and shall contain the delivery date and terms of delivery of the Critical Deliverable. Developers will be retaining the Source Code for the Software and providing Customer with the output formats only. The output is to be used only within the scope of the Software as outlined in Exhibit and does not include the following. replication duplication or otherwise copying the Software in any form not authorized by Developers creating new Software based on the code its functions or other Proprietary Rights as outlined in Paragraph sale or distribution of the code in any form or any relinquishment of copyright by Developers in any way. 4. Ownership Rights. Except for Customers Proprietary Material defined below contained in the Software Developers shall hold all right title and interest in and to the Software. 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 Software 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 Software 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 Software or any component or characteristic thereof. Customer shall not do anything that may infringe upon or in any way undermine Developers right title and interest in the Software as described in this Paragraph 4. Notwithstanding the above Customer shall retain and Developer shall have no Proprietary Rights whatsoever in all of Customers intellectual property rights in any and all text images or other components and or materials owned by Customer or which Customer has the legal right to use that are delivered to Developers including but not limited to software related documentation Customer marketing material logos and tag lines Customers Proprietary Material Developers agree that it shall not use Customers Proprietary Material for any other purpose than those expressly set forth in this Agreement. 5. Software Development. Software Development and Services described here are provided for Linux Windows Macintosh Sun Solaris UNIX systems only unless otherwise specified. Unless otherwise agreed upon by Developers and Customer any modifications required to the Software code or other component related to its operation that are result of third party changes to resources required by the Software shall be considered ADDITIONAL and will fall outside of the Specifications. Third party modifications may include but are not limited to. patches fixes security flaws errors updates upgrades or any other changes to third party operating systems plug ins or any required resources not created by Developers.
6. Specific Enhancements. Developers and Customer acknowledge that at some time during the Term of this Agreement that enhancements to the Software may be proposed by either Developer or Customer which fall outside of the scope of the Specifications. Upon such proposal Developers shall confer in good faith with Customer concerning the feasibility of developing such enhancements and the time frame for developing testing and incorporating such enhancements. Developers and Customer shall mutually agree in writing as to whether Developers shall pursue the development of such enhancements and if so which party will fund such development. The Specifications will be amended to include such enhancements. 7. Backups and Redundancies for Development. Developers will maintain off site storage of all stages of the Source Code and other backup media related to this Agreement to ensure Software integrity and protection and will be responsible for setting up daily procedure for backing up all data. Developers agree to update all backups of code on daily basis unless otherwise agreed upon in the Specifications. Backups will be maintained for one year from the acceptance date of the project. 8. Acceptance. The terms and conditions contained in this Section will apply to the initial release of the Software as well as to subsequent release upgrades enhancements or any other version thereof. Customer shall evaluate any beta or final version of each Deliverable and shall submit an acceptance or rejection to Developers within days days after Customers receipt of an agreed upon transmission of each Deliverable. 9. Testing and Quality Assurance. Developers agree to thoroughly test the Software Product including without limitation each and every release version and enhancement thereof as appropriate under the circumstances at all appropriate stages of development and shall document its testing by written test documents delivered to Customer. Developers will submit its test plans to Customer so as to ensure that Customers standards of quality are maintained and Developers agree to subsequently modify the test plans to accommodate Customers requests if Customer reasonably deems necessary. Quality Assurance or test documentation shall include detailed descriptions of the tests conducted their results and any outstanding or unresolved issues. Developers will not deploy the Product Software or any enhancement thereof unless Customer and Developers agree upon such action in writing. 10. Adherence to Schedule.
If Developers fail transmission of any Critical Deliverable within the dates specified in the Schedule or fail to meet Milestone as defined in the Specifications then Breach of Agreement Breach shall be considered to have occurred. Customer may. amend the Schedule to include correction period; or suspend the Schedule until the problem is corrected at the sole expense of Developers subject to Customers reasonable satisfaction; or terminate this Agreement. Delivery of all Deliverables not defined in the Specifications as Critical Deliverables shall be considered estimates and delivery shall not be subject to Breach. Developers shall not be held responsible for any delays due to. milestones missed by Customer delays due to Customer Deliverables delays due to transmission equipment failure strikes riots disasters or other natural occurrences. 11. Support Services. Developers will be available to respond to Customers questions about Software and Software problems. Developers will staff help desk with combination of phone and email support services from 9. am to 5. pm Monday through Friday time zone. Developers will be responsible for maintaining an ongoing log of support requests actions taken and track user support requests to completion. 12. Compensation. For all of Developers services under this Agreement Customer shall compensate Developers in cash pursuant to the terms of Exhibit attached hereto. In the event Customer fails to make any of the payments referenced in Exhibit by the deadline set forth in Exhibit Developers have the right but are not obligated to pursue any or all of the following remedies. terminate the Agreement remove equipment owned by Developers whether leased to Customer by Developers or not and any Developers Personnel or Staff from Customer location bring legal action or Customer may suspend development of the Software and is responsible for any schedule changes required and additional financial impact.
13. Confidentiality. Customer and Developers acknowledge and agree that the Specifications and all other documents and information related to the development of the Software the Confidential Information will 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. 14. Limited Warranty and Limitation on Damages. Developers warrant that the Software will conform to the Specifications. If the Software does not conform to the Specifications Developers shall be responsible to correct the Software without unreasonable delay at Developers sole expense and without charge to Customer to bring the Software into conformance with the Specifications. This warranty shall be the exclusive warranty available to Customer. Customer waives any other warranty express or implied. Customer acknowledges that Developers do not warrant that the Software will work on all platforms. Customer acknowledges that Developers will not be responsible for the results productivity or any other measurable metric not specified in Exhibit obtained by Customer on the Software. Customer waives any claim for damages direct or indirect and 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 Exhibit attached hereto. Developers will monitor the reliability and stability of the Software for period of up to days to ensure that it performs in accordance with the Specifications. If modifications are required at any time Developers will confer in good faith with Customer concerning the appropriateness of any modifications and mutually agree whether or not to make such modifications; provided however that such agreement will not be deemed to relieve Developers from its obligations to ensure that the Product continues to conform to the Specifications and compensation estimates as specified in Exhibit A. 15. Independent Contractor. Developers shall be retained as independent contractors. Developers will be fully responsible for payment of their own income taxes on all compensation earned under this Agreement. Customer will not withhold or pay any income tax social security tax or any other payroll taxes on Developers behalf. Developers understand that they will not be entitled to any fringe benefits that Customer provides for its employees generally or to any statutory employment benefits including without limitation workers compensation or unemployment insurance.
16. 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. 17. General Provisions. 17 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 both parties hereto. 17 Governing Law. This Agreement shall be governed by and construed in accordance with the laws of the State of state or province. Exclusive jurisdiction and venue shall be in the county County state or province Superior Court.
17 Binding Effect. This Agreement shall be binding upon and enure to the benefit of Customer and Developers and their respective successors and assigns providing that Developers may not assign any of their obligations under this Agreement without Customers prior written consent. 17 Waiver. The waiver by either party 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. 17 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. 17 No Right to Assign.
Customer has no right to assign sell modify or otherwise alter the Software except upon the express written advance approval of Developers whose consent can be withheld for any reason. 17 Right to Interrupt Services Labor or Removal of Software Resources. In the event Customer fails to make any of the payments set forth on Exhibit within the time prescribed in Exhibit Developers have the right to remove the Software until payment in full is paid plus accrued late charges of 2% per month. 17 Indemnification. Developers warrant that the Software will conform to the Specifications or such other Specifications as are agreed to in writing by Developers for period of days from the date of completion of the Software. If the Software does not conform to the Specifications as Customers sole remedy Developers shall be responsible to correct the Software without unreasonable delay at Developers sole expense and without charge to Customer to bring the Software into conformance with the Specifications set forth in Exhibit B. This warranty shall be the exclusive warranty available to Customer. Customer waives any other warranty express or implied. Customer acknowledges that Developers are not responsible for the results obtained by Customer on the Software. Customer acknowledges that Developers are not responsible for fixing problems errors or omissions on the Software once Customer has tested proofed and approved the Software and either written approval has been given to Developers or the Software has been mass produced or transmitted in the Public Domain in any way. Customer waives any claim for damages direct or indirect and 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 Exhibit attached hereto. No action regardless of form arising out of any claimed Breach of this Agreement or transactions under this Agreement may be brought by either party more than one year after the cause of action has occurred. 17 No Responsibility for Theft. Developers will have no responsibility for any third party disrupting intruding or otherwise copying files or reverse engineering in part or in whole on all or any part of the Software at any time. 17. 10 Right to Make Derivative Works. Developers will have the exclusive rights in making any derivative works from any of its work practices coding programming or other work on the Software that is related to its pre existing Developers Code as outlined in the Specifications.
17. 11 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. 17. 12 Identification of Developers. Customer agrees that Developers identification may be annotated within the code as the authors. Customer also agrees to put Developers copyright notices on the Software and the relevant content therein. 17. 13 No Responsibility for Loss. Developers are not responsible for any down time lost files lost productivity improper use or any other loss that may occur in the operation of the Software. 17. 14 Transfer of Rights.
In the event Developers are unable to continue maintenance and support of the Software non exclusive rights to the Software will be granted to Customer. This transfer shall not include the transfer of third party Software or tools used by Developers in the creation or maintenance of the Software or any part thereof. 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