WATERFALL

PRESENTED BY :
ROMESA QAMAR

PRESENTED TO :
IRFAN AHMAD
REQUIREMENT
DEVELOPMENT

It is process of studying stack holders need to arrive at a

set of complete and prioritized requirement which forms
the basis for design and development of the project .
PHASES
• Requirement elicitation
• Requirement analysis
• Requirement specification
• Requirement validation
 REQUIREMENT ELICITATION
( REQUIREMENT ENGINEERING)

REQUIREMENT
GATHERING PROBLEMS PROBLEMS

It is the practice of collecting • Understanding • Guidelines

the requirements of a system • Use of models
• Consistent language
from the user customer and
other stack holders • visualization
ELICITATION TECHNIQUES

 Interview  Refreshment  Case study

 Questionnaire  Brain storming  Observation
 Prototyping  Laddering  Document analysis
 seminars  Story cards  Sorting
 REQUIREMENT ANALYSIS

THE PROCESS OF STUDYING A PROCEDURE IN ORDER TO IDENTIFY

ITS GOALS AND PURPOSES TO CREATE SYSTEM AND PROCEDURE
THAT WILL
ACHIEVE THEM IN AN EFFICIENT WAY.
TOOLS OF ANALYSIS

 Data flow diagram  Decision table  Data dictionary

 flowchart  Decision tree  Structure English

DECISION TREE
SPECIFICATION

When a program id finalized , its documentation is prepared . Final documentation is provided to user to
the user . It guides the user how to use the program in the most efficient way. Another purpose of
specification of documentation is to allow some other programmer to modify the code if necessary .

SPECIFICATION SHOULD BE DONE IN EACH STEP DURING DEVELOPMENT OF A

PROGRAM.
SPECIFICATION
TYPES

o FORMAL
o INFORMAL
VALIDATION

THAT STATED REQUIREMENTS EXPRESSED BY THE

STACKHOLDER MATCH THE STACKHOLDERS UNDERSTANDING
OF THE PROBLEM AND THE STACKHOLDERS NEEDS.