Object-Oriented Modeling and Design with UML¶
Blaha, M., James Rumbaugh, O. M., & 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¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. 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