Requirements, Features and Functionality of Bugs in Software Testing Methodologies

Requirements, Features and Functionality of Bugs

The Requirements and the specifications which are developed from the requirements can be incomplete, unclear or self-contradictory. They can be misunderstood or impossible understand
During the design process, the specifications which don't have the flaws in them may be change. The extra features are added, modified and deleted
Requirements, especially, as expressed in specifications are a major source of expensive bugs
The range in form a few percentage to more than 50%, depending on the application and environment
What hurts most about the bugs is that they are the earliest to infect the system and the last to leave

Specification problem usually create corresponding feature problems
A feature can be wrong, missing or useless
It is easy to detect the missing feature or a case
A wrong feature could have deep design implications
If the features are removed, then the software may become more complicate, consume more resources and encourage more bugs

Providing correct, clear, implementable and testable feature specifications in not enough
Features usually come in groups or related features
The features of each group and the interaction of features within the group are usually well tested
The problem id unpredictable interactions between feature groups or even between individual features
Example: The telephone is provided with call holding and call forwarding. The interactions between these two features may have bugs
Every application has its unique set of features and a much bigger set of unspecified feature interaction potentials and therefore result in feature interaction bugs

Due to communication problems between humans, most of the feature bugs are arised
To avoid this, it is better to use a high-level, formal specification languages or systems
Such languages and systems provide short term support but in the long run, does not solve the problem
Short term Support: Specification languages facilitate formalization of requirements and inconsistency and ambiguity analysis
Long Term Support: Assume that we have a great specification language and that can be used to create unambiguous, complete specifications with unambiguous complete tests and consistent test criteria
The specification problem has been shifted to a higher level but not eliminated

Functional test techniques are based on the behavioural description of software
Most of these techniques like transaction flow testing, syntax testing, domain testing, logic testing and state testing are useful in testing functional bugs