Requirements defects:

• A valid requirement which is mandatory and supposed to code (or implement) is missed. The root cause of this defect is due to not capturing this requirement in the specification document. These types of observations are categorized as ‗Missed requirements defects‘ since the requirements are missed from requirement specification document.

• These types of defects are usually caused by business analyst‘s oversight.

• Example: Tester observation while testing the Website: Tester found that ‗Disclaimer‘ link is missing in the website. According to organization/webmaster guidelines it is mandatory to show ‗Disclaimer‘ link in the website so tester expressed his/her concern that the ‗Disclaimer‘ link is missing and to fix this developer expects the business analyst to document in requirement specification document.

Coding defects:

• The requirements have been coded incorrectly due to which behavior of an implemented software function is not in accordance with the requirement specification documents.

• The other frequently occurred defects made by developers are due to Missed to code for the requirements which listed in requirement specification document Coding the requirements which are not specified in the requirement specification document

• These types of defects are usually caused by developer‘s oversight.

• Example: Requirement as per specification document: If user clicks on ‗Home‘ link in a website then ‗Home‘ page should be presented to the user. Tester observation while testing the ‗Home‘ link: Tester found that ‗About Me‘ page is displayed each time the ‗Home‘ link is clicked which is a deviation in the behavior from the requirement specification document. This is an example of coding defect.