0% found this document useful (0 votes)
124 views

SDLC Models

The document discusses several software development life cycle (SDLC) models, including their pros and cons. It begins with an overview of SDLC phases such as planning, analysis, design, coding, testing, and deployment. Then it examines the waterfall model, B-model, incremental model, V-model, spiral model, rapid application development model, agile model, XP model, unified process model, and wheel-and-spoke model. For each model, it outlines the main characteristics and highlights some of the key advantages and disadvantages. The document provides an overview of different approaches to structuring software development projects.

Uploaded by

Nilima Pokharel
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
124 views

SDLC Models

The document discusses several software development life cycle (SDLC) models, including their pros and cons. It begins with an overview of SDLC phases such as planning, analysis, design, coding, testing, and deployment. Then it examines the waterfall model, B-model, incremental model, V-model, spiral model, rapid application development model, agile model, XP model, unified process model, and wheel-and-spoke model. For each model, it outlines the main characteristics and highlights some of the key advantages and disadvantages. The document provides an overview of different approaches to structuring software development projects.

Uploaded by

Nilima Pokharel
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 18

2022

SDLC Models

TEAM MEMBERS
- NILIMA POKHAREL
- DIPESH CHAUDHARY
- KAMAL THAPA
- MANISHA SHARMA
Contents
Introduction............................................................................................................................................... 3

Overview............................................................................................................................................... 3

Phases of SDLC .................................................................................................................................... 3

SDLC Models ........................................................................................................................................... 5

Waterfall Model .................................................................................................................................... 5

Pros of Waterfall model .................................................................................................................... 5

Cons of Waterfall model ................................................................................................................... 5

B-Model ................................................................................................................................................ 6

Pros of B- model ............................................................................................................................... 7

Cons of B- model .............................................................................................................................. 7

Incremental Model ................................................................................................................................ 7

Pros of Incremental model ................................................................................................................ 7

Cons of Incremental model ............................................................................................................... 7

V-Model ................................................................................................................................................ 8

Pros of V-Model ............................................................................................................................... 8

Cons of V-model............................................................................................................................... 8

Spiral Model ......................................................................................................................................... 9

Pros of Spiral Model ......................................................................................................................... 9

Cons of Spiral Model ........................................................................................................................ 9

Rapid Application Model ................................................................................................................... 10

Pros of Rapid Application Model ................................................................................................... 10

Cons of Rapid Application Model .................................................................................................. 10

Agile Model ........................................................................................................................................ 11

Pros of Agile Model........................................................................................................................ 11

Cons of Agile Model ...................................................................................................................... 11


XP-Model ........................................................................................................................................... 12

Pros of XP Model ........................................................................................................................... 12

Cons of XP Model .......................................................................................................................... 12

Unified Process Model ....................................................................................................................... 13

Pros of Unified Process Model ....................................................................................................... 13

Cons of Unified Process Model ...................................................................................................... 13

Wheel-and-spoke Model ..................................................................................................................... 13

Pros of Wheel and spoke Model ..................................................................................................... 13

Cons of Wheel and spoke model .................................................................................................... 14

Conclusion .......................................................................................................................................... 14

References............................................................................................................................................... 15
Introduction

Overview
SDLC stands for Software Development Life Cycle model. It is the process of creation of standard
quality software with precisely defined steps (Altvater, 2021). By this model high quality software can
be produced with lowest budget in a short period of time. Project team can achieve their objectives and
reduce risks of project by following the steps of SDLC wisely. It identifies all the requirements of
completing a project, estimates cost and time, detect risks and evaluate future opportunities of the project.
Therefore, SDLC is the modern method of creating a good software.

Phases of SDLC
Software Development Life Cycle model consists of six phases. They are described below.

Software Development
Life Cycle

Fig 1. Phases of SDLC


Planning phase includes plans and objectives for the upcoming project. It is also called feasibility phase.
Risks are defined and it is checked whether the project will be feasible or not. In this phase, project
outlines are defined, cost and time are predicted and resources are determined. Thus, planning phase is
the initial stage where all the significant decisions are made and implemented.

Analysis phase includes gathering of all the requirements needed for project development. In this phase,
prototype requirements are defined, alternatives to existing prototype are evaluated and research is
conducted to indentify the end-users needs (Preston, 2022). This phase is displayed graphically in SRS
document. All the important requirements of the software and hardware for the development of the
system are determined to prevent the overdrawing of funding and resources.

Design phase includes prototyping and designing software after the identification of the requirements
for software development. After the software architects completes the design, developers team receive
the design in a document format and coding is started according to design.

Coding phase includes selecting a suitable programming language and initiating to code. Different tasks
are splited into modules and these modules are allocated to eligible developers. Coding is done by
programmers in a team.

