Introduction:
A Software Requirement Specifications (SRS) document is a detailed description of the software system to be developed. It outlines the functional and non-functional requirements, goals of implementation, and various other aspects of the software. However, out of the given options, the one that is NOT desired in a good SRS document is the presence of algorithms for software implementation.

Functional Requirements:
Functional requirements describe the specific behavior of the software system. These requirements define what the software should do and how it should respond to different inputs or user actions. They outline the features, functions, and capabilities that the software must possess to fulfill user needs. Including functional requirements in an SRS document is essential as they provide a clear understanding of the software's expected behavior.

Non-Functional Requirements:
Non-functional requirements encompass aspects of the software system that are not directly related to its functionality but are equally important for its success. These requirements include performance, reliability, security, usability, maintainability, and other qualities that the software should possess. Non-functional requirements provide guidelines for the overall quality of the software and ensure that it meets the necessary standards.

Goals of Implementation:
The goals of implementation describe the objectives or aims that the software development team wants to achieve while implementing the software system. These goals may include meeting specific deadlines, adhering to budget constraints, using specific technologies or methodologies, or achieving certain performance benchmarks. Including the goals of implementation in the SRS document helps align the development process with the overall project objectives.

Algorithms for Software Implementation:
Algorithms for software implementation refer to the step-by-step procedures or instructions that define how the software system will perform specific tasks or operations. While algorithms play a crucial role in software development, they are not typically included in an SRS document. Detailed algorithms are usually documented separately in design documents or technical specifications that are created during the later stages of the software development process.

Conclusion:
In conclusion, a good Software Requirement Specifications (SRS) document should include functional requirements, non-functional requirements, and goals of implementation. However, it does not include detailed algorithms for software implementation. Algorithms are typically documented in separate design documents or technical specifications.