Please enable JavaScript.
Coggle requires JavaScript to display documents.
K1: Remember (2.3.2 Non-functional Testing (Evaluates characteristics of…
K1: Remember
2.3.2 Non-functional Testing
Evaluates characteristics of systems and software such as
8.1 Usability, performance efficiency or security. :check:
“how well” the system behaves.
Can and often should be performed at all test levels, and done as early as possible.
The late discovery of non-functional defects
4.1 Can be extremely dangerous to the success of a project.
Black-box techniques
7.1 May be used to derive test conditions and test cases for nonfunctional testing.
The thoroughness of non-functional testing
10.1 Can be measured through non-functional coverage.
11 Non functional coverage
11.1 Is the extent to which some type of non-functional element has been exercised by tests, and is expressed as a percentage of the type(s) of element being covered.
Non-functional test design and execution
9.1 May involve special skills or knowledge, such as knowledge of the inherent weaknesses of a design or technology
2.1.2 Software Development Lifecycle Models in Context
Must be selected and adapted to
1.3 The context of project :check:
1.4 Product characteristics :check:
1.2 The project goal, :check:
1.5 The type of product :check:
1.6 Business priorities :check:
1.1 Identified
product
and project risks :check:
Reasons why must be adapted:
2.2 Difference in product risks of systems
2.3 Units can be part of a project or program
2.1 Short time to deliver a product to the market
Depending on the context of the project
3.1 To combine or reorganize test levels and/or test activities.
May be combined.
Chapter 2: Testing Throughout the Software Development Lifecycle :
FL-2.1.2 (K1) Identify reasons why software development lifecycle models must be adapted to the context of project and product characteristics