User requirements specifications: a hierarchical structure covering strategical, tactical and operational requirements.

Abstract

The present study is a long-term review and follow-up on conclusions and recommendations on the role and contents of a User Requirements Specification Document (URD) from a previous in-depth case study. The follow-up comprises a succession of investigations and two case studies to explore the role and contents of a URD within systems development and assessment, thereby gradually extending and refining the original recommendations. Finally, the recommended three-layered structure and approach for a URD were applied in full scale within a real-life project, in which the URD serves as the basis for a Call for Tender. The preparation was entirely user-driven with the aid of a consultant for four man months. The present paper outlines the essence of the approach and the outcome of applying the recommended structure, with numerous examples of the implications.