0% found this document useful (0 votes)
3K views8 pages

User Requirement Specification (Urs) For

This document defines the user requirements for a new system called <SYSTEM NAME> for <CUSTOMER NAME>. It includes sections for approvals, revision history, purpose, references, background, system description, objectives and benefits. The main section lists the key user requirements grouped under headings like system requirements, physical requirements, infrastructure, disaster recovery, backups, and security. Requirements are assigned IDs and defined in tables. The document establishes a framework for specifying functions, data, interfaces, availability, and other aspects of the new system to meet the needs of the customer.

Uploaded by

Ali Hamza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3K views8 pages

User Requirement Specification (Urs) For

This document defines the user requirements for a new system called <SYSTEM NAME> for <CUSTOMER NAME>. It includes sections for approvals, revision history, purpose, references, background, system description, objectives and benefits. The main section lists the key user requirements grouped under headings like system requirements, physical requirements, infrastructure, disaster recovery, backups, and security. Requirements are assigned IDs and defined in tables. The document establishes a framework for specifying functions, data, interfaces, availability, and other aspects of the new system to meet the needs of the customer.

Uploaded by

Ali Hamza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 8

Standard Form Doc No: SF-GEN-01

Revision No. 00 Date printed: 04/01/2022

USER REQUIREMENT SPECIFICATION (URS)

For

<SYSTEM NAME>

<CUSTOMER NAME>

APPROVALS

Approval of this document signifies that its contents are accurate, clear, consistent, complete and
objectively verifiable.
FUNCTIONAL AREA REQUIRED APPROVER DATE
AUTHOR/ CREATOR PRINT NAME

SIGN NAME

APPROVER PRINT NAME


(Custom Software)
SIGN NAME

APPROVER PRINT NAME


(<Customer Name>)
SIGN NAME

Custom Software
Doc Ref: SP-GEN-01 User Requirements Specification Page 1 of 8
Confidential
Standard Form Doc No: SF-GEN-01

Revision No. 00 Date printed: 04/01/2022

1. REVISION HISTORY

ISSUE NO: REASON FOR REVISION DATE

Custom Software
Doc Ref: SP-GEN-01 User Requirements Specification Page 2 of 8
Confidential
Standard Form Doc No: SF-GEN-01

Revision No. 00 Date printed: 04/01/2022

TABLE OF CONTENTS

1..........REVISION HISTORY.....................................................................................................2

2..........PURPOSE.......................................................................................................................4

3..........REFERENCES/ ATTACHMENTS.............................................................................4

4..........BACKGROUND............................................................................................................4

5..........SYSTEM DESCRIPTION............................................................................................4

6..........OBJECTIVES & BENEFITS.......................................................................................4

7..........USER REQUIREMENTS.............................................................................................5
7.1 System Requirements........................................................................................................5
7.2 Physical and Environmental Requirements.....................................................................6
7.3 Infrastructure.....................................................................................................................6
7.4 Disaster Recovery..............................................................................................................6
7.5 Back-up and Restore..........................................................................................................7
7.6 Archival and Retrieval.......................................................................................................7
7.7 Hardware Documentation.................................................................................................7
7.8 Documentation...................................................................................................................7
7.9 Software Maintenance.......................................................................................................7
7.10 System Administration......................................................................................................7
7.11 Logical Security..................................................................................................................8
7.12 Electronic Records and Electronic Signature Requirements..........................................8

8..........TERMS & DEFINITIONS............................................................................................8

9..........APPENDICES.................................................................................................................8

Custom Software
Doc Ref: SP-GEN-01 User Requirements Specification Page 3 of 8
Confidential
Standard Form Doc No: SF-GEN-01

Revision No. 00 Date printed: 04/01/2022

2. PURPOSE
This document will define the user requirement for <System Name> for <customer name>.

3. REFERENCES/ ATTACHMENTS

4. BACKGROUND

5. SYSTEM DESCRIPTION

6. OBJECTIVES & BENEFITS

Custom Software
Doc Ref: SP-GEN-01 User Requirements Specification Page 4 of 8
Confidential
Standard Form Doc No: SF-GEN-01

Revision No. 00 Date printed: 04/01/2022

7. USER REQUIREMENTS
1 System Requirements
Requirements to be traced in the lifecycle as part of a Requirements Traceability Matrix (RTM)
will be detailed in tables with a “URS ID” column.
URS ID Requirement

Functionality

1.1

Data Requirements

1.2

System Interface Requirements

1.3

Data Input and Output Requirements


1.4

System Availability Requirements

1.5
System User Location Requirements

1.6

System Flexibility Requirements

1.7

System Integrity Requirements

1.8

System Reliability Requirements


1.9
System Robustness Requirements

1.10

System Usability Requirements


Custom Software
Doc Ref: SP-GEN-01 User Requirements Specification Page 5 of 8
Confidential
Standard Form Doc No: SF-GEN-01

Revision No. 00 Date printed: 04/01/2022

URS ID Requirement
1.11

System Efficiency Requirements

1.12
System Performance Requirements

1.13

1.14

1.15
System Processing Requirements
1.16
Additional Requirements
1.17

2 Physical and Environmental Requirements

URS ID Requirement

2.1

3 Infrastructure
URS ID Requirement
3.1

4 Disaster Recovery

URS ID Requirement

4.1

5 Back-up and Restore

URS ID Requirement

5.1

Custom Software
Doc Ref: SP-GEN-01 User Requirements Specification Page 6 of 8
Confidential
Standard Form Doc No: SF-GEN-01

Revision No. 00 Date printed: 04/01/2022

6 Archival and Retrieval

URS ID Requirement

6.1

7 Hardware Documentation

URS ID Requirement

7.1

8 Documentation

URS ID Requirement

8.1

9 Software Maintenance

URS ID Requirement

9.1

10 System Administration

URS ID Requirement

10.1

11 Logical Security

URS ID Requirement

11.1

Custom Software
Doc Ref: SP-GEN-01 User Requirements Specification Page 7 of 8
Confidential
Standard Form Doc No: SF-GEN-01

Revision No. 00 Date printed: 04/01/2022

12 Electronic Records and Electronic Signature Requirements

URS ID Requirement

12.1

TERMS & DEFINITIONS

TERM DEFINITION

APPENDICES

Custom Software
Doc Ref: SP-GEN-01 User Requirements Specification Page 8 of 8
Confidential

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy