 |
|
 |
 |
 |
All modelling solutions at some stage require taking into account the data required for business cases being processed or for business rules to execute against. However, most models expect there to be data analysts to carry out this task, often with no regard to processes.
Corporate Modelling has a differing approach, working from the process as being the central aspect of the model and the data being there only to facilitate the processes that are involved and required. As a result of this approach we can allow the business team to create candidate data requirements as they define their processes in a simple flat file approach which is then fed to the Logical Data Modeller. We can also allow them to associate an existing data model with their process which has already been modelled.
Our approach to business centric data models, as defined in the book Business Process Implementation, is basically to capture all the data for the process request or service request and add to this set of data fields as the process gets defined adding in more fields as business rules require them should they not be in the model already.
Our approach to data models is that there are only simple attributes such as an address line or zip code and complex attributes such as an address or customer. Complex attributes are made up of other simple or complex attributes and the relationships between these complex attributes allows us to pick the correct approach for deploying these to databases, either relational or object orientated.
This simple approach together with the ability for type definitions, such as say address types, to have the values defined and stored in the model, makes the understanding of the model, its deployment and its usability in the business rules definition much easier. Business modelling staff can work on a logical rather than purely a physical approach and technical team members can work at either.
|
 |
 |
|
|