How often is UML diagramming used "in the real world?" -

almost every 1 of programming classes has made use of uml, none have explained when or might used in professional setting. done every single file in project, or there rule of thumb of when might want use it? also, more commonly done hand (which i've dreaded) or using sort of generator?

_{this question example of opinion-based , broad question no real problem solve behind , no 1 correct possible answer}

certainly in amount of millions of software developers there learned use uml , use it. , there either did not learn use uml or don't use whatever reason

• i recall in pre-agile era believed no "big" software can realized without thorough analysis , modeling phase , no "big" software contract can signed if business documents don't include uml-style pictures

  and in countries still true , government-owned agencies declare kind of documentation software contractor must provide, , of requirements uml picture form

  see also:

  • wikipedia: rational unified process (rup)
  • wikipedia: software requirements specification
  • programmers: writing software requirement specification

so there uml believers, uml skeptics , uml haters, it depends on ... things.

i'm uml believer

• and example mr. kenji hiranabe change vision, inc company behind astah uml modeling tool , says

  ...is modeling obsolete? uml dead? don't think so. in article...

  as foreword article modeling in agile age: keep next code scale agile teams

• my favorite guideline guru said in interview mark collins-cope objective view magazine on sep 12, 2014

  grady booch, creator of unified modelling language (uml):

  "the uml should used reason alternatives. put diagrams. throw use cases against it. throw away diagrams write code against best decision. repeat (and refactor)"

how evaluate "..uml...commonly...real world.." depends on want see , software development best practices adopt in your own work