Develop applications rapidly through emakin BPM’s low-code concept. Design each process graphically and using model-driven methodology.
Today, software is developed by first creating a concept model and then transforming the model into source code.
However, an application’s source code lacks the clarity of the model and it’s often hard to understand and to decipher the original intention.
Programmers must constantly «wrap» and «unwrap» domain concepts into the source code and vice versa. This is an error-prone process, which can be completely avoided by using BPM.
Implement software with an explicit graphical process model.
Directly implement an application’s process model.
Intentional programming when creating software.
Apply Service-Oriented Architecture (SOA) as a general architecture model.
Allows end-users to customize the application’s process model.
The implementation of an application clearly shows its purpose.
Domain experts are able to participate actively in application development.
The manual transformation of the graphical process model into code isn’t necessary.
If the process model == the execution model, then the implementation is self-documenting.
Today, “workflow” means far more than being simply an aid to manage documents and forms routing — it has become a systems development platform in its own right and a way to develop new business applications.
Advocates of BPM point to the fact that 75% of workflow projects succeed while 75% of application development projects fail.
It appears that defining a business system in terms of work item flow is easier, and more flexible than trying to develop the same functionality as bespoke software.
This isn’t surprising, since the flow of work among people, systems, and machines is a natural way to envision, design, build, manage, and operate an information technology infrastructure. It’s more akin to the way business people think than it is to software engineering.