Scribd
Upload
17 views

SRS as per the IEEE

The IEEE 830-1998 standard outlines a structured approach for Software Requirements Specifications (SRS), detailing the necessary components for documenting software requirements. It includes sections such as Introduction, Overall Description, Specific Requirements, and Appendices, each addressing various aspects like purpose, product functions, user classes, and performance requirements. This comprehensive format ensures thorough documentation and clear communication of software requirements.

Uploaded by

Deepak Ulape
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
17 views

SRS as per the IEEE

The IEEE 830-1998 standard outlines a structured approach for Software Requirements Specifications (SRS), detailing the necessary components for documenting software requirements. It includes sections such as Introduction, Overall Description, Specific Requirements, and Appendices, each addressing various aspects like purpose, product functions, user classes, and performance requirements. This comprehensive format ensures thorough documentation and clear communication of software requirements.

Uploaded by

Deepak Ulape
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

The IEEE (Institute of Electrical and Electronics Engineers) standard for Software Requirements

Specifications (SRS) is defined in IEEE 830-1998, titled "IEEE Recommended Practice for Software
Requirements Specifications." This standard provides a structured approach to documenting the
requirements for a software system.

Here’s a general outline of the IEEE 830-1998 SRS format:

1. Introduction

- 1.1 Purpose: Defines the purpose of the SRS and the intended audience.

- 1.2 Scope: Outlines the software product to be specified, including its boundaries, major features,
and goals.

- 1.3 Definitions, Acronyms, and Abbreviations: Provides definitions for terms, acronyms, and
abbreviations used in the SRS.

- 1.4 References: Lists any references to other documents or standards that are pertinent to the
SRS.

- 1.5 Overview: Gives an overview of the remaining sections of the SRS.

2. Overall Description

- 2.1 Product Perspective: Describes the context and origin of the product, including its relationship
to other systems.

- 2.2 Product Functions: Provides a high-level summary of the software’s functions.

- 2.3 User Classes and Characteristics: Identifies the different user types and their needs.

- 2.4 Operating Environment: Specifies the hardware, software, and other environmental
constraints.

- 2.5 Design and Implementation Constraints: Lists any constraints on design and implementation.

- 2.6 User Documentation: Details the documentation and training materials provided to users.

- 2.7 Assumptions and Dependencies: Describes any assumptions and dependencies that could
impact the software requirements.

3. Specific Requirements

- 3.1 Functional Requirements: Provides detailed descriptions of the functions the software must
perform.

- 3.2 External Interface Requirements: Details interactions between the software and other systems
or users.

- 3.2.1 User Interfaces: Specifies the user interface requirements.


- 3.2.2 Hardware Interfaces: Describes the hardware interfaces if applicable.

- 3.2.3 Software Interfaces: Outlines any software interfaces.

- 3.2.4 Communications Interfaces: Defines the communication protocols and standards.

- 3.3 Performance Requirements: Specifies performance constraints and criteria.

- 3.4 Design Constraints: Describes constraints related to the design of the software.

- 3.5 Software System Attributes: Details attributes such as reliability, availability, security, and
maintainability.

- 3.6 Other Requirements: Includes any other requirements not covered in the above sections.

4. Appendices

- 4.1 Glossary: Provides a glossary of terms used in the SRS.

- 4.2 Analysis Models: Includes diagrams and models that support the requirements, such as data
flow diagrams or use case diagrams.

- 4.3 Issue Tracking: Optional section for tracking unresolved issues or changes.

This structure helps ensure that all aspects of the software requirements are thoroughly documented
and clearly communicated.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy