Software patterns

Communications of the ACMPublished 1 October 1996

Douglas C. Schmidt, Mohamed E. Fayad, Ralph E. Johnson

DOI10.1145/236156.236164

Source URL

Citations152

SJR quartileQ1

SJR score1.15

SNIP3.34

Abstract

article Free Access Share on Software patterns Authors: Douglas C. Schmidt Computer Science at Washington University, St. Louis, Mo. Computer Science at Washington University, St. Louis, Mo.View Profile , Mohamed Fayad University of Nevada, Reno University of Nevada, RenoView Profile , Ralph E. Johnson Computer Science department, University of Illinois at Urbana-Champaign Computer Science department, University of Illinois at Urbana-ChampaignView Profile Authors Info & Claims Communications of the ACMVolume 39Issue 10Oct. 1996 pp 37–39https://doi.org/10.1145/236156.236164Published:01 October 1996Publication History 94citation2,542DownloadsMetricsTotal Citations94Total Downloads2,542Last 12 Months183Last 6 weeks14 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

Keywords

Computer Science

Design Patterns: Elements of Reusable Object-Oriented Software

21,864 Citations1994Erich Gamma, Richard F. Helm +2 more

The book is an introduction to the idea of design patterns in software engineering, and a catalog of twenty-three common patterns, which most experienced OOP designers will find out they've known about patterns all along.

Pattern-oriented Software Architecture: A System of Patterns

2,998 Citations1996Frank Buschmann

IEEE Transactions on Software EngineeringEmpirical Studies of Programming Knowledge

868 Citations1984Elliot Soloway, Kate Ehrlich

Two empirical studies attempt to evaluate the hypothesis that expert programmers have and use two types of programming knowledge: programming plans, which are generic program fragments that represent stereotypic action sequences in programming, and rules of programming discourse, which capture the conventions in programming and govern the composition of the plans into programs.

IEEE Transactions on Software EngineeringThe Role of Domain Expenence in Software Design

391 Citations1985Beth Adelson, Elliot Soloway

The knowledge and skills that were central to each of the above contexts are described and discussed and the functional utility of each is discussed.

Communications of the ACMObject-oriented patterns

353 Citations1992Peter Coad

Object-oriented analysis and object-oriented design rely on classes and objects as the lowest level building blocks to form patterns with specific relationships between them, which standardize small piecework into a larger unit and become building blocks for program design and construction.

Communications of the ACMThe case for case studies of programming problems

297 Citations1992Marcia C. Linn, Michael Clancy

The authors' case studies explain and defend the decisions made by an expert to produce a solution to the problem at hand, and contrast effective and ineffective strategies for solving this problem and related problems.

View PDF

Communications of the ACMUsing design patterns to develop reusable object-oriented communication software

189 Citations1995Douglas C. Schmidt

It is often hard to directly reuse existing algorithms, detailed designs, interfaces, or implementations in these systems due to the growing heterogeneity of hardware/software architectures and the increasing diversity of operating system platforms.

View PDF

Cognitive issues in reusing software artifacts

42 Citations1989Bruce Curtis

Theory and Practice of Object SystemsA family of design patterns for application‐level gateways

42 Citations1996Douglas C. Schmidt

The primary contribution of this paper is to describe a family of design patterns that underly many object-oriented communication software systems and illustrates how knowledge of the relationships and trade-offs among patterns helps guide the construction of reusable communication software frameworks.