[Sigia-l] IA system components - add to the list!

[Boniface Lau]

>  
> : > A methodology that is "stringent, highly structured" does not
> : > mean it cannot handle well a wide variety of problems. The key
> : > is in a methodology's robustness.
> 
> What is methodology robustness then? 

Methodology robustness is about how a methodology performs in various
situations. One of the factors affecting a methodology's robustness is
the spectrum of intended coverage. For example, a methodology designed
with one particular environment in mind often does not perform well in
other environments.

But what people called methodology is too often just a "copy" of a
way of doing things. It is like "tell me how you do things now and I
will make it a methodology". A more "sophisticated" version combines a
handful of "copies". Copy-based methodology naturally has little, if
any, design. Let alone robustness.

Developing a robust methodology requires extensive effort, iterations,
and evolutions. Therefore, a robust methodology is not likely to be
something that you can buy off-the-shelf or from silver bullet
franchises.


> It is not the "stringent, highly structured" characteristics, I
> suppose I could assume that it is the opposite then, 'modularity' or
> flexibility of the methodology.

"Modularity" is not the opposite of "stringent, highly structured".
In fact, something that is "highly structured" often has high
"modularity".

"Stringent, highly structured" is about how tight and fine is the
control.

"Modularity" is about how fine something is organized. 


> To my understanding these are characteristics of a toolbox 

A toolbox is just a collection of tools. There is no organization to
speak of. No wonder a toolbox is not "highly structured". In fact,
there is no structure at all.

A methodology ensures what is done is indeed the right thing. Whatever
tools in a toolbox are therefore put into good use.

Thus, toolbox and methodology each has its own unique role. One is not
a replacement for the other.


Boniface