Q1

SDLC is essential for the development process because:

 SDLC transform the idea of a project into a functional and completely operational
structure. SDLC serves as a pipeline for implementing software projects in a structured
manner. As a result, companies have a procedure they can use for improving software
quality and optimizing the overall development process.
 SDLC outlines each task required to put together a software application. This helps to
reduce waste and increase the efficiency of the development process.
 SDLC ensures the project to stay on track and continue to be a feasible investment for the
company.

Q2
Two additional SDLC process models:
1. V-shaped model

(via https://www.geeksforgeeks.org/)
The V-model is also called as Verification and Validation model. Instead of moving
down in a linear way like waterfall model, the process steps are bent upwards after the
coding phase, to form the typical V shape. The V-Model demonstrates the relationships
between each phase of the development life cycle and its associated phase of testing.
Testing is emphasized in this model more than the waterfall model. The testing
procedures are developed early in the life cycle before any coding is done, during each of
the phases preceding implementation.
 Verification Phases
 Business Requirement Analysis
  System Design
 Architectural Design
 Module Design
 Coding Phase
 Validation Phases
 Unit Testing
 Integration Testing
 System Testing
 Acceptance Testing
 Application
 Requirements are well defined, sincerely documented and stuck.
 Product definition is strong.
 Generation isn't dynamic and is well understood through the task group.
 There are not any ambiguous or undefined requirement.

2. Big Bang Model

The Big Bang model is an SDLC model where we will not follow any precise procedure.
The development just begins with the essential money and efforts as the input, and the
output is the software developed which may or may not be as per client requirement. This
Big Bang Model does not follow and there is a very slight planning essential. There is
little in the way of formal process and the focus is on expending the organizations energy
to develop the final software. Defined phases, gateway criteria, documentation, testing,
etc. are all considered nonessential and are likely not to exist.

Q3
In my opinion, the agile methods are suitable for mid-level or lower scale projects. They are not
suitable for large projects because:
- Agile is not suitable for large software projects which have many team members. These
large projects are usually get divided into many smaller scale projects that has a concrete
structure and does not have place for a lot of mistakes to adapt.
- A trust relationship must exist between members of the team, which is hard for large
projects which include a large number of members. It takes time to build trust amongst
team members.
 - Large projects often have a deadline to hit, but that goes against the Agile ethos that
software is delivered when it is ready, and not to a hard date on a project schedule. The
outcome and timeline of agile development are less predictable. The product owner needs
to allow the opportunity to be flexible with the project scope and timeline.

Q4
In my opinion, agile development is NOT an unplanned software development process. There is
a common misconception that agile is unplanned. People think that agile is without architecture
or design, and agile is without documentation. However, agile actually emphasizes those
activities and make them continuous activities instead of separate project phases. Agile focuses
on getting started with familiar architecture and requirements rather than spending crucial time
on setting up a long-term plan. The Agile development emphasizes “responding to change” over
“following a plan.” Planning in agile is not a rigid structure but a progressive one. Implementing
a short-term plan in agile is more efficient rather than wasting efforts on preparing an elaborate
plan. The team members learn from feedback and iterations, and agile planning is based these
changes and is organized into iterations with a short-term time frame.
 Works Cited

Agile is not Unplanned. (n.d.). Retrieved January 16, 2021, from

https://coding.abel.nu/2013/09/agile-is-not-unplanned/

Essentials: System Development Life Cycle [Guide]. (2019, November 07). Retrieved January
16, 2021, from https://www.intellectsoft.net/blog/what-is-system-development-life-cycle/

Importance of SDLC in Software testing: Performance Lab. (2020, July 22). Retrieved January
16, 2021, from https://performancelabus.com/software-testing-importance-sdlc/#1

Jevtic, G. (2020, October 08). What is SDLC? How the Software Development Life Cycle
Works. Retrieved January 16, 2021, from https://phoenixnap.com/blog/software-
development-life-cycle

LogiGear, Says:, & Says:. (2020, September 23). Pros and Cons of Agile Software Development:
LogiGear Blog. Retrieved January 16, 2021, from https://www.logigear.com/blog/agile-
testing/agile-software-development/

SDLC Big Bang Model in Software Development Lifecycle (SDLC) Tutorial 17 January 2021 -
Learn SDLC Big Bang Model in Software Development Lifecycle (SDLC) Tutorial
(25980): Wisdom Jobs India. (n.d.). Retrieved January 16, 2021, from
https://www.wisdomjobs.com/e-university/software-development-lifecycle-sdlc-tutorial-
1513/sdlc-big-bang-model-25980.html

Software Development Life Cycle. (2015, February 27). Retrieved January 16, 2021, from
http://www.althority.com/sdlc/

When to Use Waterfall vs. Agile. (2019, May 17). Retrieved January 16, 2021, from
https://www.macadamian.com/learn/when-to-use-waterfall-vs-agile/

Zalavadia, S. (2015, December 01). Why Agile Fails in Large Enterprises. Retrieved January 16,
2021, from https://www.infoq.com/articles/agile-fails-enterprise/