Skip to Content
Author's profile photo Former Member

Setting the Granularity or Appropriate Level of Detail for Modeling Business Processes

In a previous article (Modeling Business Processes Using BPMN and ARIS) I dealt with modeling business processes using the Business Process Modeling Notation (BPMN), which is a relatively easy task. A more complex task to deal with is finding the right level of granularity (or level of detail) to guide you when modeling your business processes. In this article, I suggest several criteria that you can follow to define what level of detail to use. The article can be found here I’ll be happy to hear any opinion, comments … Natty Gur.

Assigned tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo David Halitsky
      David Halitsky
      During the largest SAP R/3 implementation in the contintental US as of 2000, serious consideration was given to using SCOR as an intermediate model between the legacy business model and the SAP business model.

      In the end, unfortunately, this idea was not adopted.

      One of the many reasons I included a "staged" slice in the "diachronic metadata repository" was to permit mappings of business functions from legacy to SCOR to SAP instead of directly from legacy to SAP.

      When clients are nervous about being "shoehorned" into the SAP view of the world too quickly, it is sometimes very beneficial to create the infrastructure whereby they can map from legacy to SCOR first.  It creates the impression that everything is on "the up-and-up" and not just being done to get the quickest possible conversion to SAP.  And apart from creating this impression, it actually does help keep things on "the up-and-up".


      Author's profile photo Benny Schaich-Lebek
      Benny Schaich-Lebek
      The link to the article is this:

      Original link in the blog is broken.