JAI

ENTERPRISES

Sdlc model

1. Requirement Phase
This is the most crucial phase of the software development life cycle for the developing
team as well as for the project manager. During this phase, the client states
requirements, specifications, expectations, and any other special requirement related to
the product or software. All these are gathered by the business manager or project
manager or analyst of the service providing company.

The requirement includes how the product will be used and who will use the product to
determine the load of operations. All information gathered from this phase is critical to
developing the product as per the customer requirements.

2. Design Phase
The design phase includes a detailed analysis of new software according to the
requirement phase. This is the high priority phase in the development life cycle of a
system because the logical designing of the system is converted into physical designing.
The output of the requirement phase is a collection of things that are required, and the
design phase gives the way to accomplish these requirements. The decision of all
required essential tools such as programming language like Java, .NET, PHP,
a database like Oracle, MySQL, a combination of hardware and software to provide a
platform on which software can run without any problem is taken in this phase.

There are several techniques and tools, such as data flow diagrams, flowcharts, decision
tables, and decision trees, Data dictionary, and the structured dictionary are used for
describing the system design.

3. Build /Development Phase

After the successful completion of the requirement and design phase, the next step is to
implement the design into the development of a software system. In this phase, work is
divided into small units, and coding starts by the team of developers according to the
design discussed in the previous phase and according to the requirements of the client
discussed in requirement phase to produce the desired result.

Front-end developers develop easy and attractive GUI and necessary interfaces to
interact with back-end operations and back-end developers do back-end coding
according to the required operations. All is done according to the procedure and
guidelines demonstrated by the project manager.

Since this is the coding phase, it takes the longest time and more focused approach for
the developer in the software development life cycle.
 JAI
ENTERPRISES

4. Testing Phase
Testing is the last step of completing a software system. In this phase, after getting the
developed GUI and back-end combination, it is tested against the requirements stated in
the requirement phase. Testing determines whether the software is actually giving the
result as per the requirements addressed in the requirement phase or not. The
Development team makes a test plan to start the test. This test plan includes all types of
essential testing such as integration testing, unit testing, acceptance testing, and system
testing. Non-functional testing is also done in this phase.

If there are any defects in the software or it is not working as per expectations, then the
testing team gives information to the development team in detail about the issue. If it is
a valid defect or worth to sort out, it will be fixed, and the development team replaces it
with the new one, and it also needs to be verified.

5. Deployment/ Deliver Phase

When software testing is completed with a satisfying result, and there are no remaining
issues in the working of the software, it is delivered to the customer for their use.

As soon as customers receive the product, they are recommended first to do the beta
testing. In beta testing, customer can require any changes which are not present in the
software but mentioned in the requirement document or any other GUI changes to make
it more user-friendly. Besides this, if any type of defect is encountered while a customer
using the software; it will be informed to the development team of that particular
software to sort out the problem. If it is a severe issue, then the development team
solves it in a short time; otherwise, if it is less severe, then it will wait for the next
version.

After the solution of all types of bugs and changes, the software finally deployed to the
end-user.

6. Maintenance

The maintenance phase is the last and long-lasting phase of SDLC because it is the
process which continues until the software's life cycle comes to an end. When a customer
starts using software, then actual problems start to occur, and at that time there's a
need to solve these problems. This phase also includes making changes in hardware and
software to maintain its operational effectiveness like to improve its performance,
enhance security features and according to customer's requirements with upcoming
time. This process to take care of product time to time is called maintenance.

Types of sdlc model:

 Waterfall model
 Spiral model
 V model
 Prototype model
 Increamental model
 Evolutionary model
 JAI
ENTERPRISES

Waterfall model:

 Requirement Gathering and analysis − All possible requirements of the

system to be developed are captured in this phase and documented in a
requirement specification document.
 System Design − The requirement specifications from first phase are
studied in this phase and the system design is prepared. This system
design helps in specifying hardware and system requirements and helps in
defining the overall system architecture.
 Implementation − With inputs from the system design, the system is first
developed in small programs called units, which are integrated in the next
phase. Each unit is developed and tested for its functionality, which is
referred to as Unit Testing.
 Integration and Testing − All the units developed in the implementation
