PRACTICAL FILE

OF

SOFTWARE VERIFICATION & VALIDATION &

TESTING

Submitted To: Submitted By:

Er. Navneet Kaur Name: SANCHIT
(Asst. Prof., CSE ) RollNo:1222368
CSE (7th sem.)

Department of Computer Science & Engineering

Seth Jai Parkash Mukand Lal Institute of Engineering & Technology,
Radaur – 135133 (Yamuna Nagar)
(Affiliated to Kurukshetra University, Kurukshetra, Haryana, India)
 INDEX

Sr. No. PRACTICAL NAME REMARKS

To identify the role of the software in today’s world across a few

1
significant domains related to day to day life.

To identify any scenario and identify suitable

2
software development model for the given scenario.

To classify the requirement into functional and non-functional

3 requirements and list four functional and non -functional
requirements for any scenario.

4 Do comparative study of various software development models.

Preparation of requirement document for standard application

problems in standard format. (eg. Library Management System,
5 Railway Reservation system, Hospital management System,
University Admission system)

6 To identify the usage of Regression Testing.

7 To identify the usage of Agile Testing.

8 To understand the importance of SDLC and STLC process.

 Practical No-1
AIM- To identify the role of the software in today’s world across a few significant
domains related to day to day life.

Background of the objective: Software has made the world a global village today. The
impact of software spans across almost all aspects of human life. All organizations, Institutions
and companies are leveraging the potential of software in automating the critical functions and
eliminating manual interventions. Software is also a predominant area for trade and export
especially for countries like India. Domains like health care, Airlines, financial Services,
Insurance , retails, Education, and many more have exploited software and still there is a lot of
scope for software to create impact and add values in multiple dimensions.

Problem Description: In the context of this background, identify the areas (or application or
systems) how software has been leveraged extensively in the following domains with example:
1. Health Care
2. Airlines
3. Banking Insurance
4. Retail
5. Education

INTRODUCTION
What is Software?
Software is a set of instructions, data or programs used to operate computers and execute
specific tasks. It is the opposite of hardware, which describes the physical aspects of a
computer. Software is a generic term used to refer to applications, scripts and programs that
run on a device. It can be thought of as the variable part of a computer, while hardware is the
invariable part.
the two main categories of software are application software and system software. An
application is software that fulfills a specific need or performs tasks. System software is
designed to run a computer's hardware and provides a platform for applications to run on top
of.
TYPES OF SOFTWARE

1. APPLICATION SOFTWARE

Application Software is the kind of programming which runs according to client demand.
Framework programming gave the stage to application programming. Elevated level dialects
are wont to compose machine programming. Its a particular reason for programming. One of
the essential things to think about the expression “application programming” is that it’s
extremely wide. That is it, more or less. In that sense, any client program is frequently called
an “application.”
2. SYSTEM SOFTWARE
System software is software designed to provide a platform for other software. Examples of
system software include operating systems (OS) like macOS, Linux, Android and Microsoft
Windows, computational science software, game engines, search engines, industrial automation,
and software as a service applications

ADVANTAGES OF SOFTWARE:

Their single greatest favourable position is that it meets exact requirements of client. Since
it’ s planned explicitly in view of one reason, client realizes that he must utilize one explicit
programming to achieve his errand.
Business that accompanies it can confine access and may think of intends to monitor their
organization additionally.
Standard updates from engineer for Licensed application programming were gotten with
rationale of wellbeing. Moreover, engineer additionally consistently sends faculty to exact
any issues which may ascend periodically.
Possibility of infections attacking hand crafted projects may be little, as long as any
business that accompanies it can limit access and ought to give you strategy to secure
their locale too.

DISADVANTAGES OF SOFTWARE:

Creating application programming intended to fulfill explicit purposes can persuade be very
exorbitant for engineers. This can influence their financial plan and their income stream,
particularly if an inordinate measure of time is spent building up a product that is not by and
large worthy.
Application programming that is utilized regularly by numerous individuals of us, at that
point shared on web, conveys a truly genuine danger of contamination by a bug or other
vindictive projects.
Creating them are a few things that takes a spread of your time since it wishes reliable
correspondence between engineer and consequently supporter. This defers whole creation
methodology, which could demonstrate to be hurtful during a couple of cases.
e programming program which can be planned explicitly for a specific business endeavour,
probably won’t be very much coordinated with various famous programming. This is
something which may demonstrate to be most obstruction for a few offices.

EXAMPLES OF SOFTWARE:
Operating systems (such as Microsoft Windows, Linux, mac OS)
Productivity Software (for example, Microsoft Office Suite including Word, Excel, and
PowerPoint)
Internet Browsers (including Firefox, Chrome, and Safari)
SECTORS:
1. EDUCATION:
The main objective is to make sure that certain concepts in the education sector are practical
and are understood better by students. Learning institutions is where students can learn
technology. The digital transition has resulted in the rearrangement and reconstruction of
companies. Nearly all schools commonly employ a different form of education software. They
tend to be very ubiquitous since the number of possible solutions and the options for the
prospected solution seems to be augmenting.

BENEFITS:
1. Smart and Clear Content
Well, this software indeed has the capability of revolutionizing how ideas and content are
created and presented to all students. Moreover, digital content that has been embedded using
artificial intelligence capacities provides sources that highly adjust to a student’s skills and
knowledge. Considering the smart ideas, it can be easily changed, distributed, and recycled
with the help of different generations of learners.

2. Enhances the Communication of Parents, Teachers, and Students

Open communication between teachers and students is crucial during the process of learning.
Respect and trust must be there so that students can be taught well. That is why, with the
introduction of applications and educational software, the strong bond can be maintained by
the usage of portals, forums, and additional interactive factors. Moreover, teachers and
students have equipment at hand that they can use to make the communication process easy.

3. Consolidation of Data

Different forms of education software are specifically created so that information can be
combined in a common repository. Focusing on the related data in a specific program is
capable of providing clear insight and analysis of precise facts about particular data. Educators
and professionals may use such ideas to be a guiding strategy for administrative and lower-
level policies in an advanced position.

4. Enhanced Efficacy and Effectiveness

The objective of any school is effectiveness and efficiency, and software used in education
aids firms in attaining their goals. Instructors use resources, for example, class resources
management software, to restrict distractions and augment concentration within the course
materials.

2. HEALTH CARE
Over the last few years, healthcare software has gained great popularity among clinics and
healthcare organizations. Medical software is crucial to the healthcare industry since it lets
healthcare providers to monitor and manage healthcare organization and patient data.
BENEFITS:
Easier access to healthcare data. Because a MPMS processes documents and data online,
it optimizes operations within a practice, allowing employees to search within electronic
documents.
Focus on quality care. By automating routine medical processes, a PMS allows healthcare
providers to concentrate on patient care.
Improved patient satisfaction. Due to standardized workflows and automated features like
instant access to patient records and history of medical treatment, medical providers can work
more effectively. This improves patient satisfaction.

3. BANKING INSURANCE
Software has become one of the most important things in our lives. From healthcare to
financial and retail industries, almost all need effective software to function smoothly. Banking
can never be too far off when it comes to using software applications. Banking software
applications have made their functioning highly efficient. The implementation of this software
ensures that productivity is increased and that there are efficient processes in place to serve
the customers better.
Internet banking is one of the most important things these days, and this would not have been
possible without the efficient banking systems software. If you are looking for ways to
implement this system in your organization, here are some of the advantages that will help you
in making your decision on whether or not to implement this system in your organization.
BENEFITS:
Multiple accounts are supported. A user can open and access multiple accounts with the
help of banking software applications. The users can also manage their investments and buy
various insurances needed for health, security and so on. In this way, the users can easily
operate from one platform and carry out various tasks in a jiffy. Although, the banking software
applications vary depending on the version, but the overall functioning and operation is usually
same.
Secured transactions are provided. One of the prime concerns of banks are to provide
secured services to their customers, and this is the reason why the banks provide a number of
security features that help customers with secured transactions. Banking software applications
provide one of the most secured transactions to customers and as a result the users are able
to trust their banks.
Ease of navigation. The customers using banking software applications are not necessarily
tech savvy, and this is where easy of operation comes into play. The interface is user friendly
and easy for them to navigate, and as a result, the customers can carry out most of the
banking without or minimal help. If the navigation is easy, then the business of the bank also
improves because there are many significant benefits to the customers, and so this will also
work out to be word of mouth marketing.
Always available for the customers
Which customer will want to wait for the support? We’ll, no one wants to wait these days. The
problems are usually the regular ones and so the software has various sections that help the
customers in various tasks. This ensures that help is available for the customers at all the time.
So when it comes to banking, the customers are always sure that there is 24 x 7 help available
to them. As a result, the banks have the opportunity to function 24 hours in a day without being
physically present to handle all the problems.

