Pages without language links

From CSSEMediaWiki
Jump to: navigation, search
Prefix 

Showing below up to 250 results starting with #1.

View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)

  1. 2005 Exam answers
  2. 2006 Exam answers
  3. 2007 Exam answers
  4. 2008 Exam answers
  5. 2009 frog design criticisms
  6. 2010 frog design criticisms
  7. 427 assessment
  8. 427 design standard
  9. A class should not depend on its users
  10. A froggy visitor
  11. About COSC427
  12. Abstract Factory
  13. Abstract class
  14. Abstract classes should be base classes
  15. Abstract vs Interface
  16. Abstraction
  17. Access levels
  18. Account setup
  19. Accountability
  20. Accountability Design
  21. Active record pattern
  22. Acyclic dependencies principle
  23. Adapter
  24. Add Parameter
  25. Advice from alumni
  26. Agent classes irrelevant
  27. Aggregation versus Composition
  28. Agile manifesto
  29. Agile methods
  30. Aidan's Design Study
  31. Alan Kay
  32. AlexsDesignStudy
  33. AlexsLibrary
  34. Alternative classes with different interfaces smell
  35. Alumni
  36. Amelioration patterns
  37. Analysis patterns
  38. Andrew Hunt 1999
  39. Anemic Domain Model
  40. Antipatterns
  41. Architectural patterns
  42. Are you gonna eat that
  43. Arthur Riel
  44. Arthur Riel 1996
  45. Association versus Dependency
  46. AudioSystems
  47. Automation
  48. Avoid accidental multiple inheritance
  49. Avoid becomes
  50. Avoid concrete base classes
  51. Avoid downcasting
  52. Avoid equals
  53. Avoid god classes
  54. Avoid inheritance for implementation
  55. Avoid inheritance for optional containment
  56. Avoid interface bloat
  57. Avoid interface pollution
  58. Avoid mixing inputs and outputs
  59. Avoid multiple inheritance
  60. Avoid no-op overrides
  61. Avoid protected data
  62. Avoid side effects
  63. Avoid verb classes
  64. Barbara Liskov
  65. BaseBean
  66. Becomes problem
  67. Behavioral completeness
  68. Benjamin's Design Study
  69. BenjaminTaylor Previous Design Work
  70. Bertrand's Design Study
  71. Bertrand Meyer
  72. Beware accessors
  73. Beware inheritance over composition
  74. Beware of many accessors
  75. Beware of non-communicating methods
  76. Beware singletons
  77. Beware type switches
  78. Beware value switches
  79. Big ball of mud
  80. Big design up front
  81. Blackboard System
  82. Boat anchor
  83. Bob Martin
  84. Bob Martin's heuristics
  85. Bob Martin's principles
  86. BrettWardsDesignStudy
  87. Bridge
  88. Builder
  89. CLU
  90. Call super
  91. Cay Horstmann 2006
  92. Chain of Responsibility
  93. Change Reference to Value
  94. Change Unidirectional Association to Bidirectional
  95. Change Value to Reference
  96. Christopher Alexander
  97. Christopher Alexander 1977
  98. Christopher Alexander 1979
  99. Circle-ellipse problem
  100. Circular dependency
  101. Citation needed
  102. Class Encapsulation
  103. Class diagram
  104. Class hierarchies should be deep and narrow
  105. Class versus Object
  106. Code smells
  107. Collapse Hierarchy
  108. Collecting Parameter
  109. Combining design patterns
  110. Command
  111. Command query separation
  112. Comments and suggestions
  113. Comments smell
  114. Common closure principle
  115. Common reuse principle
  116. Component versus Module
  117. Composite
  118. Constant interface
  119. Contain contents not parents
  120. Contained objects should not use each other
  121. Containment implies uses
  122. Copy Constructor vs the Encapsulation Boundary
  123. Coupling and cohesion
  124. Cut and paste programming
  125. DMA Design Project
  126. DMA Design Project - Source Code
  127. DMA Design Project - first submission
  128. DMA Design Project first draft
  129. Data class smell
  130. Data clumps smell
  131. Data mapper pattern
  132. David Parnas
  133. Decomposition
  134. Decorator
  135. Defer identification of state variables pattern
  136. Define classes by behavior, not state pattern
  137. Define default values via explicit protocol pattern
  138. Delegation
  139. Dependency injection
  140. Dependency inversion principle
  141. Design Project
  142. Design by contract
  143. Design examples
  144. Design maxims
  145. Design maxims Equivalence
  146. Design patterns
  147. Design patterns break rules
  148. Designfest
  149. Diamond Problem
  150. Different Design
  151. Distribute system intelligence
  152. Divergent change smell
  153. Do not change the state of an object without going through its public interface
  154. Do the simplest thing that could possibly work
  155. Documenting Patterns
  156. Domain model pattern
  157. Don't burn your base class
  158. Don't expose mutable attributes
  159. Don't repeat yourself
  160. Double Dispatch
  161. Duplicate Observed Data
  162. Duplicate code smell
  163. Editing Tips
  164. Eliminate case analysis
  165. Eliminate irrelevant classes
  166. Empty method over-rides
  167. Encapsulate Collection
  168. Encapsulate Downcast
  169. Encapsulate Field
  170. Encapsulate concrete state pattern
  171. Encapsulate that which varies
  172. Encapsulation
  173. Encapsulation boundary
  174. Encapsulation is hierarchical
  175. Enum idiom
  176. Equals vs the Encapsulation Boundary
  177. Erich Gamma
  178. Establishing priorities
  179. Exam Quick Reference
  180. Exam questions
  181. Extensibility
  182. Extract Class
  183. Extract Hierarchy
  184. Extract Interface
  185. Extract Method
  186. Extract Subclass
  187. Extract Superclass
  188. Extreme programming
  189. Facade
  190. Factor implementation differences into subcomponents
  191. Factory Method
  192. Fat interfaces
  193. Favor composition over inheritance
  194. Favour containment over association
  195. Favour deep hierarchies
  196. Feature envy smell
  197. Flyweight
  198. Frogs design
  199. Frogs second design
  200. Front controller pattern
  201. Functional decomposition
  202. Gang of Four
  203. Gang of Four 1995
  204. GenA: A Genetic Algorithms Framework
  205. GenericGuidelines
  206. Getter and setter policy
  207. Getters and setters
  208. God object
  209. Goto considered harmful
  210. Greg Searle's captains log star date
  211. Greg Searle's design
  212. Greg Searle's project blackjack
  213. Guitar Amplifier Design
  214. Guitar Tutor Design
  215. Guitar Tutor Report
  216. Hall of fame
  217. Have courage
  218. Hide Delegate
  219. Hide Method
  220. Hide data within its class
  221. Hide your decisions
  222. Hierarchical Model View Controller
  223. Hillside Group
  224. HistoryCrumbs.user.js
  225. How to assess
  226. Identify message layers pattern
  227. Identity map pattern
  228. Idioms
  229. If it ain't broke don't fix it
  230. Immutable object
  231. Impedance mismatch
  232. Implement behavior with abstract state pattern
  233. Inappropriate intimacy smell
  234. Incomplete library class smell
  235. Information hiding
  236. Inheritance
  237. Inheritance for specialization
  238. Inline Class
  239. Inline Method
  240. Inline Temp
  241. Instance
  242. Intelligent children pattern
  243. Interface
  244. Interface segregation principle
  245. Interface should be dependent on model
  246. Interpreter
  247. Introduce Explaining Variable
  248. Introduce Foreign Method
  249. Introduce Local Extension
  250. Introduce Null Object

View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)

Views
Personal tools
Toolbox