Mary Frederick answered
The difference between project and product in software testing is the same type of difference which exists in any other project and product. This is like comparing apples and oranges, they are different in matter, form and design among some of the qualities they possess. The only sameness lies in the fact both are food, both are fruit.
Project and product testing is done at different times; however, the intent of testing is the same. A project has as its purpose to create a product. A product is the result of project. In reality a project is basically a plan for the design, architecture and development of software. Testing is part of a project and for those projects aimed at the creation of good software testing begins when the project begins and continues through the duration of the project. Projects are determined by the need or needs of others to possess a product, which will maximize the uses, for which it is intended.
Project managers and teams come together to design, and develop software. They ask questions and determine the answer through the use of applications, computer language, codes, etc. The act of designing, building and developing software is called a project. The end result of the project is the product, in this case software. The quality of the software continues to be tested, even after it is on the market and being used by those for whom it was intended.
The purpose of software testing beginning with the initiation of a project to build software is to produce a good product, which is the goal of a project. Testing begins and ends with good software, software that keeps it's promise over a long duration. In users terms good software works and makes the users work easier. Good projects lead to good products and consistent testing is the key to good products.
Project and product testing is done at different times; however, the intent of testing is the same. A project has as its purpose to create a product. A product is the result of project. In reality a project is basically a plan for the design, architecture and development of software. Testing is part of a project and for those projects aimed at the creation of good software testing begins when the project begins and continues through the duration of the project. Projects are determined by the need or needs of others to possess a product, which will maximize the uses, for which it is intended.
Project managers and teams come together to design, and develop software. They ask questions and determine the answer through the use of applications, computer language, codes, etc. The act of designing, building and developing software is called a project. The end result of the project is the product, in this case software. The quality of the software continues to be tested, even after it is on the market and being used by those for whom it was intended.
The purpose of software testing beginning with the initiation of a project to build software is to produce a good product, which is the goal of a project. Testing begins and ends with good software, software that keeps it's promise over a long duration. In users terms good software works and makes the users work easier. Good projects lead to good products and consistent testing is the key to good products.
