Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Requirements analysis
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Stakeholder issues=== Steve McConnell, in his book ''Rapid Development'', details a number of ways users can inhibit requirements gathering: * Users do not understand what they want or users do not have a clear idea of their requirements * Users will not commit to a set of written requirements * Users insist on new requirements after the cost and schedule have been fixed * Communication with users is slow * Users often do not participate in reviews or are incapable of doing so * Users are technically unsophisticated * Users do not understand the development process * Users do not know about present technology This may lead to the situation where user requirements keep changing even when system or product development has been started.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)