phase are integrated into a system after testing of each unit. Post
integration the entire system is tested for any faults and failures.
 Deployment of system − Once the functional and non-functional testing
is done; the product is deployed in the customer environment or released
into the market.
 Maintenance − There are some issues which come up in the client
environment. To fix those issues, patches are released. Also to enhance the
product some better versions are released. Maintenance is done to deliver
these changes in the customer environment.

Application
 Requirements are very well documented, clear and fixed.
 Product definition is stable.
 Technology is understood and is not dynamic.
 There are no ambiguous requirements.
 JAI
ENTERPRISES
 Ample resources with required expertise are available to support the
product.
 The project is short.
Advantages
 Simple and easy to understand and use
 Easy to manage due to the rigidity of the model. Each phase has specific
deliverables and a review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well
understood.
 Clearly defined stages.
 Well understood milestones.
 Easy to arrange tasks.
 Process and results are well documented.
Disadvantages
 High amounts of risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.
 Not suitable for the projects where requirements are at a moderate to high
risk of changing. So, risk and uncertainty is high with this process model.
 It is difficult to measure progress within stages.
 Cannot accommodate changing requirements.
Spiral model

Spiral Model - Design

 JAI
ENTERPRISES
The spiral model has four phases. A software project repeatedly passes through these
phases in iterations called Spirals.

Identification
This phase starts with gathering the business requirements in the baseline spiral. In the
subsequent spirals as the product matures, identification of system requirements,
subsystem requirements and unit requirements are all done in this phase.
This phase also includes understanding the system requirements by continuous
communication between the customer and the system analyst. At the end of the spiral,
the product is deployed in the identified market.

Design
The Design phase starts with the conceptual design in the baseline spiral and involves
architectural design, logical design of modules, physical product design and the final
design in the subsequent spirals.

Construct or Build
The Construct phase refers to production of the actual software product at every spiral.
In the baseline spiral, when the product is just thought of and the design is being
developed a POC (Proof of Concept) is developed in this phase to get customer feedback.
Then in the subsequent spirals with higher clarity on requirements and design details a
working model of the software called build is produced with a version number. These
builds are sent to the customer for feedback.

Evaluation and Risk Analysis

Risk Analysis includes identifying, estimating and monitoring the technical feasibility and
management risks, such as schedule slippage and cost overrun. After testing the build,
at the end of first iteration, the customer evaluates the software and provides feedback.
The following illustration is a representation of the Spiral Model, listing the activities in
each phase. Based on the customer evaluation, the software development process enters the
next iteration and subsequently follows the linear approach to implement the feedback suggested
by the customer. The process of iterations along the spiral continues throughout the life of the
software.

Application

 When there is a budget constraint and risk evaluation is important.

 For medium to high-risk projects.
 Long-term project commitment because of potential changes to economic
priorities as the requirements change with time.
 Customer is not sure of their requirements which is usually the case.
 Requirements are complex and need evaluation to get clarity.
 New product line which should be released in phases to get enough
customer feedback.
 Significant changes are expected in the product during the development
cycle.
The advantages of the Spiral SDLC Model are as follows −
 Changing requirements can be accommodated.
 Allows extensive use of prototypes.
 Requirements can be captured more accurately.
 JAI
ENTERPRISES
 Users see the system early.
 Development can be divided into smaller parts and the risky parts can be
developed earlier which helps in better risk management.
The disadvantages of the Spiral SDLC Model are as follows −
 Management is more complex.
 End of the project may not be known early.
 Not suitable for small or low risk projects and could be expensive for small
projects.
 Process is complex
 Spiral may go on indefinitely.
 Large number of intermediate stages requires excessive documentation.

V model

V-Model - Verification Phases

There are several Verification phases in the V-Model, each of these are explained in
detail below.

Business Requirement Analysis

This is the first phase in the development cycle where the product requirements are
understood from the customer’s perspective. This phase involves detailed
communication with the customer to understand his expectations and exact
requirement. This is a very important activity and needs to be managed well, as most of
the customers are not sure about what exactly they need. The acceptance test design
planning is done at this stage as business requirements can be used as an input for
acceptance testing.

System Design
 JAI
