One key abstraction

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
m (Reverted edits by Ebybymic (Talk); changed back to last version by MartinvanZijl)
 
Line 1: Line 1:
----
 
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
 
----
 
=[http://otypaxixa.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
 
----
 
=[http://otypaxixa.co.cc CLICK HERE]=
 
----
 
</div>
 
 
:''A class should capture one and only one key abstraction.'' --Riel's Heuristic 2.8, [[Arthur Riel 1996]]
 
:''A class should capture one and only one key abstraction.'' --Riel's Heuristic 2.8, [[Arthur Riel 1996]]
  

Latest revision as of 03:11, 25 November 2010

A class should capture one and only one key abstraction. --Riel's Heuristic 2.8, Arthur Riel 1996

A class should represent one key abstraction of the domain model, no more and no less. A key abstraction is generally a noun in a requirements statement. If a key abstraction maps to more than one class, the designer may be representing each function of the abstraction as a class. If several key abstractions map to one class, the designer may be creating a centralized system and needs to split the class into several smaller classes.

See also

Personal tools