4. AIRLINES
Without software, modern aviation as we know it would not exist. For example, it wouldn’t be
possible to manage flight plans, air traffic control, autopilot systems and complex maintenance
routines. There are a lot of automated software systems that aviation currently relies on.
Eg Aircraft maintenance
BENEFITS:

User-friendly
An aircraft maintenance software is user-friendly. It makes keeping records, scheduling and
rescheduling flights, plane maintenance, and maintaining inventories easier. It also helps
maintain the payrolls of the staff and flight crew, along with sharing reports and tracking all
kinds of flight data.
Excellent Customer Support
Online aircraft maintenance software allows the company to provide excellent customer
service by staying alert and responding to queries 24/7. The online chatbots enable the staff to
tend to their customer needs and manage the questions anytime. This also helps business
owners to assess their customer feedback and look into areas that can be improved by
providing better services.
Cloud Storage
An aircraft management software allows the flight company to store their records and
operational data on cloud storage. The saving system of the cloud is more secure than
conventional storing devices. The best aspect of cloud storage is that it can be accessed,
altered, and updated by the permitted employees. This means that a change in one area leads
to the automatic update in other areas affected by the change.

5. RETAIL
With the advent of technology, retail software are quickly becoming buzz in all sector of retail
businesses — from fast food outlets to trendy gift shops. A comprehensive retail management
system can encompass all retail business requirements to improve inventory positions,
increase profit and better customer service reducing operational and wage costs. Big or small,
every retailer undoubtedly may enjoy immediate return on their investment choosing the right
retail software.
BENEFITS:
Hassle-free in Inventory Management. Retail software will provide details on current
stock of items, reminding additional stock requirements to smoothly operate the
business, inventory cost estimations etc. Maintaining stock details and sales through a
computerized POS system will provide accurate information about the stock movement.
Thus any theft, wastage, damage of items can be tracked efficiently.
Auto calculation of tax. Professional retail software should be capable of all types of
VAT and Tax calculations, with multi-currency facility.
Proper anticipation of sales trends. Various MIS reports help to forecast sales
correctly so that you can stock more products that give you greater profits and fewer
products that give you the least amount of profit. This will contribute to your business
overall profitability and success.
No longer checkout lines. Your customers will appreciate a quicker, more accurate
checkout experience they will get from the right retail point of sale software. For faster
credit card authorizations, select a retail software package with integrated credit card
processing and high-speed credit card authorizations via an Internet gateway.
Correctly examining sales & expenses. A complete retail software will provide you
consolidated data on the money your business owes to different vendors (i.e. Accounts
Payables) and the money owed by customers to your business (i.e. Accounts
Receivable), allowing you to monitor and control the collection and disbursement at any
time – easily calculating daily gross revenue, cost and profit.
Positive Decision. Trendy BI reports with statistics/graphs boost the strength of the
software which eventually may provide shortened lead-time to respond (in making any
strategic decision even) to any market chan
 Practical No-2
AIM: To identify any scenario and identify suitable software development model for the
given scenario.
Software Development Life Cycle (SDLC) is a process used by the software industry to design,
develop and test high quality softwares. The SDLC aims to produce high-quality software that
meets or exceeds customer expectations, reaches completion within time and cost estimates.
● SDLC is the acronym for Software Development Life Cycle.
● It is also called the Software Development Process.
● SDLC is a framework defining tasks performed at each step in the software development
process.
● ISO/IEC 12207 is an international standard for software life-cycle processes. It aims to be the
standard that defines all the tasks required for developing and maintaining software.

What is SDLC?
SDLC is a process followed for a software project, within a software organization. It consists of a
detailed plan describing how to develop, maintain, replace and alter or enhance specific software.
The life cycle defines a methodology for improving the quality of software and the overall
development process.
The following figure is a graphical representation of the various stages of a typical SDLC.
A typical Software Development Life Cycle consists of the following stages −
Stage 1: Planning and Requirement Analysis
Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the
senior members of the team with inputs from the customer, the sales department, market surveys and
domain experts in the industry. This information is then used to plan the basic project approach and to
conduct product feasibility study in the economical, operational and technical areas.
Planning for the quality assurance requirements and identification of the risks associated with the
project is also done in the planning stage. The outcome of the technical feasibility study is to define the
various technical approaches that can be followed to implement the project successfully with minimum
risks.
Stage 2: Defining Requirements
Once the requirement analysis is done the next step is to clearly define and document the product
requirements and get them approved from the customer or the market analysts. This is done through
an SRS (Software Requirement Specification) document which consists of all the product
requirements to be designed and developed during the project life cycle.
Stage 3: Designing the Product Architecture
SRS is the reference for product architects to come out with the best architecture for the product to be
developed. Based on the requirements specified in SRS, usually more than one design approach for
the product architecture is proposed and documented in a DDS - Design Document Specification.
This DDS is reviewed by all the important stakeholders and based on various parameters as risk
assessment, product robustness, design modularity, budget and time constraints, the best design
approach is selected for the product.
A design approach clearly defines all the architectural modules of the product along with its
communication and data flow representation with the external and third party modules (if any). The
internal design of all the modules of the proposed architecture should be clearly defined with the
minutest of the details in DDS.
Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the product is built. The programming code is
generated as per DDS during this stage. If the design is performed in a detailed and organized manner,
code generation can be accomplished without much hassle.
Developers must follow the coding guidelines defined by their organization and programming tools like
compilers, interpreters, debuggers, etc. are used to generate the code. Different high level
programming languages such as C, C++, Pascal, Java and PHP are used for coding. The
programming language is chosen with respect to the type of software being developed.
Stage 5: Testing the Product
This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are
mostly involved in all the stages of SDLC. However, this stage refers to the testing only stage of the
product where product defects are reported, tracked, fixed and retested, until the product reaches the
quality standards defined in the SRS.
 Stage 6: Deployment in the Market and Maintenance
Once the product is tested and ready to be deployed it is released formally in the appropriate market.
Sometimes product deployment happens in stages as per the business strategy of that organization.
The product may first be released in a limited segment and tested in the real business environment
(UAT- User acceptance testing).
Then based on the feedback, the product may be released as it is or with suggested enhancements in
the targeting market segment. After the product is released in the market, its maintenance is done for
the existing customer base.

SDLC Models
There are various software development life cycle models defined and designed which are followed
during the software development process. These models are also referred to as Software Development
Process Models". Each process model follows a Series of steps unique to its type to ensure success in
the process of software development.
Following are the most important and popular SDLC models followed in the industry −

● Waterfall Model
● Iterative Model
● Spiral Model
● V-Model
● Big Bang Model
Other related methodologies are Agile Model, RAD Model, Rapid Application Development and
Prototyping Models.

SDLC - Waterfall Model

The Waterfall Model was the first Process Model to be introduced. It is also referred to as
a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model,
each phase must be completed before the next phase can begin and there is no overlapping in the
phases.
The Waterfall model is the earliest SDLC approach that was used for software development.
The waterfall Model illustrates the software development process in a linear sequential flow. This
means that any phase in the development process begins only if the previous phase is complete. In
this waterfall model, the phases do not overlap.

Waterfall Model - Design

The Waterfall approach was the first SDLC Model to be used widely in Software Engineering to ensure
success of the project. In "The Waterfall" approach, the whole process of software development is
divided into separate phases. In this Waterfall model, typically, the outcome of one phase acts as the
input for the next phase sequentially.
The following illustration is a representation of the different phases of the Waterfall Model.
The sequential phases in Waterfall model are −
● 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.
All these phases are cascaded to each other in which progress is seen as flowing steadily downwards
(like a waterfall) through the phases. The next phase is started only after the defined set of goals are
achieved for previous phase and it is signed off, so the name "Waterfall Model". In this model, phases
do not overlap.
 Waterfall Model - Application
Every software developed is different and requires a suitable SDLC approach to be followed based on
the internal and external factors. Some situations where the use of Waterfall model is most appropriate
are −
● Requirements are very well documented, clear and fixed.
● Product definition is stable.
● Technology is understood and is not dynamic.
● There are no ambiguous requirements.
● Ample resources with required expertise are available to support the product.
● The project is short.

Waterfall Model - Advantages

The advantages of waterfall development are that it allows for departmentalization and control. A
schedule can be set with deadlines for each stage of development and a product can proceed through
the development process model phases one by one.
Development moves from concept, through design, implementation, testing, installation,
troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds in
strict order.

Some of the major advantages of the Waterfall Model are as follows −

● 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.

Waterfall Model - Disadvantages

