Blunder Dome Sighting  

Hangout for experimental confirmation and demonstration of software, computing, and networking. The exercises don't always work out. The professor is a bumbler and the laboratory assistant is a skanky dufus.

Click for Blog Feed
Blog Feed

Recent Items
Why Not .rtfx? The Suitability of RTF for Open Int...
Recipe for Nano-ISV Success? J. D. Meier just post...
The Difference Between Resolution and Size: Or, My...
Specialization is for Insects I’ve become a regula...
Getting to Unicode: The Least That Could Possibly ...
Dear Microsoft: No Thanks for the Updates
Raymond Chen: What Feature Did You Remove Today?
More Spolsky Gems: Open-Source, the Desktop, and S...
Is There an MVC in the House?
Nano-ISV Are I, Are I

This page is powered by Blogger. Isn't yours?

Locations of visitors to this site
visits to Orcmid's Lair pages

The nfoCentrale Blog Conclave
Millennia Antica: The Kiln Sitter's Diary
nfoWorks: Pursuing Harmony
Numbering Peano
Orcmid's Lair
Orcmid's Live Hideout
Prof. von Clueless in the Blunder Dome
Spanner Wingnut's Muddleware Lab (experimental)

nfoCentrale Associated Sites
DMA: The Document Management Alliance
DMware: Document Management Interoperability Exchange
Millennia Antica Pottery
The Miser Project
nfoCentrale: the Anchor Site
nfoWare: Information Processing Technology
nfoWorks: Tools for Document Interoperability
NuovoDoc: Design for Document System Interoperability
ODMA Interoperability Exchange
Orcmid's Lair
TROST: Open-System Trustworthiness



What Is Object-Oriented Design?

I have noticed that many treatments of object-oriented technologies (e.g., practically any text on Java or C#) seem to gloss over the hard-won principles around coupling, cohesion, separation of concerns, and those qualities that have software be confirmable (testable), maintainable, robust, and durable.  And any of those others, like secure, stable, dependable, as well.

Well, I may have simply not been looking in the good places. 

Today, Uncle Bob (this guy, I think) published a column on “What Is SOA, Really?” the first of a series.  Now, it seems to me that Service-Oriented Architecture (SOA) is wearing out its next-big-thing luster, and I find myself glazing over by the growing crop of ungrounded testimonials to it.  That isn’t what Uncle Bob is doing.  And I appreciate that this is being related to what happens in business practices and situated activities farther out than the innards of Object-Oriented Technologies (OOT to you).

But the greatest bonus of all was the articles link to the collection of principles on “What Is OO Design?”  (a.k.a. OOPSwhat?).

I went looking into the Common Closure Principle Principle[?], and found a comprehensive treatment on granularity.  Some of the other three-letter acronyms for principles are also recounted under cover of an article on stability. 

I love this stuff.  I don’t know how solidly it relates to what I attempt in my ad hoc nano-ISV projects, but I am going to give this material a closer look.  I’m expecting a terrific way to calibrate my development approaches and course-correct toward these principled qualities.  I might even start using UML.

This is my on-line marker for that material.  I grabbed the PDFs and filed them all neatly in a folder I keep on architetto\Methodologies where Windows Desktop Search is going to give me text-search access into them.

Construction Structure (Hard Hat Area) You are navigating Orcmid's Lair.

template created 2004-06-17-20:01 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-04-30 22:33 $
$$Revision: 21 $