In this section of Software Engineering – Software Requirements.It contain Software Requirements Analysis MCQs (Multiple Choice Questions Answers).All the MCQs (Multiple Choice Question Answers) requires in depth reading of Software Engineering Subject as the hardness level of MCQs have been kept to advance level.These Sets of Questions are very helpful in Preparing for various Competitive Exams and University level Exams.
 

Practice it now to sharpen your Concepts

 

1
. It is relatively common for different customers to propose conflicting requirements, each arguing that his or her version is the right one.
  • True
  • False
2
. The system specification describes the
  • Function, performance and constraints of a computer-based system
  • implementation of each allocated system
  • element software architecture
  • time required for system simulation
3
. The best way to conduct a requirements validation review is to
  • examine the system model for errors
  • have the customer look over the requirements
  • send them to the design team and see if they have any concerns
  • use a checklist of questions to examine each requirement
4
. The use of traceability tables helps to
  • debug programs following the detection of run-time errors
  • determine the performance of algorithm implementations
  • identify, control, and track requirements changes
  • none of the above
5
. The job of the requirements engineer is to categorize all stakeholder information in a way that allows decision makers to choose an internally consistent set of requirements.
  • True
  • False
6
. The nature of collaboration is such that all system requirements are defined by consensus of a committee of customers and developers.
  • True
  • False
7
. Which of following is not a UML diagram used creating a system analysis model?
  • activity diagram
  • class diagram
  • dataflow diagram
  • state diagram
8
. Requirements engineering is a generic process that does not vary from one software project to another.
  • True
  • False
9
. During project inception the intent of the of the tasks are to determine
  • basic problem understanding
  • nature of the solution needed
  • people who want a solution
  • none of the above
  • a, b, c
10
. Three things that make requirements elicitation difficult are problems of
  • budgeting
  • scope
  • understanding
  • volatility
  • b, c, d
11
. A stakeholder is anyone who will purchase the completed software system under development
  • True
  • False
12
. It is relatively common for different customers to propose conflicting requirements, each arguing that his or her version is the right one.
  • True
  • False
13
. Which of the following is not one of the context-free questions that would be used during project inception?
  • What will be the economic benefit from a good solution?
  • Who is behind the request for work?
  • Who will pay for the work?
  • Who will use the solution?
14
. Non-functional requirements can be safely ignored in modern software development projects
  • True
  • False
15
. In collaborative requirements gathering the facilitator
  • arranges the meeting place
  • can not be a customer
  • controls the meeting
  • must be an outsider
16
. Which of the following is not one of the requirement classifications used in Quality Function Deployment (QFD)?
  • exciting
  • expected
  • mandatory
  • normal
17
. The work products produced during requirement elicitation will vary depending on the
  • size of the budget
  • size of the product being built.
  • software process being used.
  • stakeholders needs.
  • both a and b
18
. User stories are complete descriptions the user needs and include the non-functional requirements for a software increment.
  • True
  • False
19
. Developers and customers create use-cases to help the software team understand how different classes of end-users will use functions.
  • True
  • False
20
. Use-case actors are always people, never system devices.
  • True
  • False
21
. The result of the requirements engineering task is an analysis model that defines which of the following problem domain(s)?
  • information
  • functional
  • behavioral
  • all of the above
22
. Analysis patterns facilitate the transformation of the analysis model into a design model by suggesting reliable solutions to common problems.
  • True
  • False
23
. In agile process models requirements engineering and design activities are interleaved.
  • True
  • False
24
. In win-win negotiation, the customer’s needs are met even though the developer’s need may not be.
  • True
  • False
25
. In requirements validation the requirements model is reviewed to ensure its technical feasibility
  • True
  • False
26
. The most common reason for software project failure is lack of functionality
  • True
  • False

 
 
You may be interested in:
Software Engineering Online Tests