The disadvantage of waterfall development is that it does not allow much reflection or revision. Once
an application is in the testing stage, it is very difficult to go back and change something that was not
well-documented or thought upon in the concept stage.
The major disadvantages of the Waterfall Model are as follows −
● No working software is produced until late during the life cycle.
● 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.
● Adjusting scope during the life cycle can end a project.
● Integration is done as a "big-bang. at the very end, which doesn't allow identifying any
technological or business bottleneck or challenges early.

WHEN TO USE WATERFALL MODEL :

In order to understand a real-life example of the waterfall model, let’s familiarize ourselves with
situations when the waterfall model is usually used:

● When the project requirements are laid down at the outset and remain more or less fixed
throughout the entire process

● When the product definition is stable and a lot of information is required before completing
each phase

● In cases where a strict timeline needs to be prepared and followed, without alterations

● In sectors involving engineering design and software development that generally demand
project management on a large scale

● In manufacturing and construction industries, where design changes are usually very
costly

EXAMPLES OR SCENARIOS:
With the evolution of technology, there were cases where large-scale enterprise systems, with the
waterfall model as the default choice, were developed over a period of two to three years but became
redundant by the time they were completed. Slowly, these enterprise systems switched over to more
flexible and less expensive models, but the waterfall model continued to be preferred in systems where:
● A human life is at stake and a system failure could result in fatalities

● Money and time are secondary factors and what matters more is the safety and stability of
a project
 ● Military and aircraft programs where requirements are declared early on and remain
constant

● Projects with an extremely high degree of oversight and/or accountability such as those in
the sectors of banking, healthcare and control systems for nuclear facilities

SDLC - Iterative Model

In the Iterative model, the iterative process starts with a simple implementation of a small set of the
software requirements and iteratively enhances the evolving versions until the complete system is
implemented and ready to be deployed.
An iterative life cycle model does not attempt to start with a full specification of requirements. Instead,
development begins by specifying and implementing just part of the software, which is then reviewed to
identify further requirements. This process is then repeated, producing a new version of the software at
the end of each iteration of the model.

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).
The following illustration is a representation of the Iterative and Incremental model −

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 constraint.
● 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 us 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 iterations is easy.
● Risks are identified and resolved during iteration; and each iteration is an easily managed
milestone.
 ● 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.

When to use the Incremental model:

● This model can be used when the requirements of the complete system are clearly defined and
understood.
● Major requirements must be defined; however, some details can evolve with time.
● There is a need to get a product to the market early.
● A new technology is being used
● Resources with needed skill set are not available
● There are some high risk features and goals.

EXAMPLES OR SCENARIOS:

User Interfaces
A requirement of a film company needs a custom system for equipment tracking, costumes, and props.
The business section included is unusual for rendering specifications for technology-based projects. To
that customers will decline, an iterative outline strategy is utilized. In a week, the developers and users
sit twice to discuss the recent system. Consumers experience the products and create new
specifications that are rigorous prioritization down to fewer workdays. In this manner, the system
emerges to be beneficial and simple to utilize.

Architecture
A firm of architecture promptly produces models and architecture animation to place in the presence of
the customer. This holds the customer involved and delivers it more possible for the firm will be selected
for a specific project.

Marketing
An e-commerce fashion website nevermore begins designed again to displace an old website.
Alternatively, the UI (user interface) is steadily contentious, altered and perfected. Track the metrics and
correlate with alterations. The development by firms are expertly established on practices that are
incomparable to its industry.

SDLC - Spiral Model

The spiral model combines the idea of iterative development with the systematic, controlled aspects of
the waterfall model. This Spiral model is a combination of iterative development process model and
sequential linear development model i.e. the waterfall model with a very high emphasis on risk
analysis. It allows incremental releases of the product or incremental refinement through each iteration
around the spiral.

Spiral Model - Design

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.

Spiral Model Application

The Spiral Model is widely used in the software industry as it is in sync with the natural development
process of any product, i.e. learning with maturity which involves minimum risk for the customer as well
as the development firms.
 ● 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.
● Customers are 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.

Spiral Model - Pros and Cons

The advantage of the spiral lifecycle model is that it allows elements of the product to be added in,
when they become available or known. This assures that there is no conflict with previous requirements
and design.
This method is consistent with approaches that have multiple software builds and releases which
allows making an orderly transition to a maintenance activity. Another positive aspect of this method is
that the spiral model forces an early user involvement in the system development effort.
On the other hand, it takes very strict management to complete such products and there is a risk of
running the spiral in an indefinite loop. So, the discipline of change and the extent of taking change
requests is very important to develop and deploy the product successfully.
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.
● 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.

When to use Spiral model:

● When costs and risk evaluation is important

 ● For medium to high-risk projects
● Long-term project commitment unwise because of potential changes to economic priorities
● Users are unsure of their needs
● Requirements are complex
● New product line
● Significant changes are expected (research and exploration)

SDLC - 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.

V-Model - Design
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.
The following illustration depicts the different phases in a V-Model of the SDLC.
 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
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 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 a 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.
When to use the V-model:

● The V-shaped model should be used for small to medium sized projects where requirements are
clearly defined and fixed.
● The V-Shaped model should be chosen when ample technical resources are available with
needed technical expertise.

High confidence of customers is required for choosing the V-Shaped model approach. Since, no
prototypes are produced, there is a very high risk involved in meeting customer expectations.

SDLC - Big Bang Model

The Big Bang model is an SDLC model where we do not follow any specific process. The development
just starts with the required money and efforts as the input, and the output is the software developed
which may or may not be as per customer requirement. This Big Bang Model does not follow a
process/procedure and there is a very little planning required. Even the customer is not sure about
what exactly he wants and the requirements are implemented on the fly without much analysis.
Usually this model is followed for small projects where the development teams are very small.

Big Bang Model ─ Design and Application

The Big Bang Model consists of focusing all the possible resources in the software development and
coding, with very little or no planning. The requirements are understood and implemented as they
come. Any changes required may or may not need to revamp the complete software.
This model is ideal for small projects with one or two developers working together and is also useful for
academic or practice projects. It is an ideal model for the product where requirements are not well
understood and the final release date is not given.

Big Bang Model - Pros and Cons

The advantage of this Big Bang Model is that it is very simple and requires very little or no planning.
Easy to manage and no formal procedures are required.
However, the Big Bang Model is a very high risk model and changes in the requirements or
misunderstood requirements may even lead to complete reversal or scrapping of the project. It is ideal
for repetitive or small projects with minimum risks.
The advantages of the Big Bang Model are as follows −
● This is a very simple model
● Little or no planning required
● Easy to manage
● Very few resources required
● Gives flexibility to developers
● It is a good learning aid for newcomers or students.
The disadvantages of the Big Bang Model are as follows −
● Very High risk and uncertainty.
● Not a good model for complex and object-oriented projects.
● Poor model for long and ongoing projects.
● Can turn out to be very expensive if requirements are misunderstood.

SDLC - Agile Model

Agile SDLC model is a combination of iterative and incremental process models with focus on process
adaptability and customer satisfaction by rapid delivery of working software products. Agile Methods
break the product into small incremental builds. These builds are provided in iterations. Each iteration
typically lasts from about one to three weeks. Every iteration involves cross functional teams working
simultaneously on various areas like −

● Planning
● Requirements Analysis
● Design
● Coding
● Unit Testing and
● Acceptance Testing.
At the end of the iteration, a working product is displayed to the customer and important stakeholders.

What is Agile?
The Agile model believes that every project needs to be handled differently and the existing methods
need to be tailored to best suit the project requirements. In Agile, the tasks are divided to time boxes
(small time frames) to deliver specific features for a release.
Iterative approach is taken and working software build is delivered after each iteration. Each build is
incremental in terms of features; the final build holds all the features required by the customer.
Here is a graphical illustration of the Agile Model −
The Agile thought process had started early in the software development and started becoming popular
with time due to its flexibility and adaptability.
The most popular Agile methods include Rational Unified Process (1994), Scrum (1995), Crystal Clear,
Extreme Programming (1996), Adaptive Software Development, Feature Driven Development, and
Dynamic Systems Development Method (DSDM) (1995). These are now collectively referred to
as Agile Methodologies, after the Agile Manifesto was published in 2001.
Following are the Agile Manifesto principles −
● Individuals and interactions − In Agile development, self-organization and motivation are
important, as are interactions like co-location and pair programming.
● Working software − Demo working software is considered the best means of communication
with the customers to understand their requirements, instead of just depending on
documentation.
● Customer collaboration − As the requirements cannot be gathered completely in the beginning
of the project due to various factors, continuous customer interaction is very important to get
proper product requirements.
● Responding to change − Agile Development is focused on quick responses to change and
continuous development.
Agile Vs Traditional SDLC Models
Agile is based on the adaptive software development methods, whereas the traditional SDLC
models like the waterfall model is based on a predictive approach. Predictive teams in the traditional
SDLC models usually work with detailed planning and have a complete forecast of the exact tasks and
features to be delivered in the next few months or during the product life cycle.
Predictive methods entirely depend on the requirement analysis and planning done in the beginning
of cycle. Any changes to be incorporated go through a strict change control management and
prioritization.
Agile uses an adaptive approach where there is no detailed planning and there is clarity on future
tasks only in respect of what features need to be developed. There is feature driven development and
the team adapts to the changing product requirements dynamically. The product is tested very
frequently, through the release iterations, minimizing the risk of any major failures in future.
Customer Interaction is the backbone of this Agile methodology, and open communication with
minimum documentation are the typical features of Agile development environment. The agile teams
work in close collaboration with each other and are most often located in the same geographical
location.

