All geek questions in one place

What should be the sequence of creating diagrams in UML?

As we know, UML contains 13 types of diagrams (structural and behavioral)

Before starting the development of software, we are in the stage of requirement and design so that a diagram should be created and when? .. What should be the sequence of creating diagrams in UML at the stage of requirement and design?

In fact, if there is no rigid sequence, then first we need to rigidly create a structural diagram, but behavior similar to an activity diagram can vary depending on the user?

Is it possible to create a deployment diagram and a component diagram as soon as?

+3
source share
4 answers

There is absolutely no rule regarding the sequence of such diagrams.

Sometimes, when the data structure and behavior of your domain model is easily defined or well documented, creating class diagrams first provides clearer abstractions that help create a sequence diagram that makes sense.

In other cases, when the nature of the domain model is unknown or unclear, it will make sense to first create a sequence diagram and then extract classes from it.

I am sure that revisions of these diagrams will become coincident with each other (for example, sequence diagrams can display what was not taken into account in class diagrams, and vice versa).

, , , .. ..

, - , . , .

. , , , .

, , , .

+4

, , UML - , . , OOA OOD (OOAD), , UML. wiki , . RUP UML.

, ( , ): 1. ( /. 2. /, . 3. /, . 4. /, OO. 5. , , .

/, , , , .

+1

, , , , , ?

. , , .

0

Usecase - . usecase . CRC , UML. , . . . .

0

Source: https://habr.com/ru/post/1717702/

More articles:


All Articles