The Stack Overflow podcast is back! Listen to an interview with our new CEO.
Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 855

A specification (often abbreviated as spec) is an explicit set of requirements to be satisfied by a material, product, or service.

0
votes
You need to let users know that the later a 'requirement' is identified in the project, the more it will cost. They may decide that they don't really need the change after all. If they insist on the c …
answered Nov 20 '10 by JeffO
0
votes
Operator and Visitor seem pretty well defined. Not sure there is a difference when an operator becomes a Visitor or a Visitor becomes a Visitor. At that point, everyone is a Visitor.
answered Jan 19 '11 by JeffO
1
vote
Agile is 10+ years old, so this isn't a new phenomenon. I would hope the specs would be a lot shorter than the code, so I don't know how much detail you need. There should be enough to keep team memb …
answered Mar 23 '11 by JeffO
12
votes
If you're finding problems during the design stage, do you really have a problem? Make sure those creating the specs don't feel like they have to do everything up front. They can't think of everythin …
answered Jan 28 '11 by JeffO