SDLC- Models
Questions and Answers-
1 SDLC- Models
1. What are the different models of the software development life cycle?
A1: There are several models used in SDLC. The commonly used SDLC methodologies or models:
• Waterfall Model
• Spiral Model
• Rapid Application Development (RAD) Model
• Iterative or Incremental Model
• Prototype Model
• V-Shaped Model
• Agile Model
2. Which SDLC model is the best?
A1: SDLC models are selected according to the requirements of the development process. Each model provides
unique features for software development. Due to that it may vary software-to-software to decide which model
is best. But nowadays the Agile Model is the most popular and widely adopted by software firms.
3.What is the Waterfall model in SDLC? with its advantages and disadvantages.
A1: The waterfall model is one of the earliest and commonly used software development processes. The
development process is in linear direction and flows steadily downward. we can move on to next phase only
after the first phase is successfully completed.it is also known as the "Linear Sequential Model". Waterfall model
generally used for small projects with stable requirements.
Phases of Waterfall model are -
1. Requirement Analysis
2.System Design
3.Implementation
4.Testing
5.Deployment
6. Maintenance
Advantages of the Waterfall Model
• Simple, easy to understand, and use.
• Suitable for small projects where requirements are well understood.
• Easy to manage due to the standard structure of the model (each phase has specific deliverables and a review
process).
• Easy to implement because of its linear process.
2 SDLC- Models
Disadvantages of Waterfall Model
• Difficulty in estimating the time and cost of the process due to which delayed delivery of the product.
• Poor model for long and ongoing projects.
• Difficulty in implementing new features or requirements in the current development process, as we can’t go
back in process for new requirements.
• Not suitable for complex projects where requirements are not fixed.
4.What is the Spiral model in SDLC?
A1: The spiral model is mostly implemented in high-risk projects. The spiral life cycle model consists of four
stages: planning, risk analysis, engineering, and evaluation. any software project goes through these stages in
iterations which are organized as spiral. The spiral model is a combination of the prototype model and the
waterfall model. Which is mostly used for large and complex projects.
(Four quadrants)
1. In the first phase, the requirements will be gathered.
2. Risks and alternative solutions will be identified and a prototype will be produced
3. Third step will be software and software test are produced in the Development and Test phase
4. Finally in the fourth phase, the output of the project is evaluated and the planning for next iteration is done.
3 SDLC- Models
5. When we can use Spiral Model?
A1: Spiral Model can be used when
• Project is large.
• For medium to high-risk projects
• When requirements are unclear and complex.
• When releases are required to be frequent.
6. What is the RAD model in SDLC?
A1: RAD stands for “Rapid Application Development”. As per the name itself, the RAD model is a model to
develop fast and high-quality software products by: Requirements using workshops.
• Prototyping and early, reiterative user testing of designs.
• The re-use of software components.
• Less formality in reviews and other team communication.
7. What is the Iterative model in SDLC?
A1: In an iterative model application will get divided in small parts and development will be done by specifying
and implementing only in small parts of the software, which can be reviewed to identify further requirements.
This process is repeated, creating a new version of the software for each cycle of the model. The iterative model
is very simple to understand and use. In this model we can’t start developing the complete software with full
specification of requirements
8. What is the Prototype model in SDLC?
A1: It is a trial version of a software. It is a sample product which is designed before starting actual testing. This
model is used when user requirements are not very clear and this software tested based on raw requirements
obtained from user. The available types of prototyping are Rapid, Incremental, Evolutionary, and Extreme.
Prototype Model will work like --
1. We will take basic requirements
2. Based on discussion, we will create initial prototype (Prototype – is a working model)
3. Once working prototype is build, we will ask client to check and use it
4. Next step will be test and enhance
5. Again, we will call user to check and use it and again we will make change as per user's feedback until we get
all the requirements from user
6. Once, all requirements are fulfilled and client will agree, then the last step will be sign off
(Sign off - Deliver the product and finish the contract)
4 SDLC- Models
9.What are the advantages and disadvantages of Prototype models?
A1: Advantages of Prototype model:
1. Users are actively involved in the development
2. Missing functionalities can be identified easily
3. Based on user feedback, SRS document is finalized
Disadvantages of Prototype Model
1. Sample model is not used for actual implementation
2. Scope of the system may expand beyond original plans
10. What is the V-shaped model in SDLC?
A1: The V-shaped model is an updated form of the waterfall model. As the name suggests, the V-shaped model
stands for the verification and validation model. The verification phase includes Development (requirements
analysis, product design, architecture design, and module design) & The validation phase consists of testing (unit
testing, system testing, integration, and acceptance testing). In a V-shaped model, a phase is started only after
successfully completing the last phase. Developers and testers work in parallel to achieve Final Product.
Left hand side will be similar to Waterfall model and the right-hand side will be testing that is associated with it.
The various phases of the V-model are --
1. Requirements Gathering
2.System Requirements
3.Architectural Design
4.Low Level Design
5.Implementation
5 SDLC- Models
Requirements Gathering:
In this phase, the Business Analyst (BA) sits with the customer and find / gather the requirements, what the team
will be working on, what the customer really wants. All the requirements are documented which will be used by
developers and testers.
When the BA is gathering the requirements from client, at the same time Testers are writing User case /
Acceptance Test Cases. These test cases are then used in Acceptance Test execution
System Requirements:
SRS is created. How will be going to making software, what resources will be working on, how much time it will
take, what all technologies team will be working on. So, these all things are considered During the System
Requirements, System test case are written which can be used later during the System Test execution.
Architectural Design:
The testing which is involved during this phase is Integration Testing.
When developers divide the software into two modules (say module 1, module 2) at the same time testers write
test cases that how this module will work when we will integrate module 1 and module 2 and what will be the
functionality. Later on, these test cases are used during the Integration testing
Low Level Design:
When Developers are writing the code for the software testers write Unit test case.
Unit testing is generally done by Developers
Implementation:
After writing the code we actually start implementation activity.
11.What are some advantages and disadvantages of the V-shaped model?
A1:
Advantages of V-shaped Model
• The higher success rate as multiple stages of testing is performed.
• Due to multiple stage testing, the quality of the product increases.
• Each stage has specific deliverables.
• Suitable for small projects where the requirements are easily understood.
6 SDLC- Models
Disadvantages of V-shaped Model
• Expensive, rigid, and least flexible.
• Software is developed during the implementation phase, so there will be no prototype of the software project.
• It is difficult to add new requirements and changes in the middle of the process as the entire system will be
updated, including test documents and requirements documents.
When to use V Model:
1. The V-shaped model should be used for small to medium sized projects where requirements are clearly
defined and fixed.
2. Experienced technical resources are available
12. What is the Agile Model in SDLC? What are the advantages of the Agile Model?
A1: Agile is a Software development methodology which is getting used widely.
it’s a Quick assign Quick Design model, In Which we break the product into small Incremental builds and then
small piece of builds are provided in multiple iteration. Agile methodology needs very limited planning. Agile
assumes that the end users' needs are always changing in IT world, within Agile all the changes are happily
welcomed. It is a combination of iterative and incremental model with focus on customer satisfaction by rapid
delivery of working software product. Within Agile there are multiple frameworks but out of which Scrum is
trending and widely used all over.
A2: The Agile method is a quick and realistic development approach to deliver software with few functional
requirements within two or three weeks. The model is based on iterative and incremental development where
requirements and solutions are developed through collaboration between cross-functional teams. At each
iteration, the software is tested.
The Agile method needs more engagement and support from the customer as testers and developers work
together to establish whether the software meets the requirements. The risks in the Agile method are minor
because constant changes are made based on user feedback.
Advantages of Agile Model
• It is easy to implement, understand, and use.
• It has simple and easy deliverables that are often planned on a sprint basis that ensures frequent and high-
quality deliverables.
• It is suitable for both small and large software development projects.
7 SDLC- Models
Disadvantages of Agile model:
• In case of some software deliverables, especially the large ones, it is difficult to assess the effort required
at the beginning of the software development life cycle.
• There is lack of emphasis on necessary designing and documentation.
• The project can easily get taken off track if the customer representative is not clear what final outcome
that they want.
