Object-Oriented Modeling and Design with UML¶
Blaha, M., Rumbaugh, J., Modeling, O., & Design with UML, 2. e. (2005). Object-Oriented Modeling and Design with UML. Prentice Hall.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Deadlock
- Identifies brittleness: systems thought to be robust can deadlock under specific interleaving of requests, revealing hidden assumptions about ordering or resource availability. Motivates design patterns: deadlock prevention strategies (lock ordering, no-hold-and-wait, timeouts) become explicit design decisions rather than afterthoughts, disciplining the system architecture. Enables proactive analysis: graph-based deadlock detection (wait-for graphs, resource allocation graphs) allows offline reasoning about which request patterns could deadlock. Supports recovery: deadlock avoidance or detection mechanisms enable systems to break cycles (abort a transaction, force release of a resource, timeout and retry) rather than hang indefinitely. Reveals coupling: deadlock is often a symptom of over-tight coupling between modules or agents; redesigning to reduce circular dependencies also improves modularity
This sourceFoundational OO modeling text by two of the originators of UML, covering design quality including coupling, cohesion, and modularity.
- Identifies brittleness: systems thought to be robust can deadlock under specific interleaving of requests, revealing hidden assumptions about ordering or resource availability. Motivates design patterns: deadlock prevention strategies (lock ordering, no-hold-and-wait, timeouts) become explicit design decisions rather than afterthoughts, disciplining the system architecture. Enables proactive analysis: graph-based deadlock detection (wait-for graphs, resource allocation graphs) allows offline reasoning about which request patterns could deadlock. Supports recovery: deadlock avoidance or detection mechanisms enable systems to break cycles (abort a transaction, force release of a resource, timeout and retry) rather than hang indefinitely. Reveals coupling: deadlock is often a symptom of over-tight coupling between modules or agents; redesigning to reduce circular dependencies also improves modularity
Domain-specific¶
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? Recorded for 1 of 2 citations of this work.
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 1 other way.
- https://books.google.com/books/about/Object_oriented_Modeling_and_Design_with.html?id=fYZQAAAAMAAJ ×1
Registry ID ref:9ad1380cdb82 · see in the full table