Lect

3/ Question to define Scope and Bondary

4/ RD process

5/ Question in Requirement Eliciation

6/ Skill

Eliciation

8/ Eliciation techniques

9/ Eliciation issues

2/ Requirement Development to

Identify business problems or issues

Understand among stakeholder and developer

Understand stakeholders’ needs and expectations

Fill in the gap between the needs and expectations

What are the customers’ expectations?

What are the immediate and future
benefits of the system?:

Why build such a system?

Who are the customers of the
development, the solution?

What is the business case?

What is the problem to be solved?

What are the “true requirements”?

Do we really have users of the system?

What are the constraints?

Discover the “unstated” expectations

What are the needs?

the problem to be solved?

Establish scenarios: How stakeholders will use the
system.

Explain the context for using the product

Validate that needs and expectations are being met

Ask what are the stakeholders’ expectations

what you want from the stakeholders

Ask about who the stakeholders are.

Where is the solution to be positioned?

What are the priorities in the overall
problem?

cost

deadlines

performance

What are the sub-problems?

Reach agreement with stakeholders.

Ask for the stakeholders’ concerns about costs,
quality and time, and other issues.

Ask how you and stakeholders will know if you are
successful.

Ask for open communication channels.

Ask for feedback about control and commitment.

Storyboarding

Questionnaire

Brainstorming

Interview

Get feedback early.

Benchmarking

Platform, Technology…

Prototyping

Successive refinement (Iterative)

Technical feasibility

Financial justification

Stakeholders

analysis

specification

elicitation

validation

not much
information on operational characteristics.

Software Engineers

not understand the application
domain

not familiar with business
processes

Different views and definitions from multiple
groups

(clarify => elicitation)

not familiar with the technical
requirements (written by the Software Engineer)

not convey the true needs of
the user’s community.

Not all participate in

(re-write => specification)

(re-evaluate => elicication)

(correct and close gaps => elicication)

Idea generation:

Idea reduction

7/ is a iterative Process to obtain

Establish requirements from stakeholders’ views

An opportunity to engage the stakeholders in
the process

A reduction in stakeholders’ resistance

An increase in the probabilities for project
success.

An opportunity for better collaboration

A stepping stone toward the problem-solving
goal

A relationship creation

An essential piece of the system

An education process for both

Interviewing is a good technique to gather
information.

Software engineers should use questions that do
not suggest a particular response.

Distributing pre-defined questions to a
sample of stakeholders

all questions can be predetermined

well to ascertain opinion trends about
specific
well-defined requirements

stakeholders population is
large and geographically distributed

Constructing a partial implementation of a system
in a quick manner

A technique for building a quick and rough version

The prototype illustrates the capabilities of the
system to users and designers.

giving users an overly optimistic impression
of completion possibilities.

occur in an existing or
envisioned system or capability.

Storyboards are a kind of “paper prototyping”.

The activity continues to evolve until real
requirements and details are worked out and
agreed upon.

Using physical media

What

how

who

Compare requirements to those
products/services