create table student

(regno varchar(150) not null,

fname varchar(150) not null,
lname varchar(150) not null,
contact varchar(150)unique,
village varchar(150) not null,
program varchar(150) not null,

constraint pg_student primary key(regno));

describe student;

* +380 98 680-03-70
* [email protected]

* Services
o
o
o
o
* Our Expertise
o
o
o
o
o
* How We Work
* Technologies
o
o
o
o
* Case Studies
* Blog
* We Hire
* Contact Us
SDLC Models Explained: Agile, Waterfall, V-Shaped, Iterative, Spiral
August 4, 2017

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.
The programming by itself assumes four stages
* Algorithm development
* Source code writing
* Compilation
* Testing and debugging
Stage 4. Testing
The testing phase includes the debugging process. All the code flaws missed during
the development are detected here, documented, and passed back to the developers to
fix. The testing process repeats until all the critical issues are removed and
software workflow is stable.
Stage 5. Deployment
When the program is finalized and has no critical issues � it is time to launch it
for the end users. After the new program version release, the tech support team
joins. This department provides user feedback; consult and support users during the
time of exploitation. Moreover, the update of selected components is included in
this phase, to make sure, that the software is up-to-date and is invulnerable to a
security breach.
SDLC MODELS
Waterfall SDLC Model
Waterfall � is a cascade SDLC model, in which development process looks like the
flow, moving step by step through the phases of analysis, projecting, realization,
testing, implementation, and support. This SDLC model includes gradual execution of
every stage completely. This process is strictly documented and predefined with
features expected to every phase of this software development life cycle model.

ADVANTAGESDISADVANTAGESSimple to use and understandThe software is ready only after

the last stage is overManagement simplicity thanks to its rigidity: every phase has
a defined result and process reviewHigh risks and uncertaintyDevelopment stages go
one by oneNot the best choice for complex and object-oriented projectsPerfect for
the small or mid-sized projects where requirements are clear and not equivocal
Inappropriate for the long-term projectsEasy to determine the key points in the
development cycleThe progress of the stage is hard to measure while it is still in
the developmentEasy to classify and prioritize tasksIntegration is done at the very
end, which does not give the option of identifying the problem in advanceUse cases
for the Waterfall SDLC model:
* The requirements are precisely documented
* Product definition is stable
* The technologies stack is predefined which makes it not dynamic
* No ambiguous requirements
* The project is short
Iterative SDLC Model
The Iterative SDLC model does not need the full list of requirements before the
project starts. The development process may start with the requirements to the
functional part, which can be expanded later. The process is repetitive, allowing
to make new versions of the product for every cycle. Every iteration (which last
from two to six weeks) includes the development of a separate component of the
system, and after that, this component is added to the functional developed
earlier. Speaking with math terminology, the iterative model is a realization of
the sequential approximation method; that means a gradual closeness to the planned
final product shape.

ADVANTAGESDISADVANTAGESSome functions can be quickly developed at the beginning of

the development lifecycleIterative model requires more resources than the waterfall
modelThe paralleled development can be appliedConstant management is requiredThe
progress is easy measurableIssues with architecture or design may occur because not
all the requirements are foreseen during the short planning stageThe shorter
iteration is - the easier testing and debugging stages areBad choice for the small
projectsIt is easier to control the risks as high-risk tasks are completed firstThe
process is difficult to manageProblems and risks defined within one iteration can
be prevented in the next sprintsThe risks may not be completely determined even at
the final stage of the projectFlexibility and readiness to the changes in the
requirementsRisks analysis requires involvement of the highly-qualified specialists
Use cases for the Iteration model:
* The requirements to the final product are strictly predefined
* Applied to the large-scale projects
* The main task is predefined, but the details may advance with the time
Spiral SDLC Model
Spiral model � is SDLC model, which combines architecture and prototyping by
stages. It is a combination of the Iterative and Waterfall SDLC models with the
significant accent on the risk analysis. The main issue of the spiral model � is
defining the right moment to make a step into the next stage. The preliminary set
time frames are recommended as the solution to this issue. The shift to the next
stage is done according to the plan, even if the work on the previous stage isn�t
done yet. The plan is introduced basing on the statistic data, received during the
previous projects even from the personal developer�s experience.

