Requirements Elicitation: Wolkite University College of Computing Department of Software Engineering

Requirements Elicitation
Wolkite university
College of Computing
Department of Software Engineering
Bekretsyon B.
April 5, 2019
Wolkite universityCollege of ComputingRequirements

Department of Elicitation Bekretsyon
Software Engineering ( April 5, 2019 B.
1 / 11
)
Introduction
Requirements elicitation
I Called requirements gathering and combine elements of:
I Problem solving, Elaboration, Negotiation and Specification
I Stakeholders work together to:
I Encourage collaborative and team-oriented approach
I Identify the problem
I Propose elements of the solution
I Negotiate different approaches, and
I Specify a preliminary set of solution requirements
I Requirements elicitation process goal:
I Understand the work that stakeholders do
I How stakeholders might use a new system
I Understand application domain and work activities
I Find out the services and system features that stakeholders want
I Determine the required performance of the system

2 / 11
)
Elicitation Techniques
I Based on source of requirements
I Organize and group the stakeholder information
I Include viewpoints to represent requirements and constraints
I Alternatively, you can use a model of the system architecture
Stakeholders:
I Questionnaires/Surveys
I Group Meetings[Facilitated Sessions, Conduct Workshops, Focus
Group, Brainstorming, Requirements Workshop and Joint
Application Development]
I Interviewing [Interview Users, Group Interviews, One-on-one
Interviews, Study improvements made by users, Look at
unintended uses and Talk so support team]
I Observation, Models [Modeling in the agile methodology,
Storyboards and state transition
3 / 11
)
Elicitation Techniques
Based on source of requirements

I Documents:
I Document Analysis [Interface Analysis, Study analogous systems,
examine suggestions, and Problems Reports]
I Request for Proposals
I System in Operation/Miscellaneous:
I Prototyping
I Work in the target environment
I Reverse Engineering and Tools
Viewpoint
I Way of collecting and organizing a set of requirements from a
group of stakeholders who have something in common.

4 / 11
)
Purpose of Elicitation
I Analyze and prepare requirements specification document

I Guide the downstream activities of software design, construction
and testing
Information to be collected:
I The list of processes within the application boundary
I Attributes of each process: inputs, outputs, transformation and
verification carried out on the inputs
I The trigger for the process
I The exit point for the process

5 / 11
)
Requirement Elicitation Process
I Requirements elicitation and analysis are an iterative processes
I A generic model for requirements engineering

6 / 11
)
Requirements discovery and understanding:

I The process of interacting with stakeholders
I Discover stakeholders requirements
I Domain requirements from stakeholders and documentation
Requirements classification and organization:

I Groups related requirements and organizes into coherent clusters
Requirements prioritization and negotiation:

I Prioritize requirements
I Find and resolve requirements conflicts through negotiation
I Agree on compromise requirements

7 / 11
)
Requirements documentation:
I Document requirements and put to the next spiral
I Maintained requirements informally on whiteboards, wikis, or
other shared spaces

8 / 11
)
Requirement Elicitation Challenges
Challenges
I Requirements in general terms and difficult to articulate
I Natural expression of requirements in implicit knowledge
I Different stakeholders with diverse requirements
I Political factors may influence the requirements of a system
I Dynamic economic and business environment

9 / 11
)
Requirement Elicitation Deliverables
I Perhaps, ”deliverables” is not the right word

I The deliverables are in intermediate form needing further
transformation
I Information as deliverables:
I Notes taken during the personal interviews
I Responses to questionnaires administered personally
I Responses to surveys
I Formats and templates
I Organizational process documentation, standards and guidelines
I Flowcharts of process steps
I List of inputs, outputs and associative processes
I Details of required reports

Software Engineering (April 5, 2019 B./ 11
10 )
Thank You...!!!!

Software Engineering (April 5, 2019 B./ 11
11 )

Requirements Elicitation: Wolkite University College of Computing Department of Software Engineering

Uploaded by

Copyright:

Available Formats

Requirements Elicitation: Wolkite University College of Computing Department of Software Engineering

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Requirements Elicitation: Wolkite University College of Computing Department of Software Engineering

Uploaded by

Copyright:

Available Formats

Requirements Elicitation

Wolkite universityCollege of ComputingRequirements

Wolkite universityCollege of ComputingRequirements

Based on source of requirements

Wolkite universityCollege of ComputingRequirements

I Analyze and prepare requirements specification document

Wolkite universityCollege of ComputingRequirements

Wolkite universityCollege of ComputingRequirements

Requirements discovery and understanding:

Requirements classification and organization:

Requirements prioritization and negotiation:

Wolkite universityCollege of ComputingRequirements

Wolkite universityCollege of ComputingRequirements

Wolkite universityCollege of ComputingRequirements

I Perhaps, ”deliverables” is not the right word

Wolkite universityCollege of ComputingRequirements

Wolkite universityCollege of ComputingRequirements

You might also like