The document discusses software engineering and testing methodologies, specifically focusing on characteristics of a Software Requirements Specification (SRS) and standards for SRS according to IEEE. It notes that IEEE 830-1998 provides guidelines for SRS documents and defines an SRS as a document that clearly describes the essential requirements, functions, and external interfaces of software in a way that can be verified through testing or other means. The lecture further explains the contents and characteristics of an SRS based on IEEE standards.
The document discusses software engineering and testing methodologies, specifically focusing on characteristics of a Software Requirements Specification (SRS) and standards for SRS according to IEEE. It notes that IEEE 830-1998 provides guidelines for SRS documents and defines an SRS as a document that clearly describes the essential requirements, functions, and external interfaces of software in a way that can be verified through testing or other means. The lecture further explains the contents and characteristics of an SRS based on IEEE standards.
The document discusses software engineering and testing methodologies, specifically focusing on characteristics of a Software Requirements Specification (SRS) and standards for SRS according to IEEE. It notes that IEEE 830-1998 provides guidelines for SRS documents and defines an SRS as a document that clearly describes the essential requirements, functions, and external interfaces of software in a way that can be verified through testing or other means. The lecture further explains the contents and characteristics of an SRS based on IEEE standards.
The document discusses software engineering and testing methodologies, specifically focusing on characteristics of a Software Requirements Specification (SRS) and standards for SRS according to IEEE. It notes that IEEE 830-1998 provides guidelines for SRS documents and defines an SRS as a document that clearly describes the essential requirements, functions, and external interfaces of software in a way that can be verified through testing or other means. The lecture further explains the contents and characteristics of an SRS based on IEEE standards.
Testing Methodologies c t u re by Le 15 Dr.Anuj Kumar anuj.kumar15@sharda.ac.in 9313346934
Department of CSE, School of Engineering and Technology
Lecture-15
Contents • Characteristics of SRS • SRS as per IEEE standards
Department of CSE, School of Engineering and Technology
Lecture-15
Department of CSE, School of Engineering and Technology
Lecture-15
Characteristics of SRS
Department of CSE, School of Engineering and Technology
Lecture-15
SRS as per IEEE standards
• The Institute of Electrical and Electronics Engineers publishes several dozen software engineering standards • IEEE 830-1998 is the 1998 revised standard • It was replaced by Standard ISO/IEC/IEEE 29148:2011, with an update in 2018. • IEEE 29148 covers the processes and information it recommends for a software requirements specification (SRS) document, as well as its format. • IEEE defines software requirements specification as, ‘a document’ that clearly and precisely describes each of the essential requirements (functions, performance, design constraints and quality attributes) of the software and the external interfaces. • Each requirement is defined in such a way that its achievement can be objectively verified by a prescribed method, for example, inspection, demonstration, analysis or test.’ • The requirements specification can be in the form of a written document, a mathematical model, a collection of graphical models, a prototype, and so on. Department of CSE, School of Engineering and Technology Lecture-15
IEEE 830-1998 Standard for SRS
Department of CSE, School of Engineering and Technology
Lecture-15
IEEE 830-1998 Standard for SRS
Department of CSE, School of Engineering and Technology
Lecture-15
IEEE 830-1998 Standard for SRS
Department of CSE, School of Engineering and Technology