ADVANTAGESDISADVANTAGESLifecycle is divided into small parts, and if the risk

concentration is higher, the phase can be finished earlier to address the treatsCan
be quite expensiveThe development process is precisely documented yet scalable to
the changesThe risk control demands involvement of the highly-skilled professionals
The scalability allows to make changes and add new functionality even at the
relatively late stagesCan be ineffective for the small projectsThe earlier working
prototype is done - sooner users can point out the flawsBig number of the
intermediate stages requires excessive documentationUse cases for the Spiral model
* Customer isn�t sure about the requirements
* Major edits are expected during the development cycle
* The projects with mid or high-level risk, where it is important to prevent these
risks
* The new product that should be released in a few stages to have enough of clients
feedback
V-shaped SDLC Model
V-shaped SDLC model is an expansion of classic waterfall model and it�s based on
associated test stage for the every development stage. This is a very strict model
and the next stage is started only after the previous phase. This is also called
�Validation and verification� model. Every stage has the current process control,
to make sure that the conversion to the next stage is possible.

ADVANTAGESDISADVANTAGESEvery stage of V-shaped model has strict results so it�s

easy to controlLack of the flexibilityTesting and verification take place in the
early stagesBad choice for the small projectsGood for the small projects, where
requirements are static and clearRelatively big risksUse cases for the V-shaped
model:
* For the projects where an accurate product testing is required
* For the small and mid-sized projects, where requirements are strictly predefined
* The engineers of the required qualification, especially testers, are within easy
reach.
Agile SDLC Model
In the agile methodology after every development iteration, the customer is able to
see the result and understand if he is satisfied with it or he is not. This is one
of the advantages of the agile software development life cycle model. One of its
disadvantages is that with the absence of defined requirements it is difficult to
estimate the resources and development cost. Extreme programming is one of the
practical use of the agile model. The basis of such model consists of short weekly
meetings � Sprints which are the part of the Scrum approach.

ADVANTAGESDISADVANTAGESCorrections of functional requirements are implemented into

the development process to provide the competitivenessDifficulties with measuring
the final cost because of permanent changesProject is divided by short and
transparent iterationsThe team should be highly professional and client-oriented
Risks are minimized thanks to the flexible change processNew requirements may
conflict with the existing architectureFast release of the first product version
With all the corrections and changes there is possibility that the project will
exceed expected timeUse cases for the Agile model:
* The users� needs change dynamically
* Less price for the changes implemented because of the many iterations
* Unlike the Waterfall model, it requires only initial planning to start the
project
Conclusion
If you are already experienced in the SDLC models and you have your own
professional opinion on this � leave your comments in the section below. If you
have questions on about picking up a correct model for your business � Contact Us,
so we could assist you in this question or visit our page dedicated to Custom
Software Development Services to learn more.
During the years of the SDLC evolution, different models were developed from the
basic cascade model to meet a huge variety of development requirements and
expectations. There is no only one suitable model for all the projects, starting
conditions and payment model. Even at the first sight, multi-purpose Agile cannot
be used widely because of some customers� unpreparedness to scale the budget. The
SDLC models often cross in the solutions and particularly look similar.
Download �2017 Global Custom Software Development Rates� to get a comprehensive
analysis of the pricing in three most popular onshore and offshore outsourcing
locations. Hourly rates cards for these territories are included.
Facebook Twitter Google+ LinkedIn
Discuss Your Project
Top of Form

Bottom of Form
Top of Form
Bottom of Form
Newsletter
Subscribe to get the latest updates from our blog
Top of Form
Bottom of Form
* Home
* Services
* How We Work
* Technologies
* Case Studies
* Blog
* We Hire
* Contact Us
* Cookies and Privacy Policy
* +380 98 680-03-70
* [email protected]
*
*
*
*
Copyright � Existek 2012 - 2018

Skip to main content

Submit CV Search candidates Contact us

Top Menu
* Employers
* Jobseekers
* Expertise and Advice
Breadcrumb of the Robert Half Website
1. worklife blog
2. Employer articles
3. 6 basic SDLC methodologies: Which one is best?
6 basic SDLC methodologies: Which one is best?
By Andrew Morris September 7, 2018 at 1:00pm
� � � �

A wise man once said that if you fail to plan, you plan to fail.
The Systems Development Life Cycle (SDLC) gives structure to the madness of
transitioning from the beginning to the end of your project without forgetting a
step.
A number of different SDLC methodologies are used today to guide professionals
through their project-based work.
Here are the key pros and cons of six of the most common SDLC methodologies.
1. Waterfall Model
Waterfall is the oldest and most straightforward of the structured SDLC
methodologies � finish one phase, then move on to the next. No going back. Each
stage relies on information from the previous stage and has its own project plan.
Waterfall is easy to understand and simple to manage.
But early delays can throw off the entire project timeline. And since there is
little room for revisions once a stage is completed, problems can�t be fixed until
you get to the maintenance stage. This model doesn�t work well if flexibility is
needed or if the project is long term and ongoing.
2. V-Shaped Model
Also known as the Verification and Validation model, the V-shaped model grew out of
Waterfall and is characterized by a corresponding testing phase for each
development stage. Like Waterfall, each stage begins only after the previous one
has ended.
This model is useful when there are no unknown requirements, as it�s still
difficult to go back and make changes.
3. Iterative Model
The Iterative model is repetition incarnate. Instead of starting with fully known
requirements, you implement a set of software requirements, then test, evaluate and
pinpoint further requirements. A new version of the software is produced with each
phase, or iteration. Rinse and repeat until the complete system is ready.
One advantage over other SDLC methodologies: This model gives you a working version
early in the process and makes it less expensive to implement changes. One
disadvantage: Resources can quickly be eaten up by repeating the process again and
again.
4. Spiral Model
One of the most flexible SDLC methodologies, the Spiral model takes a cue from the
Iterative model and its repetition; the project passes through four phases over and
over in a �spiral� until completed, allowing for multiple rounds of refinement.
This model allows for the building of a highly customized product, and user
feedback can be incorporated from early on in the project. But the risk you run is
creating a never-ending spiral for a project that goes on and on.
5. Big Bang Model
A bit of an anomaly among SDLC methodologies, the Big Bang model follows no
specific process, and very little time is spent on planning. The majority of
resources are thrown toward development, and even the client may not have a solid
grasp of the requirements. This is one of the SDLC methodologies typically used for
small projects with only one or two software engineers.
Big Bang is not recommended for large or complex projects, as it�s a high-risk
model; if the requirements are misunderstood in the beginning, you could get to the
end and realize the project may have to be started all over again.
6. Agile Model
By breaking the product into cycles, the Agile model quickly delivers a working
product and is considered a very realistic development approach. The model produces
ongoing releases, each with small, incremental changes from the previous release.
At each iteration, the product is tested.
This model emphasizes interaction, as the customers, developers and testers work
together throughout the project. But since this model depends heavily on customer
interaction, the project can head the wrong way if the customer is not clear on the
direction he or she wants to go.
Which SDLC is right for you?
Each of these SDLC methodologies offers unique process for the variety of project
challenges you will encounter in your career.
Finding the right one depends heavily on not just the expected outcome, but the
parameters by which the project is executed.
Tags

Technology

X
Need to hire?
More From the Blog...

Qualifications vs. experience: What to look for in a candidate

The battle between qualifications vs. experience is an age-old conundrum of the
recruitment world. Find out what to look for in a candidate.
Read More
Upskilling and training � who in your team is responsible for it?
In an ever-changing business and recruitment landscape, upskilling and training
isn�t just a �nice to have�, it�s a necessity. But who is responsible for...
Read More

First 30 days in a new job � 30 tips to remember

Feeling anxious about starting your new job? Consider these 30 tips to follow to
help maximise your first 30 days in a new job and ensure you make the...
Read More
Our company
* About us
* Our locations
* Join Robert Half
* Newsletter sign-up
Expertise & Advice
* Salary Guide
* Management advice
* Career advice
* Research and insights
Services
* Search jobs
* Job directory
* Search candidates
* Request talent
* Online timesheet login
* e-Learning
Connect with us
* worklife blog
* LinkedIn
* Facebook
* Twitter
* Google+
* YouTube
� 2018 Robert Half All Rights Reserved.
Privacy statement | Website terms of use | Corporate info | Sitemap | Feedback
IT'S TIME WE ALL WORK HAPPY.�
Skip to main content

Submit CV Search candidates Contact us