ENTERPRISES
Once you have the clear and detailed product requirements, it is time to design the
complete system. The system design will have the understanding and detailing the
complete hardware and communication setup for the product under development. The
system test plan is developed based on the system design. Doing this at an earlier stage
leaves more time for the actual test execution later.

Architectural Design
Architectural specifications are understood and designed in this phase. Usually more
than one technical approach is proposed and based on the technical and financial
feasibility the final decision is taken. The system design is broken down further into
modules taking up different functionality. This is also referred to as High Level Design
(HLD).
The data transfer and communication between the internal modules and with the outside
world (other systems) is clearly understood and defined in this stage. With this
information, integration tests can be designed and documented during this stage.

Module Design
In this phase, the detailed internal design for all the system modules is specified,
referred to as Low Level Design (LLD). It is important that the design is compatible
with the other modules in the system architecture and the other external systems. The
unit tests are an essential part of any development process and helps eliminate the
maximum faults and errors at a very early stage. These unit tests can be designed at this
stage based on the internal module designs.

Coding Phase
The actual coding of the system modules designed in the design phase is taken up in the
Coding phase. The best suitable programming language is decided based on the system
and architectural requirements.
The coding is performed based on the coding guidelines and standards. The code goes
through numerous code reviews and is optimized for best performance before the final
build is checked into the repository.

Validation Phases
The different Validation Phases in a V-Model are explained in detail below.

Unit Testing
Unit tests designed in the module design phase are executed on the code during this
validation phase. Unit testing is the testing at code level and helps eliminate bugs at an
early stage, though all defects cannot be uncovered by unit testing.

Integration Testing
Integration testing is associated with the architectural design phase. Integration tests are
performed to test the coexistence and communication of the internal modules within the
system.

System Testing
System testing is directly associated with the system design phase. System tests check
the entire system functionality and the communication of the system under development
 JAI
ENTERPRISES
with external systems. Most of the software and hardware compatibility issues can be
uncovered during this system test execution.

Acceptance Testing
Acceptance testing is associated with the business requirement analysis phase and
involves testing the product in user environment. Acceptance tests uncover the
compatibility issues with the other systems available in the user environment. It also
discovers the non-functional issues such as load and performance defects in the actual
user environment.

V- Model ─ Application
V- Model application is almost the same as the waterfall model, as both the models are of
sequential type. Requirements have to be very clear before the project starts, because it
is usually expensive to go back and make changes. This model is used in the medical
development field, as it is strictly a disciplined domain.
The following pointers are some of the most suitable scenarios to use the V-Model
application.
 Requirements are well defined, clearly documented and fixed.
 Product definition is stable.
 Technology is not dynamic and is well understood by the project team.
 There are no ambiguous or undefined requirements.
 The project is short.

V-Model - Pros and Cons

The advantage of the V-Model method is that it is very easy to understand and apply.
The simplicity of this model also makes it easier to manage. The disadvantage is that the
model is not flexible to changes and just in case there is a requirement change, which is
very common in today’s dynamic world, it becomes very expensive to make the change.
The advantages of the V-Model method are as follows −
 This is a highly-disciplined model and Phases are completed one at a time.
 Works well for smaller projects where requirements are very well
understood.
 Simple and easy to understand and use.
 Easy to manage due to the rigidity of the model. Each phase has specific
deliverables and a review process.
The disadvantages of the V-Model method are as follows −
 High risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.
 Not suitable for the projects where requirements are at a moderate to high
risk of changing.
 Once an application is in the testing stage, it is difficult to go back and
change a functionality.
 No working software is produced until late during the life cycle.

Iterative model
 JAI
ENTERPRISES

Iterative Model - Design

Iterative process starts with a simple implementation of a subset of the software
requirements and iteratively enhances the evolving versions until the full system is
implemented. At each iteration, design modifications are made and new functional
capabilities are added. The basic idea behind this method is to develop a system through
repeated cycles (iterative) and in smaller portions at a time (incremental).
Iterative and Incremental development is a combination of both iterative design or
iterative method and incremental build model for development. "During software
development, more than one iteration of the software development cycle may be in
progress at the same time." This process may be described as an "evolutionary
acquisition" or "incremental build" approach."
In this incremental model, the whole requirement is divided into various builds. During
each iteration, the development module goes through the requirements, design,
implementation and testing phases. Each subsequent release of the module adds
function to the previous release. The process continues till the complete system is ready
as per the requirement.
The key to a successful use of an iterative software development lifecycle is rigorous
validation of requirements, and verification & testing of each version of the software
against those requirements within each cycle of the model. As the software evolves
through successive cycles, tests must be repeated and extended to verify each version
of the software.

