Oxford defines it as “a diagram of the sequence of movements or actions of people or things involved in a complex system or activity.”
In my case, flowcharts signify the start and end of a certain user journey. This journey involves certain inputs, processes, decisions, and outputs (which could be an input to another process).
Use cases of flowcharts span multiple domains from systems design, business analysis, process improvement, project management and software development.
In the context of process or systems, actors or swimlanes is the party or individual responsible for a specific input, sub-process, or output.
In the context of process or systems, inputs are the trigger or cause before a specific process can start.
Example can be a document or an output from another process.
In the context of process or systems, outputs are the result after a specific process is conducted.
Example can be a document or an update to a database.
In the context of process or systems, it is a Yes/No question that needs to be answered before performing a specific process.
An answer to a “yes” question performs one process. An answer to a “no” performs another/different process.
There are other symbols used in flowcharting as explained here.
PS. The actor or swimlane image above is not an actual symbol used in flowcharting.