There are hundreds of books on the subject. If you go looking for some, get recent ones as the "current wisdom" changes pretty rapidly.
You'll find most of the denizens of this board are into "agile" methodologies that don't like to separate requirements and coding into distinct phases. Instead we try to make them concurrent activities during a short sprint from concept to code, say between a week or 30 days. Of course that means you can't capture all the requirements for a large system and get them nailed down and approved, then start coding and finish the system in 30 days. It means you pick one feature of the system, work closely with users and those who set requirements to build the feature.
It's fascinating stuff and it really works, but it's challenging to many think about working without a proscribed set of steps.
You might find The Object Primer 3rd Edition (www.ambysoft.com/theObjectPrimer.html) to be of interest. It covers the full lifecycle going from initial requirements modeling to code. The book covers all of UML 2 plus other types of models (user stores, data models, UI stuff), agile techniques, and test driven development (TDD).