Why Requirements Management?
Hello, Phil? This is Maria in Human Resources. We're having a problem with the employee system you programmed for us. An employee just changed her name to Sparkle Starlight, and we can't get the system to accept the name change. Can you help?"
"She married some guy named Starlight?"
"No, she didn't get married, just changed her name," Maria replied.
"That's the problem. It looks like we can change a name only if someone's marital status changes."
"Well, yeah, I never thought someone might just change her name. I don't remember you telling me about this possibility when we talked about the system. That's why you can get to the Change Name dialog box only from the Change Marital Status dialog box," Phil said.
"I assumed you knew that people could legally change their name anytime they like," responded Maria.
"We have to straighten this out by Friday or Sparkle won't be able to cash her paycheck. Can you fix the bug by then?"
------------------------------------------------------
Mission:“Our Job is to give the customer, on time and on cost, not what he wants, but what he never dreamed he wanted; and when he gets it, he recognizes it as something he wanted all the time”- From the book, The circle of Innovation: You Can’t Shrink from Greatness, Knopf,1997------------------------------------------------------
Common Sense: By the way, what is that?
- Software Engineer ---------------------------------------------
Fools rush in where angels fear to tread.
A stitch in time saves nine.
Measure twice, cut once.
Look before you leap.
What do all these sayings have in common?
They're all about thinking before acting.
Why?
Saves time, money, effort and embarrassment.
In Software Engineering, common sense disappears? More often than not, Yes it is.