ControlDraw
This web was generated automatically from a sample ControlDraw model.
Move the mouse over the diagram area - you can click on the objects that have numbers by them to go to the detailed diagram for the object. It is a bit like using ControlDraw (but that is much more powerful!)
Go to ControlDraw.co.uk


List of Diagrams
[First] [Previous]][Next][Last]
001 - index
002 - About Process Control
003 - Your Business
004 - For Manufacturers
005 - For EPC Companies
006 - For Systems Integrators
007 - For DCS/PLC suppliers
008 - Education
009 - Process Operation
010 - Process Control Systems
011 - Automation Software Design
012 - Functional Design
013 - S88 Links
014 - Process Design
015 - Design Documents
016 - FRS
017 - P&ID
018 - Process Descriptions
019 - SDS
020 - URS
021 - PCS Graphic
022 - Engineers
023 - For DCS/PLC Programmers
024 - For Automation Engineers
025 - For Process Engineers
026 - Process Eng Diagram Flow
027 - For Project Managers
028 - Project Management ControlDraw
029 - For Instrument Engineers
030 - Automation Design
031 - Requirements Analysis Process
032 - Instrument Engineering
033 - Diagrams
034 - Logic Diagrams
035 - Control Loops
036 - PFC
037 - Process Flow Diagram
038 - Sequential Function Charts
039 - State Transition Diagrams
040 - Polymorphic
041 - Controldraw Software
042 - Automation Models
043 - Hierarchical Objects
044 - Database
045 - IO List
046 - Data lists
047 - S88 Models
048 - S88 Recipes
049 - S88 Physical Model
050 - Process Cells
051 - Units
052 - Equipment Modules
053 - Control Modules
054 - S88 Procedures
055 - Recipe Procedure
056 - Unit Procedure
057 - Operation
058 - Phase
059 - State Matrices
060 - State Based Control
061 - Control Design Reviews
062 - ControlDraw Reviewer
063 - Overview
064 - Why Controldraw
065 - FAQ
066 - Controldraw Compared
067 - Main Screen
068 - Matrix Screen
069 - Life Cycle
070 - Life Cycle and Models
071 - Specifications
072 - Functional Requirements Spec
073 - Functional Design Specification
074 - User Requirements
075 - Support
076 - Download
077 - Standards
078 - Services
079 - About Web Site
080 - ControlDraw Prices
081 - History
082 - History of Control
083 - History of ControlDraw
084 - History of S88
085 - History of Diagrams
086 - Documentation for the Life Cycle
087 - Large distributed projects
088 - System Development Structure
089 - The RTF Editor
090 - ControlDraw with CAD
091 - Web Layout
092 - Prototyping Partnership
093 - All pages
094 - IEC1131
095 - OnePageOverview

 20 - URS (Web Page)


The User Requirement Specification (URS) specifies the requirements of the user for individual aspects of the facility, equipment, and systems in terms of function, throughput, operability, and applicable standards, what functions will be carried out, the data on which the system will operate, and the operating environment.
In practise there are both Functional requirements and Non-functional requirements
Non-functional requirements include constraints (eg project time scale) and what deliverables will be provided by the system ( documentation, training, testing, tools etc).
The URS is the stage at which the user's requirements are defined in sufficiently precise detail to allow suppliers to produce tenders for the work. This may involve a feasibility study.
The following guidelines should be followed during the production of the specification:
1. Each requirement statement to be uniquely referenced, and no longer than 250 words.
2. Requirement statements should not be duplicated nor contradicted.
3. The URS should express requirements and not design solutions.
4. Each requirement should be testable.
5. The URS must be understood by both user and supplier; ambiguity and jargon should be avoided.
6. Wherever possible, the URS should distinguish between mandatory/regulatory requirements and desirable features.
7. There may need to be a formal review of the URS between the user and supplier to check understanding and that requirements have been met (or not) in the Functional Specification.

A major part of the effort of producing good requirements specifications is defining the Functional Requirements


Page Review Status: None Version 329