Business Logic can make your Package Development more agile, can reduce customization costs, and can reduce merge costs for subsequent release cycles.
Business Logic is 50% of your system. Espresso Logic addresses over 95% of this logic, reducing it over an order of magnitude - each rule represents a page of code. And rules are extensible, enabling you to automate not just simple examples, but complex problems such as cloning an order, payment processing, or exploding a bill of materials.
Such agility provides a strategic competitive advantage is delivering packages.
Communicating what your product does is always a challenge. Logic Filtering can provide a transparent view of your systems' business processes, the Use Cases, the Requirements for each - with full traceability to the logic that implements them.
Customers are more likely to buy what they can more readily understand.
Classic packaged systems incur enormous costs for customization via code. With Espresso Logic, such customization is provided in Logic Classes. Such customized logic classes can extend and override core (delivered) logic classes, and automatic dependency-based logic ordering ensures the revised logic runs in the correct order.
This can represent a dramatic reduction in customization costs for consumers. Suppliers can improve margins by reducing time and material installation costs.
This is a strategic competitive advantage. Package suppliers utilizing a logic-driven "applitecture" can compete not only by getting to market faster, but also by enabling their customers to extend and customize the package faster and easier.
Even worse, traditional approaches often require expensive code merges when new versions of the core product is released. Espresso Logic short-circuits this entire problem using inheritance with dependency-based ordering. Customizations - represented in extended Logic (sub) Classes, simply inherit newly supplied core product logic - no merging is required for business logic.