Gathering requirements and documenting the actors and behaviors is a fun exercise, but it still doesn't tell us how to build the system. What we have accomplished to this point is to define the system behavior and describe functionality. The objective to this point has been to gather requirements and describe as much of the system behavior as possible. It is important to understand as many of the requirements that the customer can provide because this will lead to a better design. At the same time, try to avoid analysis paralysis. While we want to gather as much as possible, it is easy to spend too much time trying to cover all of the details. This can lead to a situation where the analysis is the best ever but no actual design and development can ever proceed. It is important to find a middle ground between no analysis and too much.