Iterative Model - Application

Like other SDLC models, Iterative and incremental development has some specific
applications in the software industry. This model is most often used in the following
scenarios −
 Requirements of the complete system are clearly defined and understood.
 Major requirements must be defined; however, some functionalities or
requested enhancements may evolve with time.
 There is a time to the market constraint.
 JAI
ENTERPRISES
 A new technology is being used and is being learnt by the development
team while working on the project.
 Resources with needed skill sets are not available and are planned to be
used on contract basis for specific iterations.
 There are some high-risk features and goals which may change in the
future.

Iterative Model - Pros and Cons

The advantage of this model is that there is a working model of the system at a very
early stage of development, which makes it easier to find functional or design flaws.
Finding issues at an early stage of development enables to take corrective measures in a
limited budget.
The disadvantage with this SDLC model is that it is applicable only to large and bulky
software development projects. This is because it is hard to break a small software
system into further small serviceable increments/modules.
The advantages of the Iterative and Incremental SDLC Model are as follows −
 Some working functionality can be developed quickly and early in the life
cycle.
 Results are obtained early and periodically.
 Parallel development can be planned.
 Progress can be measured.
 Less costly to change the scope/requirements.
 Testing and debugging during smaller iteration is easy.
 Risks are identified and resolved during iteration; and each iteration is an
easily managed milestone.
 Easier to manage risk - High risk part is done first.
 With every increment, operational product is delivered.
 Issues, challenges and risks identified from each increment can be
utilized/applied to the next increment.
 Risk analysis is better.
 It supports changing requirements.
 Initial Operating time is less.
 Better suited for large and mission-critical projects.
 During the life cycle, software is produced early which facilitates customer
evaluation and feedback.
The disadvantages of the Iterative and Incremental SDLC Model are as follows −
 More resources may be required.
 Although cost of change is lesser, but it is not very suitable for changing
requirements.
 More management attention is required.
 System architecture or design issues may arise because not all
requirements are gathered in the beginning of the entire life cycle.
 Defining increments may require definition of the complete system.
 Not suitable for smaller projects.
 Management complexity is more.
 End of project may not be known which is a risk.
 Highly skilled resources are required for risk analysis.
 Projects progress is highly dependent upon the risk analysis phase.
Short point
 JAI
ENTERPRISES
 Module by module working
 Customer maximum interaction
 Large projects
 Early release product demand
 Flexible to changes

Prototype model

Short point
 Customer is not clear with idea
 Throwaway model
 Good for technical and requirement risk
 Increase in cost of development

Evolutionary model
 It is combination of iterative and incremental model of sdlc
 Incremental model first implement a few basic features and deliver to the
customer. Then build next part and deliver it again repeat this step until the
desired system is fully released.
 Iterative model - advantage is feedback process in every phase
 Also known as “design a little ,build a little, test a little, deploy a little”
 JAI
ENTERPRISES

STLC (software testing lifecycle)

What is Software Testing Life Cycle (STLC)?

Software Testing Life Cycle (STLC) is a sequence of specific activities conducted during
the testing process to ensure software quality goals are met. STLC involves both
verification and validation activities. Contrary to popular belief, Software Testing is not
just a single/isolate activity, i.e. testing. It consists of a series of activities carried out
methodologically to help certify your software product. STLC stands for Software Testing
Life Cycle.
 JAI
ENTERPRISES

STLC Phases
There are following six major phases in every Software Testing Life Cycle Model (STLC
Model):

STLC Model Phases

1. Requirement Analysis
2. Test Planning
3. Test case development
4. Test Environment setup
5. Test Execution
6. Test Cycle closure

Each of these stages has a definite Entry and Exit criteria, Activities & Deliverables
associated with it.

What is Entry and Exit Criteria in STLC?

 Entry Criteria: Entry Criteria gives the prerequisite items that must be completed
