RE: Is "simplicity" a useful architectural constraint?

> The related architectural document was only 40 pages and tied 
> together a
> series of other specifications.  This modular approach enabled (or
> should have enabled) a layperson to read each specification and
> understand it as a component.  Each modular specification also made
> normative references to other protocols, themselves governed by
> specifications (examples: W3C schema, SOAP, HTTP, MIME).  

Okay, how about a refined metric:

(Size in pages) + (no. of specs dependent upon)X(weighting factor)

> 
> <sigh> It all seems so simple on paper ;-)

Well, yeah! Every time.

[I wonder if Tim's regretted posting his simple question, yet?]

Received on Thursday, 3 January 2002 13:44:00 UTC