How to Break Software
E560746
"How to Break Software" is a practical software testing book that teaches systematic techniques for finding defects by thinking like an attacker of software systems.
All labels observed (2)
| Label | Occurrences |
|---|---|
| How to Break Software canonical | 1 |
| How to Break Software Security | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5996891 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: How to Break Software Context triple: [James Whittaker (software engineer), notableWork, How to Break Software]
-
A.
How To Become A Hacker
"How To Become A Hacker" is a widely read essay by Eric S. Raymond that explains hacker culture, ethics, and the skills and attitudes needed to participate in the open-source software community.
-
B.
SmartBear Software
SmartBear Software is a software company known for its tools that support API development, testing, and monitoring, including stewardship of the popular Swagger ecosystem.
-
C.
The Cathedral and the Bazaar
The Cathedral and the Bazaar is a highly influential essay and book on open-source software development that contrasts centralized, top-down programming models with decentralized, collaborative approaches.
-
D.
The Practice of Programming
The Practice of Programming is a widely respected book by Brian W. Kernighan and Rob Pike that teaches practical software development techniques, emphasizing clear code, debugging, testing, and performance.
-
E.
Working Effectively with Legacy Code
Working Effectively with Legacy Code is a widely respected software engineering book by Michael Feathers that teaches practical techniques for understanding, testing, and safely modifying existing codebases.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: How to Break Software Target entity description: "How to Break Software" is a practical software testing book that teaches systematic techniques for finding defects by thinking like an attacker of software systems.
-
A.
How To Become A Hacker
"How To Become A Hacker" is a widely read essay by Eric S. Raymond that explains hacker culture, ethics, and the skills and attitudes needed to participate in the open-source software community.
-
B.
SmartBear Software
SmartBear Software is a software company known for its tools that support API development, testing, and monitoring, including stewardship of the popular Swagger ecosystem.
-
C.
The Cathedral and the Bazaar
The Cathedral and the Bazaar is a highly influential essay and book on open-source software development that contrasts centralized, top-down programming models with decentralized, collaborative approaches.
-
D.
The Practice of Programming
The Practice of Programming is a widely respected book by Brian W. Kernighan and Rob Pike that teaches practical software development techniques, emphasizing clear code, debugging, testing, and performance.
-
E.
Working Effectively with Legacy Code
Working Effectively with Legacy Code is a widely respected software engineering book by Michael Feathers that teaches practical techniques for understanding, testing, and safely modifying existing codebases.
- F. None of above. chosen
Statements (41)
| Predicate | Object |
|---|---|
| instanceOf |
book
ⓘ
software testing book ⓘ |
| aimsAt |
quality assurance engineers
ⓘ
software developers ⓘ software testers ⓘ |
| approach |
systematic test case design
ⓘ
thinking like an attacker of software systems ⓘ |
| author | James A. Whittaker NERFINISHED ⓘ |
| contains |
checklists for defect discovery
ⓘ
practical testing examples ⓘ step-by-step test procedures ⓘ |
| countryOfPublication |
United States of America
ⓘ
surface form:
United States
|
| covers |
boundary testing concepts
ⓘ
common software failure modes ⓘ error guessing techniques ⓘ input domain testing ⓘ |
| emphasizes |
attacking software from the outside
ⓘ
systematic exploration of input space ⓘ test design over test execution ⓘ |
| field |
software engineering
ⓘ
software testing ⓘ |
| focusesOn |
attacker mindset in testing
ⓘ
defect discovery ⓘ practical software testing ⓘ |
| genre |
non-fiction
ⓘ
technical literature ⓘ |
| intendedOutcome |
earlier detection of software defects
ⓘ
higher software reliability ⓘ |
| language | English ⓘ |
| objective |
help readers find more bugs in less time
ⓘ
improve effectiveness of software testing ⓘ |
| publisher | Addison-Wesley NERFINISHED ⓘ |
| relatedWork | How to Break Software: A Practical Guide to Testing NERFINISHED ⓘ |
| teaches |
black-box testing techniques
ⓘ
systematic techniques for finding software defects ⓘ |
| topic |
defect-based testing
ⓘ
risk-based testing ⓘ test heuristics ⓘ |
| usedAs | reference for software testing courses ⓘ |
| usedBy |
practicing software testers
ⓘ
students of software engineering ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: How to Break Software Description of subject: "How to Break Software" is a practical software testing book that teaches systematic techniques for finding defects by thinking like an attacker of software systems.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
How to Break Software Security