2 ms·
"in an ideal world, requirements would be stable before coding starts" It is and they are. I think the common misconception is that requirements change during
by edw519 19y ago
"in an ideal world, requirements would be stable before coding starts"
It is and they are.
I think the common misconception is that requirements change during the project. My experience is that this is a rarity
What really happens is that OUR VIEW of the requirements changes during the project. The business rules didn't just suddenly change because we are building something. We NEVER NAILED THEM DOWN in the first place. This isn't hard to comprehend; analysis is a lost art and probably the most fragile link in the SDLC chain.
"What do you mean, when we file the record, a traveler should print out next to the supervisor's desk? Who told you that?"
"Joe did."
"What did Mary say?"
"I don't know. I didn't ask her."
"Ask her. Once you get her answer, change the specs."
(A silly little example, but is I had a nickel for every time that happened...)
- dhimes 19y agoIn my experience, this depends a lot on the project. Often, with new ideas, new uses will come up once the 'opinion leaders' get their hands on something real. Then, the requirements, in fact, do change (if you're smart).