User contributions
From CSSEMediaWiki
(Latest | Earliest) View (newer 50 | older 50) (20 | 50 | 100 | 250 | 500)
- 01:35, 8 October 2008 (diff | hist) Quick Reference
- 00:18, 8 October 2008 (diff | hist) 2005 Exam answers
- 10:49, 7 October 2008 (diff | hist) Beware of many accessors
- 10:46, 7 October 2008 (diff | hist) N Beware of many accessors (New page: If there are too many accessors for fields within a class (especially public accessors), that indicates there are large number of requests requiring thoes fields. If a class is designed pr...)
- 10:23, 7 October 2008 (diff | hist) Double Dispatch
- 10:19, 7 October 2008 (diff | hist) Double Dispatch
- 11:17, 6 October 2008 (diff | hist) Service layer pattern
- 11:17, 6 October 2008 (diff | hist) N Service layer pattern (New page: The definition for the Service Layer Pattern is “defines an application’s boundary with a layer of services that establishes a set of available operations and coordinates the applicati...)
- 10:51, 6 October 2008 (diff | hist) N Table module pattern (New page: The short definition for the Table Module Pattern is: “a single instance that handles the business logic for all rows in a database table or view”. The Table Module pattern introduces...)
- 10:26, 6 October 2008 (diff | hist) N Domain model pattern (New page: The short definition for the Domain Model Pattern is: “an object model of the domain that incorporates both behavior and data”. The domain model is created in an application by introd...)
- 10:06, 6 October 2008 (diff | hist) Transaction script pattern
- 10:04, 6 October 2008 (diff | hist) N Transaction script pattern (New page: The short definition for the Transaction Script Pattern is: “Organizes business logic by procedures where each procedure handles a single request from the presentation.” When the Tran...)
- 03:05, 5 October 2008 (diff | hist) N Send messages to components instead of to self (New page: For an inheritance-based framework, behaviors achieved by overridden method is better to be replaced by encapsulate these methods into components, hence a component-based framework will be...)
- 02:52, 5 October 2008 (diff | hist) N Separate methods that do not communicate (New page: If there are different ways to view different objects in a class, then it is a good signal that such a class needs to be split. In a good design, a class should only represent a single typ...)
- 02:35, 5 October 2008 (diff | hist) Subclasses should be specializations
- 02:28, 5 October 2008 (diff | hist) N Subclasses should be specializations (New page: Johnson and Foote defined that subclass should be considered as a specialized entity of the superclass. Hence subclass does not redefine any of the method which is already defined in the s...)
- 02:09, 5 October 2008 (diff | hist) N Class hierarchies should be deep and narrow (New page: A good class hierarchy design should be several layers deep. In a good design, a base class should not have large number of direct children classes (i.e. a superclass has 28 subclasses). I...)
- 00:30, 5 October 2008 (diff | hist) N Reduce the number of arguments (New page: A method with a large number of arguments can be very hard to read, such a method should be considered for redesigning. A method which requires large number of arguments can be break down ...)
- 00:17, 5 October 2008 (diff | hist) N Recursion introduction (New page: When an operation need the method in one class to communicate to a method another class, then the interface of these two class (the method) should be named the same. If it happens to be th...)
- 22:39, 4 October 2008 (diff | hist) N Reuse release equivalence principle (New page: The formal defintion for Reuse/Release Equivalency Principle is: “The granule of reuse if the granule of release. Only components that are released through a tracking system can be effec...)
- 21:43, 4 October 2008 (diff | hist) Information hiding
- 21:41, 4 October 2008 (diff | hist) N Hide your decisions (New page: Hide your decisions is the base concept for encapsulation, modularity and abstraction. It emphasizes encapsulating the “design secret” from the external user. Hide your decision is jus...) (top)
- 21:35, 4 October 2008 (diff | hist) Information hiding
- 21:35, 4 October 2008 (diff | hist) N Information hiding (New page: == Information Hiding == Information hiding firstly came out in a paper David Parnas wrote “On the Criteria to Be Used in Decomposing Systems Into Modules” (1972 ACM). Information hid...)
- 03:59, 1 October 2008 (diff | hist) N File:PrintProduction.jpg (top)
- 03:58, 1 October 2008 (diff | hist) User:Chen Qing (→Source Code) (top)
- 03:02, 1 October 2008 (diff | hist) User:Chen Qing (→Print Product Family)
- 02:58, 1 October 2008 (diff | hist) N File:PrintProduction.zip (top)
- 02:57, 1 October 2008 (diff | hist) User:Chen Qing (→Source Code)
- 02:34, 1 October 2008 (diff | hist) User:Chen Qing
- 02:08, 1 October 2008 (diff | hist) User:Chen Qing (→Print Product Family)
- 01:59, 1 October 2008 (diff | hist) User:Chen Qing (→Main Design Decisions)
- 01:58, 1 October 2008 (diff | hist) User:Chen Qing
- 01:55, 1 October 2008 (diff | hist) User:Chen Qing
- 01:31, 1 October 2008 (diff | hist) User:Chen Qing
- 01:30, 1 October 2008 (diff | hist) User:Chen Qing
- 01:19, 1 October 2008 (diff | hist) File:PrintProduction PrintCompany.jpg (uploaded a new version of "Image:PrintProduction PrintCompany.jpg") (top)
- 01:17, 1 October 2008 (diff | hist) N File:PrintProduction PrintCompany.jpg
- 01:13, 1 October 2008 (diff | hist) User:Chen Qing
- 01:03, 1 October 2008 (diff | hist) N File:PrintProduction PrintJob.jpg (top)
- 01:02, 1 October 2008 (diff | hist) User:Chen Qing
- 14:19, 30 September 2008 (diff | hist) User:Chen Qing
- 14:02, 30 September 2008 (diff | hist) N File:PrintProduction Products.jpg (top)
- 14:00, 30 September 2008 (diff | hist) User:Chen Qing
- 08:49, 22 September 2008 (diff | hist) Fat interfaces
- 08:48, 22 September 2008 (diff | hist) Fat interfaces
- 08:47, 22 September 2008 (diff | hist) Fat interfaces
- 08:46, 22 September 2008 (diff | hist) N Fat interfaces (New page: A fat interface is usually the one which is aimed at serving more than one set of clients. A fat interface looks powerful but indeed quite harmful. By using fat interface, we unavoidably i...)
- 08:17, 22 September 2008 (diff | hist) N Encapsulation is hierarchical (New page: When people are talking about object oriented designs, one common problem they are facing is deciding if a member of a class should be open to everyone outside or should just kept known by...)
- 06:24, 14 September 2008 (diff | hist) File:HighLevelOverview.jpg (uploaded a new version of "Image:HighLevelOverview.jpg": Reverted to version as of 06:20, 14 September 2008) (top)
(Latest | Earliest) View (newer 50 | older 50) (20 | 50 | 100 | 250 | 500)
