Bad software requirements can jeopardize projects. There is a considerable literature on software requirements, but practice is far behind: what passes for requirements in industry usually consists of a few use cases or user stories, which are useful but not sufficient for a solution. Can we fix requirements engineering (known in other circles as business analysis) so that it is no longer the weak link in software engineering?
This video presents ongoing work intended to help industry produce more useful requirements. It includes precise definitions of software requirements concepts and a standard plan for requirements specifications, intended to replace the venerable but woefully obsolete IEEE standard from 1998. The plan contains four books covering the four “PEGS” of requirements engineering. The approach builds on existing knowledge to define a practical basis for software requirements engineering and provide projects with precise and helpful guidelines.
Video producer: https://www.acm.org/
