SDLC

SDLC( SOFTWARE DEVELOPMENT LIFECYCLE)-

Is a systematic process for building software that ensures the quality and
correctness of the software.
WHY SDLC?
• It offers a basis for project planning, scheduling, and estimating
• Provides a framework for a standard set of activities
• It is a mechanism for project tracking and control
• Increase visibility of project planning to all involved stakeholders of the development
process
• Increase and enchace development speed
• Improved client relations
• Helps you to decrease project risk
SDLC PHASES
• Phase 1: Requirement collection and analysis
• Phase 2: Feasibility study
• Phase 3: Design
• Phase 4: Coding
• Phase 5: Testing
• Phase 6: Installation/Development
• Phase 7: Maintenance
REQUIREMENT COLLECTION AND ANALYSIS
• This is the first stage in SDLC process. It is conducted by the senior team members with
inputs form all the stakeholders and domain experts in the industry
• Planning for quality assuranc and recognization of the risks involved is also done at this
stage
• This stage gives a clearer picture of the scope of the entire project and the anticipated
issues, opportunities and defectiveness.
• This helps to finalize the necessary timeline to finish the project
PHASE 2: FEASIBILITY STUDY
• Once the requirement analysis phase is completed the next step is to define and
document software needs. This process is conducted with the help of “SOFTWARE
REQUIREMENT SPECIIFICATION also known as “SRS” document, includes everything
which should be designed and developed during the project life cycle.
*These the are mainly types of feasibilities checks:
-ECONOMIC
-OPERATION FEASIBILITY
-TECHNICAL
-SCHEDULE
FEASIBILITY CHECKS:
• ECONOMIC
- can we complete the project within the budget or not?
FEASIBILITY CHECKS:
• Operational Feasibility
- Can we create operations which is expected by the client?
FEASIBILITY CHECKS:
• Technical
• -Need to check whether the current computer systems can support the software
FEASIBILITY CHECKS:
• SCHEDULE
- Can the project be completed within the given schedule or not.
PHASE 3:
• In this third phase, the system and software design documents are prepared as per the
requirement specification document.
• This helps define overall system architecture.
• This serves as next input for the next phase

*There are 2 kinds of design documents developed in this phase:

1. HIGH-LEVEL DESIGN (HLD)
2. LOW-LEVEL DESIGN (LLD)
HIGH-LEVEL DESIGN
• Brief description and name of each module
• An outline about the functionality of every module
• Interface relationship and dependencies between modules
• Database tables identified along with their key elements
• Complete architecture diagrams along with technology details
LOW-LEVEL DESIGN (LLD)
• Functional logic of the modules
• Database tables, which include type and size
• Complete detail of the interface
• Addresses all types of dependency issues
• Listing of error message
• Complete input and outputs for every module
PHASE 4: CODING
• In this phase, developers start building the entire system by writing code using the
chosen programming language.
• In this phase task are divided into units or modules and assigned to the various
developers
• It is the longest phase of the SDLC process
PHASE 5: TESTING
• Once the software is complete, it is deployed in the testing environment.
• The testing team starts the functionality of the system
• This is done to verify that the entire application works according to the customer
requirement
• This is where QA team will find bugs/errors, and then Developer is the one who will fix
them.
• This is done until the software is bug-free, stable and working
PHASE 6: INSTALLATION
• Once the software testing phase is over and no bugs or errors left in the system the final
deployment starts
• The final software is released and checked for deployment issues

*The Major steps in this phase are

-installation of hardware and software
-user training
-documentation
a. how to execute the package
b. how to enter data
c. how to process the data
PHASE 7: MAINTENANCE
• Once the system is deployed and customer start using the developed system, these are
the 3 activities to follow
- bug fixing- bugs are reported because of some scenarios which are not tested
-upgrade – upgrading the application to the newer version of the software
-enhancement- adding some new feature into the existing software
POPULAR SDLC MODELS
• Software Development Process Models.
1) Big-Bang model
2) Code-and-fix model
3) Waterfall model
4) V model
5) Incremental model
6) RAD model
7) Agile model
8) Iterative model
9) Spiral model
10) Prototype model
 1) BIG-BANG MODEL

• Big-Bang is the SDLC(Software Development Life cycle) model in which no particular

process is followed.
• Generally this model is used for small projects in which the development teams are small.
It is specially useful in academic projects.
• This model is needs a little planning and does not follow formal development.
• The development of this model begins with the required money and efforts as an input.
• The output of this model is developed software, that may or may not be according to the
requirements of the customer.
ADVANTAGES OF BIG-BANG MODEL
• Big-Bang model is a simple model.
• It needs little planning.
• It is simple to manage. It needs just a few resources to be developed.
• It is useful for students and new comers.
DISADVANTAGES OF BIG-BANG MODEL

• It is a very high risk model.

• This model is not suitable for object oriented and complex projects.
• Big-Bang is poor model for lengthy and in-progress projects.
2.CODE-AND-FIX MODEL
• Code and fix model is one step ahead from the Big-Bang model. It identifies the product
that must be tested before release.
• The testing team find the bugs then sends the software back for fixing. To deliver the
fixes developers complete some coding and send the software again for testing. This
process is repeated till the bugs are found in it, at an acceptable level.
ADVANTAGES OF CODE-AND-FIX MODEL
• This model is suitable for small projects.
• It needs less project planning.
Disadvantages of Code-and-fix
• It is difficult to accommodate changes.
• It is not clear what will be delivered and when.
• It is difficult to assess quality.
3) WATERFALL MODEL

