COCOMO-Model
August 28, 2024Software-Engineering
August 28, 2024Software-Engineering
|
Question 362
|
Which of the following is not defined in a good software requirement specification(SRS) document?
|
Functional requirement
|
|
|
Goals of implementation
|
|
|
Nonfunctional requirement
|
|
|
Algorithm for software implementation
|
Question 362 Explanation:
The software requirements specification document is a requirements specification for a software system, is a complete description of the behavior of a system to be developed and
may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose
constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints)
An SRS document should clearly document the following aspects of a system: Functional Requirements, Non-Functional Requirements and Goals of implementation
may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose
constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints)
An SRS document should clearly document the following aspects of a system: Functional Requirements, Non-Functional Requirements and Goals of implementation
Correct Answer: D
Question 362 Explanation:
The software requirements specification document is a requirements specification for a software system, is a complete description of the behavior of a system to be developed and
may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose
constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints)
An SRS document should clearly document the following aspects of a system: Functional Requirements, Non-Functional Requirements and Goals of implementation
may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose
constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints)
An SRS document should clearly document the following aspects of a system: Functional Requirements, Non-Functional Requirements and Goals of implementation