Wikipedia:Articles for deletion/Pattern-Oriented Software Architecture

The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.

The result was keep‎. (non-admin closure) — Benison (Beni · talk) 17:57, 24 December 2024 (UTC)[reply]

Pattern-Oriented Software Architecture

[Hide this box] New to Articles for deletion (AfD)? Read these primers!

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

Article does not comply with MOS and there are no references cited. Se7enNationArmy2024 (talk) 17:36, 17 December 2024 (UTC)[reply]

Note: This discussion has been included in the list of Literature-related deletion discussions. Shellwood (talk) 17:48, 17 December 2024 (UTC)[reply]
Note: This discussion has been included in the deletion sorting lists for the following topics: Engineering, Computing, and Software. WCQuidditch ☎ ✎ 20:15, 17 December 2024 (UTC)[reply]

Keep per the significant coverage in multiple independent reliable sources. Wikipedia:Notability (books)#Criteria says:
A book is presumed notable if it verifiably meets, through reliable sources, at least one of the following criteria:
1. The book has been the subject of two or more non-trivial published works appearing in sources that are independent of the book itself. This can include published works in all forms, such as newspaper articles, other books, television documentaries, bestseller lists, and reviews. This excludes media re-prints of press releases, flap copy, or other publications where the author, its publisher, agent, or other self-interested parties advertise or speak about the book.
Sources
1. DeLano, David E. (December 1996). "C++ Report book review of Pattern-Oriented Software Architecture: A System of Patterns". In Rising, Linda (ed.). The Patterns Handbook: Techniques, Strategies, and Applications. Cambridge: Cambridge University Press. pp. 518–521. ISBN 0-521-64818-1. Retrieved 2024-12-22 – via Internet Archive.
  The book's appendix excerpts the entire review of Pattern-Oriented Software Architecture: A System of Patterns written by David E. DeLano in C++ Report in December 1996. The book review notes: "If I have anything negative to say about the book, it is that some of the language and grammar usage feels awkward to the reader. Early versions of the patterns reviewed on the World Wide Web suffered in the use of the language and grammar, but subsequent editing has fixed most of the readability problems. Some portions of the narrative text suffer some of the same stiffness and flow problems, but the importance of the content causes the reader to overlook the style issues. Overall this text is good and I recommend it as an addition to any collection of books on patterns. It also serves as good reading for those interested in topics on software development. As stated earlier in this review, this text should be viewed as a supplement, not a replacement, for existing pattern literature."
2. Glassborow, Francis (October 2000). "Review: Pattern-Oriented Software Architecture". ACCU. Archived from the original on 2024-12-22. Retrieved 2024-12-22.
  The review notes: "The main material is proceeded by an introductory chapter putting it into perspective. The book concludes with two chapters. The first of these is on using patterns as a whole. The final chapter looks at what has happened in the pattern movement since the publication of the first volume and takes a brief look ahead. ... If you understand this and have sufficient experience to be responsible for large-scale design then you should add this book to your library, after having read it once. This book is one of the more important contributions to the literature on 'patterns' and deserves to become a standard text on its specified area of interest."
3. Graham, Ian (October 1997). "Pattern-oriented software architecture (Book Review)". Journal of Object-Oriented Programming. 10 (6): 75–76. ISSN 0896-8438. EBSCOhost 500514125.
4. Murali, D. (2005-06-06). "Control is the key to the Net". Business Line. Factiva BSNLNE0020050605e16600021. Archived from the original on 2024-12-22. Retrieved 2024-12-22.
  The article notes: "Another heavy-duty book for the week is Pattern-Oriented Software Architecture, Volume 3 which is on 'patterns for resource management'. It has been written by Michael Kircher and Prashant Jain, and published by Wiley Dreamtech (www.wileydreamtech.com), bringing down the Indian price to about a tenth of the original US tag. First, a definition of 'resource'. It is an entity that is available in limited supply as for instance "memory synchronisation primitives file handles network connections security tokens and database sessions. "Identifying resource can be challenging, point out the authors. "Very often, the non-functional requirements of a piece of software such as performance scalability flexibility stability security and quality of service depend heavily on efficient resource management."Where do patterns come in? They help capture best practice in solving problems in almost every domain, explain Kircher and Jain. ... A pattern is called Lazy Acquisition, I learn, though I'm too lazy to find out what it does. As for the book, however the pattern I'd suggest software guys and gals to follow is 'eager acquisition'."
5. Less significant coverage:
  1. Linthicum, David S. (1997-10-01). "Patterns demystified. (integrating patterns into software development cycles) (Application Architect) (Technology Tutorial)(Column)". DMBS. Vol. 10, no. 11. M&T Publishing. ISSN 1041-5173. Factiva dbms000020011006dta10005t.
    The article provides two sentences of coverage about the subject. The article notes: "However, the best book on patterns for application architects is Pattern-Oriented Software Architecture (John Wiley & Sons, 1996) by Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal. (It served as a reference for me for this column, by the way.)"
  2. Bansiya, Jagdish (1998-06-01). "Automating design-pattern identification: DP++ is a tool for C++ programs. (Technology Tutorial)(Tutorial)". Dr. Dobb's Journal. Vol. 23, no. 6. Factiva dobb000020010916du6100022.
    The article provides one sentence of coverage about the subject. The article notes: "While several popular design patterns have been catalogued and described by the GoF in Design Patterns, Frank Buschmann's Pattern-Oriented Software Architecture. A System of Patterns (John Wiley & Sons, 1996), and other books, most designers are not aware of these pattern solutions."
  3. Yang, Bin (2001-05-01). "E++: A pattern language for Java Internet applications, Part 1; Weaving the design patterns together". JavaWorld. Factiva javw000020010711dx510001c.
    The article notes: " Contains many interesting architecture and design patterns:Pattern-Oriented Software Architecture A system of Patterns, F. Buschmann, et al. (New York: John Wiley & Sons, 1996)"
  4. Clemente, Paul (July 2005). "Comparing the SEI's Views and Beyond Approach for Documenting Software Architecture with ANSI-IEEE 1471-2000". Software Engineering Institute. Retrieved 2024-12-22 – via Internet Archive.
    The article notes: "Patterns are published in the literature; perhaps the best-known catalog of architectural patterns is the twovolume set Pattern-Oriented Software Architecture [Buschmann 96, Schmidt 00]."
There is sufficient coverage in reliable sources to allow Pattern-Oriented Software Architecture to pass Wikipedia:Notability#General notability guideline, which requires "significant coverage in reliable sources that are independent of the subject".
Cunard (talk) 10:13, 22 December 2024 (UTC)[reply]

Keep per Cunard. That’s enough for GNG and NBOOK. That the article is oddly written is not a reason for deletion. PARAKANYAA (talk) 02:05, 24 December 2024 (UTC)[reply]

The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.