Testing phase includes evaluation of the modules in order to prevent unnecessary bugs. Reviewing of
the developed software is done and if any issues are detected in the software , developers are ordered to
fix those issues and repair the software. Regression testing and retesting are done done again and again
until the software meets the expectations of the users.

Deployment phase includes deploying the software to the market where consumers will get the chance
to use the developed software. Product is pushed across different environments like testing and staging
areas (Team, 2022). Due to the deployment phase, stakeholders can use the product carefully catching
the final issues before releasing the product in the competitive market.

Maintainence phase includes maintainng and improving the software after it has been released in the
market. Just reaching the product into the market is not enough. The product is updated according to the
changing needs of the end-users. Issues reported by the users shouldnot be neglected. Many changes are
carried out that consists of bugs fixing, software updating, fixing the consumers issues and improving
the software furthermore.
SDLC Models
Waterfall Model
Waterfall model is a continuous model which splits software development process into defines phases
that makes easy to carry out several tasks. Each phase of waterfall model should be completed before
the beginning of next phase (Martin, 2022). Waterfall model was created by Winston Royce in 1970.
Waterfall model consists of six stages that are described below.

Pros of Waterfall model


- It is feasible for small projects with well-defined requirements.
- Project structure is clear, precise and well designed (Kishore, 2021).
- Smooth information transfer as each phase is completed before the beginning of next phase.
- It executes project within allocated deadline due to its strict schedule of tasks completion.

Cons of Waterfall model


- Errors can be corrected only at the time of phase.
- Much time of developers is needed for the documentation.
- It is not suitable big projects as requirements frequently alters.
- Feedback of clients cannot be considered at the time ongoing phase
B-Model
B- Model is the extended form of waterfall model. The model was created by Birrell and Ould. Each
stage is dependent to other stages. All the phases of this model are arranged in B-shaped.

Fig 2. Phases of B Model

Fig 2 shows that B model initiates with inception phase in which needs are identified for the new system.
Then its goes to analysis phase where problems of the development of the system is defined,
specifications for the system are created and feasibility study is done. Third stage is design phase where
structure, interfaces, input and output of the system is designed. Now production phase begins in which
code is written, tested and documentation is made for the system. After system is produced it passes
through operation phase that uses the system in the business. Then the system goes through evaluation
phase that evaluates the developed system. Finally, in the maintenance phase, inception of ideas are
done and system is improved and updated furthermore.
Pros of B- model
- It is flexible as it interacts with the requirements of the system.
- Any phase can be reversed to previous in case errors happen to occur.
- Any changes are carried out in the maintenance phase at the same period of time.

Cons of B- model
- It is steady in making changes. For every modification, another analysis and design can be
conducted for new system requirements that makes the investigation understood properly.

Incremental Model
Requirements for the software development are fragmented into multiple independent modules. Each
repeating process go through different phases i.e. requirement identification, designing, code writing and
testing. Each succeeding release adds function to the former release till the functionality of the system
designed is implemented. After the initial increment implemented, system is set into production, vital
requirements are labelled in the 1st increment and additional features included in further increments.

Pros of Incremental model


- It easy to recognize errors (Martin, 2022).
- It is more flexible and easy to test and debug.
- It handles risks during iteration time only.
- Prominent functionality is received by clients early.

Cons of Incremental model


- It needs proper planning.
- It requires distinct module interfaces.
- Cost of implementing this model is high.
V-Model
In V-model, processes of software development sequentially performs in a V-shape. Since the issues of
found by the waterfall model at end stage was hard for the engineers to fix. So in order to overcome this
problem, V-model was introduced (Prasanna, 2022). This model confirms implementing testing right
from the initial phases of the software development. V model works by Verification and Validation.
Verification includes inactive analysis of testing without directing code for instance, reviews and
inspection whereas validation includes dynamic analysis of testing by directing code for instance and
categorizing functional & non-functional testing under validation.

Fig 4. How V-Model works

Pros of V-Model
- It is straightforward, uncomplicated, user friendly and has solid base to use.
- It is time saving as trial designing and development is done before coding.
- This model tracks errors proactively that aids in fixing bugs and system issues.
- It doesn’t have loopholes and disallows unidirectional data flow during development process.

Cons of V-model
- V model is very rigid regarding utilization and execution process is complex.
- Lack of initial prototypes makes it difficult to produce professional software.
- Object-oriented system is unsuitable to build due to its design uncertainties,.
Spiral Model
Spiral model is the most critical SDLC model (Prasanna, 2022). It supports many risk handling attributes.
Fig 5. Shows that spiral with many loops are resembled by this model. The count of loops in the spiral
is not discoverable and they may vary. Each loop in the spiral is called as phase of development process
of the software. The count of phases needed can be modified by the project manager regarding risks.

Fig 5. Loops of Spiral Model

Pros of Spiral Model


