By Topic

Is the European industry moving toward solving requirements engineering problems?

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

3 Author(s)

Requirements engineering is critical for successful software development. Nowadays, software development organizations are not likely to question the importance of issues related to requirements management (RM) and specification. However, despite its importance, the requirements process has traditionally been connected with a host of problems. Frederick Brooks (1987) used the two Aristotelian categories, essential and accidental, to classify these problems. As systems become more complex, software developers can do little to overcome essential difficulties such as software invisibility or pressure for change. However, several surveys have highlighted principal flaws in the requirements process that can be linked to accidental difficulties such as tool integration or bad documentation. Not only are these problems solvable, they're also often ones that researchers have already addressed. For years, researchers have conducted requirements engineering-related surveys, revealing problems and identifying potential solutions. Yet according to our own survey, RE problems persist.

Published in:

Software, IEEE  (Volume:19 ,  Issue: 6 )