We produce SRS for-
- Define the functional requirements of the system.
- Identify the boundaries of the system
- Identify the users of the system
- Describe the interactions between the system and the users
- Establish a common language for conversation between client and development team about the system
- Provide a basis of modeling the use cases
To produce an SRS- we need to sit for one or more meetings with the “business owners” and “end users” of the system.
The purpose of these interviews are-
- Prepare a clear documentation of the business process
- Identify and establish the scope of the system
The outcome of this process is
- A formal documentation (SRS) of the system
- Details functional requirements of the system.
Formal document also helps to
- Ensure the agreements between development team and customer of the system
- Resolving any disagreements over perceived system scope as development proceeds
Example of Sample SRS
Now we will see a sample of SRS document where the owner of an Airline wants customers to be able to
- View Flight information
- Reserve tickets for flight using a web registration system
So after the interviewing with the business manager and ticketing agents the software designers draft an SRS document. The document contains the list of functional requirements are given below-
- Any user (no matter registered or non-registered) can browse the website to view the flight information
- Only registered users will be able to book flights
- New customers who want to book flights must complete a registration form providing their name, address, company name, phone number, fax number, and e-mail address.
- A customer is classified as either a corporate customer or a retail customer.
- Customers can search for flights based on destination and departure times.
- Customers can book flights indicating the flight number and the number of seats requested.
- The system sends customers a confirmation via e-mail when the flight is booked.
- Corporate customers receive frequent flier miles when their employees book flights.
- Frequent-flier miles are used to discount future purchases.
- Ticket reservations may be canceled up to one week in advance for an 80 percent refund.
- Ticketing agents can view and update flight information.
In this partial SRS document, you can see that several succinct statements define the system scope. They describe the functionality of the system as viewed by the system’s users and identify the external entities that will use it.
It is important to note that the “SRS does not contain references to the technical requirements of the system.”
Once the SRS is developed, the functional requirements it contains are transformed into a series of use case diagrams.
CSM, CSPO, CSD, CSP-SM, CSP-PO (ScrumAlliance.org)
Certification Profile Link-
Currently working as Lead Team (Application Architecture) at Raven Systems Ltd. Passion for software development especially agile practices such as TDD with in depth knowledge of Object Oriented Programming, SOLID Principles, Gang of Four Design Patterns, Some Enterprise Application Architectural Patterns. Over 8 years of software development experience ASP.NET. Has the ability to understand and transform complex business requirements into software ensuring applications are delivered on time. Also experience in non Microsoft .NET technologies such as Dapper.Net, Git, Structure Map & Angular, Bootstrap, HTML-5, CSS-3 etc.