Requirement Elicitation

Question 1

Which models are part of the elicitation process?

Answer 1

1) class diagram

2) use case diagram

Question 2

What two questions are answered during requirements elicitation and analysis?

Answer 2

1. How can we identify the purpose of a system?
   (What are the requirements, what are the constraints?)
2. What is inside, what is outside the system?

Question 3

Techniques bridging the gap between end user and developer to elicit Requirements?

Answer 3

1) Questionnaires: Asking the end user a list of pre- selected questions
2) Task Analysis: Observing end users in their operational environment
3) Scenarios: Describe the use of the system as a series of interactions between a specific end user and the system
4) Use cases: Abstractions that describe a class of scenarios.

Question 4

What are the four types of Scenarios and what are they for?

Answer 4

1) As-is scenario:
• Describes a current situation. Commonly used in re-engineering projects
• Example: Description of Letter-Chess

2) Visionary scenario:
• Describes a future system
• Example: Home Computer of the Future

3) Evaluation scenario:
• Description of a user task against which the system is to be evaluated.
• Example: Four users (two novice, two experts) play in a TicTac Toe tournament in a game framework.

4) Training scenario:
• A description of the step by step instructions that guides a novice user through a system
• Example: How to play Tic Tac Toe in a game framework.

Question 5

Heuristics for finding scenarios: what four questions should you ask yourself or the client?

Answer 5

1) What are the primary tasks that the system needs to
perform?
2) What data will the actor create, store, change, remove or add in the system?
3) What external changes does the system need to know about?
4) What changes or events will the actor of the system need to be informed about?

Question 6

Three types of Requirements?

Answer 6

1) Functional requirements
• Describe the interactions between the system and its
environment independently of the implementation “An operator must be able to define a new game“ (reset button)

2) Nonfunctional requirements
• Aspects not directly related to functional behavior
“The response time must be less than 1 second” (setting)

3) Constraints
• Imposed by the client or the environment
“The implementation language must be Java “
• Also called “Pseudo requirements”. (A rule u must follow)