How often is the UML “in the real world?” Chart used.

Question

Almost every one of my programming classes used UML, but none of them explained when and where it can be used in professional settings. Is this done for every single file in the project, or is there any rule of thumb when you can use it? In addition, is this most often done manually (which I have always been afraid of) or using some kind of generator?

Answer 1

_{This question is a very good example of an opinion-based and very broad question, without a real problem to solve it, and not a single correct answer}

Of course, in the number of millions of software developers, there are some who have learned to use UML and use it. And there are those who either did not learn to use UML , or simply did not use it for any reason.

• I remember that in the pre-trial era, it was believed that no “big” software could be implemented without a thorough analysis and modeling phase, and no “big” software contract could be signed if business documents did not include some UML - figurative images

  And in some countries this is still the case, and government agencies say they have to provide a documentation software provider, and for some requirements, a UML image is a good form

  See also:

  • Wikipedia: Rational Unified Process (RUP)
  • Wikipedia: software requirements specification
  • Programmers: Writing a Software Specification

So there are UML believers, UML skeptics and even UML haters, it depends on ... things.

I am a UML believer

• and so for example Mr. Kenji Hiranabe of Change Vision, Inc., a UML asta modeling tool company, and he says

  ... Is modeling obsolete? Is UML dead? I do not think so. In this article...

  as a preface to Agile Age Modeling: What you need to do next to Code to scale Agile Teams

• My favorite guide is what the Guru said in an interview with Mark Collins-Cope for Objective View on September 12, 2014.

  Grady Butch, creator of the Unified Modeling Language (UML) :

  "UML should be used for reasoning about alternatives. Put some diagrams. Drop some use cases against it. Drop these diagrams and then write some code against you, the best option. Repeat (and refactoring)."

How do you finally evaluate "..UML ... usually ... the real world .." depends on what you want to see and what the best software development you use in your own work

Answer 2

It depends on your role, in most developer roles you will rarely, if ever, use it. I see that this is useful if you are developing something, for example, as a new database structure or when archiving a new system or application.

This can be useful for leading developers, architects or IT managers at the stages of developing an application for exchanging ideas with business people, as well as for drawing up a plan for the development team that will build it.