It would be nice if you could go directly from the requirements to the code with some simple push-button technology. Unfortunately, it simply doesn't work that way. The best that modern practice can offer is a series of constructs that will help you move closer to the direct translation goal.
One of these techniques, the use-case realization, takes advantage of the unique characteristics of the use case and the UML's modeling constructs and stereotypes to help drive design. This has many advantages in shortening the path from requirements to implementation.
Other modern practices offer us the clarity of viewing our efforts in the "4+1" architectural views construct. We have found that this helps provide a separation of concerns that increases resilience and improves out understanding of the system, while at the same time assuring that the system design conforms to all necessary requirements. This makes it much easier for the various stakeholders in the implementation process to develop and assess the design as it evolves.