Lesson System specifications Task Match each word to a suitable definition

1.	2.	3.	4.	5.	6.	7.
8.

What is a System Requirement Specification (SRS)?

A SRS is a document which sets out what the client expects and what is expected of the software system which is being developed. It is a mutual agreement and insurance policy between client and developer and is a vital part of the Software Development Lifecycle.
The SRS is a technical document which provides a framework for the software development process. It provides an overview of the software or application including what it should do and what its parameters are, how it will interact with its environment and the end users, and its hardware and software requirements.
The SRS should be able to be read and understood by all the parties involved in the production of the software, including clients, designers, coders, testers and end users.

Can you do without a SRS?

Sure you can;

• 
  if you don’t want to have a overview of the project and a reference point available to the whole development team
  
• 
  if you don’t want to know what the software is supposed to do and how it will perform
  
• 
  if you don’t want to inspire confidence in stakeholders, users and your own development team
  
• 
  if you don’t want the development team to know the specifications and are willing to leave things open to a variety of interpretations
  
• 
  if you’re not interested in the expected costs and are not worried about time implications.
  

Who writes the SRS?
Many people can be involved in the process, not least of all the client. The project manager will be at the forefront of what is produced, but the writing can also include system analysts, programmers, technical writers and product marketers.