Re: Orthogonal requirements

On Mon, 20 Nov 2006 07:17:16 -0600, trichecoiob@xxxxxxxxxx wrote
(in article <1164028636.658798.232520@xxxxxxxxxxxxxxxxxxxxxxxxxxx>):

I read that requirements must be measurable, universal, and

"orthogonal"... I do not grasp the meaning...
any example ?


A dictionary definition of "orthogonal" is "pertaining to or involving right
angles or perpendiculars"

As the term is frequently used in an engineering context, "orthogonal"
can mean "no overlap." So, if I say that "these two requirements are
orthogonal," I am actually saying that "these two requirements are
totally independent of each other, e.g., a change in one requirement
does not affect the other.

Another way of looking at it is to say that if all the requirements are
orthogonal to each other, then there is no duplication of information.
(Note that this is not saying that the information is complete.)

The general advice is that software engineers should strive for a
high degree of orthogonality, everything else being equal.

-- Ed


.