Scribd
Upload
332 views

How To Write A Software Development Proposal

This document provides guidance on how to write an effective software development proposal. It explains that the proposal should diagnose the problem, prescribe a treatment, and describe the plan of work. The document recommends including components like an executive summary, scope of work, technical plan, management plan, commercial plan, and appendices. It provides details on what should be included in each of these sections, such as the problem description in the executive summary and the project methodology in the management plan. Overall, the document advises that the proposal should focus on the problem domain and clearly convey the solution and benefits to the customer.

Uploaded by

Abdul Rafey
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
332 views

How To Write A Software Development Proposal

This document provides guidance on how to write an effective software development proposal. It explains that the proposal should diagnose the problem, prescribe a treatment, and describe the plan of work. The document recommends including components like an executive summary, scope of work, technical plan, management plan, commercial plan, and appendices. It provides details on what should be included in each of these sections, such as the problem description in the executive summary and the project methodology in the management plan. Overall, the document advises that the proposal should focus on the problem domain and clearly convey the solution and benefits to the customer.

Uploaded by

Abdul Rafey
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 20

How to write a

software
By:
Fa16-bcs-060
Fa16-bcs-132

development
Fa16-bcs-096
Fa16-bcs-054
Fa16-bcs-232

proposal
Introduction

Software engineering proposal is a


document that a software developer
submits to a business customer for
acceptance.
The proposal describes the problem to be
solved and explains the resulting benefits
to the customer.
Important in a Project Proposal

 The key for a great proposal is to invent a great idea.


 There is no “official template” for writing software
proposals.
 To sum up: Content is the key. Form just helps to convey
it.
 The most important thing about a software engineering
proposal is that the proposal is about the problem
domain, not about programming.
Main Things

There are three key things of a software


development proposal:
1. DIAGNOSE PROBLEM
2. PRESCRIBE TREATMENT
3. DESCRIBE PLAN OF WORK
Components

 • Cover Page
 • Table of contents
 • Executive Summary
 • Scope of work
 • Technical Plan
 • Management Plan
 • Commercial Plan
 • Appendices
Cover Page/Project Title

• Name of the Service


• Name of the Organization the proposal is
addressed to
• Date
• Name of the Organization
Table of Contents

• All headers with page numbers


• Sections
• Subsections
Executive Summary

 Comes from written reports/proposals


 Doesn’t contain all of the details
 Capture the reader’s attention.
 Make sure your executive summary can stand on its
own.
 Keep things positive.
Scope of Work

 • Understanding of Requirement
 • Quantifiable Service Scope
 • Inclusions
 • Exclusions
 • Assumptions
Technical Plan

 • Technical Specification
 • Phases
 • Details of each phase
Management Plan

 • Project methodology
 • Status reporting
 • Quality Assurance
 • Team
Structure & Hierarchy
Roles & Responsibilities
Commercial Plan

• Cost
• Duration
• Payment Breakup
• Taxes
• Exclusions & Assumptions
Commercial plan (cont)

• Penalties
• General Terms & Conditions
• Specific Terms & Conditions
• Dispute Resolution
Appendices

 • Samples previous works


 • Recommendations & References
 • Technical Writeup & Brochures
Add-ons Sections

 Some important sections for Software Proposal


 Project Members
 Changes
 Budget
 Benefits/Constrains
Project Members

 The project members should include the


project champion and stakeholders. The
champion is usually an executive who
drives the overall project and budget.
The stakeholder is usually an internal
promoter or sponsor
Changes

 Provides a log
Budget

 The Budget is probably the


most important part to
some executives. They are
all anxious to know how
much the system will cost
them or how much of an
impact this project will have
on their department
budget
Benefits/Constrains

 At the end of the document the few benefits and


constraints of the projects can be highlighted.

You might also like