This link has been bookmarked by 25 people . It was first bookmarked on 28 Jul 2006, by Philip Guth.
-
12 Jun 15
-
30 Apr 15
-
12 Dec 13
-
09 Dec 13
-
inheritance, polymorphism, and object persistence.
-
An example is class normalization, the object-oriented version of data normalization, a collection of simple rules for reducing coupling and increasing cohesion within your object designs.
-
The object-oriented (OO) paradigm is a development strategy based on the concept that systems should be built from a collection of reusable components called objects. Instead of separating data and functionality as is done in the structured paradigm, objects encompass both. While the object-oriented paradigm sounds similar to the structured paradigm, as you will see at this site it is actually quite different. A common mistake that many experienced developers make is to assume that they have been “doing objects” all along just because they have been applying similar software-engineering principles. To succeed you must recognize that the OO approach is different than the structured approach.
-
A use case describes a sequence of actions that provide a measurable value to an actor and is drawn as a horizontal ellipse. An actor is a person, organization, or external system that plays a role in one or more interactions with your system. Actors are drawn as stick figures. Associations between actors and classes are indicated in use-case diagrams, a relationship exists whenever an actor is involved with an interaction described by a use case. Associations between actors and use cases are modeled as lines connecting them to one another, with an optional arrowhead on one end of the line indicating the direction of the initial invocation of the relationship.
-
-
26 May 12
-
20 Jan 12
-
05 Dec 11
-
In the data world there is a common process called data normalization by which you organize data in such a way as to reduce and even eliminate data redundancy, effectively increasing the cohesiveness of data entities. Can the techniques of data normalization be applied to object schemas? Yes, but this isn’t an ideal approach because data normalization only deals data and not behavior. We need to consider both when normalizing our object schema. We need to rethink our approach. Class normalization is a process by which you reorganize the structure of your object schema in such a way as to increase the cohesion of classes while minimizing the coupling between them.
Fund
-
-
27 Jul 11
-
20 Dec 10
-
06 Dec 10
-
14 Aug 08
-
04 Aug 08
-
02 Jul 08
-
23 Mar 08
-
15 Oct 07
-
07 Sep 06
-
13 Mar 06
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.