• The waterfall model is the classic model or oldest model and is known as mother of all
the model. It is widely used in government projects and many vital projects in company.
• The waterfall model is also called as 'Linear sequential model' or 'Classic life cycle
model'.
• In this model, each phase is executed completely before the beginning of the next phase.
Hence the phases do not overlap in waterfall model.
• This model is used for small projects.
• In this model, feedback is taken after each phase to ensure that the project is on the right
path.
• Testing part starts only after the development is completed.
• i) Communication
The software development starts with the communication between customer and developer.

ii) Planning
It consists of complete estimation, scheduling for project development.

iii) Modeling
• Modeling consists of complete requirement analysis and the design of the project i.e algorithm,
flowchart etc.
• The algorithm is the step-by-step solution of the problem and the flow chart shows a complete flow
diagram of a program.
• iv) Construction
• Construction consists of code generation and the testing part.
• Coding part implements the design details using an appropriate programming language.
• Testing is to check whether the flow of coding is correct or not.
• Testing also checks that the program provides desired output.
• v) Deployment
• Deployment step consists of delivering the product to the customer and taking feedback from them.
• If the customer wants some corrections or demands for the additional capabilities, then the change is
required for improvement in the quality of the software.
ADVANTAGES OF WATERFALL MODEL
• The waterfall model is simple and easy to understand, to implement, and use.
• All the requirements are known at the beginning of the project, hence it is easy to
manage.
• It avoids overlapping of phases because each phase is completed at once.
• This model works for small projects where the requirements are easily understood.
• This model is preferred for those projects where the quality is more important as
compared to the cost of the project.
DISADVANTAGES OF THE WATERFALL MODEL
• This model is not good for complex and object oriented projects.
• In this model, the changes are not permitted so it is not fit for moderate to high risk
changes in project.
• It is a poor model for long duration projects.
• The problems with this model are uncovered, until the software testing.
• The amount of risk is high.
4) V MODEL

• V model is known as Verification and Validation model.

• This model is an extension of the waterfall model.
• In the life cycle of V-shaped model, processes are executed sequentially.
• Every phase completes its execution before the execution of next phase begins.
i) Requirements
• The requirements of product are understood from the customers point of view to know
their exact requirement and expectation.
• The acceptance test design planning is completed at requirement stage because,
business requirements are used as an input for acceptance testing.
ii) System Design
• In system design, high level design of the software is constructed.
• In this phase, we study how the requirements are implemented their technical use.
iii) Architecture design
• In architecture design, software architecture is created on the basis of high level design.
• The module relationship and dependencies of module, architectural diagrams, database
tables, technology details are completed in this phase.
iv) Module design
• In module phase, we separately design every module or the software components.
v) Coding Phase
• The actual code design of module designed in the design phase is grabbed in the coding
phase.
• On the basis of system and architecture requirements, we decide the best suitable
programming language.
• The coding is executed on the basis of coding guidelines and standards.
Advantages of V-model
• V-model is easy and simple to use.
• Many testing activities i.e planning, test design are executed in the starting, it saves more
time.
• Calculation of errors is done at the starting of the project hence, less chances of error
occurred at final phase of testing.
• This model is suitable for small projects where the requirements are easily understood.
Disadvantages of V-model
• V-model is not suitable for large and composite projects.
• If the requirements are not constant then this model is not acceptable.
 Verification Validation

Verification is the process to find whether the software meets the specified The validation process checks whether the software meets requirements and
requirements for particular phase. expectations of the customer.

It evaluates an intermediate product. It evaluates the final product.

The objective of verification is to check whether software is constructed The objective of validation is to check whether the specifications are correct
according to requirement and design specification. and satisfy the business need.

It describes whether the outputs are as per the inputs or not. It explains whether outputs are accepted by the user or not.

Verification is completed before the validation. It is completed after the verification.

Plans, requirement, specification, code are evaluated in the verifications. Actual product or software is tested under validation.
5) INCREMENTAL MODEL

• The incremental model combines the elements of waterfall model and they are applied in
an iterative fashion.
• The first increment in this model is generally a core product.
• Each increment builds the product and submits it to the customer for suggesting any
modifications.
• The next increment implements the customer's suggestions and add additional
requirements in the previous increment.
• This process is repeated until the product is completed.
For example, the word-processing software is developed using the incremental model.
• i) Communication
The software development starts with the communication between customer and
developer.

ii) Planning
It consists of complete estimation, scheduling for project development.

iii) Modeling
• Modeling consists of complete requirement analysis and the design of the project like
algorithm, flowchart etc.
• The algorithm is a step-by-step solution of the problem and the flow chart shows a
complete flow diagram of a program.
• iv) Construction
• Construction consists of code generation and the testing part.
• Coding part implements the design details using an appropriate programming language.
• Testing is to check whether the flow of coding is correct or not.
• Testing also checks that the program provides desired output.
• v) Deployment
• Deployment step consists of delivering the product to the customer and taking feedback from them.
• If the customer wants some corrections or demands for the additional capabilities, then the change is required for
improvement in the quality of the software.
• Advantages of Incremental model
• This model is flexible because the cost of development is low and initial product delivery is faster.
• It is easier to test and debug in the smaller iteration.
• The working software is generated quickly in the software life cycle.
• The customers can respond to its functionalities after every increment.
• Disadvantages of the incremental model
• The cost of the final product may cross the cost initially estimated.
• This model requires a very clear and complete planning.
• The planning of design is required before the whole system is broken into smaller increments.
• The demands of customer for the additional functionalities after every increment causes problem in the system
architecture.