ISTQB Advanced Test Analyst 4. Testing Software Quality Characteristics

Get Started. It's Free
or sign up with your email address
Rocket clouds
ISTQB Advanced Test Analyst 4. Testing Software Quality Characteristics by Mind Map: ISTQB Advanced Test Analyst 4. Testing Software Quality Characteristics

1. Standards

1.1. ISO 25000

1.2. superseded ISO 9126

2. Functionality

2.1. Accuracy

2.1.1. Any Stage of Lifecycle

2.1.2. Functional accuracy involves testing the application's adherence to the specified or implied requirements and may also include computational accuracy.

2.1.3. targeted on incorrect handling of data or situations

2.2. suitability

2.2.1. Defects discovered=>system will not be able to meet the needs of the user

2.2.2. Suitability testing involves evaluating and validating the appropriateness of a set of functions for its intended specified tasks.

2.2.3. can be based on use cases

2.2.4. Lifecycle

2.2.4.1. system testing

2.2.4.2. later stages of integration testing

2.3. interoperability

2.3.1. Lifecycle

2.3.1.1. component integration testing

2.3.1.2. system testing

2.3.1.2.1. determine how well the fully developed system interacts with other systems

2.3.2. Techniques

2.3.2.1. decision tables

2.3.2.2. state transition diagrams

2.3.2.3. use cases

2.3.2.4. combinatorial testing

2.3.3. Typical defects

2.3.3.1. incorrect data exchange between interacting components

2.3.4. how software systems interact with each other?

2.3.5. Testing must cover all the intended target environments

2.3.6. focus

2.3.6.1. Usage of industry-wide communications standards

2.3.6.2. Is system adjust accordingly to the communications needs of the systems it interacts with?

2.4. compliance

2.5. Security

3. Reliability

3.1. maturity (robustness)

3.2. fault-tolerance

3.3. recoverability

3.4. compliance

4. Usability

4.1. Usability testing tests the ease by which users can use or learn to use the system to reach a specified goal in a specific context

4.2. Measuring:

4.2.1. Effectiveness

4.2.1.1. enable to achieve specified goals

4.2.2. Efficiency

4.2.3. Satisfaction

4.3. Sub-Characteristics

4.3.1. learnability

4.3.2. operability

4.3.3. attractiveness

4.3.4. compliance

4.3.5. Accessibility

4.3.5.1. the accessibility to software for those with particular needs or restrictions

4.3.5.2. Consider the relevant standards

4.3.5.2.1. Web Content Accessibility Guidelines

4.3.5.2.2. Disability Discrimination Acts

4.3.6. Understandability

4.4. Testing Steps

4.4.1. Formative Usability Testing

4.4.1.1. conducted iteratively during the design and prototyping stages to help guide (or "form")

4.4.2. Summative Usability Testing

4.4.2.1. conducted after implementation to measure the usability

4.5. Tester Skills

4.5.1. Sociology

4.5.2. Psychology

4.5.3. Conformance to national standards (including accessibility standards)

4.5.4. Ergonomics

4.6. Conducting surveys and questionnaires

4.6.1. SUMI (Software Usability Measurement Inventory)

4.6.2. WAMMI (Website Analysis and MeasureMent Inventory)

5. Efficiency

5.1. Performance (time behavior)

5.2. resource utilization

5.3. compliance

6. Maintainability

6.1. analyzability

6.2. changeability

6.3. stability

6.4. testability

6.5. compliance

7. Portability

7.1. adaptability

7.2. installability

7.3. co-existence

7.4. replaceability

7.5. compliance