What is functional requirement document?
A functional requirements document is the most important document for development and it describes what this system should do. What happens when you define ambitious functional requirements?
Sometimes implementation of these requirements can create completely unexpected results perhaps because of these ambitious statements. This applies to any kind of development but particularly to new software development and testing. See the picture below. Sorry - this picture is 1.6 MB to read the text better.

ambitious software requirements
A classic example of ambitious software requirements

Defects (bugs)related definitions in software development - testing

Software Defect. The difference between the functional specification (including user documentation) and actual program text (source code and data). Often reported as problem and stored in defect-tracking and problem-management system

Software Defect. Also called a fault or a bug, a defect is an incorrect part of code that is caused by an error. An error of commission causes a defect of wrong or extra code. An error of omission results in a defect of missing code. A defect may cause one or more failures.[Robert M. Poston, 1996.]

Software Defect. A flaw in the software with potential to cause a failure.. [Systematic Software Testing by Rick D. Craig and Stefan P. Jaskiel 2002]

Software Defect Age. A measurement that describes the period of time from the introduction of a defect until its discovery. . [Systematic Software Testing by Rick D. Craig and Stefan P. Jaskiel 2002]

Requirements (IEEE)b> (1) A condition or capability needed by a user to solve a problem or achieve an objective (2) A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard. specification, or other formally imposed documents. (3) A documented representation of a condition or capability as in (1) or (2). See: design requirement, functional requirement, implementation requirement, interface requirement, performance requirement, physical requirement.

Specification (IEEE). A document that specifies, in a complete, precise, verifiable manner, the requirements, design, behavior, or other characteristics of a system or component, and often, the procedures for determining whether these provisions have been satisfied. Contrast with requirement. See: specification, formal; specification, requirements; specification, functional; specification, performance; specification, interface; specification, design; coding standards; design standards

On this site you can find jokes about software testers, software testing, QA, funny online quiz for software testers as well as information about software testing like software testing dictionary, samples of software testing documentation including test case template and more ...

Software Testing Quiz
© June 2006 http://www.geocities.com/xtremetesting/