1. What is the first step of requirement elicitation ?
a) Identifying Stakeholder
b) Listing out Requirements
c) Requirements Gathering
Explanation: Stakeholders are the one who will invest in and use the product, so its essential to chalk out stake holders first.
2. Starting from least to most important, choose the order of stakeholder.
ii. Entry level Personnel
iv. Middle level stakeholder
a) i, ii, iv, iii
b) i, ii, iii, iv
c) ii, iv, i, iii
Explanation: Users are your customers, they will be using your product, thus making them most important of all.
3. Arrange the tasks involved in requirements elicitation in an appropriate manner.
iii. Requirements Gathering
a) iii, i, ii, iv
b) iii, iv, ii, i
c) iii, ii, iv, i
d) ii, iii, iv, i
Explanation: Requirements gathering captures viewpoint from different users followed by evaluation of those view points.Now comes the task of checking the relative importance of the requirements and finally to consolidate or bind together the information collected.
4. What are the types of requirement in Quality Function Deployment(QFD) ?
a) Known, Unknown, Undreamed
b) User, Developer
c) Functional, Non-Functional
d) Normal, Expected, Exciting
Explanation: According to QFD, Normal, Expected and Exciting requirements maximizes customer satisfaction from the Software Engineering Process.
5. What kind of approach was introduced for elicitation and modelling to give a functional view of the system ?
a) Object Oriented Design (by Booch)
b) Use Cases (by Jacobson)
c) Fusion (by Coleman)
d) Object Modeling Technique (by Rambaugh)
Explanation: Use Case captures who does what with the system, for what purpose, without dealing with system internals.
6. What are the kinds of actors used in OOSE ?
d) Both a and b
Explanation: A primary actor is one having a goal requiring the assistance of the system whereas, a secondary actor is one from which system needs assistance.There is no such thing as ternary actor in Software Engineering.
7. Why is Requirements Elicitation a difficult task ?
a) Problem of scope
b) Problem of understanding
c) Problem of volatility
d) All of the mentioned
Explanation: Users specify unnecessary technical detail that may confuse, rather than clarify overall system objectives.Also, the customers/users are not completely sure of what is needed, have a poor understanding of the capabilities and limitations of their computing environment and they do not understand that the requirements change over time.
8. What requirement gathering method developed at IBM in 1970s is used for managing requirement elicitation ?
d) Both a and b
Explanation: Joint application design (JAD) is a process used to collect business requirements while developing new information systems for a company.Requirements traceability is concerned with documenting the life of a requirement and providing bi-directional traceability between various associated requirements.
9. Requirements elicitation is a cyclic process
Explanation: Requirements traceability provides bi-directional traceability between various associated requirements.
10. How many Scenarios are there in elicitation activities ?
Explanation: As-is Scenario, Visionary Scenario, Evaluation Scenario and Training Scenario are the four scenarios in requirement elicitation activities.
Sanfoundry Global Education & Learning Series – Software Engineering.