pdfcoffee.com-systems…
Id I S%
)
252 of 832
The degree to which we understand (or can understand) the current and future state of the business and corresponding software requirements.
• Stability: This is the last of the three functional requirements factors where agile and hybrid approaches make different assumptions and therefore reach different conclusions regarding BRUF. Stability is the extent to which software requirements stay the same (or change only slowly) over time. o ” Agile assumption: Numerous agile sources make broad claims that business requirements are changing more rapidly in a broad range of companies in recent years due to an increasingly dynamic market environment This provides another explanation as to why agile argues against the value of BRUF: even if we can capture requirements completely and accurately at the beginning of a project, those BRUF specifications will become rapidly out of date during software construction. Thus agile argues for detailing requirements at the “last responsible moment”—right before a feature is constructed. This is shown via the solid line at the bottom of the graph in Figure 5-14. o ^ Hybrid assumption: In contrast, hybrid assumes that requirements are reasonably stable, preserving the value of BRUF during software construction. This is shown via the dashed line at the top of the graph in Figure 5-14.
As with interdependence and clarity, this characteristic will vary from project to project. Teams should adjust their level of BRUF accordingly.
Stability
The degree to which software requirements remain the same over time.