Exams Attended

Mock Exams

Make Homepage

Bookmark this page

Subscribe Email Address

SDLC Interview Questions and Answers

Ques 11. What are the differences between Agile and Waterfall Methodologies?

AgileWaterfall
It separates the project development lifecycle into sprints.The software development process is divided into distinct phases.
It follows an incremental approachWaterfall methodology is a sequential design process.
Agile methodology is known for its flexibility.Waterfall is a structured software development methodology so most times it can be quite rigid.
Agile can be considered a collection of many different projects.Software development will be completed as one single project.
Agile is quite a flexible method that allows changes to be made in the project development requirements even if the initial planning has been completed.There is no scope for changing the requirements once the project development starts.
The agile methodology follows an iterative development approach because of this planning, development, prototyping, and other software development phases may appear more than once.All the project development phases like designing, development, testing, etc. are completed once in the Waterfall model.
The test plan is reviewed after each sprintThe test plan is rarely discussed during the test phase.
Agile development is a process in which the requirements are expected to change and evolve.The method is ideal for projects which have definite requirements and changes not at all expected.
In Agile methodology, testing is performed concurrently with software development.In this methodology, the “Testing” phase comes after the “Build” phase
Agile introduces a product mindset where the software product satisfies the needs of its end customers and changes itself as per the customer’s demands.This model shows a project mindset and places its focus completely on accomplishing the project.
The agile methodology works exceptionally well with Time & Materials or non-fixed funding. It may increase stress in fixed-price scenarios.Reduces risk in the firm fixed price contracts by getting a risk agreement at the beginning of the process.
Prefers small but dedicated teams with a high degree of coordination and synchronization.Team coordination/synchronization is very limited.
Product owner with team prepares requirements just about every day during a project.Business analysis prepares requirements before the beginning of the project.
The test team can take part in the requirements change without problems.It is difficult for the test to initiate any change in requirements.
The description of project details can be altered anytime during the SDLC process.Detail description needs to implement the waterfall software development approach.
The Agile Team members are interchangeable, as a result, they work faster. There is also no need for project managers because the projects are managed by the entire teamIn the waterfall method, the process is always straightforward so, the project manager plays an essential role during every stage of SDLC.

Is it helpful? Add Comment View Comments
 

Ques 12. Describe waterfall software development life cycle model.

Waterfall is a sequential and non-iterative SDLC model which describes the flowing of phases downwards one by one. The process does not start a phase unless the previous phase is completed once and for all completely. The waterfall model consists of the following phases:

    • Requirements gathering
    • Design
    • Implementation
    • Testing
    • Maintenance 

Is it helpful? Add Comment View Comments
 

Ques 13. Briefly describe the phases in the waterfall model.

  • Requirements gathering: All the requirements are gathered and analysis is performed for the complete system.
  • Design: Various design models are created for the complete system after the requirements gathering phase has been completed and ended.
  • Implementation: The complete system is implemented once the design for the system has been frozen.
  • Testing: The complete system is tested after all the construction and integration has completed.
  • Maintenance: Post implementation support carries out after the implementation of the system. 

Is it helpful? Add Comment View Comments
 

Ques 14. Explain the strengths of the waterfall model.

The strengths of the waterfall model are:

  • No planning needed
  • Works well for small projects with fixed and clear requirements.
  • Lesser cost as planning overhead is less
  • Quickest delivery of the complete system 

Is it helpful? Add Comment View Comments
 

Ques 15. Explain the weaknesses of the waterfall model.

Weaknesses of waterfall model are:

a) It is Inflexible
b) Accommodating changes is very hard
c) Longest tangible delivery time. The customer does not see anything but the whole product when itís ready.
d) Unsuitable for large projects and where requirements are not clear. 

Is it helpful? Add Comment View Comments
 

Most helpful rated by users:

©2023 WithoutBook