McqMate
Sign In
Hamberger menu
McqMate
Sign in
Sign up
Home
Forum
Search
Ask a Question
Sign In
McqMate Copyright © 2024
→
Computer Science Engineering (CSE)
→
Software Engineering
→
Requirements should specify ‘what’ but n...
Q.
Requirements should specify ‘what’ but not ‘how’.
A.
true
B.
false
Answer» A. true
1.3k
0
Do you find this helpful?
13
View all MCQs in
Software Engineering
Discussion
No comments yet
Login to comment
Related MCQs
The requirements that result from requirements analysis are typically expressed from one of three perspectives or views.WhaT is that perspective or view ?
In software system requirements, the interface requirements are
Which of the following is a systematic attempt to specify threats to the project plan?
The information we need to capture during requirements analysis not include
If in a software system, the operation is incorrect if results are not produced accor- ding to the specified timing requirements then the software system is referred as
Which one of the statements is not correct during requirements engineering?
Which one is not a type of requirements?
Which one is not a requirements elicitation technique?
Which is not a type of requirements under quality function deployment?
The software life cycle can be said to consist of a series of phases. The classical model is referred to as the waterfall model. Which phase may be defined as “The concept is explored and refined, and the client’s requirements are elicited?”