www.usoft.com To www.usoft.com

Topics started by Frans.Willem.Duijnhouwer

3 Topics

Frans.Willem.Duijnhouwer
Frans.Willem.Duijnhouwer
published in Community blog

Does using the USoft platform cause vendor lock-in?Vendor lock-in

Does using the USoft platform cause vendor lock-in? Customers sometimes ask USoft whether they become completely dependent on us and our software if they go into business with USoft. In short, whether a so-called vendor lock-in occurs when using the USoft low-code platform? Fortunately, this is not the case. This short article explains why not.  What is a vendor lock-in?  To begin, it is important to provide a good description of vendor lock-in. A vendor lock-in means that customers are and remain dependent on a vendor to a greater or lesser extent. For example, customers cannot easily migrate from one product to another. In addition, changing or adding functionality may no longer be possible or may be limited. This is something you will always need the vendor to address. With any technology, there is always a certain degree of vendor lock-in. Even open-source software is subject to some degree of lock-in. There are often no license fees and sometimes there is not even a vendor, but th

370
Frans.Willem.Duijnhouwer
1 year ago
Frans.Willem.Duijnhouwer
Frans.Willem.Duijnhouwer
published in Community blog

What is a Rules Engine?

Business rules based on human logic Automate the 'rules' instead of the processes The use of a Rules Engine The advantages of a rules engine in brief  When to use a rules engine? The core of the USoft low-code platform is the rules engine. This ensures optimal data consistency and thus safeguards the quality of all data entering the system and possibly being redistributed to other systems. The rules engine also simplifies system programming and enables us to work in low-code. But what exactly is a rules engine? How exactly does it guarantee quality and when is it wise to use a rules engine? In this article I will explain it.To explain the rules engine it is good to start with an analogy. Rules engines start from well-defined definitions:There are persons. Pieter is a person. Abby is a person. A person can love another person. If a person loves another person, they should send him or her flowers. Abby loves Pieter.It is a simplistic model, but in this we can recognize: the data model, d

1972
Frans.Willem.Duijnhouwer
2 years ago
Frans.Willem.Duijnhouwer
Frans.Willem.Duijnhouwer
published in Share your best practices

Five tips to work efficiently with USoft Studio

Last few months I have been working with USoft Studio a lot to get to understand and at the same time capture the business rules for one of our customers. Within USoft Studio, we use the Semantics for Business Vocabulary and Rules (SBVR) and standard techniques to create diagrams for object-fact modelling (SBVR diagrams), process flows (BPMN 2.0) and/or database modelling (ER diagrams). There are a lot of manuals available on these topics, but when working with USoft Studio I got some real hands-on experience, which might help you all as well. This short article aims to give you tips to work with USoft Studio as efficiently as possible, based on my personal experience.Tip 1. Do not try to define the entire galaxyWhen defining a set of rules, a pitfall is that you try to define everything. Definitions will result in a nice green term noun concept to indicate you have defined what you mean with it. This “reward” makes you want to get more and more green terms, which is a good thing, but

540
Frans.Willem.Duijnhouwer
2 years ago

Badge winners

Show all badges
Terms & ConditionsCookie settings