Uncategorized pages
From CSSEMediaWiki
Showing below up to 362 results starting with #1.
View (previous 500 | next 500) (20 | 50 | 100 | 250 | 500)
- 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 froggy visitor
- About COSC427
- Abstract vs Interface
- Access levels
- Account setup
- Accountability Design
- Active record pattern
- Add Parameter
- Advice from alumni
- Agile manifesto
- Agile methods
- Aidan's Design Study
- Alan Kay
- AlexsDesignStudy
- Alumni
- Antipatterns
- Are you gonna eat that
- Arthur Riel
- AudioSystems
- Avoid equals
- Avoid inheritance for implementation
- Avoid mixing inputs and outputs
- Avoid side effects
- Barbara Liskov
- Becomes problem
- Behavioral completeness
- Benjamin's Design Study
- BenjaminTaylor Previous Design Work
- Bertrand Meyer
- Beware accessors
- Big ball of mud
- Big design up front
- Blackboard System
- Boat anchor
- Bob Martin
- Bob Martin's heuristics
- BrettWardsDesignStudy
- CLU
- Change Reference to Value
- Change Unidirectional Association to Bidirectional
- Change Value to Reference
- Christopher Alexander
- Citation needed
- Class diagram
- Collapse Hierarchy
- Collecting Parameter
- Combining design patterns
- Comments and suggestions
- Copy Constructor vs the Encapsulation Boundary
- Cut and paste programming
- DMA Design Project
- DMA Design Project - Source Code
- DMA Design Project - first submission
- DMA Design Project first draft
- Data mapper pattern
- David Parnas
- Decomposition
- Defer identification of state variables pattern
- Define classes by behavior, not state pattern
- Define default values via explicit protocol pattern
- Dependency injection
- Design Project
- Design by contract
- Design examples
- Design maxims
- Design maxims Equivalence
- Design patterns break rules
- Designfest
- Diamond Problem
- Different Design
- 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
- Duplicate Observed Data
- Editing Tips
- Empty method over-rides
- Encapsulate Collection
- Encapsulate Downcast
- Encapsulate Field
- Encapsulate concrete state pattern
- Encapsulate that which varies
- Encapsulation is hierarchical
- 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
- Extreme programming
- Fat interfaces
- Favor composition over inheritance
- Frogs design
- Frogs second design
- Front controller pattern
- Functional decomposition
- Gang of Four
- GenA: A Genetic Algorithms Framework
- GenericGuidelines
- Getter and setter policy
- Getters and setters
- Goto considered harmful
- 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
- Hide Delegate
- Hide Method
- 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
- Inline Class
- Inline Method
- Inline Temp
- Intelligent children pattern
- Introduce Explaining Variable
- Introduce Foreign Method
- Introduce Local Extension
- Introduce Parameter Object
- Introduction to the Terrain Renderer
- Inversion of control
- 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
- John Hofman's Design Study
- John Hofman's Log
- John Hofman US001
- Johnson and Foote 1988
- Jojo's 2008 Design Study
- Jojo's OO Design Project Log
- Joshua Bloch
- Joshua Bloch 2006 Bumper Sticker API Design
- Jumble
- Keep accessors and mutators separate
- Keep last years stuff
- Ken Auer
- Ken Auer 1995
- Kent Beck
- Kent Beck 2003
- Kris's Design Study
- Language Spectrum
- Law of Demeter
- Law of leaky abstractions
- Lazy load pattern
- Lecture sequence
- Lecture times
- List of OO Languages
- LukasKorsikaDesignStudy
- Main Page
- Make all Member Variables Private
- Make constructors blocking
- Managing complexity
- Many to many association idiom
- Martin Doms' Design Study
- Martin Fowler
- Martins Design Study
- Matthew's Design Study
- Maxim Hierarchy
- Michael's Design Study
- Michael's Log
- Michal's Design Study
- Mike's Design Study
- Mock objects
- Model the room
- Model view controller
- Monsters design
- Move Field
- Move Method
- Move methods
- Mujtaba's Initial Design
- Mujtaba's Log
- Mujtaba's design study
- My actual Project, I think.
- Named constants
- Nelson Shaw Design Project
- Nelson Shaw Project Log
- Nick's Design Study
- Nick Brettel's eight puzzle design
- No Global Variables
- No Peter Pan objects
- No silver bullet
- OOTetris Design
- OO Python Character Animation Design Study
- OO culture
- OO gurus
- OO tools
- OO wisdom
- Oliver Cardwell/Project
- Once and only once
- One Into Many
- One hour tour
- Option-operand separation
- Orthogonality
- PLoP
- PLoP (Software Patterns Series)
- PLoP 1995
- Page controller pattern
- Parallel hierarchies problem
- Parameterise Method
- Parse tree design
- Party of five 1996
- PaulDesignStudy
- Peer To Peer
- Perfect OO Language
- PluS XML format
- Poker Simulator Design Log
- Poker Simulator Design Writeup
- Premature optimization
- Presentation Abstraction Control
- Presentation separation idiom
- Preserve Whole Object
- Professionalism
- Program to the interface not the implementation
- Project ideas
- Properties
- Properties / Fields / Attributes
- Pull Up Constructor Body
- Pull Up Field
- Pull Up Method
- Push Down Field
- Push Down Method
- Put semantic constraints in class definition
- Put semantic constraints in constructors
- Quick Reference
- Quotes
- RL Design Study Log
- Ralph Johnson
- Real name
- Rebecca Wirfs-Brock
- Rebecca Wirfs-Brock 1990
- Refactoring
- Refactoring and design
- Refactoring and performance
- Reinvent the wheel
- Remove Middle Man
- Remove Parameter
- Remove Setting Method
- Remove assignments to Parameters
- Rename Method
- Replace Array with Object
- Replace Conditional with Polymorphism
- Replace Constructor with Factory Method
- Replace Data Value with Object
- Replace Error Code with Exception
- Replace Exception with test
- Replace Inheritance with Delegation
- Replace Magic Number with Symbolic Constant
- Replace Method with Method Object
- Replace Parameter with Explicit Methods
- Replace Parameter with Method
- Replace Temp with Query
- Replace Type Code with Class
- Robert Cecil Martin 1996a
- Robert Cecil Martin 1996b
- Robert Cecil Martin 1996c
- Robert Cecil Martin 1996d
- Robert Cecil Martin 1996e
- Robert Cecil Martin 1997a
- Robert Cecil Martin 1997b
- Row data gateway pattern
- Schools of thought
- Scrum
- Self Encapsulate Field
- Separate Query from Modifier
- Separation of concerns
- Serialization
- Server Requests
- Service layer pattern
- Shallow VS Deep Copy
- Shalloway and Trott 2002
- Sign your work
- Similar patterns and how to tell them apart
- Single choice principle
- Smalltalk
- Software crisis
- Software reuse
- Sorcerers design
- Spaghetti code
- Split Temporary Variable
- Square-rectangle problem
- Start here
- State machine design
- Stephen's Design Study
- Stovepipe system
- Strategy meets Template
- Substitute Algorithm
- Super quick exam ref
- Swiss army knife
- Table data gateway pattern
- Table module pattern
- Tanmay's Design Study
- Tanmay's Log
- Teaching and learning style
- Tell, don't ask
- Template view pattern
- Terrain Renderer Design
- Test Driven Development
- Text design
- The Alexander conspiracy
- Toast
- TobiW's Design Study
- Tour Guide Project Page
- Trains design
- Transaction script pattern
- Transform view pattern
- Trygve Reenskaug
- Unified Modeling Language
- Unit Test
- Unit of work pattern
- Use lazy initialization pattern
- Vehicles and operators design
- Vendor lock-in
- Video rental system
- Wal's Fish Tank
- Ward Cunningham
- Ward and Kent
- Warfarin Design
- What is Bad Design
- Why refactoring works
- Wiki etiquette
- Wiki tips
- Wiki users
- You ain't gonna need it
