Unified management for Uniview’s IP cameras, NVRs, hybrid NVRs, network keyboards, of software requirement specification devices, and etc. Note: Functions and system requirements may vary with software version. Note: Actual functionality may vary depending on device capability. Live view, recording, email, preset, sound and etc.
Copyright 2011-2018 Zhejiang Uniview Technologies Co. An SRS is written in precise, clear and plain language so that it can be reviewed by a business analyst or customer representative with minimal technical expertise. In this article I explain the major sections of a typical Software Requirement Specification document. I also provide a generic SRS template which can be customized for your project needs. What is the need for an SRS document? Software Requirements Specification is usually the first deliverable for any software project.
As they say, first impression is the best impression! A good SRS document specifies all the features required in the final system including technical requirements and interface requirements. SRS document is used by the customer to determine whether the software vendor has provided all the features in the delivered software system. To the Software vendor it provides a solid foundation to fix the scope of the software system.
Did not find what they wanted? Try here
A well defined SRS enables software developers to accurately estimate the amount of effort required to build the software product. Function point analysis and SMC are some the techniques adopted for estimating effort. A good SRS enables experienced developers to convert the requirements directly to a technical design. For example, a well defined data dictionary can be easily converted to a database specification. Since SRS precisely defines project scope, it ensures that customer expectations don’t change during software development.
What are the contents of an effective SRS document? There is no single precise template for writing good Software Requirement Specifications. The contents of an SRS document depends on the software product being developed and also on the expertise of the people doing the requirement elicitation. Product vision One of the most important items in the requirements specification is the precise scope definition of the project. Accuracy of this is important since SRS is also used for estimation and costing.
This section should include a brief overview of the project and should also indicate the goals of the project including its benefits. Sometimes it is better to separate the project scope into a separate document. If the project is for the development of a product, product vision defines the scope and the target user base of the product. Functional Requirements Functional requirements specify the business requirements of the project in detail. Usually business requirements are specified in terms of the actions that user performs on the software system.
This is known as the use case model. But not all requirements need to be specified as use cases. Functional requirements should contain a combination of use cases and plain textual description of system features. For a small systems, a single diagram can be used to depict all the use cases in the system. This identifies the various types of users interacting with the software system. Purpose of the use case and how and when it is invoked by the user. This should also include an identifier for easy reference.