Scribd
Upload
8 views

TDD as a model for enhancing reliability-1

Uploaded by

Vishnupriya Sivakumar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
8 views

TDD as a model for enhancing reliability-1

Uploaded by

Vishnupriya Sivakumar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

SOFTWARE ENGINEERING

DIGITAL ASSIGNMENT – 1

HARI HARRA RAJU [24MCA1069]

GOKULNATH [24MCA1031]
25, AUGUST, 2024

TEST DRIVEN DEVELOPMENT


FOR ENHANCING SOFTWARE RELIABILITY
Hari harra raju S, Gokulnath E

Abstract - The software product must be reliable and quality bound according to the end-user requirements
and the quality standards. A large majority of development teams inside software companies often face
problems such as bugs, poor code, and poor testing techniques. All these together result in inefficient or
poor software in reference to the customer's requirement. Despite the promising number and types of new
methodologies and frameworks introduced to support the production of high-quality software products, the
challenges identified earlier prevail. Those identified problems create a certain pressure to find or already
embrace an alternative way toward the conventional methodologies of software development since several
of the identified problems are attributed to the traditional models. The paradigm "Test Driven
Development" may effectively solve the issues identified. This approach is highly mandatory to describe
and trace the test cases related to the software product before entering the real coding phase or process.
With the help of this technique, most of the edge cases and risks can be surfaced before entrance into the
software construction phase. Hence, developers can meet those challenges with better care. A core concern
of our study is to analyze "Test Driven Development" to the extent that it adds reliability to software. This
would be done by reviewing the literature existing and analyzing the research finds, which would state the
applicability of the "Test Driven Development" model within various contexts and software applications.

Index Term - TDD, Test driven development, Reliability, Quality, Risks, Requirements, Software Product

INTRODUCTION

With the present software era, attaining a relevant issues. Dependable, quality products
standard quality for a truly reliable product is perform accordingly and meet the user's
definitely a challenge. Starting from simple expectation sufficiently. Any software product
functionality, such as setting up alarms in case that is not dependable and quality will cause
one wants to wake up early in the morning, losses not only to the clients but also the company
towards ordering food through the internet and that is developing that software. The above losses
buying new clothes, managing money transfer might lead to major losses comprising customer
functions digitally, and even booking a travel dissatisfaction, financial loss, and organizational
ticket, the involvement of software products in reputation loss that might lead to a possible loss
daily life is everywhere. It plays the crucial role in customers in the future. So far, the
of interacting with the way people interact or run development processes and tools have been
their businesses. For it to be identified as a enhanced but, yet questions about the reliability
software product, it must therefore address the of the software remain. Bug issues, inferior code
quality, and lack of appropriate testing are the implementation and its repercussions on quality
problems most software developing and reliability regarding the software in question
organizations are still faced with. This has in different contexts. Therefore, this research
always led to the generation of software aims to investigate the benefits and challenges of
products that are generally of poor quality and implementing "Test-Driven Development" and
less reliable in terms of the fulfillment of the its efficiency in solving problems occurring
needs of the users or the clients. This flaw throughout the software development process.
mainly arises from the traditional methodologies Therefore, it can really provide developers and
in practice. In most of the traditional strategies, their teams with extremely useful guidance that
test cases are developed soon after the can help improve methodologies, following the
completion of the coding phase, due to which ideas and advantages that have been
boundary cases are most of the time ignored. demonstrated by "Test-Driven Development."
Under normal circumstances, these kinds of The organizational impacts of using "Test-Driven
defects are detected at the eleventh hour of the Development" are such that the software
development process hence, at such points, developed by the organization is reliable and has
making changes in the code really becomes a better quality. This would then mean that the
much more elusive and laborious due to the fact organization could involve the users with fewer
that modification has to be done in several problems.
elements. to solve these kinds of issues only
“Test-Driven Development" approach has been
introduced. In ”Test-driven development"
approach developers have to write the test cases
before they can actually start coding for the
software product. In essence, this approach
alows software developers to view and develop
hypothetical risk scenarios that would bring
about problems during the course of the
development phase and handle these problems
with precision. It can be summarized well as a
sort of iterative process, a test is developed first,
but it fails then, the minimal code needed for the
test to pass is coded up and finally, the new code
is refactored for all the currently available tests
to pass. Sometimes this is referred to as the Red-
Green-Refactor cycle In the test driven
development process test cases are created
before writing the code for the product so the
risks and edge cases can be identified before
hand. so the developers can write code
according to that which will result in a software
product that meets the requirements specified by
the client and hence high quality, reliable
software. This research determines the possible
benefits of "Test-Driven Development" in
improving software reliability and quality. With
that, covered next is a serious study of the
previous research and reported real-
implementation cases of using "Test-Driven
Development". This research paper examines
the findings using a variety of sources that will
be helpful in delving deep into the

You might also like