- It is appropriate for developing large-scale projects.
- It has risks managing features and administration at each and every phases.
- It is compliant in including replacements requests in project requirements.
- Customers can adapt and utilize the evolution of product before completing the project.

Cons of Spiral Model


- It is not suitable for small projects as it is very expensive.
- Maintenance of prototypes is difficult as dictates & protocols should be followed properly.
- Project management is difficult due to the need of documentation size in intermediate stages.
- Due to the count of undiscovered phases at the project initiation, management of time is difficult.
Rapid Application Model
RAD model is like agile methodology and it concentrates on constant repetitions and prototypes that are
based on the user feedbacks (Egeonu, 2022). Instead of rigid development plans, this model aids in
incorporating updates that are based on usages. By using this model changes to design can be made,
features can be removed or add and interfaces can be edited without disturbing the entire process.
Therefore, rapid prototypes testing is translated and further improvements are done. Below is the figure
that shows how the Rapid Application Model works.

Fig 6. How RAD Model works

Pros of Rapid Application Model


- It Integrates system from the beginning.
- Initial reviews are occurred quickly.
- It Enhances component reusability.
- It reduces the time for software development.
- It facilitates user feedbacks and ensures stakeholders are satisfied with final product.

Cons of Rapid Application Model


- It requires a skilled team of developers or designers.
- Modularized projects can only be built by this model.
- With the presence of many stakeholders, it is difficult to manage.
- A powerful team and good individual performances are acceptable.
Agile Model
Agile software development refers to an iterative approach to software development, in which cross-
functional teams collaborate to evolve requirements and solutions. Agile development benefits teams by
enabling them to deliver value faster, with higher quality and predictability, and by enabling them to
respond to change more effectively.

Fig 7. Phases of Agile Model

Pros of Agile Model


- Issues can be detected and fixed faster.
- Software can be developed quicker (Olic, 2020).
- Changes can be adapted and responded sooner.
- Immediate feedbacks can be received from team.
- Premature optimization is a process of less worries.
- Ideas can be experimented and tested as its cost is low.

Cons of Agile Model


- It is difficult for new members to get up to speed with documentation because it gets sidetracked.
- Since progress happens over several cycles, it's harder to measure progress than it is in Waterfall.
- Due to constant interaction between developers and customers, it requires more time and energy.
- Since the Agile Model has no clear ends, projects can become long lasting.
XP-Model
XP model is a form of agile model. It aims at developing high quality software and greater life quality
life for development team. This model was introduced by Kent Beck. Extreme programming model
works on five values: communication, simplicity, feedbacks, courage and respect. Team members have
great role in tracking, customer, programming, testing and coaching (Kukhnavets, 2018).

Fig 8. Planning/ feedback loops of XP Model

Pros of XP Model
- XP model processes are visible and accountable.
- It increases employees’ satisfaction and retention.
- Constant feedbacks can be created for making changes.
- Extremely simple code can be created and improved at any time.
- It saves costs and time needed for project realization and documentation.

Cons of XP Model
- This model is more focused on coding side rather than on designing.
- It is not the best option for geographically separated programmers.
- There is lack of measurement of code quality assurance.
- There is lack of defects documentation.
Unified Process Model
Unified process model is a object-oriented software development model. This model was introduced by
Ivar Jacobson, Grady Bootch and James Rambaugh. It is produced by Rational Corporation. Design and
documentation is done with the help of UML. It is incorporated in IBM RMC product. IBM stands for
International Business Machine Corporation and RMC stands for Rational Method Composer. IBM
permits to design, customize and personalize the model. Its features are: use case directed, process
repetition, incremental, delivered by web technology and customized in modular form.

Pros of Unified Process Model


- It produces good documentation.
- It offers of risk management support.
- It helps in reusing components reducing time duration.
- It offers proper online support like tutorials and trainings.

Cons of Unified Process Model


- Expert professional team needed.
- It is complex and unorganized process model.
- It is more dependent in the risk management.
- It’s not easy for integration again and again.

Wheel-and-spoke Model
Wheel and Spoke Model is constant parallel software development methodology (Thing, 2022). It is a
modification of spiral model and works with small initial teams. This model can be used best in the
design phase and prototyping phase. This model is a bottom up process. In this model, new requirements
of system are defined by several unique programs and good API is generated. Initial prototype is
implemented and given to first program for the integration into needs which forms the 1st spoke of the
model. Then a proper feedback is collected from the 1st program and then changes are created back to
the prototype. Now the common prototype can be used by next program with added changes which forms
another spoke of the model. Final product is the union of features used by many programs forming a
wheel. Finally, testing and bug fixing are fed back into code base that form spokes.

Pros of Wheel and spoke Model


- Few programmers are required as it has low initial risks.
- Team can gain expertise of different programs that can be used for next program.
Cons of Wheel and spoke model
- Bottlenecks can be created by the model which is major issue.

