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 engineering
(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!
==Criticism== Problem structuring, a key aspect of requirements engineering, has been speculated to reduce design performance.<ref>{{cite journal|last1=Ralph|first1=Paul|last2=Mohanani|first2=Rahul|title=Is Requirements Engineering Inherently Counterproductive?|date=May 2015|publisher=IEEE|url=https://www.researchgate.net/publication/272793687|doi=10.13140/2.1.3831.6321}}</ref> Some research suggests that it is possible if there are deficiencies in the requirements engineering process resulting in a situation where requirements do not exist, software requirements may be created regardless as an [[illusion]] misrepresenting design decisions as requirements <ref>{{Cite journal| doi=10.1007/s00766-012-0161-4 | title=The illusion of requirements in software development| journal=Requirements Engineering | volume=18 | issue=3 | pages=293β296| date=September 2013| last=Ralph | first=P. | arxiv=1304.0116| bibcode=2013AIPC.1516..293R| s2cid=11499083}}</ref>
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)