Software Development Life Cycle: A Comparison of Waterfall, V-Model, and Spiral Model, Study Guides, Projects, Research of Computer Vision

An overview of three popular software development life cycle models: Waterfall, V-Model, and Spiral Model. The Waterfall Model is a linear-sequential approach, while the V-Model adds testing to each phase. The Spiral Model adds risk analysis and prototyping to the Waterfall Model. Understanding the strengths and weaknesses of each model is crucial for selecting the appropriate one for a development project.

Typology: Study Guides, Projects, Research

2016/2017

Uploaded on 06/19/2022

rd-chhanel
rd-chhanel 🇳🇵

3.5

(6)

24 documents

1 / 9

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1
Network Security 2017
Task 1:
Describe any two iterative & two sequential lifecycle model:
Introduction:
It is the software development process used by software industry to design, develop and test the
quality of software’s. The main aim of software development life cycle is to provide the quality
software as per the customers requirements within a particular time and in a given budget.it consists
of detailed plan to make software, maintain, replace, alter and enhance specific software. There are
various software development life cycle model defined and designed which are followed during the
software development process. Each model follows unique steps at the time of software
development. The most popular models of software development life cycle like waterfall, v model,
prototyping and spiral are shortly described below.
Sequential model:////////////////
Water Fall Model: diagram////////////////////
It is the most widely used model for software development. It is also known as linear-sequential life
cycle model. It is easy to use and understand. Each step is well defined and after completion of first
phase we only move to the second phase. There is no overlapping of phases.
Requirements – defines needed information, function, behavior, performance and interfaces
Design – data structures, software architecture, interface representations, algorithmic details.
Implementation – source code, database, user documentation, testing.
Phases:///////////////////////
Waterfall Strengths
Easy to understand, easy to use
Provides structure to inexperienced staff
Milestones are well understood
Sets requirements stability
Good for management control (plan, staff, track)
Works well when quality is more important than cost or schedule
Waterfall Deficiencies
Rajan Raj Pant (HND / Third Semester)
pf3
pf4
pf5
pf8
pf9

Partial preview of the text

Download Software Development Life Cycle: A Comparison of Waterfall, V-Model, and Spiral Model and more Study Guides, Projects, Research Computer Vision in PDF only on Docsity!

Task 1: Describe any two iterative & two sequential lifecycle model: Introduction: It is the software development process used by software industry to design, develop and test the quality of software’s. The main aim of software development life cycle is to provide the quality software as per the customers requirements within a particular time and in a given budget.it consists of detailed plan to make software, maintain, replace, alter and enhance specific software. There are various software development life cycle model defined and designed which are followed during the software development process. Each model follows unique steps at the time of software development. The most popular models of software development life cycle like waterfall, v model, prototyping and spiral are shortly described below. Sequential model://////////////// Water Fall Model: diagram//////////////////// It is the most widely used model for software development. It is also known as linear-sequential life cycle model. It is easy to use and understand. Each step is well defined and after completion of first phase we only move to the second phase. There is no overlapping of phases.  Requirements – defines needed information, function, behavior, performance and interfaces  Design – data structures, software architecture, interface representations, algorithmic details.  Implementation – source code, database, user documentation, testing. Phases://///////////////////// Waterfall Strengths  Easy to understand, easy to use  Provides structure to inexperienced staff  Milestones are well understood  Sets requirements stability  Good for management control (plan, staff, track)  Works well when quality is more important than cost or schedule Waterfall Deficiencies Rajan Raj Pant (HND / Third Semester)

 All requirements must be known upfront  Deliverables created for each phase are considered frozen – inhibits flexibility  Can give a false impression of progress  Does not reflect problem-solving nature of software development – iterations of phases  Integration is one big bang at the end  Little opportunity for customer to preview the system (until it may be too late) When to use the Waterfall Model  Requirements are very well known  Product definition is stable  Technology is understood  New version of an existing product  Porting an existing product to a new platform. v-model: v model is known as verification and validation model. It is same like waterfall fall model but it includes testing for each corresponding development stage. After each phases are tested and verified than only we move to the next phase so there is a direct relation of each phases with testing phase. The following illustration depicts the different phases in a V-Model of the SDLC. Phases?////////////////// Qx zThe advantages of the V-Model method are as follows − Rajan Raj Pant (HND / Third Semester)

•Adds risk analysis, and 4gl RAD prototyping to the waterfall model •Each cycle involves the same sequence of steps as the waterfall process model Phases of spiral model are described below:

  1. Determine objectives, alternatives and constraints •Objectives: functionality, performance, hardware/software interface, critical success factors, etc. •Alternatives: build, reuse, buy, sub-contract, etc.
  2. Evaluate alternatives, identify and resolve risks •Study alternatives relative to objectives and constraints •Identify risks (lack of experience, new technology, tight schedules, poor process, etc. •Resolve risks (evaluate if money could be lost by continuing system development
  3. Develop next-level product  Typical activities:  Create a design  Review design Develop code Inspect code  Test product Rajan Raj Pant (HND / Third Semester)

 Spiral Quadrant

  1. Plan next phase  Typical activities  Develop project plan  Develop configuration management plan  Develop a test plan  Develop an installation plan Spiral Model Strengths  Provides early indication of insurmountable risks, without much cost  Users see the system early because of rapid prototyping tools  Critical high-risk functions are developed first  The design does not have to be perfect  Users can be closely tied to all lifecycle steps  Early and frequent feedback from users  Cumulative costs assessed frequently Spiral Model Weaknesses  Time spent for evaluating risks too large for small or low-risk projects  Time spent planning, resetting objectives, doing risk analysis and prototyping may be excessive  The model is complex Risk assessment expertise is required  Spiral may continue indefinitely  Developers must be reassigned during non-development phase activities  May be hard to define objective, verifiable milestones that indicate readiness to proceed through the next iteration. When to use?  When there is a budget constraint and risk evaluation is important.  For medium to high-risk projects.  Long-term project commitment because of potential changes to economic priorities as the requirements change with time.  Customer is not sure of their requirements which is usually the case.  Requirements are complex and need evaluation to get clarity.  New product line which should be released in phases to get enough customer feedback. Rajan Raj Pant (HND / Third Semester)

P2:

Describe with an example why a particular life cycle model is elected for a development environment. There are various software development life cycle model that are used based on projects. Software development life cycle model includes sequential and iterative model. Waterfall, v-model fall under sequential where as agile, spiral, prototyping etc fall under iterative model. based on the business requirements and project contents we choose the sdlc model. knowing and understanding each model and when to use it, the advantages and disadvantages of each one is important to know which one is suitable for the project context. Taking this on concern I choose v model software development life cycle for a development environment. Example:////////// As my project requirements are fixed and have a limited budget and time I choose v modle. Factors Waterfall V-Shaped Evolutionary Prototyping Spiral Iterative and Incremental Agile Unclear User Requirement Poor Poor Good Excellent Good Excellent Unfamiliar Technology Poor Poor Excellent Excellent Good Poor Complex System Good Good Excellent Excellent Good Poor Reliable system Good Good Poor Excellent Good Good Short Time Schedule Poor Poor Good Poor Excellent Excellent Strong Project Management Excellent Excellent Excellent Excellent Excellent Excellent Cost limitation Poor Poor Poor Poor Excellent Excellent Visibility of Stakeholders Good Good Excellent Excellent Good Excellent Rajan Raj Pant (HND / Third Semester)

Skills limitation Good Good Poor Poor Good Poor Documentation Excellent Excellent Good Good Excellent Poor Component reusability Excellent Excellent Poor Poor Excellent Poor Viewing requiurements and project context I choose v model as it is best fit model which is easy to use and easy to understand. M1: Rajan Raj Pant (HND / Third Semester)