Sdlc models
One of the basic notions of the software development process is
SDLC models which stands for Software Development Life Cycle
models. SDLC – is a continuous process, which starts from the
moment, when it’s made a decision to launch the project, and it
ends at the moment of its full remove from the exploitation. There is
no one single SDLC model. They are divided into main groups, each
with its features and weaknesses.
Evolving from the first and oldest “waterfall” SDLC model, their
variety significantly expanded. The SDLC models diversity is
predetermined by the wide number of product types – starting with
a
web application development
to a complex medical software. And
if you take one of the SDLC models mentioned below as the basis –
in any case, it should be adjusted to the features of the product,
project, and company. The most used, popular and important SDLC
models are given below:
Waterfall model
Iterative model
Spiral model
V-shaped model
Agile model
No matter what type of the models has been chosen, each of them
has basic stages which are used by every
software development
company
. Let’s explore those stages as this is important for the
understanding of the each of SDLC models and the differences
between them.
BASIC STAGES OF SOFTWARE DEVELOPMENT LIFE CYCLE
Stage 1. Planning and requirement analysis
Each software development life cycle model starts with the analysis,
in which the stakeholders of the process
discuss the requirements for the final product. The goal of this stage
is the detailed definition of the system requirements. Besides, it is
needed to make sure that all the process participants have clearly
understood the tasks and how every requirement is going to be
implemented. Often, the discussion involves the QA specialists who
can interfere the process with additions even during the
development stage if it is necessary.
Stage 2. Designing project architecture
At the second phase of the software development life cycle, the
developers are actually designing the architecture. All the different
technical questions that may appear on this stage are discussed by
all the stakeholders, including the customer. Also, here are defined
the technologies used in the project, team load, limitations, time
frames, and budget. The most appropriate project decisions are
made according to the defined requirements.
Stage 3. Development and programming
After the requirements approved, the process goes to the next stage
– actual development. Programmers start here with the source code
writing while keeping in mind previously defined requirements. The
system administrators adjust the software environment, front-end
programmers develop the user interface of the program and the
logics for its interaction with the server.
