The number of IT project overspends and failures suggest that many IT projects do not conform to requirements. Despite decades of development the IT industry still seems to lack an effective method of ensuring that a project will be right first time. This paper outlines an ORM based requirements engineering process that aims to reduce the number of IT project failures. The main deliverable of the process is a formal description of WHAT a system is required to do without reference to HOW is to be done. Data or process, which comes first? This paper answers this question by showing how to define processes by starting with an object-role model. To use the approach in this paper you will need the Object-Role Modeling tool embedded within the database function of Microsoft Visual Studio for Enterprise Architects 2003 or later together with two referenced books [Halpin 01] and [Halpin 03].