Design patterns
Lasater, Christopher G · CERN Document Server (European Organization for Nuclear Research) · 2007
Cited by 0
Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 10,000 papers for “design patterns”
Lasater, Christopher G · CERN Document Server (European Organization for Nuclear Research) · 2007
Cited by 0
eXamen.press · 2008
Cited by 0
Owen Astrachan, Garrett Mitchener, Geoffrey Berry et al. · ACM SIGCSE Bulletin · 1998
The field of software patterns has seen an explosion in interest in the last three years. Work to date has been on the recognition, cataloging, and finding of patterns with little attention to the use of patterns, especially by students and practitioners not well-versed in object-oriented technologies. This project addresses pattern use through the development of several programming and pedagogical frameworks that supply support for using patterns throughout a computer science curriculum. Although we do not claim that patterns are Brooks' silver bullet [10], their use can help cope with the accidental complexity of software development and, we argue, their use is essential for a successful adoption of object-oriented techniques in academic computer science programs. This project addresses practical concerns of the computer science and software engineering communities in using, teaching, and learning patterns. In this paper we argue that patterns are an essential programming and pedagogical tool and report on our work in making them accessible to the educational community.
Cited by 36
Zhenyu Cheryl Qian · 2007
No abstract available.
Cited by 4
Adriana, Wilde · EdShare Southampton (University of Southampton) · 2017
Cited by 0
Anil Kumar Rangisetti · Apress eBooks · 2024
You have learned important OOP concepts such as encapsulation, data hiding, inheritance, and polymorphism for handling software development challenges. This chapter introduces the design patterns and how they are useful to identify general solutions for common software development problems.
Cited by 0
Shane Sendall Swiss, Shane Sendall · 2007
this paper, I address these questions by offering a means to judge the quality of examples for teaching design patterns: a list of desirable characteristics. The proposed list can be used to gauge the quality of examples and/or it can be used to guide the development of examples
Cited by 0
Ruben Leivas Ledo; Brice Copy · CERN Document Server (European Organization for Nuclear Research) · 2005
Cited by 0
Kevin Lano, José Luiz Fiadeiro, Luís Andrade · 2002
Design patterns are standard design structures which have been found to be useful in many different applications. They therefore provide a set of ready-made solutions to design problems which are encountered in software development, and a repertoire of building blocks for software design. This chapter gives a brief history of software design patterns and their role and purpose. Java examples of the most frequently used patterns: the State, Template Method, Observer, Visitor, Iterator, Mediator and Proxy patterns are defined, and a list of all widely used design patterns, with a brief description of each, is also included.
Cited by 0
University of Salford Institutional Repository (University of Salford) · 2014
Cited by 0
Cited by 0
x · Zenodo (CERN European Organization for Nuclear Research) · 2025
Cited by 0Open access
Adam L. Davis · Apress eBooks · 2016
In object-oriented programming (OOP), design patterns are useful organizations of state and behavior that make your code more readable, testable, and extensible.
Cited by 0
Buddy James, Lori Lalonde · Apress eBooks · 2015
A design pattern in programming is the equivalent of a recipe in cooking. Can you make chocolate chip cookies without following a recipe? Of course, you can. However, you will be investing a lot of time and effort into trying to solve an issue that’s already been solved. You will basically reinvent the wheel, we mean, the cookie.
Cited by 0
John F. Dooley, Vera A. Kazakova · Apress eBooks · 2024
Do you reinvent the wheel each time you write code? Do you have to relearn how to iterate through an array every time you write a program? Do you have to reinvent how to fix a dangling else in every if statement you write? Do you need to relearn insertion sort or binary search every time you want to use them? Of course not!
Cited by 0
Petraq J. Papajorgji, Panos M. Pardalos · RePEc: Research Papers in Economics
Abstract Well before software engineers started using patterns, design patterns an architect named Christopher Alexander wrote two books that describe the use of patterns in building architecture and urban planning. The first book is titled A Pattern Language: Towns, Buildings, Construction, [3], published in 1977 and the second one is titled The Timeless Way of Building, [4], published in 1979. These two books not only changed the way structures were built, but they had a significant impact in another not closely related field, the field of software engineering.
Cited by 0
Jason Lee Hodges · Apress eBooks · 2019
The primary theme in software engineering is that of reuse over reiteration. You’ve seen this several times in this book already with the concepts of abstraction, modularity, inheritance, data structures, and algorithms. This same concept can be applied to software design. Design patterns are a set of best practices to use when encountering a specific problem in object-oriented software design. Similar to algorithms, these are proven solutions that should be reused in similar scenarios rather than being rewritten or rediscovered. Unlike algorithms, design patterns are typically not measured in terms of time complexity because their focus pertains more to writing code that can be easily understood, maintained, and decoupled from other parts of the code base.
Cited by 4
Christoph Denzler, Dominik Gruntz · 2008
In computer science curricula the two areas programming and software engineering are usually separated. In programming students learn an object oriented language and then deepen their knowledge in other languages, algorithms and data structures. On the other hand software engineering starts with discussing processes and then addresses topics like requirements engineering, software design and software architectures.
Cited by 6
Kenneth Barclay, John Savage · Elsevier eBooks · 2004
Cited by 0
Apress eBooks · 2006
Now that you’ve read about OOP concepts and best practices, and you’ve seen OOP applied within some ActionScript 2.0 examples, it’s time to get more involved and look at troubleshooting your code and making it more efficient. This is where design patterns come in.
Cited by 0