Why prepare a URS?

Are you adding to a system, upgrading a system, or completely changing it?

The "User Requirements Specification" (URS) is a powerful document that can be used to:

• Set a vision for the system and the benefits anticipated
• Clarify scope and boundaries, and interactions with other systems
• Agree requirements between departments
• Assess software and suppliers, often as part of a tender document of some kind
• Ensure software demonstrations cover what's important
• Avoid risk of inappropriate purchases (and they do otherwise happen!)
• Steer implementation to achieve the benefits

It's common for key issues to be highlighted by preparing a URS, that would not otherwise have become apparent until too late.

Depending on the scope of the system, the document can be very short, or somewhat longer. It's a matter of being concise, but with sufficient detail to achieve its purpose. Aspects to cover include, inter alia:

• Business background and future
• Objectives and benefits
• Systems context, architecture and interactions
• Management information
• Functional requirements, highlighting core aspects and what may be different
• Transaction examples
• Sizing
• Existing systems, and any specific issues to address
• Technical preferences
• Supplier aspects

If you would like to discuss how to go about preparing a URS, do contact me.
Chris Challis
challisc @ camwells.co.uk
+44(0)1628 632914