Chapter 11 Value Engineering of Requirements

DOI: 10.1201/9781003129509-11

What, Why, When, and How of Value Engineering

Up until now, we have had a very little discussion of the costs of certain features that customers may wish to include in the system requirements. Part of the reason is that it made sense to separate that very complex issue from all of the other problems surrounding requirements elicitation, analysis, representation, validation, verification, and so on. Another reason for avoiding the issue is that it is a tricky one.

In the early 1980s, Barry Boehm proposed a model for software projects called the funnel curve that helped explain why software effort and cost prediction were so hard (Boehm 1981). The model had been around ...

Get Requirements Engineering for Software and Systems, 4th Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.