Incremental Process Model

Incremental Model is a process of software development where

requirements are broken down into multiple standalone modules of

software development cycle. Incremental development is done in steps

from analysis design, implementation, testing/verification,

maintenance.
Continue…
Each iteration passes through the requirements, design, coding and
testing phases. And each subsequent release of the system adds
function to the previous release until all designed functionality has
been implemented.
Continue…
Continue…
• The system is put into production when the first increment is
delivered.
• The first increment is often a core product where the basic
requirements are addressed, and supplementary features are added
in the next increments.
• Once the core product is analyzed by the client, there is plan
development for the next increment.
Characteristics of Incremental Model
• System development is broken down into many mini development
projects
• Partial systems are successively built to produce a final total system
• Highest priority requirement is tackled first
• Once the requirement is developed, requirement for that increment
are frozen
RAD Model
• RAD model is Rapid Application Development model.
• It is a type of incremental model.
• In RAD model the components or functions are developed in parallel
as if they were mini projects.
• The developments are time boxed, delivered and then assembled into
a working prototype.
Iterative Model
• This model leads the software development process in iterations. It
projects the process of development in cyclic manner repeating every
step after every cycle of SDLC process.
• The software is first developed on very small scale and all the steps
are followed which are taken into consideration. 
• On every next iteration, more features and modules are designed,
coded, tested and added to the software.
• Every cycle produces a software, which is complete in itself and has
more features and capabilities than that of the previous one.
Continue…
• After each iteration, the management team can do work on risk
management and prepare for the next iteration.
• Because a cycle includes small portion of whole software process, it is
easier to manage the development process but it consumes more
resources.
Spiral Model
Spiral model is a combination of both, iterative model and one of the
SDLC model. It can be seen as if you choose one SDLC model and
combine it with cyclic process (iterative model).
Continue…
• This model considers risk, which often goes un-noticed by most other
models. 
• The model starts with determining objectives and constraints of the
software at the start of one iteration.
• Next phase is of prototyping the software.
• This includes risk analysis. 
• Then one standard SDLC model is used to build the software.
V – model
The major drawback of waterfall model is we move to the next stage
only when the previous one is finished and there was no chance to go
back if something is found wrong in later stages. V-Model provides
means of testing of software at each stage in reverse manner.
Continue…
Continue…
At every stage, test plans and test cases are created to verify and
validate the product according to the requirement of that stage.
For example, in requirement gathering stage the test team prepares all
the test cases in correspondence to the requirements. Later, when the
product is developed and is ready for testing, test cases of this stage
verify the software against its validity towards requirements at this
stage.
This makes both verification and validation go in parallel. This model is
also known as verification and validation model.
Software Project Management
The job pattern of an IT company engaged in software development
can be seen split in two parts:
• Software Creation
• Software Project Management
Continue…
A project is well-defined task, which is a collection of several operations
done in order to achieve a goal. A Project can be characterized as:
• Every project may has a unique and distinct goal.
• Project is not routine activity or day-to-day operations.
• Project comes with a start time and end time.
• Project ends when its goal is achieved hence it is a temporary phase
in the lifetime of an organization.
• Project needs adequate resources in terms of time, manpower,
finance, material and knowledge-bank.
Software Project
A Software Project is the complete procedure of software development
from requirement gathering to testing and maintenance, carried out
according to the execution methodologies, in a specified period of time
to achieve intended software product.
Need of SPM
• Software is said to be an intangible product.
• Software development is a kind of all new stream in world business and
there’s very little experience in building software products.
• Most software products are tailor made to fit client’s requirements.
• The most important is that the underlying technology changes and
advances so frequently and rapidly that experience of one product may
not be applied to the other one.
• All such business and environmental constraints bring risk in software
development hence it is essential to manage software projects
efficiently.
Continue…
Continue…
• The image above shows triple constraints for software projects
• It is an essential part of software organization to deliver quality
product, keeping the cost within client’s budget constrain and deliver
the project as per scheduled. 
• There are several factors, both internal and external, which may
impact this triple constrain triangle.
• Any of three factor can severely impact the other two.
• Therefore, software project management is essential to incorporate
user requirements along with budget and time constraints.