.NET Buzz Forum - Udi's first principle of design

Articles |
News |
Weblogs |
Books |
Forums

Artima Forums | Articles | Weblogs | Java Answers | News

Sponsored Link •

.NET Buzz Forum
Udi's first principle of design

0 replies on 1 page.

Welcome Guest
Sign In

Back to Topic List

Reply to this Topic

Search Forum

Threaded View


Previous Topic		Next Topic

Flat View: This topic has 0 replies on 1 page

Udi Dahan

Posts: 882
Nickname: udidahan
Registered: Nov, 2003

Udi Dahan is The Software Simplist

Udi's first principle of design

Posted: Jan 29, 2006 3:39 PM

This post originated from an RSS feed registered with .NET Buzz by Udi Dahan.
Original Post: Udi's first principle of design Feed Title: Udi Dahan - The Software Simplist Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple. This blog is about how I do it.	Latest .NET Buzz Posts Latest .NET Buzz Posts by Udi Dahan Latest Posts From Udi Dahan - The Software Simplist

Software development principle #1:

For any classes A and B in a system, A should interact with B through an interface.

Corrollary #1:

If the atomic parts of software are not loosely coupled, it will be more difficult to create loosely coupled packages out of those parts.

Corrollary #2:

By induction, creating non-loosely-coupled atomic parts of software, increases the relative level of coupling of higher level abstractions.

Corrollary #3:

It is difficult to create higher level abstractions that the level of coupling between them is lower than that of the lower-next-level abstractions.

Conclusion:

Coupling behaves much like fractals: low level characteristics can be seen recurring through higher level views.

If you do not loosely-couple in the small, it may be futile in the large.

Read: Udi's first principle of design

Previous Topic

Next Topic


	Web Artima.com