The constant updating jargon buster for software testers on the Internet.
Let me know if you want me to add anything else here.
Size of the source file, measured in bytes
All-inclusive count of lines in source code file
Lines of code, excluding comment and blank lines
Effective lines of code, excluding comments, blank lines, and stand-alone braces or parenthesis
Logical lines of code, that is, statements as identified by logical separators such as semicolons
Comment density: comment lines/eLOC
Number of basic blocks: sequences of statements with one entry point, one exit point, and no internal branches
Average number of lines per basic block
Control structure nesting level: minimum, maximum, and average
Number of loops
Number of first order intervals
Maximum order of intervals
Number of linear code sequences
Number of branches in the control flow graph
Number of defined functions (or methods, procedures, …)
Number of formal parameters of functions
Number of return points of functions
Interface complexity: FPar + FRet
Weighted methods per class sum of the complexities of methods in all classes, divided by the number of classes parametric with respect to a measure of complexity in methods
Depth of the inheritance tree of a class
Number of children (subclasses) of a class
Response to a class number of methods that may be executed in response to a method call to an object of the class (transitive closure of the calling relation)
Coupling between object classes number of classes with which the class is coupled
Lack of cohesion in methods number of methods with pairwise disjoint sets of instance variables referenced within their respective method bodies
Ability to provide the required functionality
Ability to provide correct results
Ability to interact with other products
Ability to protect access to private data and guarantee a level of service
Ability to avoid failures
Ability to maintain a suitable level of functionality even in the presence of external failures
Ability to recover data and resume function after a failure
Ease of understanding the product
Ease of training users
Ease of working with the product
Degree of appreciation by users
Ability to satisfy average and maximum response time requirements
Amount of resources needed for executing the software
Ease of analysing the software to reveal faults
Ease of changing the software
Ability to interact with other products
Ability to minimise the effects of changes
Ease of testing the software
Ability to be adapted to new environments
Ease of installing the software
Ability to share resources with other products
Ability to be replaced by other products
Business Analysis / Business Analyst
British Computer Society
Customer Relationship Manager
Chartered Quality Institute
Institute of Electronic and Electrical Engineers
Information System Examination Board
International Standards Organisation
International Systems Testing Qualification Board
Local Area Network
Projects In Controlled Environments version 2
Risks, Assumptions, Issues & Dependencies
Route Cause Analysis
Rational Unified Process
Software Development Lifecycle
System Integration Testing
System(s) Under Test
Testing Maturity Model Integrated
Test Process Improvement
User Acceptance Testing
Virtual Private Network
Wide Area Network
Web Service Delivery Language
Extendable Markup Language
Quality Management System
Software engineering – Software product Quality Part 1
Software engineering – Software product Quality Part 2
Software engineering – Software product Quality Part 3
Software engineering – Software product Quality Part 4
Information Technology Software life cycle processes
Information Technology Software product evaluation
Information Technology System and software integrity levels
Application Lifecycle management system lifecycle processes
Application Lifecycle management software process assessment
Service Support Standards
Information security standard
Parts 1&2 Testing standards and test techniques.
The International standard of software testing.
Standard Computer Dictionary
Standard Glossary of software engineering terms
Software Quality Assurance Plans
Standard for test plans and test documentation.
Unit testing standard
Verification and validation standard
Software reviews standard
Classification of defect anomalies
Standard for Project Management
Open Security Web Application Project
Information System Examination Board (CTFL, CTIL,CTAL & CTPL) accreditation for software testing.
International Software Testing Qualifications Board (CTFL, CTIL,CTAL & CTPL) accreditation for software testing.
The version control of the document and various revisions.
The attribute used to sign off the document and approve the approach.
A list of resources which need to visibility the master test plan.
An overall view of the document and its purpose.
An introduction to the way the document is required and the project background. This attribute will also include test standards used and a reference to acronyms.
Scope of Testing
The functional test plan will include the scope of the test activities clearly delineating what will be out of scope and any limiting factors.
The test results at the end of testing detailing what has passed and what has failed.
A list of defects captured during the test or a reference to the defect tracking tool.
The list of criteria which forms the software acceptance.
Defect Disposition Plan
The plan of any defects which will be addressed in a future release of the software.
Any lessons learned during the project which could potentially improve future test engagements.
Commercial Of The Shelf