Develop applications rapidly through Emakin BPM’s low-code nature , as designing the process graphically and using model-driven methodology.
Software is developed by creating a concept model and then transforming the model into source code.
The source code of an application lacks the clarity of the model and it is often hard to understand the original intention.
Programmers must constantly «wrap» and «unwrap» domain concepts into code constructs and vice versa. This is an error-prone process.
Implement software with an explicit graphical process model.
Directly implement an application’s process model.
Intentional programming when creating software.
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 show it’s purpose.
Domain experts are able to participate actively in the application development.
The manual transformation of the graphical process model into the code is not necessary.
If process model == execution model, then the implementation is self-documenting.
Today, workflow is far more than 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 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 is not 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 is closer to the way business people think than software engineering.