Validating object-oriented software at design phase by achieving MC/DC

This paper deals with a new technique for validating object-oriented software at design phase of project development. There are several modeling diagrams used at design phase of Software Development Life Cycle. But in this paper, we focus on UML Activity Diagram. In our work, first we construct the...

Full description

Saved in:
Bibliographic Details
Published in:International journal of system assurance engineering and management 2019-08, Vol.10 (4), p.811-823
Main Authors: Barisal, Swadhin Kumar, Behera, Suvam Suvabrata, Godboley, Sangharatna, Mohapatra, Durga Prasad
Format: Article
Language:English
Subjects:
Document markup languages
Engineering
Engineering Economics
Extensible Markup Language
Java
Logistics
Marketing
Object oriented programming
Organization
Original Article
Program verification (computers)
Project development
Quality Control
Reliability
Safety and Risk
Software development
Software testing
Source code
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:This paper deals with a new technique for validating object-oriented software at design phase of project development. There are several modeling diagrams used at design phase of Software Development Life Cycle. But in this paper, we focus on UML Activity Diagram. In our work, first we construct the UML activity diagram for the given system using ArgoUML. Then, the XML (“EXtensible Markup Language”) code is generated for the constructed activity diagram. Next, this XML code is translated to XSD (“XML Schema Definition”) code. This XSD code is given as input to JAXB (“Java Architecture for XML Binding”), which generates the Java template. Then, this Java template is instrumented to a complete Java program with minimal manual effort. Next, we carryout concolic testing of this Java code using jCUTE. This tool generates test cases by taking the Java program as input. Then, the obtained test suite and generated Java source code are inputed into our in-house developed tool named COPECA (COverage PErcentage CAlculator) to calculate MC/DC (Modified Condition/Decision Coverage) score. We have achieved 56.31% MC/DC on doing experiment with fourteen activity diagrams, which is a fair (moderate) achievement compared to the existing work.
ISSN:0975-6809
0976-4348
DOI:10.1007/s13198-019-00815-8