Software Service

Client
Provider
Gets the details of what is the need

Performs Feasibility analysis

Makes Technology decisions

Infrastructure decisions are done

People - personnel analysis

Visit http://softwaretestinghelp.org
Proposed solution in terms of Functionality
•Detailed analysis of what the problem is - diagnosis
•Understand the diagnosis and propose solution
•Show the plan how the software is going to be built

Schedules
•How long does it take for the project to be done
•What are the different phases and specific schedules

Technology decisions
•Decide what databases, servers and programming language implementations to incorporate
•At this point, keeping the technical information to a minimum is important

Budget
•How much money is going to be involved and in what areas
•Payment schedules and account information etc.
•This section is optional- some teams choose to include in the proposal doc and some don't

ETAs
•Delivery schedules
•What can the client expect in terms of milestones
•What kind of response and response time can be expected in terms of issues

Maintenance Agreements
•Post delivery what kind of support will the software service provider can expect

Service Level agreement

•An example is: the final product delivered will not contain more than 3 low priority bugs

Legal contracts

Visit http://softwaretestinghelp.org
Initiate Define Design Code Test Deploy

Visit http://softwaretestinghelp.org