Cubetto Flowchart

"In elementary algebra, a quadratic equation (from the Latin quadratus for "square") is any equation having the form
ax^2+bx+c=0
where x represents an unknown, and a, b, and c are constants with a not equal to 0. If a = 0, then the equation is linear, not quadratic. The constants a, b, and c are called, respectively, the quadratic coefficient, the linear coefficient and the constant or free term.
Because the quadratic equation involves only one unknown, it is called "univariate". The quadratic equation only contains powers of x that are non-negative integers, and therefore it is a polynomial equation, and in particular it is a second degree polynomial equation since the greatest power is two.
Quadratic equations can be solved by a process known in American English as factoring and in other varieties of English as factorising, by completing the square, by using the quadratic formula, or by graphing." [Quadratic equation. Wikipedia]
The flowchart example "Solving quadratic equation algorithm" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Mathematics solution from the Science and Education area of ConceptDraw Solution Park.

This example was redesigned from the Wikipedia file: LastResortHotel BookRoom Process.png. [en.wikipedia.org/ wiki/ File:LastResortHotel_ BookRoom_ Process.png]
This file is licensed under the Creative Commons Attribution-ShareAlike 3.0 License. [creativecommons.org/ licenses/ by-sa/ 3.0/ ]
"Event partitioning is an easy-to-apply systems analysis technique that helps the analyst organize requirements for large systems into a collection of smaller, simpler, minimally-connected, easier-to-understand ‘mini systems’ / use cases. ...
Defining requirements.
Single process in a fictitious hotel using data flow diagram notation.
Single use case in a fictitious hotel using use case diagram notation.
This approach helps the analyst to decompose the system into ‘mentally bite-sized’ mini-systems using events that require a planned response. The level of detail of each response is at the level of ‘primary use cases’. Each planned response may be modelled using DFD notation or as a single use case using use case diagram notation.
The basic flow within a process or use case can usually be described in a relatively small number of steps, often fewer than twenty or thirty, possibly using something like ‘structured English’. Ideally, all of the steps would be visible all at once (often a page or less). The intention is to reduce one of the risks associated with short-term memory, namely, forgetting what is not immediately visible (‘out of sight, out of mind’). ...
Single process in a fictitious hotel using data flow diagram notation." [Event partitioning. Wikipedia]
The DFD example "Last resort hotel book room process" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Data Flow Diagrams solution from the Software Development area of ConceptDraw Solution Park.