Using Design Patterns to Develop Reusable Object-Oriented Communication Software (1995)
Cached
Download Links
- [www.compapp.dcu.ie]
- [www.computing.dcu.ie]
- DBLP
Other Repositories/Bibliography
| Citations: | 53 - 0 self |
BibTeX
@MISC{Schmidt95usingdesign,
author = {Douglas C. Schmidt},
title = {Using Design Patterns to Develop Reusable Object-Oriented Communication Software},
year = {1995}
}
Years of Citing Articles
Bookmark
 |
 |
 |
 |
 |
 |
OpenURL
Abstract
Factory, and Singleton). Tactical patterns have a relatively localized impact on a software architecture. For instance, the Iterator pattern [7] allows elements in a collection to be accessed sequentially without violating data encapsulation. Although this pattern is widely applicable, the problem it addresses does not have sweeping architectural implications. In contrast, strategic design patterns have an extensive impact on the software architecture for solutions in a particular domain. For example, the HalfSync /Half-Async pattern [15] decouples synchronous I/O from asynchronous I/O in a system to simplify concurrent programming effort without degrading execution efficiency. This pattern greatly simplifies synchronization strategies in complex concurrent systems (such as BSD Unix). We focused most of our energy on documenting patterns related to our domain (communication software), and we reused existing tactical patterns rather than reinventing them. Focusing on strategic domain p...
