Use Cases are the most utilized technique to specify software requirements. Currently, there are several proposals based on this technique to address the problem of determining the scope and construction sequence of a software, but most of them lack ease of use from the developer's perspective. In this paper, we present an approach to determine software construction sequences which emphasizes easiness from the developers' point of view and a controlled experiment based on this approach with professionals who have had at least two years of experience in software projects. The results obtained from this experiment show that our approach enables developers to define construction sequences more precisely than with other ad-hoc techniques. © 2009 Springer-Verlag Berlin Heidelberg.