Tuesday, September 02, 2008
Requirements vs Features
Do business analysts understand the distinction...
In the past, I have blogged about the fact that while American developers can work with requirements, but Indian IT outsourcing developers need specifications, the subtle distinction between requirements and features hasn't been deeply discussed.
For the word overloading crowd, my distinction will be lost. Anyway, In deciding what to do next, what the first step is, one must consider requirements in order to implement desired features. A feature is more or less encapsulated in a general statement meant to define what a user might expect. A requirement is a more specific and concrete statement to define what a programmer must consider in the coding of and actualization of the desired features.
The real question is should business analysts separate these two notions?
| | View blog reactionsIn the past, I have blogged about the fact that while American developers can work with requirements, but Indian IT outsourcing developers need specifications, the subtle distinction between requirements and features hasn't been deeply discussed.
For the word overloading crowd, my distinction will be lost. Anyway, In deciding what to do next, what the first step is, one must consider requirements in order to implement desired features. A feature is more or less encapsulated in a general statement meant to define what a user might expect. A requirement is a more specific and concrete statement to define what a programmer must consider in the coding of and actualization of the desired features.
The real question is should business analysts separate these two notions?
