All pages
From CSSEMediaWiki
Jump to:
navigation
,
search
All pages
Display pages starting at:
Display pages ending at:
Namespace:
(Main)
Talk
User
User talk
CSSEMediaWiki
CSSEMediaWiki talk
File
File talk
MediaWiki
MediaWiki talk
Template
Template talk
Help
Help talk
Category
Category talk
All pages
|
Previous page (2005 Exam answers)
2005 Exam answers
2006 Exam answers
2007 Exam answers
2008 Exam answers
2009 frog design criticisms
2010 frog design criticisms
427 assessment
427 design standard
A Genetic Algorithms Framework
A class should not depend on its users
A froggy visitor
About COSC427
Abstract Factory
Abstract Factory pattern
Abstract class
Abstract classes should be base classes
Abstract vs Interface
Abstraction
Access levels
Account setup
Accountability
Accountability Design
Active record pattern
Acyclic dependencies principle
Adapter
Add Parameter
Advice from alumni
Agent classes irrelevant
Aggregation versus Composition
Agile manifesto
Agile methods
Aidan's Design Study
Alan Kay
AlexsDesignStudy
AlexsLibrary
Alternative classes with different interfaces smell
Alumni
Amelioration patterns
Analysis Patterns
Analysis patterns
Andrew Hunt 1999
Anemic Domain Model
Anti patterns
Antipatterns
Architectural patterns
Are you gonna eat that
Arthur Riel
Arthur Riel 1996
Association versus Dependency
AudioSystems
Automation
Avoid accidental multiple inheritance
Avoid becomes
Avoid concrete base classes
Avoid downcasting
Avoid equals
Avoid god classes
Avoid inheritance for implementation
Avoid inheritance for optional containment
Avoid interface bloat
Avoid interface pollution
Avoid mixing inputs and outputs
Avoid multiple inheritance
Avoid no-op overrides
Avoid protected data
Avoid side effects
Avoid verb classes
Barbara Liskov
BaseBean
Becomes problem
Behavioral completeness
Benjamin's Design Study
BenjaminTaylor Previous Design Work
Bertrand's Design Study
Bertrand Meyer
Beware accessors
Beware inheritance over composition
Beware of many accessors
Beware of non-communicating methods
Beware singletons
Beware type switches
Beware value switches
Big ball of mud
Big design up front
Blackboard System
Boat anchor
Bob Martin
Bob Martin's heuristics
Bob Martin's principles
BrettWardsDesignStudy
Bridge
Builder
CLU
CQS
Call super
Cay Horstmann 2006
Chain of Responsibility
Change Reference to Value
Change Unidirectional Association to Bidirectional
Change Value to Reference
Christopher Alexander
Christopher Alexander 1977
Christopher Alexander 1979
Circle-ellipse problem
Circular dependency
Citation needed
Class Encapsulation
Class diagram
Class hierarchies should be deep and narrow
Class versus Object
Code smell 1 - Duplicate Code
Code smells
Collapse Hierarchy
Collecting Parameter
Combining design patterns
Command
Command query separation
Comments and suggestions
Comments smell
Common closure principle
Common reuse principle
Component versus Module
Composite
Composite pattern
Constant interface
Contain contents not parents
Contained objects should not use each other
Containment implies uses
Copy Constructor vs the Encapsulation Boundary
Coupling
Coupling and cohesion
Course assessment
Cut and paste programming
DBC
DMA Design Project
DMA Design Project - Source Code
DMA Design Project - first submission
DMA Design Project first draft
DTSTTCPW
Data class smell
Data clumps smell
Data mapper pattern
David Parnas
Decomposition
Decorator
Decorator pattern
Defer identification of state variables pattern
Define classes by behavior, not state pattern
Define default values via explicit protocol pattern
Delegation
Dependency injection
Dependency inversion principle
Design Patterns
Design Project
Design by contract
Design examples
Design maxims
Design maxims Equivalence
Design patterns
Design patterns break rules
Design smells
Design study
Designfest
Diamond Problem
Different Design
Distribute system intelligence
Divergent change smell
Do not change the state of an object without going through its public interface
Do the simplest thing that could possibly work
Documenting Patterns
Domain model pattern
Don't burn your base class
Don't expose mutable attributes
Don't repeat yourself
Double Dispatch
Double dispatch
Duplicate Code Smell
Duplicate Observed Data
Duplicate code smell
EXtreme Programming
EXtreme programming
Editing Tips
Eliminate case analysis
Eliminate irrelevant classes
Empty method over-rides
Encapsulate Collection
Encapsulate Downcast
Encapsulate Field
Encapsulate concrete state pattern
Encapsulate that which varies
Encapsulation
Encapsulation boundary
Encapsulation is hierarchical
Enum Idiom
Enum idiom
Equals vs the Encapsulation Boundary
Erich Gamma
Establishing priorities
Exam Quick Reference
Exam questions
Extensibility
Extract Class
Extract Hierarchy
Extract Interface
Extract Method
Extract Subclass
Extract Superclass
Extract class
Extreme programming
Facade
Factor implementation differences into subcomponents
Factory Method
Factory Method pattern
Fat interfaces
Favor composition over inheritance
Favour composition over inheritance
Favour containment over association
Favour deep hierarchies
Feature envy smell
Flyweight
Flyweight pattern
Frogs design
Frogs second design
Front controller pattern
Functional decomposition
Gang Of Four 1995
Gang of Four
Gang of Four 1995
Gang of four
GenA: A Genetic Algorithms Framework
Generalisation
GenericGuidelines
Getter and setter policy
Getters and setters
God class
God object
Goto considered harmful
Greg Searle's Captains Log Star Date
Greg Searle's Design
Greg Searle's Project Blackjack
Greg Searle's captains log star date
Greg Searle's design
Greg Searle's project blackjack
Guitar Amplifier Design
Guitar Tutor Design
Guitar Tutor Report
Hall of fame
Have courage
Hello there this is a test
Hide Delegate
Hide Method
Hide data within its class
Hide your decisions
Hierarchical Model View Controller
Hillside Group
HistoryCrumbs.user.js
How to assess
Identify message layers pattern
Identity map pattern
Idioms
If it ain't broke don't fix it
Immutable object
Impedance mismatch
Implement behavior with abstract state pattern
Inappropriate intimacy smell
Incomplete library class smell
Information hiding
Inheritance
Inheritance for implementation
Inheritance for specialization
Inline Class
Inline Method
Inline Temp
Instance
Intelligent children
Intelligent children pattern
Interface
Interface segregation principle
Interface should be dependent on model
Interpreter
Introduce Explaining Variable
Introduce Foreign Method
Introduce Local Extension
Introduce Null Object
Introduce Parameter Object
Introduce common base class
Introduce common data class
Introduction to the Terrain Renderer
Inventory and Accounting
Inversion of control
Iterator
Iterator pattern
JITAS Design Study
JUnit
James Ashford Design Study
James Ashford Log
Janina's Design Study
Jason's Useful Links Page
Java Collections Framework
Jenny Harlow
Jim Coplien
Joey's design study
Joff's Place
JoffreHorlor
John Hofman's Design Study
John Hofman's Log
John Hofman US001
Johnson and Foote's heuristics
Johnson and Foote 1988
Jojo's 2008 Design Study
Jojo's 2009 Design Study
Jojo's OO Design Project Log
Joshua Bloch
Joshua Bloch 2006 Bumper Sticker API Design
Jumble
Keep accessors and mutators separate
Keep it simple
Keep it simple, stupid
Keep last years stuff
Keep related data and behavior in one place
Ken Auer
Ken Auer 1995
Kent Beck
Kent Beck 2003
Kris's Design Study
Kris's Project Log
LSP
Language Spectrum
Large class smell
Law of Demeter
Law of demeter
Law of leaky abstractions
Lazy class smell
Lazy initialization
Lazy load pattern
Lecture sequence
Lecture times
Limit compositions in a class
Limit hierarchy depth
Liskov substitution principle
List of OO Languages
Long method smell
Long parameter list smell
LukasKorsikaDesignStudy
MVC
Previous page (2005 Exam answers)
Views
Special page
Personal tools
Log in / create account
Navigation
Main page
Community portal
Current events
Recent changes
Random page
Help
Search
Toolbox
Special pages