Agile Model - Pros and Cons

Agile methods are being widely accepted in the software world recently. However, this method may not
always be suitable for all products. Here are some pros and cons of the Agile model.
The advantages of the Agile Model are as follows −
● Is a very realistic approach to software development.
● Promotes teamwork and cross training.
● Functionality can be developed rapidly and demonstrated.
● Resource requirements are minimum.
● Suitable for fixed or changing requirements
● Delivers early partial working solutions.
● Good model for environments that change steadily.
● Minimal rules, documentation easily employed.
● Enables concurrent development and delivery within an overall planned context.
● Little or no planning required.
● Easy to manage.
● Gives flexibility to developers.
The disadvantages of the Agile Model are as follows −
● Not suitable for handling complex dependencies.
● More risk of sustainability, maintainability and extensibility.
● An overall plan, an agile leader and agile PM practice is a must without which it will not work.
● Strict delivery management dictates the scope, functionality to be delivered, and adjustments to
meet the deadlines.
● Depends heavily on customer interaction, so if the customer is not clear, the team can be driven
in the wrong direction.
● There is a very high individual dependency, since there is minimum documentation generated.
● Transfer of technology to new team members may be quite challenging due to lack of
documentation.
 Practical No-3
AIM: To classify the requirement into functional and non-functional requirements and
list four functional and non -functional requirements for any scenario

What is Software Testing?

Testing is the process of executing a program with the aim of finding errors. To
make our software perform well it should be error-free. If testing is done
successfully, it will remove all the errors from the software.
Software Testing is a method to check whether the actual software product
matches expected requirements and to ensure that the software
product is Defect free.
It involves execution of software/system components using manual or
automated tools to evaluate one or more properties of interest.
The purpose of software testing is to identify errors, gaps or missing
requirements in contrast to actual requirements.
Types of Software Testing: -

Here are the software testing types. Typically Testing is classified into three
categories.
Functional Testing

Non-Functional Testing or Performance Testing

Maintenance (Regression and Maintenance)

Types of Software Testing in Software Engineering

Testing Category Types of Testing

Functional Testing • Unit Testing
• Integration Testing
• Smoke
• UAT ( User Acceptance Testing)
• Interoperability
• So on
Non-Functional Testing • Performance
• Load
• Volume
• Scalability
• Usability
• So on
Maintenance • Regression
• Maintenance
Functional vs Non Functional Requirements:

Requirements analysis is very critical process that enables the success of a system or
software project to be assessed. Requirements are generally split into two
types: Functional and Non-functional requirements.
Functional Requirements: These are the requirements that the end user specifically
demands as basic facilities that the system should offer. All these functionalities need to be
necessarily incorporated into the system as a part of the contract. These are represented or
stated in the form of input to be given to the system, the operation performed and the output
expected. They are basically the requirements stated by the user which one can see directly in
the final product, unlike the non-functional requirements.
Non-functional requirements: These are basically the quality constraints that the system
must satisfy according to the project contract. The priority or extent to which these factors are
implemented varies from one project to other. They are also called non-behavioral
requirements.
They basically deal with issues like:
Portability
Security
Maintainability
Reliability
Scalability
Performance
Reusability
Flexibility
Following are the differences between Functional and Non Functional
Unit Testing: This software testing basic approach is followed by the programmer to test the unit of
the program. It helps developers to know whether the individual unit of the code is working
properly or not.

Integration testing: It focuses on the construction and design of the software. You
need to see that the integrated units are working without errors or not.

System testing: In this method, your software is compiled as a whole and then tested
as a whole. This testing strategy checks the functionality, security, portability,
amongst others.

Alpha Testing
Alpha Testing is a type of acceptance testing; performed to identify all possible issues and
bugs before releasing the final product to the end users. Alpha testing is carried out by the
testers who are internal employees of the organization. The main goal is to identify the tasks
that a typical user might perform and test them.

To put it as simple as possible, this kind of testing is called alpha only because it is done early
on, near the end of the development of the software, and before beta testing. The main focus
of alpha testing is to simulate real users by using a black box and white box techniques.

Beta Testing

Beta Testing is performed by “real users” of the software application in “real

environment” and it can be considered as a form of external User Acceptance
Testing.

It is the final test before shipping a product to the customers. Direct feedback from
customers is a major advantage of Beta Testing. This testing helps to test products in
the customer's environment.
Beta version of the software is released to a limited number of end-users of the
product to obtain feedback on the product quality. Beta testing reduces product
failure risks and provides increased quality of the product through customer
validation.
 Alpha Testing Beta Testing

Alpha testing involves both the white box and Beta testing commonly uses black box
black box testing. testing.

Alpha testing is performed by testers who are

Beta testing is performed by clients who
usually internal employees of the
are not part of the organization.
organization.

Alpha testing is performed at developer’s Beta testing is performed at end-user of

site. the product.

Reliability and security testing are Reliability, security and robustness are
not checked in alpha testing. checked during beta testing.

Beta testing also concentrates on the

Alpha testing ensures the quality of the quality of the product but collects users
product before forwarding to beta testing. input on the product and ensures that the
product is ready for real time users.
Alpha testing requires a testing environment Beta testing doesn’t require a testing
or a lab. environment or lab.
Alpha testing may require long execution Beta testing requires only a few weeks of
cycle. execution.
Most of the issues or feedback collected
Developers can immediately address the
from beta testing will be implemented in
critical issues or fixes in alpha testing.
future versions of the product.
 Practical No-4

AIM: Do Comparative Study of Various Software Developments Models.

1. Classical Waterfall Model: The Classical Waterfall model can be considered as the basic model and
all other life cycle models are based on this model. It is an ideal model. However, the Classical Waterfall
model cannot be used in practical project development, since this model does not support any
mechanism to correct the errors that are committed during any of the phases but detected at a later
phase. This problem is overcome by the Iterative Waterfall model through the inclusion of feedback
paths.
2. Spiral Model :
Spiral Model is a software development life cycle model which is highly used for risk driven models.
Based on the risk patterns of a given project, the spiral model helps developers to increase the
efficiency of model as most risk already handled. It consist of number of loops which are forming a spiral
shape where each loop is called phase of software development cycle.
3. Incremental Model :
Incremental Model is a model of software development where the product is, analyzed, designed,
implemented and tested incrementally until the product is finished. Multiple development cycles take
place and these cycles are divided into more smaller modules. Generally a working software in
incremental model is produced during first module Each subsequent release of the module adds
function to the previous release. In incremental model, process continues till the complete system is
achieved.
4. V-mode :
V-model is the most important model that is used in the process of software testing. It is also known
as Verification and Validation Model. It is Introduced by the late Paul Rook in 1980s. V-model is a
sequential process in which the next phase begins only after the completion of the present phase. In
this model, steps don’t move in a linear way while the steps are bent upwards.

Difference between Spiral model and waterfall model :

S.NO. Waterfall Model Spiral Model

Waterfall model works in sequential 1. While spiral model works in

1. method. evolutionary method.

In waterfall model errors or risks are

2. In spiral model errors or risks are identified
identified and rectified after the
2. completion of stages. and rectified earlier.

Waterfall model is adopted by

3. customers. 3. While spiral model is adopted by developers.
 Waterfall model is applicable for small
4. project. 4. While Spiral model is used for large project.

5. While in spiral model requirements and

In waterfall model requirements and
5. early stage planning is necessary. early stage planning is necessary if required.

6. Flexibility to change in spiral model

Flexibility to change in waterfall model is
6. Difficult. is not Difficult.

There is high amount risk in waterfall

7. model. 7. There is low amount risk in spiral model.

Waterfall model is comparatively

8. inexpensive. 8. While cost of spiral model is very expensive.

