Our Documentation Services:
User Requirements Specification
The URS describes the business needs for what users require from the system. 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. Requirements outlined in the URS are usually tested in the Performance Qualification or User Acceptance Testing. User Requirements Specifications are not intended to be a technical document; readers with only a general knowledge of the system should be able to understand the requirements outlined in the URS.
Software Requirements Specification
The Software Requirements Specification (SRS) is a document that describes requirements for a software product, program or set of programs. Requirements in the software requirements specification are expressed in normal language and are not concerned with technical implementation. That’s what the design documents are for. In software development, the software requirements specification represents the results of the requirements analysis and describes the requirements of the software under development.
System Specification Document
The System Specification Document (SSD) describes the operational and performance requirements of a system, such as a computer. It is considered a high-level document that dictates global functions. System specifications help to define the operational and performance guidelines for a system. It may outline how the system is expected to perform, and what that may include. Key specifications may include interface definitions, document design rules and functional areas.
Software Development Plan
The Software Development Plan (SDP) describes a developer's plans for conducting a software development effort. The SDP provides the acquirer insight and a tool for monitoring the processes to be followed for software development.
Interface Control Document
Interface Control Document (ICD) is a document that describes the interface(s) to a system or subsystem. It may describe the inputs and outputs of a single system or the interface between two systems or subsystems. It can be very detailed or pretty high level, but the point is to describe all inputs to and outputs from a system. Interface control documents are a key element of systems engineering as they define and control the interface(s) of a system, and thereby bound its requirements. An ICD should only describe the interface itself, and not the characteristics of the systems which use it to.
Our Technology Toolkit:
