Professional Documents
Culture Documents
QUALITATIVE QUANTITATIVE
RESEARCH RESEARCH
METHODOLOGY METHODOLOGY
WATERFALL MODEL
THIS SDLC MODEL INCLUDES
GRADUAL EXECUTION OF EVERY
STAGE COMPLETELY. THIS
PROCESS IS STRICTLY
DOCUMENTED AND PREDEFINED
WATERFALL MODEL
WITH FEATURES EXPECTED TO
EVERY PHASE OF THIS SOFTWARE
DEVELOPMENT LIFE CYCLE
MODEL.
ADVANTAGES DISADVANTAGES
Simple to use and understand The software is ready only after the last stage is over
Easy to classify and prioritize tasks Integration is done at the very end, which does not give the
option of identifying the problem in advance
ITERATIVE 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
ITERATIVE MODEL 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.
ADVANTAGES DISADVANTAGES
Some functions can be quickly developed at the beginning Iterative model requires more resources than the waterfall
of the development lifecycle model
The progress is easy measurable Issues with architecture or design may occur because not all
the requirements are foreseen during the short planning stage
The shorter iteration is - the easier testing and debugging Bad choice for the small projects
stages are
It is easier to control the risks as high-risk tasks are The process is difficult to manage
completed first
Problems and risks defined within one iteration can be The risks may not be completely determined even at the final
prevented in the next sprints stage of the project
Flexibility and readiness to the changes in the Risks analysis requires involvement of the highly-qualified
requirements specialists
SPIRAL MODEL
WHICH COMBINES
ARCHITECTURE AND
PROTOTYPING BY STAGES. IT IS A
COMBINATION OF THE ITERATIVE
SPIRAL MODEL AND WATERFALL SDLC MODELS
WITH THE SIGNIFICANT ACCENT
ON THE RISK ANALYSIS.
ADVANTAGES DISADVANTAGES
Lifecycle is divided into small parts, and if the risk Can be quite expensive
concentration is higher, the phase can be finished
earlier to address the treats
The development process is precisely documented The risk control demands involvement of the highly-
yet scalable to the changes skilled professionals
The scalability allows to make changes and add new Can be ineffective for the small projects
functionality even at the relatively late stages
The earlier working prototype is done - sooner users Big number of the intermediate stages requires
can point out the flaws excessive documentation
V-SHAPED MODEL
THIS IS A VERY STRICT MODEL
AND THE NEXT STAGE IS STARTED
ONLY AFTER THE PREVIOUS
PHASE. THIS IS ALSO CALLED
“VALIDATION AND VERIFICATION”
V SHAPE MODEL MODEL. EVERY STAGE HAS THE
CURRENT PROCESS CONTROL, TO
MAKE SURE THAT THE
CONVERSION TO THE NEXT STAGE
IS POSSIBLE.
ADVANTAGES DISADVANTAGES
Testing and verification take place Bad choice for the small projects
in the early stages
Good for the small projects, where Relatively big risks
requirements are static and clear
AGILE 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
AGILE MODEL 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.
ADVANTAGES DISADVANTAGES
Corrections of functional Difficulties with measuring the final
requirements are implemented into cost because of permanent changes
the development process to provide
the competitiveness
Project is divided by short and The team should be highly professional
transparent iterations and client-oriented
Risks are minimized thanks to the New requirements may conflict with
flexible change process the existing architecture
Fast release of the first product With all the corrections and changes
version there is possibility that the project will
exceed expected time
COMPENTENCY 1: JAVA PROGRAMMING