before testing can begin.
 Exit Criteria: Exit Criteria defines the items that must be completed before testing
can be concluded

You have Entry and Exit Criteria for all levels in the Software Testing Life Cycle (STLC)

In an Ideal world, you will not enter the next stage until the exit criteria for the previous
stage is met. But practically this is not always possible. So for this tutorial, we will focus on
activities and deliverables for the different stages in STLC life cycle. Let’s look into them in
detail.

Requirement Phase Testing

Requirement Phase Testing also known as Requirement Analysis in which test team
studies the requirements from a testing point of view to identify testable requirements
and the QA team may interact with various stakeholders to understand requirements in
detail. Requirements could be either functional or non-functional. Automation feasibility
for the testing project is also done in this stage.
Activities in Requirement Phase Testing

 Identify types of tests to be performed.

 Gather details about testing priorities and focus.
 JAI
ENTERPRISES
 Prepare Requirement Traceability Matrix (RTM).
 Identify test environment details where testing is supposed to be carried out.
 Automation feasibility analysis (if required).

Deliverables of Requirement Phase Testing

 RTM
 Automation feasibility report. (if applicable)

Test Planning in STLC

Test Planning in STLC is a phase in which a Senior QA manager determines the test plan
strategy along with efforts and cost estimates for the project. Moreover, the resources,
test environment, test limitations and the testing schedule are also determined. The Test
Plan gets prepared and finalized in the same phase.
Test Planning Activities

 Preparation of test plan/strategy document for various types of testing

 Test tool selection
 Test effort estimation
 Resource planning and determining roles and responsibilities.
 Training requirement

Deliverables of Test Planning

 Test plan /strategy document.

 Effort estimation document.

Test Case Development Phase

The Test Case Development Phase involves the creation, verification and rework of test
cases & test scripts after the test plan is ready. Initially, the Test data is identified then
created and reviewed and then reworked based on the preconditions. Then the QA team
starts the development process of test cases for individual units.
Test Case Development Activities

 Create test cases, automation scripts (if applicable)

 Review and baseline test cases and scripts
 Create test data (If Test Environment is available)

Deliverables of Test Case Development

 JAI
ENTERPRISES
 Test cases/scripts
 Test data

Test Environment Setup

Test Environment Setup decides the software and hardware conditions under which a
work product is tested. It is one of the critical aspects of the testing process and can be
done in parallel with the Test Case Development Phase. Test team may not be involved in
this activity if the development team provides the test environment. The test team is
required to do a readiness check (smoke testing) of the given environment.
Test Environment Setup Activities

 Understand the required architecture, environment set-up and prepare hardware

and software requirement list for the Test Environment.
 Setup test Environment and test data
 Perform smoke test on the build

Deliverables of Test Environment Setup

 Environment ready with test data set up

 Smoke Test Results.

Test Execution Phase

Test Execution Phase is carried out by the testers in which testing of the software build is
done based on test plans and test cases prepared. The process consists of test script
execution, test script maintenance and bug reporting. If bugs are reported then it is
reverted back to development team for correction and retesting will be performed.
Test Execution Activities

 Execute tests as per plan

 Document test results, and log defects for failed cases
 Map defects to test cases in RTM
 Retest the Defect fixes
 Track the defects to closure

Deliverables of Test Execution

 Completed RTM with the execution status

 Test cases updated with results
 Defect reports
 JAI
ENTERPRISES

Test Cycle Closure

Test Cycle Closure phase is completion of test execution which involves several activities
like test completion reporting, collection of test completion matrices and test results.
Testing team members meet, discuss and analyze testing artifacts to identify strategies
that have to be implemented in future, taking lessons from current test cycle. The idea is
to remove process bottlenecks for future test cycles.
Test Cycle Closure Activities

 Evaluate cycle completion criteria based on Time, Test coverage, Cost,Software,

Critical Business Objectives, Quality
 Prepare test metrics based on the above parameters.
 Document the learning out of the project
 Prepare Test closure report
 Qualitative and quantitative reporting of quality of the work product to the
customer.
 Test result analysis to find out the defect distribution by type and severity.

Deliverables of Test Cycle Closure

 Test Closure report

 Test metrics