CSC/ECE 517 Fall 2007/wiki3 3 ab: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
Line 15: Line 15:
#[http://designparadigm.wordpress.com/ Java by Experience]
#[http://designparadigm.wordpress.com/ Java by Experience]
#[http://www.codeproject.com/vb/net/OOPbyExample.asp OO Programming By Example]
#[http://www.codeproject.com/vb/net/OOPbyExample.asp OO Programming By Example]
#[http://www.babysentry.com/tech_specs_benefits.htm Benefits of the Three-Tiered Architecture]

Revision as of 01:37, 16 November 2007

Topic

Take the principle of Separation of Responsibility and catalog the information on it available on the Web. Find good descriptions and good, concise, understandable examples. Tell which you consider the best to present to a class.

Introduction

Separation of Responsibility

In Object-Oriented programming, each individual object should have as few responsibilities as possible, ideally one responsibility per object. That is to say,

Principle of Separation of Responsibility

Reference

  1. Elegance and classes
  2. [1]
  3. [2]
  4. [3]
  5. Java by Experience
  6. OO Programming By Example
  7. Benefits of the Three-Tiered Architecture
Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2007/wiki3_3_ab&oldid=8578"