uml (Unified Modeling Language) arises from the need to establish a unified language for modeling Any professional ophware project, but it is really necessary to have all the diagrams that UML does not offer, There are currently 8 and these dictate the correct form of software development.

Unified modeling language is the meaning in Spanish for these acronyms. Through UML it is possible establish the requirements and structures necessary to establish a software system prior to the process Code writing length.

In other words, just like an architect needs plans of the building that will build, the work team You need UML diagrams that dictate the topics of the software to be developed, which favor the members participate and intercommunicate easily, and ranging from analysts, designers, area specialists and of course programmers.

Since UML is used in medium-high complexity systems, high-level languages ​​are expected And of course object -oriented programming, so to work at UML can be considered a pre-requisite, have experience in object-oriented language, have complex and of course development Develop according to software architecture standards.

concepts/diagrams

Among the fundamental concepts of object orientation are the following:

  • a model is an abstraction of the problem that is attempted resolve.

  • A domain is the world where the problem comes from.
  • a model consists of objects that interact with each other sending messages.
  • each object has its own characteristics (attributes) and operations that can perform (methods); the values ​​assigned to an object at a certain time determine its State.

  • a class is a mold to describe an object that groups characteristics (attributes) and behaviors (methods).
  • the objects are instances of classes.

The 8 diagrams that form the UML base are listed below, and dictate the way it is designed a system:

  • use-cua

  • classes

  • objects

  • sequence

  • collaboration

  • state (Statechart)

  • activity

  • components

use cases

object diagram
is a type of diagram that shows a Complete or partial view of the objects of a system at an instant of specific execution.

sequence diagram
the diagram of Sequence is a type of diagram used to model interaction between objects.

File: creapais.png

collaboration diagram
a Collaboration is essentially a diagram that shows organized interactions around roles Unlike sequence diagrams, collaboration diagrams, also called Communication diagrams explicitly show roles relationships.

eg. Diagram status of a washing machine.

EXTERNAL IMAGE DDE.JPG

activity diagram (the famous diagram of Flow!)
The flow diagram or Activity diagram is the graphical representation of the algorithm or process. 

Component diagram
a component diagram, such as A software system is divided into components and shows the dependencies between them. The components Physics include files, headwaters, shared libraries, modules, executables, or packages.

State diagram in UML

The theme is enough and each of these diagrams has its rules, I invite you to learn more about UML on this wiki which is dedicated to the subject.

https://wikium.wikispaces.com/

Personally, personally, personally, personally, personally, I consider that these diagrams for professional and well documented software are necessary, since in a future, if someone else takes up the project that we work, with these diagrams he will understand it from faster and so, a more software development process will be carried out controlled.