|
RAD - Rapid Application Development
Skelta BPM.NET is based on set of ASP.NET reusable server components. This way it is possible to add BPM functionality to the application you are developing, just by drag & drop these server controls to any ASP.NET page. These server components are:
- Process Designer;
- Task Inbox;
- Forms Designer;
- Business Activity Monitoring;
- Queue Management;
- Hierchical Calendar and
- Process Management and Repository.
These controls delivers an entire modifyable user interface, so it be aligned with the hosting application aestethics, and also delivers an middleware API, so any feature can be programatically automated.
Skelta BPM.NET also exposes its high-end workflow services to developers, through an extended and detailed API. The Skelta BPM.NET services are:
- Workflow Engine;
- Email and SMS communication services;
- Task Scheduller;
- Load Balancing and Fault Taulerance services.
|
|
|
|
Four-Layer .NET Architecture
By adding Skelta BPM.NET components to your 3-layer .NET application, you are adding a new abstraction layer: The Business Processes layer.
With Skelta BPM.NET you split the Business Logic layer in two: Business Objects and Business Processes. Then, because Skelta BPM.NET exposes a friendly user interface, you can expose the application business processes to Business Users, without writing a single line of code.
Moreover, your application will gain competitive advantages in two important aspects:
- Easy maintenance: Due to Skelta BPM.NET processes repository and versioning, you can deploy new processes versions, or create and deploy new processes, without the need ot compiling and deploy the entire application and without impact on existing running processes.
- High reuse of Business Objects: With Skelta BPM.NET, instead of developing and compiling the entire application, you can develop components and make them available at Skelta BPM.NET Tool Box, so they can be used at the process and user interface levels. This decreases the time to develop new features while once again decrease the negative impact of new application versions deployment and users trainning.
| 3-Layer Architecture |
4-Layer Architecture |
| Presentation |
Presentation |
|
Business Logic |
Business Processes |
| Business Objects |
|
Database |
Database | |
|
|
|