Software Engineering Unit-4 (Q-1)
-
How many phases are there in Requirement Analysis ?
-
3
-
4
-
5
-
6
-
Explore the essentials of requirement analysis in software engineering through this focused quiz. It covers phases, critical issues, iterative processes, and specification roles, enhancing understanding crucial for system developers.
Quiz Preview
- 2.
Requirements analysis is critical to the success of a development project.
-
True
-
False
Correct Answer
A. TrueExplanation
Requirements must be actionable, measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.Rate this question:
-
- 3.
_________ and _________ are the two issues of Requirement Analysis.
-
Performance, Design
-
Stakeholder, Develop
-
Functional, Non-Functional
-
None
Correct Answer
A. Stakeholder, DevelopExplanation
Option a and c are the types of requirements and not the issues of requirement analysis..Rate this question:
-
- 4.
Requirements Analysis is an Iterative Process.
-
True
-
False
Correct Answer
A. TrueExplanation
Requirements analysis is conducted iteratively with functional analysis to optimize performance requirements for identified functions, and to verify that synthesized solutions can satisfy customer requirements.Rate this question:
-
- 5.
Requirements should specify ‘what’ but not ‘how’.
-
True
-
False
Correct Answer
A. TrueExplanation
‘What’ refers to a system’s purpose, while ‘How’ refers to a system’s structure and behavior.Rate this question:
-
- 6.
Who writes the Software Requirement Specifications Document(SRS)?
-
System Developer
-
System Analyst
-
System Tester
-
None of these above
Correct Answer
A. System DeveloperExplanation
The correct answer is System Developer. The Software Requirement Specifications (SRS) document outlines the detailed description of the software system to be developed. It includes information about the system's functionalities, features, and constraints. The SRS document is typically prepared by the system developer, who is responsible for understanding the client's requirements and translating them into a comprehensive document that serves as a guide for the development team. System analysts and testers may contribute to the SRS document by providing their inputs and feedback, but the primary responsibility lies with the system developer.Rate this question:
-
- 7.
What is the goal of the requirements analysis and specifications phase of software development life cycle ?
-
Determining scope of the software
-
Analyzing the cost of development
-
Understanding the customer requirements and organize them in an informal document
-
None of these above
Correct Answer
A. Understanding the customer requirements and organize them in an informal documentExplanation
The goal of the requirements analysis and specifications phase of the software development life cycle is to understand the customer requirements and organize them in an informal document. This phase involves gathering and analyzing the needs and expectations of the customer, documenting them in a clear and concise manner, and ensuring that all stakeholders have a common understanding of the requirements. This document serves as a reference for the development team and helps in the subsequent phases of the software development process.Rate this question:
-
- 8.
What is the final outcome of the requirements analysis and specifications phase ?
-
Drawing the data flow diagram
-
The SRS Document
-
Coding the project
-
The User Manual
Correct Answer
A. The SRS DocumentExplanation
The final outcome of the requirements analysis and specifications phase is the SRS Document. This document outlines the detailed requirements and specifications for the project, including functional and non-functional requirements, system architecture, user interface design, and any other relevant information. It serves as a blueprint for the development team to understand and implement the project accurately. The SRS Document is crucial for ensuring that the final product meets the client's expectations and serves as a reference for project stakeholders throughout the development process.Rate this question:
-
- 9.
Which of the following is not desirable characteristic of SRS document?
-
Concise
-
Ambiguous
-
Verifiable
-
Traceable
Correct Answer
A. AmbiguousExplanation
An SRS document should be concise, verifiable, and traceable, as these characteristics ensure clarity, accuracy, and accountability in the requirements. However, ambiguity is not desirable in an SRS document as it can lead to confusion, misunderstandings, and potential errors in the development process. Therefore, it is important for an SRS document to be clear and unambiguous to facilitate effective communication and understanding between stakeholders and development teams.Rate this question:
-
- 10.
Which one of the following is a functional requirement ?
-
Maintainability
-
Portability
-
Robustness
-
None of the mentioned
Correct Answer
A. None of the mentionedExplanation
All are non-functional requirements representing quality of the system. Functional requirements describe what the software has to do.Rate this question:
-
Quiz Review Timeline (Updated): Mar 21, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
-
Current Version
-
Mar 21, 2023Quiz Edited by
ProProfs Editorial Team -
Jan 05, 2017Quiz Created by
Namitapatel
Back to top