Requirments Vs Specification ?
-
As part of my future article, I would like to put forth the question, just to gauge the understanding Can you please describe in a line for the meaning of Requirments and Specification from your personl experience?
cheers, Super ------------------------------------------ Too much of good is bad,mix some evil in it
-
Requirements are a conversation between project leads and external stake holders. Specifications are a conversation between project leads and the developers. Properly written, those two audiences should never have to read the others' document.
How about "Conception" vs. "Inception" ? (by their respective definitions of course)
-
As part of my future article, I would like to put forth the question, just to gauge the understanding Can you please describe in a line for the meaning of Requirments and Specification from your personl experience?
cheers, Super ------------------------------------------ Too much of good is bad,mix some evil in it
Requirements are what the customer needs. Specifications are what he says he wants.
-
As part of my future article, I would like to put forth the question, just to gauge the understanding Can you please describe in a line for the meaning of Requirments and Specification from your personl experience?
cheers, Super ------------------------------------------ Too much of good is bad,mix some evil in it
I remember reading a line of code, reporting to the manager there was a bug in the code. "It can't be, it's written per specification." Well, I haven't seen the specification document, could I see it? After reading it, I agreed the code exactly matched the specification. I could see the manager was satisfied that she had won me over and the code was right, so I said "It's just too bad that it doesn't do what it is supposed to do." That got her attention and after reviewing what it was actually doing, she agreed that it wasn't doing what it was supposed to do. Thank God the naming conventions were so well laid out that by just looking at the code I knew what the requirement for this segment of the code was and the specification didn't satisfy the requirement. Basically a requirement is a statement of what the code is supposed to do, the specification is the implementation plan to meet the requirement. With a field name of Maximum_Thread_Count_Allowed, I could tell that was the requirement, the Current_Thread_Count was properly being tracked and it could generate Maximum_Thread_Count_Allowed + 2 * Thread_Count_Increment threads. All they had to do to fix it was to change a "-" to a "+" (or Vise-Versa, can't remember the formula I saw in 2005.) in the "IF" clause. There are user requirements and implementation requirements. The first is the constraints the client puts on the code, the second are the requirements the coder has to meet so the code will properly run on the environment it is designed for. The specification should cover both sets of requirements. The user may require that older data is removed using a maintenance schedule. When the daily maintenance is run, it must complete within 24 hours or it fails the implementation requirement.