Advanced

A Study on Software Requirements Specifications - some examples

Rolandsson, Tanja (2010)
Department of Informatics
Abstract
The software requirements specification (SRS) is an important document, since it forms a basis for subsequent activities in the systems development process. In this thesis, nine SRSs are analyzed in order to demonstrate similarities and differences in SRS composition and requirements organization, and to show what type of requirements is the most common one. The results show that SRSs are structured either by following the IEEE (Institute of Electrical and Electronics Engineers) standard 830 with three main sections (introduction – overview – list of requirements), or another structure (introduction – references – list of requirements). How the specific requirements in the SRSs are structured differ from SRS to SRS. The most frequent type... (More)
The software requirements specification (SRS) is an important document, since it forms a basis for subsequent activities in the systems development process. In this thesis, nine SRSs are analyzed in order to demonstrate similarities and differences in SRS composition and requirements organization, and to show what type of requirements is the most common one. The results show that SRSs are structured either by following the IEEE (Institute of Electrical and Electronics Engineers) standard 830 with three main sections (introduction – overview – list of requirements), or another structure (introduction – references – list of requirements). How the specific requirements in the SRSs are structured differ from SRS to SRS. The most frequent type of requirements is functional requirements. This shows that even though using standards might not be the only way to formulate documents, they are being used and serve their purposes, at least to some extent. (Less)
Please use this url to cite or link to this publication:
author
Rolandsson, Tanja
supervisor
organization
year
type
M2 - Bachelor Degree
subject
keywords
Software requirements specification, requirements engineering, functional requirements, non-functional requirements, IEEE 830, Informatics, systems theory, Informatik, systemteori
language
English
id
1546022
date added to LUP
2010-01-26 00:00:00
date last changed
2010-08-03 10:53:02
@misc{1546022,
  abstract     = {The software requirements specification (SRS) is an important document, since it forms a basis for subsequent activities in the systems development process. In this thesis, nine SRSs are analyzed in order to demonstrate similarities and differences in SRS composition and requirements organization, and to show what type of requirements is the most common one. The results show that SRSs are structured either by following the IEEE (Institute of Electrical and Electronics Engineers) standard 830 with three main sections (introduction – overview – list of requirements), or another structure (introduction – references – list of requirements). How the specific requirements in the SRSs are structured differ from SRS to SRS. The most frequent type of requirements is functional requirements. This shows that even though using standards might not be the only way to formulate documents, they are being used and serve their purposes, at least to some extent.},
  author       = {Rolandsson, Tanja},
  keyword      = {Software requirements specification,requirements engineering,functional requirements,non-functional requirements,IEEE 830,Informatics, systems theory,Informatik, systemteori},
  language     = {eng},
  note         = {Student Paper},
  title        = {A Study on Software Requirements Specifications - some examples},
  year         = {2010},
}