Work Product Descriptor (Artifact): Logical Process Model
The Logical Process Model defines the logical activities and processes, involved in and important to the business. The processes in the system are incorporated into the model, and may include relationships to the entities and roles involved in the processes.
Purpose

The Logical Process Model is a view of the structure of logical activities, which produce and consume logical entities, and that when structured into a model define the logical processes.

The Business Process Model defines the business processes involved in the system under study, as defined by the scope of the modeling effort. The objective is to clearly define the business processes involved—what the system does in support of the business. The definition must be valid for the defined scope, and must eliminate any ambiguity regarding what they represent.

The workflow of a business activity describes what the business must do to provide the value the business actor requires. The business processes consists of a sequence of activities that, together, produce something of value for the business actor. The workflow often consists of a basic flow and one or more alternative flows. The structure of the workflow is described graphically with the help of a BPMN-based diagram. In summary, a business process is a sequence of activities that, together, produce something of value to the business actor.  

Optionally, relationships between business activities and business entities may be defined, namely the business entities consumed, produced or modified by the activity. This should be limited since they can quickly clutter the diagram and make it more confusing.

Relationships
Contained Artifacts
RolesResponsible: Modified By:
Input ToMandatory: Optional: External:
  • None
Output From
Main Description

The Logical Process viewpoint defines the Activities and Processes involved in the system or enterprise, as defined by the scope of the modeling effort. Depending upon the context and scope of the modeling effort, the level of detail at this logical level may be quite extensive or be very broad and conceptual. It illustrates the sequence flow of the Logical Activities, forming a process, along with events, gateways and actors. It is a way of expressing the business workflows through the definition of individual activities, events, gateways and the flow between them. Logical Entities added to this diagram help in understanding how they are involved in the processes, but this should be done sparingly since they can add confusion and clutter to the diagram. See: Whitepaper: BPMN Resources.

Properties
Optional
Planned
Illustrations
Templates
Reports
Tailoring
Impact of not having

Failure to produce this model means you run the risk that architects and designers will give only superficial attention to the way the business operates. They will do what they know best, which is to design and build software in the absence of proper business knowledge. The result often is that the constructed systems do not support the needs of the business.

Representation Options

A Logical Process Model is a BPMN Collaboration Diagram illustrating the sequence flow of the business process, along with the organizations and actors.

UML Representation: Package stereotyped as «LPL_LPM» containing BPMN Collaboration diagrams.

A Logical Process Model may have the following properties:

  • Introduction: A textual description that serves as a brief introduction to the model.
  • Packages: The packages in the model, representing a hierarchy of activities.
  • Collaboration Diagram: The highest level model (package) illustrating the main activities of the system.
  • Activities: The activities and structured activities in the model, representing a hierarchy of activities stereotyped as «LPL_Subprocess», «LPL_Task», etc.
  • Events: The events in the model, stereotyped as «LPL_Subprocess», «LPL_Task», etc.
  • Entities:  Entities in the model stereotyped as «LPL_Start», «LPL_End», etc.
  • Roles: Roles in the model stereotyped as «LPL_Role».
  • Relationships: The relationships in the model, owned by the packages.
  • Diagrams: The diagrams in the model, owned by the packages.

The Logical Process Model is a BPMN Collaboration Diagram (or set of them).

Most things defined at the logical level will go on to be described in detail during the definition of the Technical level. This artifact is generally enclosed within the Logical Perspective artifact.

The Logical Process Model is a way of expressing the workflows through the definition of individual activities and the flow between them. Logical entities added to this diagram help in understanding how they are involved in the processes in terms of object flows. However, this should be limited since they can quickly clutter the diagram.

Decide on the following:

  • The activity structure for the Logical Process Model, see: Guideline: Pool and Lane Usage;
  • Properties to include;
  • Whether or not any extensions to the Unified Modeling Language (UML) are needed; additional stereotypes or profile for example;
  • The level of formality and detail in the model (see  Guideline: Logical Perspective);
  • Tailoring applicable to individual sub-work products;
  • Whether a single model or multiple models will be used.

The modeling elements are too extensive to include, see: Supporting Material: LPL Summary.

More Information
Concepts
Guidelines
Supporting Materials
© David W. Enstrom, 2025. All rights reserved.