Project & Product Testing

What is the Difference between Project and Product testing?

Replies to This Discussion

Permalink Reply by Arun on July 30, 2010 at 4:13pm

Project - Creating new software from Scrap - and it is implemented to customer.

Product - 1)Software is already created and it is modified acording to customer need, and it is implemented at customer end.2)More than one customer will use the software.

▶ Reply

Permalink Reply by Ajay Sanodaria on July 30, 2010 at 4:27pm

Thanks Arun,

Actually, arun i want the technical answer for it.

▶ Reply

Permalink Reply by Rakesh on July 30, 2010 at 4:39pm

Hi Ajay,

Project Testing:
1. Generally project testing done based on Client requirements
2. Scope of security testing is limited
3. User acceptance testing is required
4. Will have only one release.
5. unsolved Bugs will be fixed in maintenance stage

Product testing:
1. Testing done based on over all requirements and current
market standards.
2. More security testing is required
3. No User acceptance testing
4. More compatibility testing will be performed.
5. Will have no of releases.
6. unsolved Bugs will fixed in next releases

Hope it will be the answer for your Query...

Thanks
Rakesh...

▶ Reply

Permalink Reply by Ajay Sanodaria on July 30, 2010 at 6:12pm

Hi Rakesh,
Thanks....

for Project Testing:
4. Will have only one release. I want to ask if we are following Agile methodology Development,then there will be more than one release. Correct?

▶ Reply

Permalink Reply by Rakesh on July 30, 2010 at 6:49pm

Yah you are correct but most of the Product development Organizations follow the SCRUM/XP or Agile methodolgy development rather than project base organization and yes in Project base compnay we send the Final relaese at one time or the Major features wise we ship it at Client end but in Product development Organization No of releases are there due to rapid modifications in a Software depending up on the different Customer's requirements and therefore more than one time testing required according to the different client's changes but in Project base only one time testing required ,thats why i stated above " Have only one release".

If i am wrong then please correct me.

Thanks

▶ Reply

Permalink Reply by Ajay Sanodaria on July 30, 2010 at 6:57pm

Thank you Rakesh. You are correct

▶ Reply

Permalink Reply by G.N.MALLIKARJUNA RAO on July 30, 2010 at 6:38pm

I have come across an application testing, a product testing and system testing but not project testing.

And any one of them or all can be taken up to deliver which can be a goal of a testing project.

A project may have to deliver several inter related applications and array of products.

For example Vehicle Tracking System is a name of the project it has server side application, client side PC application and embedded system which is actual product (Tracker) that customer will buy. In this project above mentioned three kind of testing (application, product, system) are done.

Characteristics of an application, product, system are different from Project.

I welcome comments.

Thanks
G.N.Mallikarjuna Rao

▶ Reply

Permalink Reply by Me on July 30, 2010 at 7:03pm

Basic difference between project testing and product testing are following :-

1. Product testing :- 1. Product testing is being developed for the all type of users (inwhich most of the features are common for the users) .

2. Customization scope always be less in product application

2. Product testing for ex : - Tally

2. Project testing :- 1. When we develop an application for the specific client . The priority always for the client requirement . The application develop as per client wish.

2. Project testing : any application which we prepared for the particular client.

Comments always welcome ..................

▶ Reply

Permalink Reply by vijayabaskar on August 2, 2010 at 12:17pm

Hi,... all are ok .. But this point alone need a small correction.

"2. Customization scope always be less in product application"

>>> We can't say as less.. It depends upon the customer need.

▶ Reply

Permalink Reply by Me on August 2, 2010 at 1:35pm

Hi Vijay,

Thanks for your comments .. actually my intention regarding customization scope is that probability of change requirement at a particual time is less than project.

Please let me know if im wrong.

Comments always welcomes