|
|
It also means that there is no definition of when the work is done. 
Dale Thompson
|
|
|
|
|
Which is correct. 
|
|
|
|
|
Not having a spec means you do all the work yourself. Since there's no spec, nobody can help you.
Not having a spec means you get into arguments with the client about what they said and what you heard.
Not having a spec means your team forgets what they're actually trying to accomplish.
Not having a spec means your team forgets the decisions graph that lead up to the requirement and its design.
Specs are written so that other people can write unit tests and acceptance tests against the specs.
Specs are written to figure out what needs further specs.
Specs are written so that everyone involved in the business can make sure that the spec works for their particular work process.
and so forth.
Marc
|
|
|
|
|
The Before-Design specs come from the users - and as a rule, they rarely know what they're talking about.
In this respect, it's on par with forcasting the weather for one's vacation in 2012. The only thing you can be sure of is that there will be some.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"How do you find out if you're unwanted if everyone you try to ask tells you to go away?" - Balboos HaGadol
|
|
|
|
|
And even then, it's nearly impossible to capture all the changes, and more importantly, the reasons for those changes!
Marc
|
|
|
|
|
Reasons?? We don't need no stinkin' reasons to change the specs 
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Or to change the specs back to how it was in the initial design! 
|
|
|
|
|
Chris Maunder wrote: We don't need no stinkin' reasons to change the specs
' ' just about sums it up
"I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon
|
|
|
|
|
Yeah, that was my vote also. In 20+ years, I've never seen a system that was coded to the original specs. Spec are what's referred to as a living document.
|
|
|
|
|
I agree with you that a spec changes over the course of the life time of the application. I also want to add that it depends on who you work for. As a contractor or consultant, I must code to spec and changes are discourage once the spec/design is signed. Its all depend on who is paying the bill. The more stricted process followed, the more successful of the project delivered on time and on budget.
|
|
|
|
|
|
I haven't found yet customers that know in advance what they expect from a product. Allways they have new ideas.
ADVICE: Avoid giving them ideas !
36. When you surround an army, leave an outlet free.
...
Do not press a desperate foe too hard.
SUN-TZU - Art of War
|
|
|
|
|
Its our job to give them ideas and help them realized in advance what to expect by writing specifications. Now they must sign the agree upon specs. Any more new ideas, treat it as additional contract.
|
|
|
|
|
I swear I saw one this morning!
|
|
|
|
|
It was moved to the correct site after everyone ran around in a panic about a *dramatic music* Java poll *gasp* appeared mistakenly on CodeProject.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Chris Maunder wrote: It was moved to the correct site after everyone ran around in a panic about a *dramatic music* Java poll *gasp* appeared mistakenly on CodeProject.
You mean you moved it to java.sun.com?
How did Sun mislay their poll then?
|
|
|
|
|
I wouldn't trust Java with some random strings from a VB app, never mind something as important as a poll.
Probably timed out waiting on the JRE getting the IP address of the server and by which time, something had gone wrong and the app decided to hijack CP instead.
Ninja (the Nerd)
Confused? You will be...
|
|
|
|
|
Chris was referring to the beta java.codeproject.com website that is being run in the (relatively) same manner as www.codeproject.com. The CodeProject is not affiliated with Sun microsystems.
Regards,
Thomas Stockwell
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Visit my homepage Oracle Studios[ ^]
|
|
|
|
|
I really find it bad that people behave with java the way they'd never behave with C#... 
moreover, as i posted in the poll, this is a "general technologic" poll, so codeproject (not java.codeproject) should allow polls of any stuff of this kind...
|
|
|
|
|
Yes and I voted on that one as well...
John
|
|
|
|
|
who is seriously doing this ??
I mean, who is doing this except for a joke, or only because the client requires as a delivery, not only the binaries but the functional documents ?
|
|
|
|
|
Sometimes it's easier to complete the project and then create any docs. You shouldn't change docs continuously in this case.
|
|
|
|
|
Always it's easier to complete the project, and then create the docs.
But... it's wrong and pointless.
How do you plan to show the work is done and charge for it, when nothing is specified?
A buffalo soldier, a dread-like rasta !
|
|
|
|
|
Specs written before requirements gathering are obsolete after.
Specs written before brainstorming are obsolete after.
Specs written before prototyping are obsolete after.
Specs written before implementation are obsolete after.
...
Citizen 20.1.01 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
