Introducing Information Management for NoSQL

As Gartner warns in the report, adopting NoSQL storage can result in Information … read more

Introducing Quantitative Enterprise Architecture

It is rather ridiculous that the discussion on Data Driven Enterprise did not … read more

OWL Modelling for Information Architects

Business Abstraction delivered OWL training customised for experienced Information Architects. The target audience … read more

Implementing DaCeMo

Data-Centric Modelling comes with different approach to the process of modelling. The approach, known as “Hub and Spoke Modelling” or “Shared Modeller Approach”, has been proven highly effective for traditional Visual Modelling, however with DaCeMo it becomes a necessity.

Traditional Visual Modelling methods, like UML, BPMN or ArchiMate, claim to be “language everyone should speak”. It requires a lot of training and mentoring to be realistic. The common anti-pattern is that contractors, new or temporary team members model the way they see fit, ruining the consistency and making models unusable.

For over a decade Business Abstraction was offering  clients “Hub and Spoke Modelling”. Under that approach, an experienced Modeller (“Hub”) is working with Business Analysts, Data Analysts, Architects of all stripes (“Spokes”), to turn their knowledge into models. The Hub is the only one creating the models, with everyone else involved understanding and reviewing the models. Modeller, on the other hand, is not involved in any meeting outside of the modelling sessions, does not communicate with anyone other than “spokes”, focusing exclusively on modelling.

Hub and Spoke has been consistently delivering superior productivity, and is credited with saving several projects.

With DaCeMo however, having a dedicated modeller is a necessity rather than a high-productivity option. A DaCeMo Modeller is expected to possess a significant array of skills:

  • Been an OWL modelling practitioner with thorough understanding of properties and patterns;
  • Knowing and understanding commonly reused ontologies;
  • Understanding ontological and production (SWRL) reasoning;
  • Ability to abstract information to the Business, and Strategic level, abstracting from implementation details imposed by more restrictive models
  • Having practical understanding of how Semantic Graph impacts the enterprise
  • Having thorough understanding of DaCeMo topl ontology, and the underlying modelling methods.
  • Command DaCeMo visualisation and publishing resources.

You cannot expect to train such expert in a jiffy, let alone expect every BA and Architect to be one. A DaCeMo Modeller is expected to be a specialist skill,