Difference between waterfall model and Incremental model :

Waterfall Model Incremental Model

1. Need of Detailed Documentation in

1. Need of Detailed Documentation in
waterfall model is Necessary. incremental model is Necessary but not too much.

2. In waterfall model early stage 2. In incremental model early stage planning is also
planning is necessary. necessary.

3. There is high amount risk in waterfall

model. 3. There is low amount risk in incremental model.

4. There is short waiting time for running

4. There is long waiting time for running
software in waterfall model. software in incremental model.

5. Waterfall model can’t handle large

project. 5. Incremental model also can’t handle large
 Waterfall Model Incremental Model

project.

6. Flexibility to change in incremental model

6. Flexibility to change in waterfall model
is Difficult. is Easy.

7. Cost of Waterfall model is Low. 7. Cost of incremental model is also Low.

8. Testing is done in incremental model after

8. Testing is done in waterfall model
after completion of all coding phase. every iteration of phase.

9. Returning to previous stage/phase in

9. Returning to previous stage/phase in
waterfall model is not possible. incremental model is possible.

10. In incremental model large team is not

10. In waterfall model large team is
required. required.

11. In incremental model overlapping of phases

11. In waterfall model overlapping of
phases is not possible. is possible.

12. There is multiple development cycles take

12. There is only one cycle in waterfall
model. place in incremental model.

Difference between Spiral model and Incremental model :

S.No. Spiral Model Incremental Model

Spiral model is a software development 1. Incremental Model is a software development model

model and is made with features of where the product is, analyzed, designed,
incremental, waterfall or evolutionary implemented and tested incrementally until the
1. prototyping models. product is finished.
 In spiral model requirements and early stage 2. In incremental model requirements and early stage
2. planning is also necessary. planning is necessary.

Flexibility to change in spiral model is not

3. that difficult. 3. Flexibility to change in incremental model is Easy.

4. There is low amount risk in spiral model. 4. There is also low amount risk in incremental model.

5. While cost of spiral model is very expensive. 5. Cost of incremental model is also Low.

6. Spiral model can handle large project. 6. Incremental model can’t handle large project.

In spiral model overlapping of phases is not 7. In incremental model overlapping of phases is

7. possible. possible.

Testing is done in spiral model at the end of 8. Testing is done in incremental model after every
8. the engineering phase. iteration of phase.

Returning to previous stage/phase in spiral 9. Returning to previous stage/phase in incremental

9. model is possible. model is possible.

10. In spiral model large team is required. 10. In incremental model large team is not required.

Difference between V-model and Spiral model :

S.No. V MODEL SPIRAL MODEL

1. Spiral model is a software development model and

V model is software development model but is made with features of incremental, waterfall or
1. development and testing are not concurrent. evolutionary prototyping models.

In V-model testing activities start with the first 2. Testing is done in spiral model at the end of the
2. stage. engineering phase.
3. Cost of V-model is expensive. 3. While cost of spiral model is also very expensive.

4. Flexibility to change in spiral model is not that

4. Flexibility of V-model is Little flexible. difficult.

5. Guarantee of success through V-model is high. 5. Guarantee of success through Spiral model is low.

User involvement in V-model is also only in

6. beginning. 6. In this user Involvement is only at the beginning.

Difference between V-model and Waterfall model:

Besides that v-model is the alternate of the waterfall model. There is some difference between
these two models which are given below.

Waterfall model V-model

1. The cost of Waterfall model is low. 1. V-model is expensive.

2. Simplicity of V-model is
2. Simplicity of Waterfall model is simple. Intermediate.

3. Flexibility of V-model is Little

3. Flexibility of Waterfall model is Rigid. flexible.

4. Waterfall model is a sequential execution 4. It is also a sequential execution

process. process.

5. Waterfall model’s steps move in a linear 5. V-model’s steps don’t move in

way. linear way.

6. User involvement in Waterfall model is only 6. User involvement in V-model is

in beginning. also only in beginning.

7. In Waterfall model testing activities start 7. In V-model testing activities start

 after the development activities are over. with the first stage.

8. Guarantee of success through Waterfall 8. Guarantee of success through

model is low. V-model is high.

9. V-model is a simultaneous
9. Waterfall model is a continuous process. process.

10. Software made using V-model,

10. Software made using Waterfall model, the the number of defects are greater
number of defects are less in comparison of in comparison of software made
software made using V-model. using Waterfall model.

11. Requirement specification in

11. Requirement specification in Waterfall V-model is also necessary in
model is necessary in beginning. beginning.

12. Waterfall model is less used now-a-days in 12. V-model is widely used in
software engineering. software engineering.

Properties of Model Water-Fall Model Incremental Model Spiral Model Rad Model
Planning in early stage Yes Yes Yes No
Returning to an earlier
No Yes Yes Yes
phase
Handle Large-Project Not Appropriate Not Appropriate Appropriate Not Appropriate
Detailed Documentation Necessary Yes but not much Yes Limited
Cost Low Low Expensive Low
Requirement Time boxed
Specifications Beginning Beginning Beginning release
Flexibility to change Difficult Easy Easy Easy
Only at the
User Involvement Only at beginning Intermediate High beginning
Maintenance Least Promotes Maintainability Typical Easily Maintained
Duration Long Very long Long Short
Risk Involvement High Low Medium to high risk Low
Framework Type Linear Linear + Iterative Linear + Iterative Linear
After completion of At the end of the After completion
Testing coding phase After every iteration engineering phase of coding
 Properties of Model Water-Fall Model Incremental Model Spiral Model Rad Model
Yes (As parallel
Overlapping Phases No No Yes
development is there)
Easily
Maintenance Least Maintainable Maintainable Yes
Maintainable
Re-usability Least possible To some extent To some extent Yes
Time-Frame Very Long Long Long Short
Working software At the end of the At the end of every At the end of every At the end of the
availability life-cycle iteration iteration life cycle
Rapid
Objective High Assurance Rapid Development High Assurance
development
Team size Large Team Not Large Team Large Team Small Team
Customer control over
Very Low Yes Yes Yes
administrator
 Practical No 5
Aim- Preparation of requirement document for standard application problems in
standard format.(e.gLibrary Management System, Railway Reservation system,
Hospital management System, University Admission system)

A Software Requirements Specification (SRS) is a document that describes the nature of

a project, software or application. In simple words, SRS document is a manual of a project
provided it is prepared before you kick-start a project/application. This document is also
known by the names SRS report, software document. A software document is primarily
prepared for a project, software or any kind of application.
There are a set of guidelines to be followed while preparing the software requirement
specification document. This includes the purpose, scope, functional and nonfunctional
requirements, software and hardware requirements of the project. In addition to this, it
also contains the information about environmental conditions required, safety and security
requirements, software quality attributes of the project etc.
What is a Software Requirements Specification document?
A Software requirements specification document describes the intended purpose,
requirements and nature of a software to be developed. It also includes the yield and cost
of the software.
In this document, flight management project is used as an example to explain few points.

LIBRARY MANAGEMENT SYSTEM

1.1 PROBLEM DEFINITION

The library management system is software, which automates the job of a librarian.
1.2 The user can inquire about the availability of a book in which he can
search by entering the author’s name or by entering the title of the
book.
1.3 The user can borrow a book. He must provide the username and the
card number, which is unique and confidential to each user. By
confirming the authenticity of a user, the library management system
provides information about the number of books already borrowed by
the user and by referring to the database whether the user can borrow
books or not. The library management system allows the user to enter
the title and the author of the book and hence issues the book if it is
available.
1.4 By entering the user details and the book details the user can return
the borrowed book.
 2.1 SYSTEM REQUIREMENT SPECIFICATION

2.2 INTRODUCTION

2.2.1 Purpose
2.2.1.1 The purpose of this SRS is to describe the
requirements involved in developing a Library
management system.
2.2.1.2 The intended audience is any person, who wants to
inquire, borrow and return the books.
2.2.2 Scope
2.2.2.1 The product is titled Library Management System.
2.2.2.2 The product will perform the following tasks
2.2.2.2.1 Enquire about the availability of books.
2.2.2.2.2 Borrow books if available.
2.2.2.2.3 Return the borrowed books.
2.2.3 Definitions, Acronyms and Abbreviations
2.2.3.1 DBMS – Database Management System.

2.2.4 References
2.2.4.1 IEEE standard 830-1998 recommended practice for Software
Requirements Specifications-Description.

2.2.5 Overview
2.2.5.1 The SRS contains an analysis of the requirements necessary
to help easy design.

2.2.5.2 The overall description provides interface requirements for the

