Howdy Ilaria,

A technique originating from systems analysis and software development, which is flexible and has a low slope learning curve as well, is flowcharting.

A flowchart is a type of diagram that represents an algorithm, methodology, workflow or process, showing the steps as boxes of various kinds, and their order by connecting them with arrows. This diagrammatic representation illustrates a solution model to a given problem. Flowcharts are used in analyzing, designing, documenting or managing a process, program or methodology in various application fields.

Flowcharts are used in designing and documenting processes, methodologies or ICT programs. Like other types of diagrams, they help visualizing the core of a method or algorithm, and thereby help us to understand the process, and to find flaws, bottlenecks, and other less-obvious features within it. There are many different types of flowcharts and each type has its own repertoire of boxes and notational conventions. The two most common types of boxes in a flowchart are:

- A processing step, usually called activity, and denoted as a rectangular box

a decision, usually denoted as a diamond.

- A flowchart is described as "cross-functional" when the page is divided into different lanes describing the control of different organizational units. A symbol appearing in a particular "lane" is within the control of that organizational unit. This technique allows the author to locate the responsibility for performing an action or making a decision correctly, showing the responsibility of each organizational unit for different parts of a single process.

Flowcharts depict certain aspects of processes and they are usually complemented by other types of diagrams. The flowchart has been defined as one of the seven basic tools of quality control, next to the histogram, Pareto chart, check sheet, control chart, cause-and-effect diagram, and the scatter diagram. Similarly, in UML, a standard concept-modeling notation used in software development, the activity diagram, which is a type of flowchart, is just one of the many different diagram types. The terms "flowchart" and "flow chart" are used interchangeably. The underlying graph structure of a flow chart is a flow graph, which abstracts away node types, their contents and other ancillary information.

Flowcharts can be modeled from the perspective of different user groups, such as managers, system analysts and clerks. There are four general types:

- Document flowcharts, showing controls over a document-flow through a system.

- Data flowcharts, showing controls over a data-flow in a system.

- System flowcharts showing controls at a physical or resource level.

- Program flowchart, showing the controls in a program within a system.

Notice that every type of flowchart focuses on some kind of control, rather than on the particular flow itself. However, there are several of these classifications. Three basic types of flowcharts can be distinguished at this level. The system flowchart, the general flowchart and the detailed flowchart.

For example two kinds of flowcharts can be used in solution planning:

- System flowcharts and program flowcharts...". More recently more differentation has been introduced in flowcharting. These include for example decision flowcharts, logic flowcharts, systems (analysis) flowcharts, product flowcharts and process flowcharts. These are just a few of the different types of flowcharts that can be used in science, business or governmental processes.

Related diagramming techniques are:

The Activity diagram; the control flow diagram; the control flow graph; the data flow diagram; the deployment flowchart; the Drakon-chart; the flow map; the functional flow block diagram; the Nassi–Shneiderman diagram; Petri nets; the Sankey diagram; the state diagram; the tree structure and the Warnier/Orr diagram.

Many flowchart software packages can be found on the Web, free of charge or with some charge. SmartDraw is a quite good software package for a low fee, with a broad application field.

So Ilaria, I hope you can find somthing of your liking in this jungle of approaches.

Good luck and lots of success,

Frank

Why not to try MPS domain specific language, its free and many research uses it. UML is too specific to Object-orientation, but MPS can bend to alternatives. 

https://www.jetbrains.com/mps/

We made a video presentation of it: https://www.youtube.com/watch?v=ZlQXWB0zplY

There is a very nice paper from Mernik on domain specific languages: When and how to develop domain-specific languages attached below

https://www.jetbrains.com/mps/

https://www.youtube.com/watch?v=ZlQXWB0zplY

Article When and How to Develop Domain-Specific Languages

Although UML seems to be the most used modelling notation, some studies reveal a lack of comprehension on it, see Otero & Dolado (2005), where authors evaluate semantic comprehension of UML against OML. Authors observe better levels of comprehension with respect to the Open Modeling Language. 

Taking into account this piece of evidence, maybe it is worth to try the OML language (http://www.amazon.es/Modeling-Language-Reference-Manual-Library/dp/0521648238).

kinds,

The core of the BPMN 2.0 (Business Process Model and Notation) could be suitable for your purpose. This notation comes from a business perspective and is therefore not so technical and theoretic.

For example, there are plugins for Microsoft Visio or Online-Tools (Signavio) to draw them.

Good Morning Ilaria,

3 examples:

UML

https://www.researchgate.net/publication/280302139_Anlisis_de_consistencia_de_Casos_de_Uso_con_simuladores_de_autmatas_finitos

BPMN 2.0

https://www.researchgate.net/publication/280302120_Circuitos_de_documentos_configurables._Aproximacin_a_un_modelo_de_datos_y_algoritmo_de_implementacin

PATTERNS

https://www.researchgate.net/publication/280302061_Implementacin_de_Patrones_en_la_Validacin_de_Modelos_Conceptuales?ev=prf_pub

Conference Paper Análisis de consistencia de Casos de Uso con simuladores de ...

Conference Paper Circuitos de documentos configurables. Aproximación a un mod...

Conference Paper Implementación de Patrones en la Validación de Modelos Conceptuales.

What about SEMAT?   

http://www.omg.org/spec/Essence/

http://semat.org

if you don't have much time to learn any new language, i would suggest that you use the basics of any workflow visual descriptions and define your own wording and shapes using colors for example

- actor: like in UML the simple illustration, or use human avatar pictues, just google it

- data: box (grey for example) 

- actions: rounded box (blue)

- decision : diamond (condition, true, false)

- loops: with a circular arrow indicating iterations, with 1, * for multiplicity

- compartments: use swim lanes to separate responsibilities and actions

again, as long as you define the meaning of these instruments in your document or presentation, you are free to use what ever you feel appropriate. it's a matter of definition.

good luck

Hi Ilaria,

While standard "generic" languages such as UML and BPMN can probably be used with some limitations to serve your needs, you could also have a look at defining your own language specific for your domain. This need not be a complicated and time consuming effort. There are powerful frameworks out there that can support this and you could have your own language (graphical or textual), complete with a studio to support it and that suits your problem in a matter of days. 

Have a look at some of the Eclipse modelling frameworks for this:

- Eclipse Modelling Framework (the underlying technology for a number of more feature-rich frameworks)

- Eclipse Sirius (for easy to create graphical languages that can be used for modelling things such as workflows or structures and data artefacts) - check out their tutorial to get started

- Eclipse Xtext (for easy to create textual languages that can also be part of your solution)

Hope this helps,

Adrian.

https://eclipse.org/modeling/emf/

https://eclipse.org/sirius/

https://eclipse.org/Xtext/

Did you try UML activity diagrams with swim lanes?

You can use 'EPF Composer' tool to model all kinds of methods/methodologies/best practices. This software is free and is based on SPEM standard.

Object-Oriented Development and the Unified Modeling Language UML

http://www.cs.kent.edu/~jmaletic/cs63901/lectures/UML.pdf

I would use BPMN. 

Also, we present here a homemade tool to work with UML requirements

https://www.researchgate.net/publication/284633757_Herramienta_para_administracin_y_validacin_de_requerimientos_de_sistemas

Article Herramienta para administración y validación de requerimient...

 Thank you, Oscar.

Your work seems interesting...do you have the English version of it? 

Not yet. I let you know when an English version would be available.