This week's book giveaway is in the Spring forum. We're giving away four copies of Pro Spring MVC with WebFlux: Web Development in Spring Framework 5 and Spring Boot 2 and have Marten Deinum & Iuliana Cosmina on-line! See this thread for details.
For me, once I know the requirement, screen shots start coming in my mind - how the screens will look like to accomplish certain functionality, I draw them - that�s for GUI. Then I start thinking about BE (mostly database), how I will store the required data (database designing), when I complete this, I get clear idea, how java code would be in raw sense. Then I do class level design, connect it with DB and GUI... mostly that's all.
Well, I use my recipe for OOAD with UML Basically is the traditional "OOAD" approach: based on the use case, I identify the main domain abstractions and their relationships, with generic ways of presenting and controlling them (my "analysis model"). Then, based on the particular technology I adapt and refine the model into something more concrete that can be easily coded... (actually, everything happens at the same time, but anyway...) Being a "visual" thinker, UML diagrams help me a lot in the process