W3C home > Mailing lists > Public > www-ws-arch@w3.org > March 2002

RE: D-AG0005 - Simplicity Requirement

From: Dilber, Ayse, ALASO <adilber@att.com>
Date: Mon, 11 Mar 2002 08:52:30 -0500
Message-ID: <5C2CE23B27AC4D449F75AFF4560419F602B3879D@OCCLUST04EVS1.ugd.att.com>
To: "Cutler, Roger (RogerCutler)" <RogerCutler@chevrontexaco.com>, "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>, <www-ws-arch@w3.org>
could "supports interoperability" be one of the measurements?
Ayse 

-----Original Message-----
From: Cutler, Roger (RogerCutler) [mailto:RogerCutler@chevrontexaco.com]
Sent: Friday, March 08, 2002 12:14 PM
To: 'Champion, Mike'; www-ws-arch@w3.org
Subject: RE: D-AG0005 - Simplicity Requirement


Measurements of 005.4 - perhaps something along the lines of whether the
reference architecture forces a programmer to use exotic constructions?  Can
be implemented without large amounts of code?  Allows simple invocations as
well as elaborations with more functionality?

-----Original Message-----
From: Champion, Mike [mailto:Mike.Champion@SoftwareAG-USA.com] 
Sent: Thursday, March 07, 2002 11:37 PM
To: www-ws-arch@w3.org
Subject: RE: D-AG0005 - Simplicity Requirement




> -----Original Message-----
> From: Champion, Mike [mailto:Mike.Champion@softwareag-usa.com]
> Sent: Thursday, March 07, 2002 9:18 PM
> To: www-ws-arch@w3.org
> Subject: D-AG0005 - Simplicity Requirement
> 

Ooops, I guess we're supposed to break this down into critical success
factors and measurements.  How about:

005.1 - The reference architecture should be easily understandable by the
target audience.

Measurements: 
* does it not contain specialized jargon not familiar to ordinary software
designers?
* is it stated in simple declarative sentences?
* is it organized in a way that allows important points to be located?
* does it use illustrations to visually describe key components and
relationships?

005.2 - The reference architecture should be as minimal as possible

* How many components does it describe?
* How many relationships among the components does it describe?
* How do these figures compare to those of notable exemplars of good
reference architectures?
* Could any components or relationships be removed without significantly
limiting the value of the architecture?

005.3  -  The reference architecture should simplify the task of a
programmer implementing specifications of components described by the
architecture.

* is the role played by each component in the overall architecture stated
clearly?
* are the interdependencies among components noted explicitly?
* are existing specs that fufill the role of a given component referenced?

005.4 - The reference architecture should simplify the task of an programmer
building web services or applications that employ web services.

[inspiration fails me at this point]
Received on Monday, 11 March 2002 08:53:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:24:56 GMT