Library Management System, product perspective, hardware
interfaces, software interfaces, communication interface,
memory constraints, product functions, user characteristics
and other constraints.

2.2.5.3 Succeeding pages illustrate the characteristics of typical naïve

users accessing the system along with legal and functional
constraints enforced that affect Library Management System
in any fashion.
2.3 THE OVERALL DESCRIPTION
2.3.1 Product perspective
2.3.1.1 Hardware interfaces
2.3.1.1.1 Hard disk: The database connectivity requires a
hardware configuration that is on-line. This makes it
necessary to have a fast database system running on
high rpm hard disk permitting complete data redundancy
and back-up systems to support the primary goal of
reliability.
2.3.1.1.2 The system must interface with the standard output
devise, keyboard and mouse to interact with this
software.
2.3.1.2 Software interfaces
2.3.1.2.1 Back End: MS-Access 2007
2.3.1.2.2 Front End: Microsoft Visual Basic 6.0
2.3.1.3 Memory Constraints
2.3.1.3.1 No specific constraints on memory.
2.3.1.4 Operations
2.3.1.4.1 The software allows three modes of operations
2.2.1.4.1.1 Enquire about the availability and status of
books.
2.3.1.4.1.2 By extracting the username and password the
software allows the user to borrow a maximum of
three books.
2.3.1.4.1.3 By extracting the username and password the
software allows the user to return the borrowed
books.
2.3.2 Product Functions
2.2.2.1.1 Enquire about the availability and status of books.
2.2.2.1.2 Search the availability of book by entering the title of the book.
2.2.2.1.3 Search the availability of book by entering the author of the book.
2.2.2.1.4 The software validates the authentic user by extracting
their user name and password.
2.2.2.1.5 After the validation of the user software allows the user to
borrow a maximum of three books based on the number of
books which where already borrowed.
2.2.2.1.6 After the validation of the user software allows the user
 2.3.3 User characteristics
2.3.3.1 The intended users of this software need not have specific
knowledge as to what is the internal operation of the system.
Thus the end user is at a high level of abstraction that allows
easier, faster operation and reduces the knowledge requirement
of end user
2.3.3.2 The Product is absolutely user friendly, so the intended users
can be the naïve users.
2.3.3.3 The product does not expect the user to possess any technical
background. Any person who knows to use the mouse and the
keyboard can successfully use this product.

2.3.4 Constraints
2.3.4.1 The user has a unique username and password, there are no
options to retrieve a password or username in case it is
forgotten or lost hence the user is requited to remember or store
the username and password.

2.4 SPECIFIC REQUIREMENTS

2.4.1 Logical Database Requirements
2.4.1.1 The system should contain databases that include all necessary
information for the product to function according to the requirements.
These include relations such as user details and book details.
2.4.1.2 The user details refer to the information such as name, card number,
no. of books borrowed, the title and the name of the author of the
books that were borrowed.
2.4.1.3 The book details refer to the information such as the title of the book,
author availability status and the number of copies that are available.
 2.5 FRONT – END DESCRIPTION

The library management system is an automated library system where the

user can search for the book by either entering the details of the book or the
author’s name. By entering the username and the password the software, by
checking the number of books that are already borrowed, enables us to borrow a
maximum of three books. And by entering the username and password (card
number), which is unique, the user can return the books.

2.6 BACK – END DESCRIPTION

The library management system consists of two tables. One contains the
student details such as the name, card number that is the password, title and the
author of the three books, which could be borrowed. The book details consist of
the title of the book, number of copies, author and the availability status.

2.7 DATA STRUCTURES

2.6.1. BOOK DETAILS

FIELD NAME TYPE CONSTRAINTS
REGISTER_NO NUMBER NOT NULL
BOOK_ID NUMBER NOT NULL
ISSUE_DATE DATE/TIME
RETURN_DAT DATE/TIME
E
BOOK_NAME TEXT

2.6.2. STUDENT DETAILS

FIELD NAME TYPE CONSTRAINTS
REGISTER_NO NUMBER NOT NULL
FNAME TEXT NOT NULL
LNAME TEXT
GENDE TEXT
R
DEPT TEXT
EMAIL TEXT
PASSWORD TEXT
NO_OF_BOOKS NUMBER
2.8 DATA FLOW DIAGRAM
3.0 TESTING:

FORM NAME INPUT EXPECTED ACTUAL STATUS

OUTPUT OUTPUT
MAIN MENU Menu Option Show Required Pass
FORM required Form was
displayed
Form
MEMBERSHIP Member Create new New Pass
FORM details member Account
are account was created
entered
LOGIN FORM Member ID If password Member Pass
and is correct, authenticat
password login. ed for future
operations.
ISSUE FORM Book ID If books Book issued Pass
issued is less
than three,
issue the
book.
RETURN/REISSUE Book ID Book returned/ Book returned/ Pass
FORM reissued reissued
BOOK ENQUIRY Book Name Book details Book details Pass
are displayed are displayed
4.0 SAMPLE FORMS

MAIN MENU FORM

MEMBERSHIP FORM

LOGIN FORM
ISSUE FORM

RETURN/REISSUE FORM
 BOOK ENQUIRY FORM

4.0 RESULT:

Thus the online Library System was implemented using the specified front end and back end
tools.
 Practical-6

AIM: To identify the usage of Regression Testing.

What is regression testing?
Regression testing is a black box testing techniques. It is used to authenticate a code change
in the software does not impact the existing functionality of the product. Regression testing is
making sure that the product works fine with new functionality, fixes, or any change in the
existing feature.

Regression testing is a type of software testing.

Test cases are re-executed to check the previous functionality of the application is working
fine, and the new changes have not produced any bugs.

Regression testing can be performed on a new build when there is a significant change in the
original functionality. It ensures that the code still works even when the changes are occurring.
Regression means Re-test those parts of the application, which are unchanged.

Regression tests are also known as the Verification Method. Test cases are often automated.
Test cases are required to execute many times and running the same test case again and
again manually, is time-consuming and tedious too.

Example of Regression testing

Here we are going to take a case to define the regression testing efficiently:
Consider a product Y, in which one of the functionality is to trigger confirmation,
acceptance, and dispatched emails. It also needs to be tested to ensure that the change in
the code not affected them. Regressing testing does not depend on any programming
language like , etc. This method is used to test the product for modifications or any updates
done. It ensures that any change in a product does not affect the existing module of the
product. Verify that the bugs fixed and the newly added features not created any problem in
the previous working version of the Software.

When can we perform Regression Testing?

We do regression testing whenever the production code is modified.

We can perform regression testing in the following scenario, these are:

1. When new functionality added to the application.

Example:
A website has a login functionality which allows users to log in only with Email. Now providing
a new feature to do login using Facebook.

2. When there is a Change Requirement.

Example:
Remember password removed from the login page which is applicable previously.
3. When the defect
fixed Example:
Assume login button is not working in a login page and a tester reports a bug stating that the
login button is broken. Once the bug fixed by developers, tester tests it to make sure Login
Button is working as per the expected result. Simultaneously, tester tests other functionality
which is related to the login button.
4. When there is a performance

issue fix Example:

Loading of a home page takes 5 seconds, reducing the load time to 2 seconds.
5. When there is an environment
change Example:
When we update the database from MySql to Oracle.

How to perform Regression Testing?

The need for regression testing comes when software maintenance includes enhancements,
error corrections, optimization, and deletion of existing features. These modifications may
affect system functionality. Regression Testing becomes necessary in this case.

Regression testing can be performed using the following techniques:

1. Re-test All:

Re-Test is one of the approaches to do regression testing. In this approach, all the test case
suits should be re-executed. Here we can define re-test as when a test fails, and we determine
the cause of the failure is a software fault. The fault is reported, we can expect a new version
of the software in which defect fixed. In this case, we will need to execute the test again to
confirm that the fault fixed. This is known as re-testing. Some will refer to this as confirmation testing.
The re-test is very expensive, as it requires enormous time and resources.

2. Regression test Selection:

o In this technique, a selected test-case suit will execute rather than an entire test-case
suit.
o The selected test case suits divided in two cases
1. Reusable Test cases.
2. Obsolete Test cases.
o Reusable test cases can use in succeeding regression cycle.
o Obsolete test cases can't use in succeeding regression cycle.

3. Prioritization of test cases:

Prioritize the test case depending on business impact, critical and frequently functionality used.
Selection of test cases will reduce the regression test suite.

What are the Regression Testing tools?

Regression Testing is a vital part of the QA process; while performing the regression we may
face the below challenges:

Time Consuming
Regression Testing consumes a lot of time to complete. Regression testing involves existing
tests again, so testers are not excited to re-run the test.

Complex
Regression Testing is complex as well when there is a need to update any product; lists of the
test are also increasing.

