UML diagrams. When are they used?

Question

So, I understand that UML diagrams help in building a program, but when are they used? Are they needed before you start coding? do you need them so you know what you need to code? Or do you use them after you have encoded the program?

Answer 1

Before, During and After.

You use them to describe requirements, proposed architecture, software development, implementation, and deployment.

Even the operating procedures for using the software can be described in the form of a UML diagram.

Answer 2

I will take a slightly different point of view.

, /, UML . , , - .

. , , , .

Answer 3

... , UML- .

UML- , , . , , .

UML - , . , (, ) ; , , , XP; .. - . , , ( UML , , , , , ).

, , UML, , .

Answer 4

UML- - , , . . , UML, , UML . , , . UML , , . . , , , . , .

Answer 5

. , , , , . . , , / , - . , UML , , .

UML , UML AndroMDA. , , , , hibernate spring. spring , UML. , , , , UML. , , UML , .

Answer 6

DSDM UML ( ).

, , , , , .

, , , , .

Answer 7

In my experience, they are mostly used before implementation to tell how the component will be built. They provide people with the opportunity to view a potential design in a good standardized format (desgin review). They can also provide a high-level view of the system for non-developers who are interested in the system (feature overview). I also saw how they were used after implementation as a reference for new developers who need to learn how the system works.