Agile Software Development¶
Martin, R. C. (2002). Agile Software Development: Principles, Patterns, and Practices. Prentice Hall.
Retired. This is not a bibliographic entry. Our extractor captured an inline prose definition from an article and stored it as a work. The concept is real; this registry record is a parsing defect. This entry is kept so the citations that pointed at it still resolve, and so the correction is visible rather than silent.
Cited by¶
6 citations across 6 artifacts.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Interface segregation principle
- The Interface Segregation Principle (ISP) — one of Robert Martin's SOLID principles — holds that clients should not be forced to depend on interface methods they do not use
This sourceThe chapter-length statement of ISP - clients should not be forced to depend upon interfaces they do not use - alongside the four other design principles later gathered under the SOLID acronym. The chapter-length treatment of ISP - ch. 12, 'ISP: The Interface-Segregation Principle' - in Martin's 2002 collection of his design principles.
SupportedVerified against the source
- The Interface Segregation Principle (ISP) — one of Robert Martin's SOLID principles — holds that clients should not be forced to depend on interface methods they do not use
- Liskov Substitution Principle
- LSP is the L in the SOLID design principles and grounds the practical interventions of preferring composition over inheritance, interface-based hierarchies over implementation inheritance, and design-by-contract assertions (formalised in Bertrand Meyer's Eiffel and in Java's JML) that make the contract explicit enough to check
This sourceMartin's principles book, whose Part II presents LSP alongside SRP, OCP, DIP and ISP and whose inheritance-versus-delegation chapter grounds the composition-over-inheritance intervention; the SOLID acronym and the JML half are later and elsewhere.
Supported in partVerified against the source
- LSP is the L in the SOLID design principles and grounds the practical interventions of preferring composition over inheritance, interface-based hierarchies over implementation inheritance, and design-by-contract assertions (formalised in Bertrand Meyer's Eiffel and in Java's JML) that make the contract explicit enough to check
- Single-Responsibility Principle
Mechanisms¶
- Dependency Constraint Check
- The rule it leans on is the acyclic dependencies principle.
This sourceStates the Acyclic Dependencies Principle as allowing no cycles in the package-dependency graph.
- The rule it leans on is the acyclic dependencies principle.
- Dependency Injection or Adapter Substitution
- The corrective is the dependency inversion principle, which says depend on abstractions where volatility warrants it, not that all dependencies must be abstracted.
This sourceIdentifies the dependency-inversion principle while cautioning that not all dependencies must be abstracted.
- The corrective is the dependency inversion principle, which says depend on abstractions where volatility warrants it, not that all dependencies must be abstracted.
- Dependency Inversion
- It is a codified principle, the "D" of the SOLID set, and the same structure underlies ports-and-adapters (hexagonal) architecture.
This sourceCodifies dependency inversion as a named object-oriented design principle.
- It is a codified principle, the "D" of the SOLID set, and the same structure underlies ports-and-adapters (hexagonal) architecture.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 3 of 6 citations: 1 supported, 2 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 3 other ways.
- https://books.google.com/books/about/Agile_Software_Development.html?id=Ak8OtwAACAAJ ×1
- https://search.worldcat.org/title/Agile-software-development-principles-patterns-and-practices/oclc/47927527 ×1
- https://www.informit.com/store/agile-software-development-principles-patterns-and-9780135974445 ×1
Registry ID ref:d52685252052 · see in the full table