Communicating business rule

Regression Testing ensures the existing product features are still in working order.
Communication about regression testing with a non-technical leader can be a difficult task.
The executive wants to see the product move forward and making a considerable time
investment in regression testing to ensure existing functionality working can be hard.
1. Identify Impact Area
2. Test Cases Increases Release by Release
3. Less Resources
4. No Accuracy
5. Repetitive Task
6. Monotonous Job
Regression testing process
The regression testing process can be performed across the builds and the releases.
Regression testing across the builds
Whenever the bug fixed, we retest the Bug, and if there is any dependent module, we go
for a Regression Testing.

For example, How we perform the regression testing if we have different builds as Build 1,
Build 2, and Build 3, which having different scenarios.

Build1
o Firstly the client will provide the business needs.
o Then the development team starts developing the features.
o After that, the testing team will start writing the test cases; for example, they write 900
test cases for the release#1 of the product.
o And then, they will start implementing the test cases.
o Once the product is released, the customer performs one round of acceptance testing.
o And in the end, the product is moved to the production server.

Build2
o Now, the customer asks for 3-4 extra (new) features to be added and also provides the
requirements for the new features.
o The development team starts developing new features.
o After that, the testing team will start writing the test case for the new features, and they
write about 150 new test cases. Therefore, the total number of the test case written is
1050 for both the releases.
o Now the testing team starts testing the new features using 150 new test cases.
o Once it is done, they will begin testing the old features with the help of 900 test cases to
verify that adding the new feature has damaged the old features or not.
o Here, testing the old features is known as Regression Testing.
o Once all the features (New and Old) have been tested, the product is handed over to
the customer, and then the customer will do the acceptance testing.
o Once the acceptance testing is done, the product is moved to the production server.

Build3
o After the second release, the customer wants to remove one of the features like Sales.
o Then he/she will delete all the test cases which are belonging to the sales module
 o And then, test the other feature for verifying that if all the other features are working fine
after removing the sales module test cases, and this process is done under the
regression testing.
Regression testing across the release
The regression testing process starts whenever there is a new Release for same project
because the new feature may affect the old elements in the previous releases.

To understand the regression testing process, we will follow the below steps:

Step1
There is no regression testing in Release#1 because there is no modification happen in the
Release#1 as the release is new itself.

Step2
The concept of Regression testing starts from Release#2 when the customer gives some new
requirements.

Step3
After getting the new requirements (modifying features) first, they (the developers and test
engineers) will understand the needs before going to the impact analysis.

Step4
After understanding the new requirements, we will perform one round of impact analysis to
avoid the major risk, but here the question arises who will do the Impact analysis?

Step5
The impact analysis is done by the customer based on their business knowledge, the
developer based on their coding knowledge, and most importantly, it is done by the test
engineer because they have the product knowledge.

Step6
Once we are done with the impact area, then the developer will prepare the impact area
(document), and the customer will also prepare the impact area document so that we can
achieve the maximum coverage of impact analysis.

Step7
After completing the impact analysis, the developer, the customer, and the test engineer will
send the Reports# of the impact area documents to the Test Lead. And in the meantime, the
test engineer and the developer are busy working on the new test case.

Step8
Once the Test lead gets the Reports#, he/she will consolidate the reports and stored in the
test case requirement repository for the release#1.

Step9
After that, the Test Lead will take the help of RTM and pick the necessary regression test
case from the test case repository, and those files will be placed in the Regression Test
Suite.
o The test lead will store the regression test case in the regression test suite for no further
confusion.
o Regression test suite: Here, we will save all the impact area test documents.
o Regression Test Cases: These are the test cases of the old releases text document
which need to be re-executed as we can see in the below image:

Step10
After that, when the test engineer has done working on the new test cases, the test lead will
assign the regression test case to the test engineer.

Step11
When all the regression test cases and the new features are stable and pass, then check the
impact area using the test case until it is durable for old features plus the new features, and
then it will be handed over to the customer.
Types of Regression Testing

The different types of Regression Testing are as follows:

o Unit Regression Testing [URT]
o Regional Regression Testing[RRT]
o Full or Complete Regression Testing [FRT]
o
 Practical no. 7
AIM: To identify the usage of Agile Testing.

Agile testing is an iterative and incremental method, and the necessities, which develop
during the cooperation between the customer and self-establish teams.In agile testing, the
word "Agile" primarily signifies something that can be performed quickly and immediately, but
also in the area of software development.The core-functional agile team implements it in
order to test the software product and its several modules. The implementation of agile testing
makes sure to deliver a high quality product as bugs or defects get deleted in the initial stage
of the project itself.

Agile Testing can create at the beginning of the project with endless incorporation between
development and testing. It is not a sequential but the continuous process.The agile testing process is
a smart way of testing complicated software, which accepts more effective results as compared to the
traditional testing procedures.In the modern days of software testing, agile testing has gained a lot of
and significance. The execution of agile testing will help us identify the initial error and elimination,
giving better results in less development time and costs.

Principles of Agile Testing

Agile Testing includes various different principles that help us to increase the productivity of our
software.

1. Constant response
2. Less documentation
3. Continuous Testing
4. Customer Satisfaction
 5. Involvement of the entire team
6. Test-Driven
7. Quick feedback

For our better understanding, let's see them one by one in detail:

1. Constant Response

The implementation of Agile testing delivers a response or feedback on an ongoing basis.

Therefore, our product can meet the business needs.In other words, we can say that the
Product and business requirements are understood throughout the constant response.

2. Less Documentation

The execution of agile testing requires less documentation as the Agile teams or all the test
engineers use a reusable specification or a checklist. And the team emphases the test rather
than the secondary information.

3. Continuous Testing

The agile test engineers execute the testing endlessly as this is the only technique to make
sure that the constant improvement of the product.

4. Customer Satisfaction

In any project delivery, customer satisfaction is important as the customers are exposed to
their product throughout the development process.
As the development phase progresses, the customer can easily modify and update requirements.
And the tests can also be changed as per the updated requirements.

5. Easy and clean code

When the bugs or defects occurred by the agile team or the testing team are fixed in a similar
iteration, which leads us to get the easy and clean code.

6. Involvement of the entire team

As we know that, the testing team is the only team who is responsible for a testing process in
the Software Development Life Cycle

. But on the other hand, in agile testing, the business analysts (BA)
and the developers can also test the application or the software.

7. Test-Driven

While doing the agile testing, we need to execute the testing process during the
implementation that helps us to decrease the development time. However, the testing is
implemented after implementation or when the software is developed in the traditional process.

8. Quick response

In each iteration of agile testing, the business team is involved. Therefore, we can get
continuous feedback that helps us to reduces the time of feedback response on development
work.

How is Agile Methodology used in Testing?

Agile Testing is a fast and informal testing process. In simple terms, we can say that it is
specified as an advanced and dynamic type of Testing that is performed regularly
throughout every iteration of the SDLC (Software Development Life Cycle) by the agile
test engineers.

If we deliver the software quickly with the best of the attributes, and the customer
satisfaction is the primary concern at some stage in the agile testing process.

Agile Testing Methodologies

When we are executing the agile testing, the team takes help from several agile
methodologies, which support them in accomplishing the precise results.

Some of the effective agile testing methodologies are as follows:

 o Test-Driven Development (TDD)
o Behavior Driven Development (BDD)
o Exploratory Testing
o Acceptance Test-Driven Development (ATDD)
o Extreme Programming (XP)
o Session-Based Testing
o Dynamic Software Development Method (DSDM)
o Crystal Methodologies

Test-Driven Development (TDD)

The test-driven development method begins with the test itself. As the name proposes, the
TDD varies upon the repetition of the development cycle.

We already knew that the first step in of development cycle is to create a unit test case. And
in the next step, we will be designing the code that fits the test case in order to execute the test
cases.

Hence, the whole code is designed until the unit test passes. Generally, the test-driven
development is executed by using the automated testing tools and implement on units and
components of the code.

Behavior-Driven Development (BDD)

The following method in agile testing is behavior-driven development. The BDD enhances
the communication between the project stakeholders to facilitate the members adequately and
understand all the components before the development process begins.
It is constructed on the same rules as TDD and ATDD. Therefore, the code is developed as
per the test case designed in this testing methodology too.

The primary purpose of this development is to emphasize the identification of business needs
and outputs. And the development should be consistent to a business output.

In behavior-driven development, we need to follow the below steps:

1. Describe the behavior.

2. Generating the test case.
3. Writing code as per the test case is specified.
4. Continuing the process until the code passes the test case.

Exploratory Testing

In Software testing, exploratory testing

