scispace - formally typeset
Search or ask a question
Author

M. Prasanna

Other affiliations: PSG College of Technology
Bio: M. Prasanna is an academic researcher from VIT University. The author has contributed to research in topics: Test case & Unified Modeling Language. The author has an hindex of 8, co-authored 11 publications receiving 204 citations. Previous affiliations of M. Prasanna include PSG College of Technology.

Papers
More filters
01 Jan 2011
TL;DR: A survey on automatic test case generation techniques that are found in the current literature is presented and problems in usage of certain techniques are identified.
Abstract: Software testing is important activity in Software Development Life Cycle. To cut down cost of manual testing and to increase reliability of it, researchers and practitioners have tried to automate it. One of the important activity in testing environment is automatic test case generation - description of a test, independent of the way a given software system is designed. This paper presents a survey on automatic test case generation techniques that are found in the current literature. Problems in usage of certain techniques are identified. Areas that needed future research are presented.

73 citations

01 Jan 2009
TL;DR: A new model based approach for automated generation of test cases in object oriented systems has been presented and Genetic Algorithm’s tree crossover has been proposed to bring out all possible test cases of a given object diagram.
Abstract: A new model based approach for automated generation of test cases in object oriented systems has been presented. The test cases are derived by analyzing the dynamic behavior of the objects due to internal and external stimuli. The scope of the paper has been limited to the object diagrams taken from the Unified Modeling Language model of the system. Genetic Algorithm’s tree crossover has been proposed to bring out all possible test cases of a given object diagram. Illustrative case study has been presented to establish the effectiveness of our methodology coupled with mutation analysis

49 citations

Proceedings ArticleDOI
01 Aug 2016
TL;DR: The combined use of risk assessment and threat model to understand the security risk of an application is explained and how the model may be identifying threats and how to frame threat prioritization for threat category is discussed.
Abstract: Risk assessment and threat modeling are conducted for different purpose. The integration of risk assessment and threat modeling process limit the risk of software-based system. Incorporating security in all phases of software development life cycle is a tedious task in many organizations. In design phase of SDLC, the 50 % software defects are identified and detected. Most of the security attacks are happen in application layer. This paper explains the combined use of risk assessment and threat model to understand the security risk of an application. We also discuss how the model may be identifying threats and how to frame threat prioritization for threat category. Finally, we recommend understanding of risk of detection and creating a fair environment to reduce the likelihood of committing criminal acts by attackers.

19 citations

Proceedings ArticleDOI
P Mani1, M. Prasanna1
25 Jul 2016
TL;DR: A technique to identify the test coverage criteria, valid and invalid path and data flow from FBD, and generate test cases from the functional block diagram with several PLC devices in a smart home system.
Abstract: Programmable logic controller (PLC) is utilized extensively for automation of the electromechanical process. The functionality of the modern PLC is equivalent to desktop computers. Software source code for PLC's is based on graphical data flow of the functional block diagram (FBD). The software development process has multiple phases. More time and cost to be spent in the testing phase. Effective software testing to be producing high quality in PLC. Test cases are part of the software testing process. If PLC test cases are generated using FBD then all the functional requirements reached. The test case has been lodged in design level to be reducing more cost and time in PLC development process. The applicable test cases are created according to the functional requirements and data flow of FBD. It has been proposed to identify the test coverage criteria, valid and invalid path and data flow from FBD. The methodology has to be completely automated to generate test cases from the functional block diagram. This paper has presented our technique with several PLC devices in a smart home system. The generated test cases achieve high test coverage.

17 citations

Proceedings ArticleDOI
01 Jul 2016
TL;DR: This paper analyses the various Black box testing methodologies and the issues related to the same and suggests ways to improve the quality of the testing activities.
Abstract: Software rules in almost all fields of science and technology. Now a days the user classes of a particular software are comparatively high based on their acceptance and quality. So it is the onus of the software developer to ensure that the software is bug free and it will perform the desired functionalities without fail. Software testing is an important activity in Software Development Life Cycle (SDLC) phases. In traditional Waterfall model, testing is the life cycle activity that is performed after the design and coding phase. The various research analytics states that nearly 30% effort of entire software development is used for performing testing activities. So testing activities plays a vital role in developing a quality software. Software testing mainly consists of three categories: Unit testing, Integration testing, System testing. Unit testing basically follows two approaches, Black box testing and White box testing. This paper analyses the various Black box testing methodologies and the issues related to the same.

16 citations


