Attacking requirements complexity using a separation of concerns

As systems become more complex, the task of defining requirements must evolve to deal with this complexity. The use of the concepts of "separation of concerns" provides a successful approach for cutting problem complexity down to the level where it can be handled. Such concepts can be added to any notation or "methodology," but are more effective if the underlying requirements definition notation provides support.<
>