What Is a BPUA Application?

A BPUA application is not a runtime process and not a business process unit. A BPUA application is a composition of business process units (use cases) connected by orchestration rules.

Application as Composition

A use case is a closed business unit. It owns its internal states, transitions, handlers, and business rules.

An application does not own business logic. Its responsibility is to connect use cases together.

In BPUA, an application defines:

• which use cases belong together
• which use case starts first
• which use case may call another use case
• which service handler should receive cross-use-case requests
• which exit states redirect into other use cases

Application Is Not a Runtime Unit

Runtime execution belongs to use case layers.

For example:

Department.SL
Department.BL
Department.DPL
Department.DAL
        

These layers are runtime units. The application is only the orchestration map that connects them.

Application and Service Handlers

When one use case needs functionality from another use case, it raises an event to the application.

The application redirects that event to the appropriate service handler of another use case.

This preserves use case independence while allowing reuse of business capabilities.

Summary

A BPUA application is a composition unit. It does not execute business logic. It orchestrates independent use cases and defines redirections between them.

Table of Content BPUA Chapter Previous: BPUA State Machine Profile Next: Structure of a BPUA Application

 

---

Business Process Programming in .Net
© 2004-2026 Laskarzhevsky Software Inc.
Unless otherwise noted, the content of this website is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0).
Code examples are provided under the MIT License.
You are free to share and adapt the material provided that appropriate credit is given and any modifications are clearly indicated.
The information provided on this website is for educational purposes only.
The author and publisher make no warranties regarding the completeness or suitability of the information and are not responsible for any damages resulting from its use.