This requirements method must be approached with caution as it typically leads to an organizational structure that places team members into functional "silos" based on the type of work that they do.

Using conservative percentages for productivity improvement based on the use-case method of capturing functional requirements, we estimate a 14% increase in productivity.

The method is based on a lightweight process geared to streamline service discovery and functional design activities during Initiation and Elaboration phases of SOA system implementation (Figure 14).