SDLC Process

In traditional Waterfall model :–

• At a high level, the project teams
would spend 15% of their time on
gathering requirements and analysis
(1.5 months)
• 20% of their time on design (2
months)
• At the end of this cycle, the project
may also have 2 weeks of User
Acceptance testing by marketing
teams.

In this approach, the customer does

not get to see the end product until the
end of the project, when it becomes
too late to make significant changes.
With Agile development methodology
–
• Each project is broken up into several
‘Iterations’.
• At the end of each iteration, a
working product should be delivered.
• Rather than spending 1.5 months on
requirements gathering, in Agile
software development, the team will
decide the basic core features that
are required in the product and
decide which of these features can
be developed in the first iteration.
• Any remaining features that cannot
be delivered in the first iteration will
be taken up in the next iteration or
subsequent iterations, based on
priority.
 Requirement Lifecycle Management
• Stakeholder identification & Collaboration
• Requirement Gathering/ Elicitation
• Requirement Document- BRD, Use cases, User Stories
• Requirement Verification- Stakeholders
• Requirement Validation
• Requirement Sign off
 Elicitation Techniques

REQUIREMENT ELICITATION
• Collecting the information and the requirements using various
techniques like
• Interviewing the client (requirements)
• Brain storming sessions (finalising the documents)
• Questionnaires (open ended - detailed / closed ended - single word)
• Workshop (activity discussion)
• Prototyping (look & feel of how the end product should be)
• Observation
Project Scope
• Software scope is a well-defined boundary, which encompasses
all the activities that are done to develop and deliver
the software product. The software scope clearly defines all
functionalities and artifacts to be delivered as a part of
the software.
In scope/out scope and scope creep
• Activities that fall within the boundaries of the scope statement
are considered “in scope” and are accounted for in the schedule
and budget.
• Scope creep (also called requirement creep, function creep,
feature creep, or kitchen sink syndrome) in project management
refers to changes, continuous or uncontrolled growth in a
project’s scope, at any point after the project begins.
Estimation
• Software development effort estimation is the process of predicting
the most realistic amount of effort (expressed in terms of person-
hours or money) required to develop or maintain software based on
incomplete, uncertain and noisy input.
 Requirement Prioritization
• Requirement prioritization is used in Software product
management for determining which requirements of a software
product should be included in a certain release. High _ Must Have
• Medium – Good to Have
• Low – Can do without
• MOSCOW Technique