Comparative Analysis of SDLC Models and Risk Management Techniques

This report provides an overview of Software Development Lifecycle (SDLC) models, including prototyping, spiral, and agile development approaches. It discusses the advantages and disadvantages of each model, emphasizing their iterative nature and practical applications. The report also explores risk management strategies within SDLC, highlighting the importance of identifying threats and implementing mitigation controls. Furthermore, it details the various development environments, such as analysis and design, development, and testing environments, and their roles in ensuring the durability and success of software projects. The analysis includes the importance of feasibility reports in addressing business issues and evaluating software viability, along with the significance of identifying and mitigating product imperfections.

Prototyping Model
Prototypes mean any Software
that are assigned for conducting
pre- experiment over it. And after
checking its durability and
maintainance, launce it in a final
programmes for performing a
specific task.
Advantages
[1] Analysis inedequate
[2] Require excessive time
[3] Development of user's
misunderstanding
[4] Implementation cost
Iterative Software Models
[1] Spiral Method [2] Agile
development

Spiral Method
In this method, the developers try to
maintain the balancing benefits of
top down and bottom up principles.
It resulted from combining both
development and prototype models .
It integrated in its function with
waterfall model. Spiral method is
preferred in massive, expensive and
complex projects. This model is
almost similar to waterfall method in
sequences,divided by preparation,
risk assessment and similarity in
structure.
Advantages
[1] uses as symbol|model for
research process
[2] Developer's early experiment
[3] Repeated the action and launch it

as commercial finally
Disadvantages
[1] Require time and cost to its final
production
[2] Performing a specific task for
evaluation and good results
[3] Designed just as a model with no
usage in future
Agile Development
It develop for increasive and gradual
growth where it can be finalized with
the inter-functioning group
collaboration.
Advantages
[1] Reducing time requirement
[2] Wider space for customer's
interaction and feedback
[3] Satisfied Customer in the

possible way
Disadvantages
[1]Capableness
[2] Needs user's communication and
corporation
[3] At the final stages, paperwork is
completed
[4] Less elemental functionality
[5] Special skills are required for
their operating bodies
Risk Management in SDLC
Models
Identify threats and their causes,
classify them and attached them to a
risk mitigation controller. Have a
vigilanty if there found threats while
forwarding the project to its final
stage

Lifecycle model for
development enviroment
>The analysis and design
enviroment
>The development Enviroment
>The Testing Enviroment;two
parts[a] The System
Integration[b]The user Acceptance
Testing Enviroment
Analysis and Design
Enviroment
It is designated for arranging and
investigating the durability of SDLC.
The condition that incorporated from
top to bottom, to the present
framework and proposed framework.
The Framework engineering is
additionally added so that it help up
in programme equipments. Inside

framework, business experts work
closely with programming engineers
Development Enviroment
This condition is characterized to the
improvement of SDLC. Advanced
with programming procedures. There
are various procedures and tools for
programme development. Likewise it
can be physical in existance where
programming development occurs.
Its developed in such way where
engineers can use it for assessing
their requirement.
Common Build Enviroment
This programme is adjusted to the
improvement durability of SDLC. In
this condition, the engineers perform
workdone in advance,inside the
programme,engineers develop
framework and utilized it for advance

programming aggregation.
Integration Testing Enviroment
It is used for Testing of SDLC
durability. Its includes accompanying
parts,the system integration Testing
Enviroment and User Acceptance
Testing Development. The SITE helps
in testing the whole framework. This
helping body making up a Software,
call it by naming {htt1}
User Acceptance Enviroment
This Testing opration occurs at the
last before the apps launch
commmercially.The idea behind this
testing is to have a good start up
reputation and finalize it to
businessmen community. It does'nt
faciliate with any sort of blunder. It is
completed in various way i.e
information management .It atleast

require two clients for their releasing
into market.
Production Enviroment
In this area, the Software is yet
utilized hypothetically. The clients
are regularingly in search of product
imperfection and bugs.
A shortcut way , in other way a
codical ways are being used by
clients, as a results, there is tons of
defaults found in Software and slow
down its marketing reputation and
value.
Feasibility Report
Feasibility report is focusing on the
bussiness issues and try to solve the
isssues that are being circulated in
the market about the specific
software.

This report try to identify the needs
of their project and possible solution
to the revealed problems providing
sufficient data, high level costing
details and all the possible
evaluation that can be used in the
Software afterwards.
Significant object
It help engineers to concentrate on
the bugs and imperfaction of the
product that was perceived at a time
of marketing.
Benefits of Feasibility
[1] Giving them a task group interest
[2] Identify new chances
[3] Info about "go\no-go" choice
[4] Corporated with bussiness
community
[5] Adoptability of various methods