Introduction to SQA (Prelims) Part 2 Flashcards
Made by a software designer or a programmer. An error may refer to a grammatical error in one or more of the code lines, or a logical error in carrying out one or more the specification requirements.
Software Errors
These software errors that causes improper functioning of the software in a specific application and in rare cases, of the software in general.
Software Faults/Software Defects
These are results of software faults. These occurs only when they are ‘“activated”, that is when a user tries to apply the specific software section that is faulty.
Software Failures
There are a wide range of reasons causes programmers to make this.
-Misunderstanding the design documentation
-Linguistic errors in programming languages
-Errors in data selection
-Data processing errors
Coding Errors
Usually prepared by the client, is one of the main cases of software errors. Causations:
-Erroneous definition of requirements
-Lack of essential requirements
-Incomplete requirements definition
-Inclusion of unnecessary requirements
Faulty Requirement
Misunderstandings are resulting from a defective client-developer communication are additional causes for errors that prevail in the early stages of the development process. Causations and signs:
-Poor understanding of the client’s instructions
-Written changes during development
-Oral changes during developments
-Lack of attention by the client to developer questions
-Lack of attention by developers dealing with requirements and changes
Client-Developer Communication Failures
Software errors can enter the system when professionals designing the system; system architects, software engineers, system analysts, and so on to formulate the software requirements into design definitions.
-Erroneous algorithms
-Process definitions that contain sequencing errors
-Erroneous definition of boundary conditions
-Illegal operation of the software system
Logical Design Errors
An action that often causes software errors. This situation occurs when the develop incorrectly interprets a requirement and developers the software based on his own understanding.
-Reuse previous work to save time
-Omit part of the required functions in an attempt to better handle time or budget pressures
-Ignore seemingly minor features, which sometimes are quite major
Deliberate Deviations from Software Requirements
Even if the quality of the “noncomplying” software is acceptable, difficulties will inevitably be presented when trying to understand it. In other words, future handling of this software (by development and/or maintenance teams) is expected to substantially increase the rate of errors.
Noncompliance with documentation and coding instructions
It affects the error rate by leaving a greater number of errors undetected or uncorrected.
-Incomplete test plans
-Failure to document, report detected errors and faults
-Failure to fix the errors due to time constraints
-Incomplete testing of software error corrections
-Incomplete corrects of detected errors due to negligence
Shortcoming of the Testing Process
The documentation errors of concern to the development and maintenance teams are those found in the design, software manuals, documents, user manual and in the “help” displays incorporated in the software.
-Errors in the design documents
-Errors in the documentation within the software user manual
-Listing of non-existing functions
-Many error messages are meaningless
Documentation Errors
User interfaces direct users in areas such as the performance of input and output activities, and data collection processing. This may cause processing failures even in cases of error-free design and coding.
User Interface and Procedure Errors
