Enter "fine grained process model" (including the quotation marks) and start reading!

https://en.wikipedia.org/wiki/Process_modeling#By_granularity should also give some orientation.

Summarizing: some kind of fine grained process model will usually be implemented on the implementation/coding/testing levels in any reasonable development department. Whereas coarser models will prevail on the management levels.

This can also be viewed in terms of parallel processing speak which nowadays refers to task based parallelism (coarse grained) and data parallelism (fine grained). Opencl talks about these but tends to concentrate on data parallelism as GPUs were its main target.  But with heterogeneous parallelism (a mix of both types and hence different hardware components we get full range which is more normal for systems. To answer your question: fine grained process will be small domain (limited - but focussed) and if you like,  tending towards specialist, as opposed to the coarse grained much larger domain with generalisation and less detail (and yes managers prefer these!). Large systems will be a patchy mix of both. Often  hardware system are example of heterogeneous parallel processing - several processors (CPU, DSP, FPGA etc)  with different roles but interacting.

In my view, software engineering process models have evolved over time and we come across various models with varying life cycles. One should not therefore, be overly worried about the evolution as long as basic models are pursued and quality models are adhered to.

Granularity:

Granularity refers to the level of detail of a process model and affects the kind of guidance, explanation and trace that can be provided.

Coarse-grained models:

Coarse-grained models, aim at simulating the behavior of Complex systems using their coarse-grained (simplified) representation.

Project manager, customer representatives, the general, top-level, or middle management require rather coarse-grained process description as they want to gain an overview of time, budget, and resource planning for their decisions.

Fine Grain Activity Models:

These are more detailed models of a specific process, which are used for understanding and improving existing processes.

Fine granularity provides more detailed capability. The nature of granularity needed is dependent on the situation at hand.

Software engineers, users, testers, analysts, or software system architects will prefer a fine-grained process model where the details of the model can provide them with instructions and important execution dependencies such as the dependencies between people.