Creating a User Requirements Specification (URS)

URS
Life without a good URS

Purpose of a URS:

  • Specify guiding regulations and industry and site standards the system must meet
  • Specify deliverables

Tips:

  1. Ensure each requirement has a unique number. This is for ease of traceability and referencing in other documents
  2. Evaluate the impact to quality in the URS itself. This will allow agreement up front for what requirements will need to be tested as part of qualification/validation, and which can be safety ignored.
  3. Each requirement should be specific and measureable so that it can be easily tested. While it’s tempting to include statements like “The XYZ system shall comply with applicable regulations” this statement really becomes meaningless because it is not specific enough, and is not testable.

Lots of examples from ISPE’s JETT consortium here.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s