is one particular type where the test engineers have the fundamental freedom to explore the
code and create the most effective software.

In simple words, we can say that if we don't have the requirement, then we do one round of
exploratory testing.

Exploratory testing is a very significant part of the agile test as it helps discover the unknown
risks from the software that a simple testing approach could not have noticed.

To explore each aspect of the software functionality, the test engineer creates various test
cases, executes different tests, and records the process to learn it and understand its
particular flow.

While performing the exploratory testing, we need to follow the below steps:

o Exploring the application in all possible ways

o Understanding the flow of the application
o Preparing a test document
o Testing the application

Acceptance Test-Driven Development (ATDD)

Another methodology of agile testing is Acceptance Test-Driven Development (ATDD). The

ATDD approach emphasizes the customer's requirements by involving the team members with
different viewpoints.The team's members of development, testing, and the customers come
together in order to develop the acceptance test from the customer's
perspective.In Acceptance Test Driven Development, the code is acquired along with the
developed acceptance test case.It is a very customer-centered methodology; the primary
objective of using the ATDD methodology is to develop a program based on the user's view.

Extreme Programming (XP)

The next significant agile methodology is Extreme Programming which is denoted

as XP. When there is a continuous modification in the user requirements, we will go for the
extreme programming methodology.The XP will help us deliver a quality product, which meets
the customer's requirements that are made clear throughout the process of development and
testing.

Session-Based Testing

In the row of various agile testing methodologies, the next methodology is Session-based
testing. It is mainly is created on the values of exploratory testing.Though session-based
testing contains some structure and on the other hand, exploratory testing is performed
unexpectedly without any planning. It is used to help us identify the hidden bugs and defects in
the particular software.

Dynamic Software Development Method (DSDM)

Another effective method of agile testing is Dynamic Software Development Method. It is a

Rapid Application Development (RAD) approach that offers a delivery framework to agile
projects.In other words, we can say that the Dynamic Systems Development technique
(DSDM) is a correlate degree agile code development approach, which gives a framework for
developing and maintaining systems.

Crystal Methodologies

The subsequent agile testing is crystal methodologies. This methodology mainly emphasizes
recording, cyclic delivery, and wrap-up, which is to make sure during the various analyses.

Agile Testing Quadrants

It has different quadrants to easily understand agile testing, which divides the whole testing
process into four parts.In addition to the four quadrants, the left two specify the test engineer
that code to write, and the right two quadrants help them understand the code improved with
the support of response to the left quadrants.These agile testing quadrants may be understood
as a traditional process or strategies to perform the end-to-end agile testing of a software
application in four different stages, as we can see in the following image:
Agile Test Plan

As compared to the waterfall model, the agile test plan is created and updated for every
release. Furthermore, the agile test plan contains those types of testing executed in a specific
iteration, such as test environments, test data requirements, test results, and infrastructure.

The agile test plans emphasize the following:

o Testing Scope: The testing scope specifies the sprint goals, test scope, and test
coverage in which the test will be implemented.

o Performance and Load Testing: Here, it specifies the different testing methods and
procedures.

o Types of testing or levels as per the feature's complexity: It defines those types of
testing or levels of testing which are going to be used. And also specifies the data and
configurations for the test and the environment in which the test will be executed.

o Mitigation or Risks Plan: It defines the backup plan prepared to overcome the risks or
issues. And it also identifies the challenges which might face at the time of testing of the
application in the current release.

o Deliverables and Milestones: It sets the deliverables and milestones of the tests as per
the customer's perspective.

o Infrastructure Consideration: It governs the infrastructure which is required to perform

the tests.

o Resourcing: It lists out the test tasks and the occurrence of tests, which defines how
many times the tests will be executed.

o Establish the New functionalities which are being tested.

 o Last-minute Modification

The most faced challenges during the agile testing are last-minute modifications by the client,
which gives significantly less time to the testing team to design the test plan, which may affect
the product quality. And sometimes, the test engineer is often required to play a semi-
developer role.

o Tools Selection

The selection of tools during agile testing is essential because if we select the wrong tool, it will
waste our time as well as money.As we already knew, the Test execution cycles are highly
reduced, and for the regression testing, we will have minimal timing.

o Lack of Documentation
Another frequently faced challenge while executing agile testing is the lack of documentation.
The probabilities of error are more agile as documentation is given less importance and
ultimately puts more burden on the testing team.

o Repeated Modifications in the code

In an agile method, requirement modification and updation are fundamental, making it the
major challenge for the Quality assurance team.

o Limited Test Coverage

In agile testing, new features are initiated quickly, decreasing the available time for the testing
teams to find whether the latest features are as per the requirement and address the business
suits.After seeing all the frequent challenges, the question arises how do we overcome them?
Therefore, in the below topic, we are going to discuss that:.

Agile Testing life cycle

Just like other types of testing has their life cycle process, Agile Testing life cycle completed
into five different phases, as we can see in the following image:
 Practical no. 8
AIM:To understand the importance of the SDLC and STLC process.

What SDLC?
SDLC (Software Development Life Cycle) defines all the standard phases which are involved
during the software development process. SDLC life cycle is a process of developing software
through a phased manner in the following order

1. Requirements Gathering
2. Design the software
3. Build the Software
4. Test
5. Deployment
6. Maintenance.

Each stage has a definite entry and exit criteria along with deliverables.

What is STLC?

Software Testing Life Cycle (STLC) is the testing process that is executed in a well-planned
manner. In the STLC process, various activities are carried out to improve the quality of the
product. However, STLC phases only deal with testing and detecting errors but not
development itself.

Different companies define different phases in STLC. However, generic Software Test Life
Cycle has the following stages.

1. Requirement Analysis
2. Test Planning
3. Test Development
4. Test Environment Setup
5. Test Execution & Closure
KEY DIFFERENCE:

SDLC defines all the standard phases which are involved during the software development
process, whereas the STLC process defines various activities to improve the quality of the
product.
SDLC is a Development Life Cycle whereas STLC is a Testing Life Cycle.
In SDLC, the development team creates the high and low-level design plans while In STLC,
the test analyst creates the System,Integration Test Plan
In SDLC, real code is developed, and actual work takes place as per the design documents,
whereas in STLC testing team prepares the test environment and executes test cases.
The SDLC life cycle helps a team to complete successful development of the software while
STLC phases only cover software testing.

Why Use SDLC?

Here, are some prime reasons for using SDLC method:

How to write a TEST CASE Software Testing Tutorial

● It aims to produce a high-quality software system which helps you to meet the
customer expectations
● A formal review is created after completion of every stage that provides optimum
management control.
● SDLC helps you to create considerable system documentation
● It produces many intermediate products which can be reviewed to verify whether
they can meet the user’s needs and are according to the stated requirement.
 ● SDLC helps you to ensures that system requirements can be traced back to stated
business requirements
● Every phase has a specific deliverable, entry and exit criteria
● Development stages go one by one which is an ideal option for the small or mid-sized
projects where requirements are clear

Why STLC?
Here, are Important reasons for using STLC method:

● STLC helps make the testing process more sophisticated, consistent and effective
● You can include milestones and deliverables for each step of the project
● Easy to understand and implement even if the model is expanded to various levels
● Time constraints are strongly built in project formulation
● Each module of the project is tested before the beginning of the another module
● The requirement of the specific project is measured against the actual result

Difference Between SDLC and STLC

Parameter SDLC STLC

Origin Development Life Cycle Testing Life Cycle

Objective The main object of SDLC life cycle is The only objective of the STLC
to complete successful development phase is testing.
of the software including testing and
other phases.

Requirement In SDLC the business analyst In STLC, the QA team analyze

Gathering gathers the requirements and requirement documents like
create Development Plan functional and non-functional
documents and create System Test
Plan
High & Low- In SDLC, the development team In STLC, the test analyst creates
Level creates the high and low-level design the Integration Test Plan
Design plans
Coding The real code is developed, The testing team prepares the
and actual work takes place as per the test environment and executes
design documents. them

Maintenance SDLC phase also includes post- Testers, execute regression suits,
deployment supports and updates. usually automation scripts to
check maintenance code
deployed.

Features of SDLC

● The model structure & functions are well documented, and the tested result is
readily available
● The project can be completed step by step before another project begun. Project
units are distinct and easily identifiable.
● Risk management is integral to the model and is handled efficiently.
● The project can be designed so that the pieces should be sourced

Features of STLC

● STLC analyze system requirements collected from clients and stakeholders

● Helps you to create traceability Matrix
● Identify the testing technique and testing types
● Prioritize the feature which should be primarily targeted on the test
● You can Analyze the Automation feasibility with STLC
● Identify the information about the testing environment where the actual test should be
executed