Skip to Main Content
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.