Software Requirement Specifications Document (SRSD) does not include which of the following ?

Question

Accepted Answer

The correct option is (1):
The Software Requirement Specification Document (SRSD) is fundamentally a "what" document, focusing on defining the external behavior, features, and constraints of the system from the user's and client's perspective. It specifies precisely what needs to be built. Consequently, the selection of specific **Algorithms for Software Implementation** is considered a design decision, detailing *how* the software will achieve the stated requirements internally. Implementation details like choosing a sorting algorithm or a specific data structure are part of the technical blueprint and belong in the System Design Document (SDD) or Detailed Design Document (DDD). The SRSD must remain independent of the implementation technology and technical design choices.

The incorrect option is (2):
**Non-Functional Requirements** (NFRs) are a mandatory and critical component of any complete SRSD. These requirements specify the system's quality attributes, such as performance, security, reliability, scalability, and usability, essentially defining *how well* the system must operate. NFRs act as constraints on the design and execution of the software, and they are essential for user satisfaction and system maintainability. For example, a requirement like "the system shall respond within 2 seconds" is an NFR that must be documented in the SRSD.

The incorrect option is (3):
**Functional Requirements** form the core content of the entire SRSD. These requirements explicitly describe the actions the system must perform, detailing the features, services, and tasks that the software provides to its users. They dictate the input, processing, and output of the system and are often documented as use cases or user stories. An SRSD that omits functional requirements would fail its primary purpose of describing the system's intended capabilities.

The incorrect option is (4):
The **Goals of Implementation** (or project objectives/purpose) are a required part of the SRSD's introductory section. This segment sets the context for the entire project, articulating *why* the software is being developed, what business problems it addresses, and how it aligns with organizational objectives. Defining these goals ensures that the development team and all stakeholders are aligned on the project's ultimate value and scope before diving into the detailed requirements.