Cited by
More filters
01 Jan 2009
TL;DR: This paper presents a meta-modelling framework for modeling and testing the robustness of the modeled systems and some of the techniques used in this framework have been developed and tested in the field.
Abstract: ing WS1S Systems to Verify Parameterized Networks . . . . . . . . . . . . 188 Kai Baukus, Saddek Bensalem, Yassine Lakhnech and Karsten Stahl FMona: A Tool for Expressing Validation Techniques over Infinite State Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 J.-P. Bodeveix and M. Filali Transitive Closures of Regular Relations for Verifying Infinite-State Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Bengt Jonsson and Marcus Nilsson Diagnostic and Test Generation Using Static Analysis to Improve Automatic Test Generation . . . . . . . . . . . . . 235 Marius Bozga, Jean-Claude Fernandez and Lucian Ghirvu Efficient Diagnostic Generation for Boolean Equation Systems . . . . . . . . . . . . 251 Radu Mateescu Efficient Model-Checking Compositional State Space Generation with Partial Order Reductions for Asynchronous Communicating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Jean-Pierre Krimm and Laurent Mounier Checking for CFFD-Preorder with Tester Processes . . . . . . . . . . . . . . . . . . . . . . . 283 Juhana Helovuo and Antti Valmari Fair Bisimulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Thomas A. Henzinger and Sriram K. Rajamani Integrating Low Level Symmetries into Reachability Analysis . . . . . . . . . . . . . 315 Karsten Schmidt Model-Checking Tools Model Checking Support for the ASM High-Level Language . . . . . . . . . . . . . . 331 Giuseppe Del Castillo and Kirsten Winter Table of

1,687 citations

Proceedings ArticleDOI
26 Feb 2010
TL;DR: Software testing is any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results, or reliability estimation.
Abstract: Software testing is any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results. Although crucial to software quality and widely deployed by programmers and testers, software testing still remains an art, due to limited understanding of the principles of software. The difficulty in software testing stems from the complexity of software: we can not completely test a program with moderate complexity. Testing is more than just debugging. The purpose of testing can be quality assurance, verification and validation, or reliability estimation. Testing can be used as a generic metric as well. Correctness testing and reliability testing are two major areas of testing. Software testing is a trade-off between budget, time and quality.

327 citations

01 Jan 1981
TL;DR: In this article, the authors provide an overview of economic analysis techniques and their applicability to software engineering and management, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.
Abstract: This paper summarizes the current state of the art and recent trends in software engineering economics. It provides an overview of economic analysis techniques and their applicability to software engineering and management. It surveys the field of software cost estimation, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.

283 citations

Book
18 Dec 2017
TL;DR: This chapter discusses software engineering, knowledge engineering and end user development approaches, and the role of case tools in the development of software quality assurance and testing.
Abstract: Salient Features: 1. Software Engineering Fundamentals: Definition of software product, software development paradigms; software engineering, knowledge engineering and end user development approaches. Software Analysis: Abstraction, partitioning and projection, system specification, software requirements specification (SRS) standards, formal specification method, specification tools, flow based, data based and object orientated analysis. 2. Systems Design: Idealized and constrained design, process oriented design (Gane and Sarson and Yourdon notations); data oriented design, Object oriented design (Booch approach), Cohesion and coupling; Design metrics, design documentation standards, Role of Case Tools. 3. Coding And Programming: Choice of programming languages, mixed language programming and call semantics, Re-engineering legacy systems, coding standard. 4. Software Quality And Testing: Software quality assurance, types of software testing (white box, black box, unit, integration, validation, system etc. 5. Software Project Management: Planning software projects, work background structures, integrating software, software design.

136 citations

Journal ArticleDOI
TL;DR: Assessment of the applications online for vulnerabilities at regular intervals and if any changes are made in the code, Webhook will trigger the vulnerability checking tool based on Hashing algorithm to check for vulnerabilities in the updated application.
Abstract: Cloud computing is a very rapidly growing technology with more facilities but also with more issues in terms of vulnerabilities before and after deploying the applications into the cloud The vulnerabilities are assessed before the applications are deployed into the cloud However, after deploying the applications, periodical checking of systems for vulnerabilities is not carried out This paper assesses the applications online for vulnerabilities at regular intervals and if any changes are made in the code, Webhook will trigger the vulnerability checking tool based on Hashing algorithm to check for vulnerabilities in the updated application The main aim of this system is to constantly scan the applications that are deployed in the cloud and check for vulnerabilities as part of the continuous integration and continuous deployment process This process of checking for vulnerabilities after every update in the application should be included in the software development lifecycle

75 citations