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.