The document discusses requirements engineering and outlines its importance, typical reasons for inadequate requirements, key activities, and best practices. It notes that companies with poor requirements have a project failure to success ratio of 3:1 and spend on average $2.24 million more per project. The main activities covered are requirements elicitation, documentation, validation and negotiation, and management. Various techniques for each activity are also described such as interviews for elicitation and inspections for validation.

1. REQUIREMENTS
ENGINEERING

2. Companies with poor requirements
and business analysis capability have
project failure to success ratio
= 3 : 1
Source - IAG Business Analysis Benchmark 2008

3. $2.24 million
more per project than those that employ
requirements best practices.
Companies with poor requirements, on an
average, spend
Source - IAG Business Analysis Benchmark 2008

4. REQUIREMENTS
ENGINEERING

5. Image Source -http://www.knovelblogs.com/

6. TYPICAL
REASONS
FOR INADEQUATE
REQUIREMENTS
ENGINEERING
Project Pressure
Communication Problem
Wrong assumption1
2
3

7. ACTIVITIESRE
REQUIREMENTS
ELICITATION
DOCUMENTATION
VALIDATION & NEGOTIATION
MANAGEMENT

8. ELICITATION
SOURCES
STAKEHOLDERS
DOCUMENTS
EXISTING SYSTEM

9. ELICITATION TECHNIQUES
SURVEY interviews questionnaires
CREATIVITY brainstorming change of perspective
DOCUMENT CENTRIC artifacts
OBSERVATION field observation

10. ACTIVITIESRE
REQUIREMENTS
ELICITATION
DOCUMENTATION
VALIDATION & NEGOTIATION
MANAGEMENT

11. DOCUMENTATION
requirement doc
is basis for
system
development
planning
architecture
design
implementation
test
change
management
contract
management
system
usage &
maintenance

12. DOCUMENTATION
WAYS
natural language
models
ह िंदी
English
中文
Activity Diagram/ DFD
Class Diagram/ ERD
State Diagram
+

13. DOCUMENTATION
STRUCTURE
customizedstandard
Rational Unified Process
ISO/ IEC/ IEEE std 29148:2011
V model
Intro
General Overview
Requirements
Appendices
Index

14. DOCUMENTATION
unambiguity & consistency
clear structure
modifiability & extensibility
completeness
traceability
BASIC STYLE
small sentences
1 requirement/ sentence

15. ACTIVITIESRE
REQUIREMENTS
ELICITATION
DOCUMENTATION
VALIDATION & NEGOTIATION
MANAGEMENT

16. VALIDATION & NEGOTIATION
conflict resolutionverify requirements
quality criteria
error detection error correction
approved
common & agreed requirements

17. VALIDATION TECHNIQUES
commenting (expert opinion)
inspections
walkthroughs
Additional Techniques
perspective based reading
validation through prototypes
usage of checklists

18. NEGOTIATION tasks
conflict
types
interest
data
value
relationship
structural
resolution
techniques
agreement
compromise
voting
decision matrix

19. ACTIVITIESRE
REQUIREMENTS
ELICITATION
DOCUMENTATION
VALIDATION & NEGOTIATION
MANAGEMENT

20. MANAGEMENT
assigning attributes
identifier
name
description
source
stability
risk
priority

21. MANAGEMENT
requirement
prioritization
goal & constraints
criteria
relevant stakeholder
selection of artifacts
technique

22. PRIORITIZATION TECHNIQUE
K
A
N
O
M
O
D
E
L BASIC
FACTORS
PERFORMANCE
FACTORS
EXCITEMENT
FACTORS

23. TRACEABILITY & VERSIONING
requirements versioning
requirements traceability
Text based reference/
hyperlink
Trace matrix Trace graph
increment
version
v 2.1

24. RE
elicitation documentation
validation & negotiation management
ways
techniques
sources
structure
quality
criteria
validation techniques
negotiation tasks
attributes
v 2.1

25. ? ? ?
thank you . . .