Anad

• May 15th, 2006

 

Hi

Usually products are first developed and then it is sold to customers. so even u follow the water fall method, at last u have to change some features according to their demand requirement. client may ask for design change after coding and testing, so difficult to maintain the water fall method.

Sujatars

 Profile Answers by Sujatars 

• Feb 27th, 2007

 

Basically a WaterFall model is Requirement Analysis -> Design->Coding->Testing->Maintainance

A waterfall model is optimable if the requirements are clear because every phase should be implemented in a sequential manner. output of one phase should be the input for next phase.we select this model if projects is small in size and user requirements are constant if any mistake in one phases ,same mistake will be repeated till the end of the process.Any change in the requirements ,rework needs to be done from phase one

Gaumzi

• Sep 3rd, 2007

 

We can use use Cyclic Waterfall Model for Product Testing. As while developing a Product we have a clear requirements as if we do not have clear requirement then organisation will not take a risk to develop a product. This is a basic difference b/w Project and Product.
After the Product has been launched the we can upgrade the Product according to the Global users which we call Versions(v1.5, v2.0 etc).
So we can use Cyclic Waterfall Model to upgrade the launched Product.

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• May 7th, 2009

 

HI

I think water fall model is not suggestable for developing a product as it's have so many disadvantages said like above.

Let me know if i'm wrong


Srinivas

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 31st, 2009

 

The Waterfall model is appropriate for small software development projects that have clearly defined requirements that are not apt to change, or if changes are anticipated and are accounted for and all phases are set up to accommodate them.  Otherwise, I would seriously consider a different software development model. 

mithr17

 Profile Answers by mithr17 

• Oct 20th, 2011

 

Same way as you would apply to a project. Waterfall is a SDLC methodology type and so its a process/ protocols followed to develop a software application. So the only difference lies with the stakeholders. If you are working on the services side you and the project team are accountable to the client, 'external' stakeholder.
In case the product is being developed in-house (within the company), the project stake holders will be the top management or the HR who is requesting IT team to build some custom tool etc. Product manager/BA will still gather requirements and prepare requirements document. You as a QA will be talking to the product manager/BA and devs to accomplish your task i.e. testing.

Since I have touched the subject of product manager...
Product managers as strategic while business analysts are tactical. A company hires a product manager to analyze processes and problems outside the company. A company hires a BA to analyze processes and problems inside the company.

A product manager may come to a BA and say that their customer wants X, and that we needed to do Y to provide it. BA will figure out what needed to happen with regards to the systems, processes, data, or organization to make Y happen. Then, BA will provide a number of options with pros and cons, and let the "powers that be" decide. The extent to which BAs work "strategically" is dependent upon how broad Y is as an initiative.

Taken from: http://blog.cauvin.org/2006/10/product-management-versus-business.html