Unique Benefits of "Freedom"

• Focus: Clear definition helps focus effort and reduce time to discover requirements

• Design Neutrality: Behavior-centric requirements are not prejudiced to OO, functional, or other design methodology

• Engineering Neutrality: Behavior-centric requirements are not prejudiced to software; can implement in hardware or hw/sw combination

• Ease of Change: encapsulating requirements results in one responsible module for each requirement, reducing cost of program evolution

• Trivial Traceability: one module per requirement eliminates need to map traceability

• Early Coding: UI prototype gets code to client much sooner; banishes taboo against coding during requirements phase