Most linked-to pages
From CSSEMediaWiki
Showing below up to 250 results starting with #251.
View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)
- Analysis patterns (9 links)
- Presentation separation idiom (9 links)
- Ken Auer (9 links)
- Object Encapsulation (9 links)
- Premature optimization (9 links)
- Beware singletons (9 links)
- Many to many association idiom (8 links)
- Avoid multiple inheritance (8 links)
- User:Yugan Yugaraja (8 links)
- The top of the class hierarchy should be abstract (8 links)
- Avoid becomes (8 links)
- Avoid equals (8 links)
- User:Paul Williams (8 links)
- Common closure principle (8 links)
- Reduce the size of methods (8 links)
- User:Douglas Wall (8 links)
- Split large classes (8 links)
- User:BenjaminTaylor (8 links)
- Hillside Group (8 links)
- Interface should be dependent on model (8 links)
- Architectural patterns (8 links)
- Resources (8 links)
- Avoid interface bloat (8 links)
- Defer identification of state variables pattern (8 links)
- God class (8 links)
- MVC (7 links)
- Encapsulate concrete state pattern (7 links)
- Class Encapsulation (7 links)
- Johnson and Foote's heuristics (7 links)
- Reduce the number of arguments (7 links)
- Double Dispatch (7 links)
- JUnit (7 links)
- Keep accessors and mutators separate (7 links)
- User:Jenny Harlow (7 links)
- Inheritance for implementation (6 links)
- Parse tree design (6 links)
- Law of demeter (6 links)
- User:John Hofman (6 links)
- Favour deep hierarchies (6 links)
- Minimize number of methods (6 links)
- User:BenMcDonald (6 links)
- User:Josh Oosterman (6 links)
- Object pool (6 links)
- Equals vs the Encapsulation Boundary (6 links)
- Beware inheritance over composition (6 links)
- Common reuse principle (6 links)
- Martin Fowler 2003 (6 links)
- Test Driven Development (6 links)
- Robert Cecil Martin 1996b (6 links)
- OO wisdom (6 links)
- Beware of many accessors (6 links)
- Named constants (6 links)
- Big ball of mud (6 links)
- A class should not depend on its users (6 links)
- Separate methods that do not communicate (6 links)
- Stable dependencies principle (6 links)
- OO gurus (6 links)
- No concrete base classes (6 links)
- User:Michael Madamba (5 links)
- OO tools (5 links)
- User:Joey Scarr (5 links)
- User:Michael Price (5 links)
- The Alexander conspiracy (5 links)
- No Global Variables (5 links)
- User:Mujtaba Alshakhouri (5 links)
- 427 assessment (5 links)
- Dependency injection (5 links)
- User:Stephen Fitchett (5 links)
- User:Nelson Shaw (5 links)
- Patterns (5 links)
- One responsibility rule (5 links)
- Robert Cecil Martin 2003 (5 links)
- UML (5 links)
- User:Linda Pettigrew (5 links)
- Hide your decisions (5 links)
- Favour composition over inheritance (5 links)
- Enum idiom (5 links)
- Jim Coplien (5 links)
- Reuse release equivalence principle (5 links)
- Model View Controller (5 links)
- User:Jenny Harlow/Design study (5 links)
- Option-operand separation (5 links)
- User:James Ashford (5 links)
- Bertrand Meyer (5 links)
- Implement behavior with abstract state pattern (5 links)
- Wals library (5 links)
- Abstract classes should be base classes (5 links)
- Subclasses should be specializations (5 links)
- User:LukeRobinson (4 links)
- State pattern (4 links)
- Robert Cecil Martin 1996e (4 links)
- User:RobertLechte (4 links)
- No silver bullet (4 links)
- Paul Clark's Design Study (4 links)
- Amelioration patterns (4 links)
- Contain contents not parents (4 links)
- Reusable frameworks over reusable components (4 links)
- Reduce implicit parameter passing (4 links)
- Kent Beck 2003 (4 links)
- Paul Clark's Whiteboard (4 links)
- Observer pattern (4 links)
- Robert Cecil Martin 1997b (4 links)
- State machine design (4 links)
- Class diagram (4 links)
- Limit hierarchy depth (4 links)
- DBC (4 links)
- User:Nick Molhoek (4 links)
- 427 design standard (4 links)
- Christopher Alexander 1977 (4 links)
- Domain model pattern (4 links)
- Robert Cecil Martin 1996a (4 links)
- User:Chen Qing (4 links)
- User:Oliver Cardwell (4 links)
- Distribute system intelligence (4 links)
- Inheritance for specialization (4 links)
- Encapsulation is hierarchical (4 links)
- Cay Horstmann 2002 (4 links)
- PLoP (4 links)
- User:Filip Kujikis (4 links)
- Getter and setter policy (4 links)
- Design Patterns (4 links)
- Robert Cecil Martin 1996c (4 links)
- Beware of non-communicating methods (4 links)
- Sign your work (4 links)
- Agile methods (4 links)
- Robert Cecil Martin 1996d (4 links)
- User:Ryan Mallon (4 links)
- Agent classes irrelevant (3 links)
- Design examples (3 links)
- Alan Davis 1995 (3 links)
- Combining design patterns (3 links)
- Single choice principle (3 links)
- Management antipatterns (3 links)
- Make all Member Variables Private (3 links)
- User:Bertrand Roussel (3 links)
- Kent Beck 2000 (3 links)
- Analysis Patterns (3 links)
- User:Scott Parlane/DesignStudy (3 links)
- Robert Cecil Martin 1997a (3 links)
- One hour tour (3 links)
- Limit compositions in a class (3 links)
- Richard Helm (3 links)
- Extensibility (3 links)
- Rebecca Wirfs-Brock 1990 (3 links)
- Refactoring and design (3 links)
- About COSC427 (3 links)
- Uncle Bob (3 links)
- Empty method over-rides (3 links)
- Separate non-communicating behaviour (3 links)
- Maxim Hierarchy (3 links)
- Spaghetti code (3 links)
- Organisational patterns (3 links)
- User:Aidan (3 links)
- Template:Documentation (3 links)
- Richard Gabriel 1996 (3 links)
- GenA: A Genetic Algorithms Framework (3 links)
- Alan Kay (3 links)
- Avoid verb classes (3 links)
- Methods should use most fields of a class (3 links)
- Joshua Bloch (3 links)
- Mujtaba's design study (3 links)
- User:Paul Clark/US-001-Add Task (3 links)
- Strategy pattern (3 links)
- Trains design (3 links)
- OO culture (3 links)
- User:Darryl Anderson (3 links)
- Arthur Riel (3 links)
- Exam questions (3 links)
- Minimal public interface (3 links)
- PLoP (Software Patterns Series) (3 links)
- Identify message layers pattern (3 links)
- Design patterns break rules (3 links)
- Christopher Alexander 1979 (3 links)
- Strategy Pattern (3 links)
- User:Paul Clark/US-002-Claim an Open Task (3 links)
- Beware accessors (3 links)
- Martin Fowler 2004 (3 links)
- Shalloway and Trott 2002 (3 links)
- Frogs second design (3 links)
- User:Paul Clark (3 links)
- Barbara Liskov (3 links)
- Ward and Kent (3 links)
- Do not change the state of an object without going through its public interface (3 links)
- No global variables or functions (3 links)
- Establishing priorities (3 links)
- Impedance mismatch (3 links)
- Send messages to components instead of to self (3 links)
- User:Paul Clark/US-003-Execute Task (3 links)
- Steve McConnell 2004 (3 links)
- A froggy visitor (3 links)
- Factor implementation differences into subcomponents (3 links)
- Managing complexity (3 links)
- Greg Searle's project blackjack (3 links)
- Gang Of Four 1995 (3 links)
- Refactoring and performance (3 links)
- Double dispatch (3 links)
- AlexsLibrary (3 links)
- Andrew Hunt 1999 (3 links)
- Agile manifesto (3 links)
- Poker Simulator Design Log (3 links)
- User:Tanmay Bhola (3 links)
- Idioms (3 links)
- Put semantic constraints in class definition (3 links)
- Immutable object (3 links)
- Inventory and Accounting (2 links)
- Michal's Design Study (2 links)
- Main Page (2 links)
- Scrum (2 links)
- Parallel hierarchies (2 links)
- User:Benjamin Kearns (2 links)
- Delegation (2 links)
- Data mapper pattern (2 links)
- Michael's Log (2 links)
- Account setup (2 links)
- Resource materials (2 links)
- Rebecca Wirfs-Brock (2 links)
- Template:Ambox/core (2 links)
- Define default values via explicit protocol pattern (2 links)
- Access levels (2 links)
- LukasKorsikaDesignStudy (2 links)
- Observations and Measurements (2 links)
- EXtreme programming (2 links)
- Active record pattern (2 links)
- Data transfer object pattern (2 links)
- Identity map pattern (2 links)
- Keep behaviour with data (2 links)
- Peter Coad 1995 (2 links)
- Tell dont ask (2 links)
- Sorcerers design (2 links)
- David Parnas (2 links)
- Teaching and learning style (2 links)
- Trygve Reenskaug (2 links)
- Avoid accidental multiple inheritance (2 links)
- Law of leaky abstractions (2 links)
- Martins Design Study (2 links)
- Planning (2 links)
- Program to the interface not to the implementation (2 links)
- Kent Beck 2007 (2 links)
- Visitor pattern (2 links)
- One Into Many (2 links)
- Oliver Cardwell/Project (2 links)
- Page controller pattern (2 links)
- Row data gateway pattern (2 links)
- Table data gateway pattern (2 links)
- Greg Searle's captains log star date (2 links)
- Grady Booch (2 links)
- Contained objects should not use each other (2 links)
- User:Jenny Harlow/Design study/Final design detail (2 links)
- Model classes not roles (2 links)
- Software crisis (2 links)