September 26, 2013
Flowcharts have been used for quite some time for visualizing and organizing business processes and making them more efficient (e.g. business process reengineering).
Now flowcharts are being used to build and link reusable programming code.
NoFlo or Flow-Based Programming (FBP) simplifies application development by using libraries of pre-written code and then dragging and dropping them into your process flows.
This leverages objected-oriented programming (OOP) and uses modules of open-source code, which are linked together to create a full program that solves a business problem.
The flowchart helps to avoid spaghetti code by providing for a more organized, modular, object-based development environment.
These flowcharts can not only be a collaborative tool where developers can build or map code, but can also be part of the systems documentation that ensures a higher-level of understanding of the total programming solution.
To me, this programming paradigm seems to have real legs:
- A process-based model for decomposing solutions
- Simple information visualization through a common flowcharting toolset, and
- Reusable object code from programming libraries in the cloud.
I'd say YesFLo--this makes a lot of programming sense. ;-)