...
Business logic (also called domain logic) defines the real-world business rules that determine how data can be created, stored, and changed (see Wikipedia definition here). Some applications use rigid business logic that is imposed or constrained by the software vendor. These This approach may limit what data can be collected or what quality control measures can be implemented in the field. WSG InventoryManager System, by contrast, is highly flexible and supports configurable business logic throughout the system. This requires, however, some configuration in order to achieve the desired business logic for your implementation.
...
Using a single data model results in all data entering a single database, where it can be easier to manage, backup, analyze.
Number of data models | Pros | Cons |
|---|---|---|
Single | Single database to backup, single set of analysis and reporting tools, single map in InventoryManager | Size of database can cause performance issues when viewing data on map, or when downloading data. Use of download filters and hosted feature layer views can mitigate this Requires additional rules, settings, etc. to ensure field data collection is optimized (e.g., hide unnecessary fields) for each cruise. |
Few | Can result in more parsimonious data models tailored to specific cruise types | Greater number of databases to backup, manage. |
Many | Provides physical separation of data into different databases to enable greater independence of backup, analysis, etc. | Organization must feel confident with designing and implementing data models in ArcGIS, organization should learn to add and manage map pages in InventoryManager. |
Business Logic Examples
The table below contains a few examples of business logic that have emerged from requirements gathering along with the approach that can be used to implement it. While there may be other ways to implement this logic within the system, the rational for the approach described is listed to help understand why that approach was selected.
Business Logic Narrative | Approach | Rational |
|---|---|---|
Our organization ALWAYS requires the measurement of DBH in the field. For cruise spec 1, loblolly pine and slash pine sawtimber must be at least 6” DBH. | Data model •Type – integer or decimal •Nullable – no (required) •Domain – not needed to meet this required but could still be relevant Rule •Criteria 1: If Field_Spec = 1 •Criteria 2: If Species IN(LP,SP) •Criteria 3: If Product = Saw •Then: DBH cannot be < 6 | Since DBH is always required, it can be enforced at the data model level by setting the field to non-nullable. Business rule with 3 criteria is used to prevent selection of Saw, when using Field Spec 1, for LP or SP trees that are less than 6” DBH. |
For most cruises merch height is not required for every tree. When it is recorded, however, we want it to be recorded as height to the nearest 5 feet. The minimum height allowed is 5 feet. The maximum height is 60 feet. | Data model •Type – integer •Nullable – yes (not required) •Domain – Coded value (5, 10, 15, 20, … , 55, 60) |