Product
Capabilities
Requirements
Implicit
Explicit
Examples
Other Specifications
Failure Modes
Internal/External
Anticipated/Unexpected
Realistic/Provoked
Challenge the fault tolerance
Models
Ex: SFDPOT from HTSM
Data
CRUD
Easy / Tricky Data
Dependencies
Surroundings
Hardware
OS
Applications
Configurations
Lanuguages
White Box
Design
Code
Product History
Error Catalogue
Document RCA
Older versions can be used as Oracles
Rumors
Actual Software
Technologies
Competitors
Business
Purpose
Business Objectives
Big Picture
Product Vision
Product Image
Business Knowledge
Legal Aspects
Team
Creative Ideas
Lateral thinking techniques
Six thinking hats
Random stimulation
Google Goggles
Internal Collections
Product specific quick tests
You
Experience
Skills
Knowledge & Familiarity
External
Public Collections
400 Software Error Book
Testing Cheat Sheet
Standards
References
Ex: Atlas for a geographic products
Searching
Power Searching with Google
Project
Project Background
Information Objectives
Implicit
Explicit
Project Risks
Prioritize based on Risks
Test Artifacts
Beta testing reports
3rd party test reports
Debt
Project Debt
Managerial Debt
Technical Debt
Software Debt
Testing Debt
Map your test ideas against these
Conversations
Informal
Mention in Passing (MIPs)
Context Analysis
Market Forces
Project Drivers
Many Deliverables
Executable
Installation Kit
Release Notes
Read me
Training material
Demos
Code
Help
Tools
Stakeholders
Quality Characterstics
Capability
Reliability
Usability
Charisma
Security
Performance
IT-bility
Installability
Maintainibility
Supportability
Compatibility
Testability
Portability
Product Fears
Loss of Image
Wrong Decisions
Damage
People won't like the software
Usage Scenarios
Field Information
Customer Environment
Users
Different Personas
Mindmap By: Rahul Parwal
Credits: Rikard Edgren, Little Black Book on Test Design