📄️ Some business rules require implementation
The USoft Studio tool supports the idea that some business rules require implementation, and others don't.
📄️ What implementation for your business rule?
Once you have decided that your business rule needs an implementation, the next step is to decide what type of implementation that should be. Choosing the best implementation for a rule is a primary skill of trained USoft developers. A business rule may be implemented in USoft in many different ways:
📄️ Implementing a rule: the process
As a developer, in a low-code platform such as USoft, you do not spend most of your time actually building an implementation.
📄️ Interpreting a business rule: example
A business rule is short and easy-to-read. But as a USoft developer, to find out how to implement it, you need to spend time interpreting the rule. Look at the rule from all sides. Also look around in Studio for additional cues to meaning and intent, and look around in the USoft implementations to see what is already there and how your implementation work will fit in.
📄️ Subject area dividers: Business areas, business objects, rule sets
In USoft, as a development team, you can optionally classify both specifications (such as business rules) and implementations by business area, by business object, and by rule set.
📄️ Implementation registration
In USoft, as a development team, you can optionally register that some specification (typically, a business rule) has been implemented in some way.
📄️ Formulations in USoft Definer
A formulation in USoft is a carefully worded statement that expresses in natural language (English or Dutch) some term or definition or business rule that helps to clarify how a business is conducted:
📄️ Vocabularies in USoft Definer
See also
📄️ Tasks and progress flags
USoft Studio has a set of progress flags. They are checkboxes that optionally allows your team to keep track of who defined, approved, built/implemented, cross-checked, tested, and documented an item.