Conclusion
Software development life cycle models are the best methodologies for creating quality software with
appropriate cost and time. All models of SDLC helps in measuring and improving development
processes of a software (Jevtic, 2019). Companies maximize the efficiency of each stages of the model.
Due to increasing power of computing, SDLC models are higher in demand by software engineers for
developing a good software. So to get faster results, companies can reduce costs and time for software
development and meet the current needs of their customers. Thus, SDLC models aids in achieving
software aims and objectives in a standard way.
References

Altvater, A. (2021, March 30). What is SDLC? understand the software development life cycle. Stackify.
Retrieved October 20, 2022, from https://stackify.com/what-is-sdlc/

Preston, M. (2022, January 21). 7 phases of the System Development Life Cycle Guide. 7 Phases of the
System Development Life Cycle Guide. Retrieved October 21, 2022, from
https://www.clouddefense.ai/blog/system-development-life-
cycle#:~:text=What%20Are%20the%207%20Phases,testing%2C%20implementation%2C%20an
d%20maintenance

Team, D. S. U. (2022, September 13). 7 stages of SDLC: Software Development Life Cycle.
DreamSoft4u. Retrieved October 21, 2022, from https://www.dreamsoft4u.com/blog/sdlc-7-
stages-of-software-development-life-cycle

Martin, M. (2022, September 17). What is waterfall model in SDLC? advantages and disadvantages.
Guru99. Retrieved October 21, 2022, from https://www.guru99.com/what-is-sdlc-or-waterfall-
model.html

Kishore, K. (2021, June 7). Advantages & disadvantages of the waterfall model. Harappa. Retrieved
October 21, 2022, from https://harappa.education/harappa-diaries/advantages-and-disadvantages-
of-waterfall-
model/#:~:text=Perhaps%20one%20of%20the%20biggest,project%20can%20easily%20get%20
muddled.

https://www.researchgate.net/figure/The-b-model-extends-the-waterfall-model-In-a-sense-the-b-
model-was-an-attempt-to-modify_fig2_220631422

Jasour Obeidat Follow Independent Researcher at Middle East Univesity. (n.d.). B shaped model.
Share and Discover Knowledge on SlideShare. Retrieved October 21, 2022, from
https://www.slideshare.net/Jasour/b-shaped-model
Martin, M. (2022, August 27). Incremental model in SDLC: Use, advantage & disadvantage. Guru99.
Retrieved October 24, 2022, from https://www.guru99.com/what-is-incremental-model-in-sdlc-
advantages-disadvantages.html

Incremental model (software engineering) - javatpoint. www.javatpoint.com. (n.d.). Retrieved October


24, 2022, from https://www.javatpoint.com/software-engineering-incremental-model

Prasanna. (2022, January 7). V model advantages and disadvantages: What is V-model? when and how
to use it?merits and demerits. A Plus Topper. Retrieved October 25, 2022, from
https://www.aplustopper.com/v-model-advantages-and-disadvantages/

Prasanna. (2022, January 16). Spiral model advantages and disadvantages: Advantages and
disadvantages of using spiral model. A Plus Topper. Retrieved October 26, 2022, from
https://www.aplustopper.com/spiral-model-advantages-and-disadvantages/

Egeonu, E. (2022, June 7). The advantages and disadvantages of the Rad Model. DistantJob. Retrieved
October 26, 2022, from https://distantjob.com/blog/rad-model-advantages-and-disadvantages/

Olic, A. (2020, October 28). Advantages and disadvantages of agile project management [checklist] ·
activecollab. ActiveCollab. Retrieved October 26, 2022, from
https://activecollab.com/blog/project-management/agile-project-management-advantages-
disadvantages

What is agile? - what is Scrum? - agile FAQ's. Cprime. (2022, October 2). Retrieved October 26,
2022, from https://www.cprime.com/resources/what-is-agile-what-is-scrum

Kukhnavets, P. (2018, March 18). Disadvantages and advantages in extreme programming. Hygger.
Retrieved October 26, 2022, from https://hygger.io/blog/disadvantages-and-advantages-of-
extreme-programming/

Rup and its phases. GeeksforGeeks. (2022, June 13). Retrieved October 26, 2022, from
https://www.geeksforgeeks.org/rup-and-its-phases/
Thing. (2022). Wheel and spoke model. DBpedia. Retrieved October 26, 2022, from
https://dbpedia.org/page/Wheel_and_spoke_model

Wikimedia Foundation. (2014, February 15). Wheel and spoke model. Wikipedia. Retrieved October
26, 2022, from
https://en.wikipedia.org/wiki/Wheel_and_spoke_model#:~:text=The%20Wheel%20And%20Spo
ke%20Model,and%20prototyping%20stages%20of%20development.

You might also like