System-Wide Requirements Specification Usage note: There is procedural guidance within this template that appears in a style named InfoBlue. This style has a hidden font attribute allowing you to toggle whether it is visible or hidden in this template. Use the Word menu ToolsOptionsViewHidden Text checkbox to toggle this setting. A similar option exists for printing ToolsOptionsPrint. 1. Introduction [Provide a brief context statement, against which the rest of the document may be understood. 2. System-Wide Functional Requirements [This category represents the F in FURPS+. It is a statement of system-wide functional requirements, not expressed as use cases. Examples include security, auditing, authentication, encryption, printing, reporting, logging, licencing.] 3. System Qualities [Qualities represent the URPS in FURPS+ classification of supporting requirements.] 3.1 Usability [Describe requirements for qualities such as easy of use, easy of learning, usability standards and localization.] 3.2 Reliability [Reliability includes the product and/or system's ability to keep running under stress and adverse conditions. Specify requirements for reliability acceptance levels, and how they will be measured and evaluated. Suggested topics are availability, recoverability, integrity, frequency of severity of failures.] 3.3 Performance [The performance characteristics of the system should be outlined in this section. Examples are response time, throughput, capacity and startup or shutdown times.] 3.4 Supportability [This section indicates any requirements that will enhance the supportability or maintainability of the system being built, including adaptability and upgrading, compatibility, configurability, scalability and requirements regarding system installation, maintainability, level of support and maintenance, documentation requirements] 4. System Constraints [Constraints are the + part of the FURPS+ classification of supporting requirements. Define the design, implementation, interface, and physical constraints for the system. Include consideration of time and cost constraints as well] 4.1 Design Constraints [This section specifies or constrains the options for designing a system. For example, if you specify that a relational database is required, that's a design constraint. Another example would be if the system had to operate as a web site or a web service] 4.2 Implementation Constraints [This section describes constraints on the coding or construction of a system. Examples might include required standards, implementation languages, and resource limits.] 4.3 Interface Constraints 4.3.1 User Interfaces [Describe the user interfaces that are to be implemented by the software. The intention of this section is to state requirements relating to the interface, such as accessibility, learnability, ease and speed of use etc. 4.3.2 Internal Software Interfaces [This section describes software interfaces to other components of the software system. These may be purchased components, components reused from another application or components being developed for subsystems outside of the scope of this SRS, but with which this software application must interact.] 4.3.3 Interfaces to External Systems or Devices [Are there any external systems with which this system must interface? Are there any constraints on the nature of the interface between this system and any external system, such as the format of data passed between these systems, and any particular protocol used? Consider both provided and required interfaces.] 4.4 Physical Constraints [This section specifies physical constraints imposed on the hardware used to house the system - shape, size, or weight, for example.] 4.5 Time Constraints [This section specifies the timeframe over which the application is expected to be developed. It might specify any milestones that have to be met, and any phased development plans] 4.6 Cost Constraints [This section specifies the cost constraints under which development must proceed.]   5. System Compliance 5.1 Licensing Requirements [Define any licensing enforcement requirements or other usage restriction requirements that are to be exhibited by the software.] 5.2 Legal, Copyright, and Other Notices [This section describes any necessary legal disclaimers, warranties, copyright notices, patent notice, wordmark, trademark, or logo compliance issues for the software.] 5.3 Applicable Standards [This section describes by reference any applicable standards and the specific sections of any such standards that apply to the system being described. For example, this could include legal, quality and regulatory standards, industry standards for usability, interoperability, internationalization, operating system compliance, and so forth.] 6. System Documentation [Describes the requirements, for on-line user documentation, help systems, help about notices, and so on. Set expectations for the documentation and to identify who will be responsible for creating it.]