UML's Use Cases are widely used for requirements capture, but they encourage a system-centric view too early and lack the semantics to properly model complete business processes — including flow, costs, timing, organisational responsibility, and manual activities. This paper proposes a richer process modelling notation that forms a superset of Use Cases and Activity Diagrams, and transitions seamlessly from high-level stakeholder models all the way to rigorous design specifications. The approach, developed and refined through teaching and consulting, addresses a persistent gap in object-oriented analysis and enterprise engineering.
The Difference Between Process Architecture and Process Modeling (and why you should care)
Process modelling initiatives frequently consume months of effort without producing meaningful results — often because teams dive into detailed models before anyone understands the big picture. This paper argues for a clear separation between process architecture (a rapid, high-level view of what processes exist, who they serve, and how they connect) and detailed process modelling and design, while keeping both perspectives fully integrated. Drawing on case studies from financial services organisations, it shows how this approach can cut project time dramatically and produce models that business stakeholders actually engage with.