SRS IN BRIEF [System Rquirements Specification]

An srs is basically an organization’s understanding (in writing) of a customer or potential client’s system requirements and dependencies at a particular point in time (usually) prior to any actual design or development work.

It’s a two-way insurance policy that assures that both the client and the organization understand the other’s requirements from that perspective at a given point in time. Benefits of a good srs establish the basis for agreement between the customers and the suppliers on what the software product is to do.

Reduce the development effort. Provide a basis for estimating costs and schedules. Provide a baseline for validation and verification. Serve as a basis for enhancement. What should the srs address to? functionality.

What is the software supposed to do? external interfaces. How does the software interact with people, the system’s hardware, other hardware, and other software? performance.

What is the speed, availability, response time, recovery time of various software functions, etc.? attributes. What are the portability, correctness, maintainability, security, etc. Considerations? design constraints imposed on an implementation. Are there any required standards in effect, implementation language, policies for database integrity, resource limits, operating environment(s) etc.?

what are the characteristics of a great srs?an srs should be
a) correct
b) unambiguous
c) complete
d) consistent
e) ranked for importance and/or stability
f) verifiable
g) modifiable
h) traceable little more about software specifications and system specifications

what is the difference between a system specification and a software specification?

very often we find that companies do not understand the difference between a system specification and a software specification. Important issues are not defined up front and mechanical, electronic and software designers do not really know what their requirements are.

The following is a high level list of requirements that should be addressed in a system specification: define the functions of the system define the hardware / software functional partitioning define the performance specification define the hardware / software performance partitioning define safety requirements define the user interface (a good user’s manual is often an overlooked part of the system specification.

Many of our customers haven’t even considered that this is the right time to write the user’s manual.) provide installation drawings/instructions. Provide interface control drawings (icd’s, external i/o)