Top Menu
* Employers
* Jobseekers
* Expertise and Advice
Breadcrumb of the Robert Half Website
1. worklife blog
2. Employer articles
3. 6 basic SDLC methodologies: Which one is best?
6 basic SDLC methodologies: Which one is best?
By Andrew Morris September 7, 2018 at 1:00pm
� � � �

A wise man once said that if you fail to plan, you plan to fail.
The Systems Development Life Cycle (SDLC) gives structure to the madness of
transitioning from the beginning to the end of your project without forgetting a
step.
A number of different SDLC methodologies are used today to guide professionals
through their project-based work.
Here are the key pros and cons of six of the most common SDLC methodologies.
1. Waterfall Model
Waterfall is the oldest and most straightforward of the structured SDLC
methodologies � finish one phase, then move on to the next. No going back. Each
stage relies on information from the previous stage and has its own project plan.
Waterfall is easy to understand and simple to manage.
But early delays can throw off the entire project timeline. And since there is
little room for revisions once a stage is completed, problems can�t be fixed until
you get to the maintenance stage. This model doesn�t work well if flexibility is
needed or if the project is long term and ongoing.
2. V-Shaped Model
Also known as the Verification and Validation model, the V-shaped model grew out of
Waterfall and is characterized by a corresponding testing phase for each
development stage. Like Waterfall, each stage begins only after the previous one
has ended.
This model is useful when there are no unknown requirements, as it�s still
difficult to go back and make changes.
3. Iterative Model
The Iterative model is repetition incarnate. Instead of starting with fully known
requirements, you implement a set of software requirements, then test, evaluate and
pinpoint further requirements. A new version of the software is produced with each
phase, or iteration. Rinse and repeat until the complete system is ready.
One advantage over other SDLC methodologies: This model gives you a working version
early in the process and makes it less expensive to implement changes. One
disadvantage: Resources can quickly be eaten up by repeating the process again and
again.
Skip to main content Submit CV Search candidates Contact us Top Menu Employers
Jobseekers Expertise and Advice Breadcrumb of the Robert Half Website worklife blog
Employer articles 6 basic SDLC methodologies: Which one is best? 6 basic SDLC
methodologies: Which one is best? By Andrew Morris September 7, 2018 at 1:00pm 6
basic SDLC methodologies: Which one is best? A wise man once said that if you fail
to plan, you plan to fail. The Systems Development Life Cycle (SDLC) gives
structure to the madness of transitioning from the beginning to the end of your
project without forgetting a step. A number of different SDLC methodologies are
used today to guide professionals through their project-based work. Here are the
key pros and cons of six of the most common SDLC methodologies. 1. Waterfall Model
Waterfall is the oldest and most straightforward of the structured SDLC
methodologies � finish one phase, then move on to the next. No going back. Each
stage relies on information from the previous stage and has its own project plan.
Waterfall is easy to understand and simple to manage. But early delays can throw
off the entire project timeline. And since there is little room for revisions once
a stage is completed, problems can�t be fixed until you get to the maintenance
stage. This model doesn�t work well if flexibility is needed or if the project is
long term and ongoing. 2. V-Shaped Model Also known as the Verification and
Validation model, the V-shaped model grew out of Waterfall and is characterized by
a corresponding testing phase for each development stage. Like Waterfall, each
stage begins only after the previous one has ended. This model is useful when there
are no unknown requirements, as it�s still difficult to go back and make changes.
3. Iterative Model The Iterative model is repetition incarnate. Instead of starting
with fully known requirements, you implement a set of software requirements, then
test, evaluate and pinpoint further requirements. A new version of the software is
produced with each phase, or iteration. Rinse and repeat until the complete system
is ready. One advantage over other SDLC methodologies: This model gives you a
working version early in the process and makes it less expensive to implement
changes. One disadvantage: Resources can quickly be eaten up by repeating the
process again and again. 4. Spiral Model One of the most flexible SDLC
methodologies, the Spiral model takes a cue from the Iterative model and its
repetition; the project passes through four phases over and over in a �spiral�
until completed, allowing for multiple rounds of refinement. This model allows for
the building of a highly customized product, and user feedback can be incorporated
from early on in the project. But the risk you run is creating a never-ending
spiral for a project that goes on and on. 5. Big Bang Model A bit of an anomaly
among SDLC methodologies, the Big Bang model follows no specific process, and very
little time is spent on planning. The majority of resources are thrown toward
development, and even the client may not have a solid grasp of the requirements.
This is one of the SDLC methodologies typically used for small projects with only
one or two software engineers. Big Bang is not recommended for large or complex
projects, as it�s a high-risk model; if the requirements are misunderstood in the
beginning, you could get to the end and realize the project may have to be started
all over again. 6. Agile Model By breaking the product into cycles, the Agile model
quickly delivers a working product and is considered a very realistic development
approach. The model produces ongoing releases, each with small, incremental changes
from the previous release. At each iteration, the product is tested. This model
emphasizes interaction, as the customers, developers and testers work together
throughout the project. But since this model depends heavily on customer
interaction, the project can head the wrong way if the customer is not clear on the
direction he or she wants to go. Which SDLC is right for you? Each of these SDLC
methodologies offers unique process for the variety of project challenges you will
encounter in your career. Finding the right one depends heavily on not just the
expected outcome, but the parameters by which the project is executed. Tags
Technology X Need to hire? More From the Blog... Qualifications vs. experience:
What to look for in a candidate Qualifications vs. experience: What to look for in
a candidate The battle between qualifications vs. experience is an age-old
conundrum of the recruitment world. Find out what to look for in a candidate. Read
More Upskilling and training � who in your team is responsible for it? Upskilling
and training � who in your team is responsible for it? In an ever-changing business
and recruitment landscape, upskilling and training isn�t just a �nice to have�,
it�s a necessity. But who is responsible for... Read More First 30 days in a new
job � 30 tips to remember First 30 days in a new job � 30 tips to remember Feeling
anxious about starting your new job? Consider these 30 tips to follow to help
maximise your first 30 days in a new job and ensure you make the... Read More Our
company About us Our locations Join Robert Half Newsletter sign-up Expertise &
Advice Salary Guide Management advice Career advice Research and insights Services
Search jobs Job directory Search candidates Request talent Online timesheet login
e-Learning Connect with us worklife blog LinkedIn Facebook Twitter Google+ YouTube
� 2018 Robert Half All Rights Reserved. Privacy statement | Website terms of use |
Corporate info | Sitemap | Feedback IT'S TIME WE ALL WORK HAPPY.� Skip to main
content Submit CV Search candidates Contact us Top Menu Employers Jobseekers
Expertise and Advice Breadcrumb of the Robert Half Website worklife blog Employer
articles 6 basic SDLC methodologies: Which one is best? 6 basic SDLC methodologies:
Which one is best? By Andrew Morris September 7, 2018 at 1:00pm 6 basic SDLC
methodologies: Which one is best? A wise man once said that if you fail to plan,
you plan to fail. The Systems Development Life Cycle (SDLC) gives structure to the
madness of transitioning from the beginning to the end of your project without
forgetting a step. A number of different SDLC methodologies are used today to guide
professionals through their project-based work. Here are the key pros and cons of
six of the most common SDLC methodologies. 1. Waterfall Model Waterfall is the
oldest and most straightforward of the structured SDLC methodologies � finish one
phase, then move on to the next. No going back. Each stage relies on information
from the previous stage and has its own project plan. Waterfall is easy to
understand and simple to manage. But early delays can throw off the entire project
timeline. And since there is little room for revisions once a stage is completed,
problems can�t be fixed until you get to the maintenance stage. This model doesn�t
work well if flexibility is needed or if the project is long term and ongoing. 2.
V-Shaped Model Also known as the Verification and Validation model, the V-shaped
model grew out of Waterfall and is characterized by a corresponding testing phase
for each development stage. Like Waterfall, each stage begins only after the
previous one has ended. This model is useful when there are no unknown
requirements, as it�s still difficult to go back and make changes. 3. Iterative
Model The Iterative model is repetition incarnate. Instead of starting with fully
known requirements, you implement a set of software requirements, then test,
evaluate and pinpoint further requirements. A new version of the software is
produced with each phase, or iteration. Rinse and repeat until the complete system
is ready. One advantage over other SDLC methodologies: This model gives you a
working version early in the process and makes it less expensive to implement
changes. One disadvantage: Resources can quickly be eaten up by repeating the
process again and again.

update person set age=20 where ID=2;