Skip to main content
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
Code code:"if (foo != bar)"
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Saves in:saves
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 not deleted user 145

Software documentation is written text that accompanies computer software. It explains how the software operates, how to install it, how to use it, and other resources for help.

4 votes

Writing a Software Requirement Specification

The main requirement for a requirement is that it is testable. If you can't figure out how to test a requirement, the odds are that it won't be implemented the way the writer intended. I've never se …
AShelly's user avatar
  • 5,773
3 votes

What Does It Usually Mean for a Feature to be "Supported"?

Support can be in the form of direct help, debugging, releasing bug fixes, providing documentation, etc. …
AShelly's user avatar
  • 5,773
0 votes

Debug function input vs expecting code users to read the documentation - How far do I go?

For a public-facing API, here's my rule(s) of thumb: Validate all inputs that can cause unexpected behavior. Validate inputs when you first see them. Don't re-validate inputs in internal helper fu …
AShelly's user avatar
  • 5,773
4 votes

Is an architecture description document a violation of the DRY Principle?

An Architecture Description, or Software Design Description does violate DRY. However, in a large organization, where projects last years, developers come and go, and the system is too large for any o …
AShelly's user avatar
  • 5,773