| The User Requirements Specifications describes the business needs for what users require from the system. The URS is generally a planning document, created when a business is planning on acquiring a system and is trying to determine specific design needs.
User Requirements Specifications are written early in the validation process, typically before the system is created. They are written by the system owner and end-users, with input from Quality Assurance.
The user requirement(s) specification (URS) is a document usually used in computer system validation that specifies what the user expects the software to be able to do as part of the Design Qualification DQ.
Once the required information is completely gathered it is documented in a URS, which is meant to spell out exactly what the software must do and becomes part of the contractual agreement. A customer cannot demand features not in the URS, while the developer cannot claim the product is ready if it does not meet an item of the URS.
The URS can be used as a guide to planning cost, timetables, milestones, testing, etc. The explicit nature of the URS allows customers to show it to various stakeholders to make sure all necessary features are described.
Formulating a URS requires negotiation to determine what is technically and economically feasible. Preparing a URS is one of those skills that lies between a science and an art, requiring both software technical skills and interpersonal skills.
The URS facilitates a starting point and traceability to ensure that basic functions are established. These basic functions will be used later for assessing risks.
The further preparation of the risk assessments, Functional Requirement Specifications FRS, and execution of the Installation Qualification (IQ), Operational Qualification (OQ), and Performance / Product Qualification (PQ), is dependent on a URS containing clear, concise, and testable requirements.
User Requirements Specification (URS) document should include the following parts and sections: (as applicable);
o Purpose
o Scope
o Background
o Hardware and Software Description
o Level-1, full details of end-user operability.
o Level-2, full details of functionality.
o Level-3, software functionality interface.
o A full description of the required system performance.
o Performance criteria, critical parameters, and operating range.
o Cleaning and maintenance requirements.
o Appropriate regulatory requirements.
o Documentation requirements.
o Training requirements.
o All industry-standard testing that may be required.
o Associated Reference Documents
o Appendices
o History of Change
o Document Approval |
