Re: Orthogonal requirements
- From: "H. S. Lahman" <h.lahman@xxxxxxxxxxx>
- Date: Mon, 20 Nov 2006 17:58:22 GMT
Responding to Trichecoiob...
I read that requirements must be measurable, universal, and
"orthogonal"... I do not grasp the meaning...
any example ?
I agree with Berard's explanation.
But I think "atomic" or "unique" would be better choices of words for your source. The key idea is that each requirement is defined at a low enough level of abstraction that it can stand on its own independently of other individual requirements. IOW, each requirement defines a unique bit of functionality _compared to other requirements at the same level of abstraction_.
However, requirements are quite often closely related. Use cases are an example of explicitly organizing requirements together when they are intimately related through a more abstract (coarse-grained) functionality. When individual requirements are closely related in this manner, I think it is tough to argue that they are orthogonal.
*************
There is nothing wrong with me that could
not be cured by a capful of Drano.
H. S. Lahman
hsl@xxxxxxxxxxxxxxxxx
Pathfinder Solutions
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
"Model-Based Translation: The Next Step in Agile Development". Email
info@xxxxxxxxxxxxxxxxx for your copy.
Pathfinder is hiring: http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH
.
- Follow-Ups:
- Re: Orthogonal requirements
- From: trichecoiob
- Re: Orthogonal requirements
- References:
- Orthogonal requirements
- From: trichecoiob
- Orthogonal requirements
- Prev by Date: Re: How to model decoupled hierarchies?
- Next by Date: Re: Howto model decoupled hierarchies?
- Previous by thread: Re: Orthogonal requirements
- Next by thread: Re: Orthogonal requirements
- Index(es):
Relevant Pages
|