Que. 1: Which SDLC model will you use for this given problem and why ?

Soln. 1: The best suitable SDLC model for this given problem is V-model. The V-model is an
SDLC model where execution of processes happens in a sequential manner in a V-shape. It is
also known as Verification and Validation model. The V-Model is an extension of the waterfall
model and is based on the association of a testing phase for each corresponding development
stage. This means that for every single phase in the development cycle, there is a directly
associated testing phase. This is a highly-disciplined model and the next phase starts only after
completion of the previous phase.
Under the V-Model, the corresponding testing phase of the development phase is planned in
parallel. So, there are Verification phases on one side of the ‘V’ and Validation phases on the
other side. The Coding Phase joins the two sides of the V-Model. In this given problem the
requirements are clearly defined. The user doesn’t require to modify the existing requirements
again & again as they are already fixed & one doesn’t have to introduce new version of this
project. Although, this model is used when ample technical resources are available with technical
expertise. The V-Model works in two phases: Development Phase & Validation Phase. The two
phases works in parallel to each other.
In this problem, the development phase will involve the development of the product, test case
design & plan for testing the work product whereas the Validation phase involves the actual
testing that is to be carried out concurrent to the development. Also, this model brings out lesser
bugs & lesser cost as developer doesn’t have to modify the product again and again. As testing is
done side by side, so the product developed is more reliable. This model is best suitable for
making the small projects that has less complexity.
We can’t use any other model for this given problem due to the following reasons:
1. We can’t use waterfall model because of its rigid flexibility & the guarantee of success is very
low.
2. As the requirements are clear & fixed and also it involves lesser risks so it is preferred over
spiral and prototype model.
3. We don’t require multiple versions or any further major modifications for this given project,
so incremental and evolutionary models.