Software testing is one of the most important steps in the process of Software Development. Testing provides
the glimpse of the proper functioning of the system under different conditions. It makes it a necessary step to
choose the best testing method for the software system to be successful and accepted by a large number of
people as the market is really competitive these days and only error free systems can survive for a longer period
of time. This paper gives the comparative analysis of two major methods of testing : Formal Specifications
Based Software Testing and Model Based Software Testing, which are used widely in the process of software
development process. It brings out how these two methods of testing can provide reliability to software system
including the major uses, advantages, and disadvantages of both the testing methods. It briefly gives the detailed
comparative analysis of these two methods of software testing. It also brings out the situations where formal
specifications based testing is more effective and efficient while model based testing being effective in others.
This comparative analysis will help one in deciding on a better testing technique, depending upon the situation,
and requirements of software, for the software to be successful in long run
One of the core quality assurance feature which combines fault prevention and fault detection, is often known as testability approach also. There are many assessment techniques and quantification method evolved for software testability prediction which actually identifies testability weakness or factors to further help reduce test effort. This paper examines all those measurement techniques that are being proposed for software testability assessment at various phases of object oriented software development life cycle. The aim is to find the best metrics suit for software quality improvisation through software testability support. The ultimate objective is to establish the ground work for finding ways reduce the testing effort by improvising software testability and its assessment using well planned guidelines for object-oriented software development with the help of suitable metrics.
This document provides an overview of software testing techniques and their maturation over time. It examines the major research results that have contributed to the growth of testing as an area. The document defines testing goals and categories, including functional vs structural testing and static vs dynamic analysis. It also discusses testing at different stages of the software lifecycle from unit to system level. The technology maturation model and research paradigms framework are used to analyze how testing techniques have evolved from initial ideas to broader solutions and changes in research questions and strategies over time.
Software Testing Outline Performances and Measurementsijtsrd
The procedure of carrying out a program or else scheme by means of the target of ruling bugs called “Software s w Testing”. It is whichever action intended by estimating a characteristic or else ability of a program system plus shaping that it congregates its requisite consequences. Testing is an essential piece in s w growth. It is generally arranged in each stage in the s w progress sequence. Classically, in excess of fifty two perecent of the progress period is used up in testing. Metrics are attainmenting significance plus receiving in commercial segments as associations raise, grown up and endeavour to get better venture values. This study talks about s w testing methods as well as measurements. Indu Maurya "Software Testing Outline: Performances and Measurements" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-5 | Issue-2 , February 2021, URL: https://www.ijtsrd.com/papers/ijtsrd38550.pdf Paper Url: https://www.ijtsrd.com/computer-science/other/38550/software-testing-outline-performances-and-measurements/indu-maurya
International Journal of Engineering Research and Applications (IJERA) is an open access online peer reviewed international journal that publishes research and review articles in the fields of Computer Science, Neural Networks, Electrical Engineering, Software Engineering, Information Technology, Mechanical Engineering, Chemical Engineering, Plastic Engineering, Food Technology, Textile Engineering, Nano Technology & science, Power Electronics, Electronics & Communication Engineering, Computational mathematics, Image processing, Civil Engineering, Structural Engineering, Environmental Engineering, VLSI Testing & Low Power VLSI Design etc.
This document discusses the theory of software testing. It covers several key topics:
1) It identifies five common problems in software testing like limitations of testing teams and issues with manual testing.
2) It describes different testing processes like verification, validation, white-box testing and black-box testing.
3) It outlines three main phases of software testing - preliminary testing, testing, and user acceptance testing - to evaluate a new software system and identify any issues.
Testing and test case generation by using fuzzy logic and nIAEME Publication
The document discusses using fuzzy logic and natural language processing techniques for software testing and test case generation. Specifically, it proposes using these techniques to enable search-based testing, automatic test case generation, and automatic fault finding. Fuzzy logic would be used to generate test cases from natural language requirements and specifications. This approach aims to make testing more efficient. The document provides background on different types of software testing (e.g. black box vs. white box) and discusses gray-box testing and test automation frameworks. It also outlines exploratory testing and functional vs. non-functional testing. The key idea is applying fuzzy logic and NLP to requirements to automatically generate test cases and detect faults.
This document provides an overview of software testing techniques and best practices covered in a course on the topic. It discusses the purpose of software testing, including verification, error detection, and validation. It then surveys common software testing methodologies like white box testing, black box testing, and unit testing. The document also includes two case studies, one on test automation and one on testing an intranet system. Finally, it provides a template for a software test plan and discusses several papers on software testing methods and techniques.
Testing throughout the software life cycle & statistic techniquesNovika Damai Yanti
CATEGORIES OF TEST DESIGN TECHNIQUES
Recall reasons that both specification-based (black-box) and structure-based (white-box) approaches to test case design are useful, and list the common techniques for each. (K1)
One of the core quality assurance feature which combines fault prevention and fault detection, is often known as testability approach also. There are many assessment techniques and quantification method evolved for software testability prediction which actually identifies testability weakness or factors to further help reduce test effort. This paper examines all those measurement techniques that are being proposed for software testability assessment at various phases of object oriented software development life cycle. The aim is to find the best metrics suit for software quality improvisation through software testability support. The ultimate objective is to establish the ground work for finding ways reduce the testing effort by improvising software testability and its assessment using well planned guidelines for object-oriented software development with the help of suitable metrics.
This document provides an overview of software testing techniques and their maturation over time. It examines the major research results that have contributed to the growth of testing as an area. The document defines testing goals and categories, including functional vs structural testing and static vs dynamic analysis. It also discusses testing at different stages of the software lifecycle from unit to system level. The technology maturation model and research paradigms framework are used to analyze how testing techniques have evolved from initial ideas to broader solutions and changes in research questions and strategies over time.
Software Testing Outline Performances and Measurementsijtsrd
The procedure of carrying out a program or else scheme by means of the target of ruling bugs called “Software s w Testing”. It is whichever action intended by estimating a characteristic or else ability of a program system plus shaping that it congregates its requisite consequences. Testing is an essential piece in s w growth. It is generally arranged in each stage in the s w progress sequence. Classically, in excess of fifty two perecent of the progress period is used up in testing. Metrics are attainmenting significance plus receiving in commercial segments as associations raise, grown up and endeavour to get better venture values. This study talks about s w testing methods as well as measurements. Indu Maurya "Software Testing Outline: Performances and Measurements" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-5 | Issue-2 , February 2021, URL: https://www.ijtsrd.com/papers/ijtsrd38550.pdf Paper Url: https://www.ijtsrd.com/computer-science/other/38550/software-testing-outline-performances-and-measurements/indu-maurya
International Journal of Engineering Research and Applications (IJERA) is an open access online peer reviewed international journal that publishes research and review articles in the fields of Computer Science, Neural Networks, Electrical Engineering, Software Engineering, Information Technology, Mechanical Engineering, Chemical Engineering, Plastic Engineering, Food Technology, Textile Engineering, Nano Technology & science, Power Electronics, Electronics & Communication Engineering, Computational mathematics, Image processing, Civil Engineering, Structural Engineering, Environmental Engineering, VLSI Testing & Low Power VLSI Design etc.
This document discusses the theory of software testing. It covers several key topics:
1) It identifies five common problems in software testing like limitations of testing teams and issues with manual testing.
2) It describes different testing processes like verification, validation, white-box testing and black-box testing.
3) It outlines three main phases of software testing - preliminary testing, testing, and user acceptance testing - to evaluate a new software system and identify any issues.
Testing and test case generation by using fuzzy logic and nIAEME Publication
The document discusses using fuzzy logic and natural language processing techniques for software testing and test case generation. Specifically, it proposes using these techniques to enable search-based testing, automatic test case generation, and automatic fault finding. Fuzzy logic would be used to generate test cases from natural language requirements and specifications. This approach aims to make testing more efficient. The document provides background on different types of software testing (e.g. black box vs. white box) and discusses gray-box testing and test automation frameworks. It also outlines exploratory testing and functional vs. non-functional testing. The key idea is applying fuzzy logic and NLP to requirements to automatically generate test cases and detect faults.
This document provides an overview of software testing techniques and best practices covered in a course on the topic. It discusses the purpose of software testing, including verification, error detection, and validation. It then surveys common software testing methodologies like white box testing, black box testing, and unit testing. The document also includes two case studies, one on test automation and one on testing an intranet system. Finally, it provides a template for a software test plan and discusses several papers on software testing methods and techniques.
Testing throughout the software life cycle & statistic techniquesNovika Damai Yanti
CATEGORIES OF TEST DESIGN TECHNIQUES
Recall reasons that both specification-based (black-box) and structure-based (white-box) approaches to test case design are useful, and list the common techniques for each. (K1)
This study empirically evaluated the use of mutation testing to improve test quality for safety-critical software. Mutation testing was applied to two airborne software systems developed using rigorous development processes and guidelines. The study identified an effective subset of mutant types, categorized the root causes of test failures, and examined relationships between program characteristics and mutation survival. The results showed how mutation testing could be useful for finding issues missed by traditional structural coverage analysis and manual peer review. Industry feedback also provided perspectives on integrating mutation testing into typical verification lifecycles for airborne software.
Prioritizing Test Cases for Regression Testing A Model Based ApproachIJTET Journal
The document summarizes a model-based approach to prioritizing regression test cases. It involves generating test cases from UML models, prioritizing them based on the number of states and transitions covered, and clustering them by severity using a dendrogram approach. This helps decrease the time and cost of regression testing by focusing testing efforts on the most important and affected areas first. The proposed approach constructs models from requirements, identifies states, prioritizes flows, generates test cases, and prioritizes the test cases based on severity to improve regression testing efficiency.
Programming testing is the stage which makes programming as usable quality
scholarly amount. Programming testing under experiences distinctive stages. The
accompanying stages according to the examination are investigation test, test
arranging, experiment or test information or test condition creation, test execution,
bugs logging, following and test strategy. Past research has been improved the
situation advance test process in nature of programming. All accessible testing forms
incorporate distinctive advancement models and diverse programming testing
procedures are performed. Each organization chooses their testing procedure
dependent on the basic condition of the applications each organization selects their
testing procedure. The security, execution and utilitarian parts are most basic in every
application these are altogether to be tried and carrying on obviously. This paper will
clarify and guaranteeing about programming applications quality to do enhanced
testing forms. The real programming testing systems are Security, Performance and
Functional are handled by Analysis, Preparation and Execution will be finished up.
Research Activities: past, present, and future.Marco Torchiano
Public seminar for Professor Position at Politecnico di Torino
- past research products
- current research activities
- future outlook
October 19, 2018
International journal of computer science and innovation vol 2015-n1-paper2sophiabelthome
This document provides a taxonomy and comparison of various automated software testing tools. It begins by introducing software testing and the importance of classifying testing tools. It then discusses the objectives of the research and limitations. Various testing methodologies and tool types are defined, including functional, management, and load testing tools. Criteria for comparing tools are outlined. Finally, 32 specific automated testing tools are described briefly, including Selenium, Ranorex, Test Complete, QTP, Watir, TOSCA, and others. The document aims to help professionals select the appropriate testing tools to meet their needs.
Software Quality Engineering is a broad area that is concerned with various approaches to improve software quality. A quality model would prove successful when it suffices the requirements of the developers and the consumers. This research focuses on establishing semantics between the existing techniques related to the software quality engineering and thereby designing a framework for rating software quality.
Test Case Optimization and Redundancy Reduction Using GA and Neural Networks IJECEIAES
More than 50% of software development effort is spent in testing phase in a typical software development project. Test case design as well as execution consume a lot of time. Hence, automated generation of test cases is highly required. Here a novel testing methodology is being presented to test objectoriented software based on UML state chart diagrams. In this approach, function minimization technique is being applied and generate test cases automatically from UML state chart diagrams. Software testing forms an integral part of the software development life cycle. Since the objective of testing is to ensure the conformity of an application to its specification, a test “oracle” is needed to determine whether a given test case exposes a fault or not. An automated oracle to support the activities of human testers can reduce the actual cost of the testing process and the related maintenance costs. In this paper, a new concept is being presented using an UML state chart diagram and tables for the test case generation, artificial neural network as an optimization tool for reducing the redundancy in the test case generated using the genetic algorithm. A neural network is trained by the backpropagation algorithm on a set of test cases applied to the original version of the system.
QUALITY METRICS OF TEST SUITES IN TESTDRIVEN DESIGNED APPLICATIONSijseajournal
New techniques for writing and developing software have evolved in recent years. One is Test-Driven
Development (TDD) in which tests are written before code. No code should be written without first having
a test to execute it. Thus, in terms of code coverage, the quality of test suites written using TDD should be
high.
In this work, we analyze applications written using TDD and traditional techniques. Specifically, we
demonstrate the quality of the associated test suites based on two quality metrics: 1) structure-based
criterion, 2) fault-based criterion. We learn that test suites with high branch test coverage will also have
high mutation scores, and we especially reveal this in the case of TDD applications. We found that TestDriven
Development is an effective approach that improves the quality of the test suite to cover more of the
source code and also to reveal more.
International Journal of Engineering Research and Applications (IJERA) is an open access online peer reviewed international journal that publishes research and review articles in the fields of Computer Science, Neural Networks, Electrical Engineering, Software Engineering, Information Technology, Mechanical Engineering, Chemical Engineering, Plastic Engineering, Food Technology, Textile Engineering, Nano Technology & science, Power Electronics, Electronics & Communication Engineering, Computational mathematics, Image processing, Civil Engineering, Structural Engineering, Environmental Engineering, VLSI Testing & Low Power VLSI Design etc.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
The document summarizes a study on the relationship between test smells and software code quality. The study investigates whether the presence of test smells is associated with increased change/defect-proneness of test code and defect-proneness of production code. The methodology examines over a million test cases across 221 releases of 10 open source projects. Test smells are detected and their correlation with change/defect metrics is analyzed to understand their impact on code quality. Preliminary results indicate tests with smells are more change/defect-prone and certain smells like Indirect Testing are strongly associated with change-proneness.
Towards formulating dynamic model for predicting defects in system testing us...Journal Papers
This document discusses developing a dynamic model for predicting defects in system testing using metrics collected from prior phases. It begins with background on the waterfall and V-model software development processes. It then reviews previous research on software defect prediction, noting limited work has focused specifically on predicting defects in system testing. The proposed model would analyze metrics collected during requirements, design, coding, and testing phases to determine which metrics best predict defects found in system testing. A case study is discussed that would apply statistical analysis to historical metrics data to formulate a mathematical equation for defect prediction. The model would then be verified by applying it to new projects and comparing predicted defects to actual defects found during system testing. The goal is to select a prediction model that estimates defects
A methodology to evaluate object oriented software systems using change requi...ijseajournal
It is a well known fact that software maintenance plays a major role and finds importance in software
development life cycle. As object
-
oriented programming has become the standard, it is very important to
understand th
e problems of maintaining object
-
oriented software systems. This paper aims at evaluating
object
-
oriented software system through change requirement traceability
–
based impact analysis
methodology
for non functional requirements using functional requirem
ents
. The major issues have been
related to change impact algorithms and inheritance of functionality.
Positive developments but challenges still ahead a survey study on ux profe...Journal Papers
This survey study summarizes previous research on UX professionals' work practices and identifies key issues: (1) UX professionals' knowledge and practices, (2) organizational integration challenges, and (3) involvement in local communities. The study surveys 422 UX professionals in 5 countries about these issues. Results show that professionals have strong UX knowledge and use common methods/tools, but organizational integration challenges remain such as lack of resources and user involvement. Involvement in local communities is still limited despite their presence. Overall progress is seen, but more work is needed to address longstanding challenges.
An empirical evaluation of impact of refactoring on internal and external mea...ijseajournal
Refactoring is the process of improving the design of existing code by changing its internal structure
without affecting its external behaviour, with the main aims of improving the quality of software product.
Therefore, there is a belief that refactoring improves quality factors such as understandability, flexibility,
and reusability. However, there is limited empirical evidence to support such assumptions.
The objective of this study is to validate/invalidate the claims that refactoring improves software quality.
The impact of selected refactoring techniques was assessed using both external and internal measures. Ten
refactoring techniques were evaluated through experiments to assess external measures: Resource
Utilization, Time Behaviour, Changeability and Analysability which are ISO external quality factors and
five internal measures: Maintainability Index, Cyclomatic Complexity, Depth of Inheritance, Class
Coupling and Lines of Code.
The result of external measures did not show any improvements in code quality after the refactoring
treatment. However, from internal measures, maintainability index indicated an improvement in code
quality of refactored code than non-refactored code and other internal measures did not indicate any
positive effect on refactored code.
The document discusses various topics related to software testing including:
1) An overview of software testing, its goals of finding bugs and evaluating quality.
2) The need for testing plans to define scope, resources, schedules and quality standards.
3) Types of testing like functional, non-functional, unit, integration and acceptance.
4) Black box and white box testing techniques.
The document describes various software testing methods and techniques. It discusses black box and white box testing methods. Black box testing evaluates software based on requirements without knowledge of internal structure, while white box testing uses knowledge of internal structure. Key black box techniques include equivalence partitioning, boundary value analysis, cause-effect graphing and comparison testing. White box techniques covered are basis path testing, loop testing and control structure testing. The document also discusses other techniques like gray box testing, fuzz testing and model-based testing.
Performance Evaluation of Software Quality ModelEditor IJMTER
With the advent of Internet revolution and the emergence of knowledge based systems, Quality acquires a wider
and more challenging dimension. Quality has evolved and undergone transformation from the inspection era to
the quality control regime and then to quality management and finally to the present TQM approach. At every
stage of the transformation “Quality” has been attaining wider dimension with respect to Customer focus,
continual improvement and has been evolving for addressing increasing demands of customers with respect to
delivery of products and services.
Regression testing concentrates on finding defects after a major code change has occurred. Specifically, it
exposes software regressions or old bugs that have reappeared. It is an expensive testing process that has
been estimated to account for almost half of the cost of software maintenance. To improve the regression
testing process, test case prioritization techniques organizes the execution level of test cases. Further, it
gives an improved rate of fault identification, when test suites cannot run to completion.
Reliability of Med-El Cochlear Implants in children. The Romania Experience.IJERA Editor
Introduction: Early detection of hearing loss significantly lowered the age of cochlear implantation. A failed CI
is a very problematic issue for the child and family and seems to be, for the moment, inevitable. This is a
retrospective review aimed to evaluate the reliability of Med-El devices implanted in children in Romania.
Materials and Methods: We designed a questionnaire to assess the incidence, the time elapsed and the reason
of total device failure. Medical-surgical data were collected from children who received Med-El cochlear
implants since the start of the National Cochlear Implant Program in 2001.
Results: There were 256 patients included. Failure Rate (6,64%) and Cumulative Survival Rate (95,31%) at 5
years were calculated. The majority of the hard and soft failures were encountered in Pulsar devices. Flap
necrosis was the most frequent medical/surgical reason for re-plantation. There was only one case of
posttraumatic device failure. Time elapsed to device failure was short – 22 months on average.
Conclusion: Cochlear implant reliability data should be considered during the choice of an implant for each
individual patient. This study confirms the safety and efficacy of Med-El cochlear implants in children for both
ceramic and non-ceramic devices.
“CLASCA”: Learning System for Classification and Capitalization of Accident S...IJERA Editor
In the process of analysis and assessment of the safety of a rail transportation system, one of the difficulties is to
ensure the completeness of the accident scenarios taken into account by all the actors involved in the
development of the system. The present work is to formalize, classify and archive the historical scenarios
experienced on transportation systems in French already certified and/or approved such that the VAL,
MAGGALY, TVM 430 of the TGV Nord. The goal is to develop a database of historical scenarios from the
know-how of the manufacturers, masters of book and experts and researchers from the French Institute
IFSTTAR to help examine the completeness of safety analyzes. The development and the operation of this basis
of scenarios have need resort to the techniques of knowledge acquisition and automatic learning. The application
of methods for the acquisition of knowledge has resulted essentially on the constitution of a database of
historical knowledge which comprises 70 scenarios relative to the risk of "collision". The exploitation by
machine learning of this basis of scenarios in order to extract the relevant knowledge in a purpose explanatory or
made decision-making the object from the system "CLASCA" presented in this paper.
E-Textiles for Screening Respiratory Disorders along with Temperature MonitoringIJERA Editor
This paper presents a branch of research where e-textiles is used for bio monitoring. This set-up is used for
screening sleep apnea and to alert physicians when there is a case of Hyperthermia. This proposal is to monitor
patients with respiratory disorders or diseases/disorders whose symptoms manifest as respiratory abnormalities
and abnormal temperature, and make it available to the doctor by plotting the values in MATLAB. Conventional
techniques used for screening and monitoring respiratory abnormalities include devices like cannula, nasal strips
etc., which are grueling and strenuous, adding to the patients’ suffering. The connection of this cutting edge
electronics field with textiles will ultimately enable both the study of deviations in the breathing rate and
temperature
This study empirically evaluated the use of mutation testing to improve test quality for safety-critical software. Mutation testing was applied to two airborne software systems developed using rigorous development processes and guidelines. The study identified an effective subset of mutant types, categorized the root causes of test failures, and examined relationships between program characteristics and mutation survival. The results showed how mutation testing could be useful for finding issues missed by traditional structural coverage analysis and manual peer review. Industry feedback also provided perspectives on integrating mutation testing into typical verification lifecycles for airborne software.
Prioritizing Test Cases for Regression Testing A Model Based ApproachIJTET Journal
The document summarizes a model-based approach to prioritizing regression test cases. It involves generating test cases from UML models, prioritizing them based on the number of states and transitions covered, and clustering them by severity using a dendrogram approach. This helps decrease the time and cost of regression testing by focusing testing efforts on the most important and affected areas first. The proposed approach constructs models from requirements, identifies states, prioritizes flows, generates test cases, and prioritizes the test cases based on severity to improve regression testing efficiency.
Programming testing is the stage which makes programming as usable quality
scholarly amount. Programming testing under experiences distinctive stages. The
accompanying stages according to the examination are investigation test, test
arranging, experiment or test information or test condition creation, test execution,
bugs logging, following and test strategy. Past research has been improved the
situation advance test process in nature of programming. All accessible testing forms
incorporate distinctive advancement models and diverse programming testing
procedures are performed. Each organization chooses their testing procedure
dependent on the basic condition of the applications each organization selects their
testing procedure. The security, execution and utilitarian parts are most basic in every
application these are altogether to be tried and carrying on obviously. This paper will
clarify and guaranteeing about programming applications quality to do enhanced
testing forms. The real programming testing systems are Security, Performance and
Functional are handled by Analysis, Preparation and Execution will be finished up.
Research Activities: past, present, and future.Marco Torchiano
Public seminar for Professor Position at Politecnico di Torino
- past research products
- current research activities
- future outlook
October 19, 2018
International journal of computer science and innovation vol 2015-n1-paper2sophiabelthome
This document provides a taxonomy and comparison of various automated software testing tools. It begins by introducing software testing and the importance of classifying testing tools. It then discusses the objectives of the research and limitations. Various testing methodologies and tool types are defined, including functional, management, and load testing tools. Criteria for comparing tools are outlined. Finally, 32 specific automated testing tools are described briefly, including Selenium, Ranorex, Test Complete, QTP, Watir, TOSCA, and others. The document aims to help professionals select the appropriate testing tools to meet their needs.
Software Quality Engineering is a broad area that is concerned with various approaches to improve software quality. A quality model would prove successful when it suffices the requirements of the developers and the consumers. This research focuses on establishing semantics between the existing techniques related to the software quality engineering and thereby designing a framework for rating software quality.
Test Case Optimization and Redundancy Reduction Using GA and Neural Networks IJECEIAES
More than 50% of software development effort is spent in testing phase in a typical software development project. Test case design as well as execution consume a lot of time. Hence, automated generation of test cases is highly required. Here a novel testing methodology is being presented to test objectoriented software based on UML state chart diagrams. In this approach, function minimization technique is being applied and generate test cases automatically from UML state chart diagrams. Software testing forms an integral part of the software development life cycle. Since the objective of testing is to ensure the conformity of an application to its specification, a test “oracle” is needed to determine whether a given test case exposes a fault or not. An automated oracle to support the activities of human testers can reduce the actual cost of the testing process and the related maintenance costs. In this paper, a new concept is being presented using an UML state chart diagram and tables for the test case generation, artificial neural network as an optimization tool for reducing the redundancy in the test case generated using the genetic algorithm. A neural network is trained by the backpropagation algorithm on a set of test cases applied to the original version of the system.
QUALITY METRICS OF TEST SUITES IN TESTDRIVEN DESIGNED APPLICATIONSijseajournal
New techniques for writing and developing software have evolved in recent years. One is Test-Driven
Development (TDD) in which tests are written before code. No code should be written without first having
a test to execute it. Thus, in terms of code coverage, the quality of test suites written using TDD should be
high.
In this work, we analyze applications written using TDD and traditional techniques. Specifically, we
demonstrate the quality of the associated test suites based on two quality metrics: 1) structure-based
criterion, 2) fault-based criterion. We learn that test suites with high branch test coverage will also have
high mutation scores, and we especially reveal this in the case of TDD applications. We found that TestDriven
Development is an effective approach that improves the quality of the test suite to cover more of the
source code and also to reveal more.
International Journal of Engineering Research and Applications (IJERA) is an open access online peer reviewed international journal that publishes research and review articles in the fields of Computer Science, Neural Networks, Electrical Engineering, Software Engineering, Information Technology, Mechanical Engineering, Chemical Engineering, Plastic Engineering, Food Technology, Textile Engineering, Nano Technology & science, Power Electronics, Electronics & Communication Engineering, Computational mathematics, Image processing, Civil Engineering, Structural Engineering, Environmental Engineering, VLSI Testing & Low Power VLSI Design etc.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
The document summarizes a study on the relationship between test smells and software code quality. The study investigates whether the presence of test smells is associated with increased change/defect-proneness of test code and defect-proneness of production code. The methodology examines over a million test cases across 221 releases of 10 open source projects. Test smells are detected and their correlation with change/defect metrics is analyzed to understand their impact on code quality. Preliminary results indicate tests with smells are more change/defect-prone and certain smells like Indirect Testing are strongly associated with change-proneness.
Towards formulating dynamic model for predicting defects in system testing us...Journal Papers
This document discusses developing a dynamic model for predicting defects in system testing using metrics collected from prior phases. It begins with background on the waterfall and V-model software development processes. It then reviews previous research on software defect prediction, noting limited work has focused specifically on predicting defects in system testing. The proposed model would analyze metrics collected during requirements, design, coding, and testing phases to determine which metrics best predict defects found in system testing. A case study is discussed that would apply statistical analysis to historical metrics data to formulate a mathematical equation for defect prediction. The model would then be verified by applying it to new projects and comparing predicted defects to actual defects found during system testing. The goal is to select a prediction model that estimates defects
A methodology to evaluate object oriented software systems using change requi...ijseajournal
It is a well known fact that software maintenance plays a major role and finds importance in software
development life cycle. As object
-
oriented programming has become the standard, it is very important to
understand th
e problems of maintaining object
-
oriented software systems. This paper aims at evaluating
object
-
oriented software system through change requirement traceability
–
based impact analysis
methodology
for non functional requirements using functional requirem
ents
. The major issues have been
related to change impact algorithms and inheritance of functionality.
Positive developments but challenges still ahead a survey study on ux profe...Journal Papers
This survey study summarizes previous research on UX professionals' work practices and identifies key issues: (1) UX professionals' knowledge and practices, (2) organizational integration challenges, and (3) involvement in local communities. The study surveys 422 UX professionals in 5 countries about these issues. Results show that professionals have strong UX knowledge and use common methods/tools, but organizational integration challenges remain such as lack of resources and user involvement. Involvement in local communities is still limited despite their presence. Overall progress is seen, but more work is needed to address longstanding challenges.
An empirical evaluation of impact of refactoring on internal and external mea...ijseajournal
Refactoring is the process of improving the design of existing code by changing its internal structure
without affecting its external behaviour, with the main aims of improving the quality of software product.
Therefore, there is a belief that refactoring improves quality factors such as understandability, flexibility,
and reusability. However, there is limited empirical evidence to support such assumptions.
The objective of this study is to validate/invalidate the claims that refactoring improves software quality.
The impact of selected refactoring techniques was assessed using both external and internal measures. Ten
refactoring techniques were evaluated through experiments to assess external measures: Resource
Utilization, Time Behaviour, Changeability and Analysability which are ISO external quality factors and
five internal measures: Maintainability Index, Cyclomatic Complexity, Depth of Inheritance, Class
Coupling and Lines of Code.
The result of external measures did not show any improvements in code quality after the refactoring
treatment. However, from internal measures, maintainability index indicated an improvement in code
quality of refactored code than non-refactored code and other internal measures did not indicate any
positive effect on refactored code.
The document discusses various topics related to software testing including:
1) An overview of software testing, its goals of finding bugs and evaluating quality.
2) The need for testing plans to define scope, resources, schedules and quality standards.
3) Types of testing like functional, non-functional, unit, integration and acceptance.
4) Black box and white box testing techniques.
The document describes various software testing methods and techniques. It discusses black box and white box testing methods. Black box testing evaluates software based on requirements without knowledge of internal structure, while white box testing uses knowledge of internal structure. Key black box techniques include equivalence partitioning, boundary value analysis, cause-effect graphing and comparison testing. White box techniques covered are basis path testing, loop testing and control structure testing. The document also discusses other techniques like gray box testing, fuzz testing and model-based testing.
Performance Evaluation of Software Quality ModelEditor IJMTER
With the advent of Internet revolution and the emergence of knowledge based systems, Quality acquires a wider
and more challenging dimension. Quality has evolved and undergone transformation from the inspection era to
the quality control regime and then to quality management and finally to the present TQM approach. At every
stage of the transformation “Quality” has been attaining wider dimension with respect to Customer focus,
continual improvement and has been evolving for addressing increasing demands of customers with respect to
delivery of products and services.
Regression testing concentrates on finding defects after a major code change has occurred. Specifically, it
exposes software regressions or old bugs that have reappeared. It is an expensive testing process that has
been estimated to account for almost half of the cost of software maintenance. To improve the regression
testing process, test case prioritization techniques organizes the execution level of test cases. Further, it
gives an improved rate of fault identification, when test suites cannot run to completion.
Reliability of Med-El Cochlear Implants in children. The Romania Experience.IJERA Editor
Introduction: Early detection of hearing loss significantly lowered the age of cochlear implantation. A failed CI
is a very problematic issue for the child and family and seems to be, for the moment, inevitable. This is a
retrospective review aimed to evaluate the reliability of Med-El devices implanted in children in Romania.
Materials and Methods: We designed a questionnaire to assess the incidence, the time elapsed and the reason
of total device failure. Medical-surgical data were collected from children who received Med-El cochlear
implants since the start of the National Cochlear Implant Program in 2001.
Results: There were 256 patients included. Failure Rate (6,64%) and Cumulative Survival Rate (95,31%) at 5
years were calculated. The majority of the hard and soft failures were encountered in Pulsar devices. Flap
necrosis was the most frequent medical/surgical reason for re-plantation. There was only one case of
posttraumatic device failure. Time elapsed to device failure was short – 22 months on average.
Conclusion: Cochlear implant reliability data should be considered during the choice of an implant for each
individual patient. This study confirms the safety and efficacy of Med-El cochlear implants in children for both
ceramic and non-ceramic devices.
“CLASCA”: Learning System for Classification and Capitalization of Accident S...IJERA Editor
In the process of analysis and assessment of the safety of a rail transportation system, one of the difficulties is to
ensure the completeness of the accident scenarios taken into account by all the actors involved in the
development of the system. The present work is to formalize, classify and archive the historical scenarios
experienced on transportation systems in French already certified and/or approved such that the VAL,
MAGGALY, TVM 430 of the TGV Nord. The goal is to develop a database of historical scenarios from the
know-how of the manufacturers, masters of book and experts and researchers from the French Institute
IFSTTAR to help examine the completeness of safety analyzes. The development and the operation of this basis
of scenarios have need resort to the techniques of knowledge acquisition and automatic learning. The application
of methods for the acquisition of knowledge has resulted essentially on the constitution of a database of
historical knowledge which comprises 70 scenarios relative to the risk of "collision". The exploitation by
machine learning of this basis of scenarios in order to extract the relevant knowledge in a purpose explanatory or
made decision-making the object from the system "CLASCA" presented in this paper.
E-Textiles for Screening Respiratory Disorders along with Temperature MonitoringIJERA Editor
This paper presents a branch of research where e-textiles is used for bio monitoring. This set-up is used for
screening sleep apnea and to alert physicians when there is a case of Hyperthermia. This proposal is to monitor
patients with respiratory disorders or diseases/disorders whose symptoms manifest as respiratory abnormalities
and abnormal temperature, and make it available to the doctor by plotting the values in MATLAB. Conventional
techniques used for screening and monitoring respiratory abnormalities include devices like cannula, nasal strips
etc., which are grueling and strenuous, adding to the patients’ suffering. The connection of this cutting edge
electronics field with textiles will ultimately enable both the study of deviations in the breathing rate and
temperature
Retrofitting Of Reinforced Concrete Column by Steel JacketingIJERA Editor
Reinforced concrete structures often require strengthening to increase their capacity to sustain additional loads,
due to change in use that resulted in additional live loads, deterioration of the load carrying elements, design
errors, construction problems during erection, aging of structure itself or upgrading to confirm to current code
requirements. These situations may require additional concrete elements or the entire concrete structure to be
strengthened, repaired or retrofitted. Common methods for strengthening columns include concrete jacketing,
fiber reinforced polymer (FRP) jacketing and steel jacketing. All these methods have been shown to effectively
increase the axial load capacity of columns.
The experimental study was carried out on RC column on designed and detailed using IS 456:2000 provisions.
The concrete mix design being performed after conducting numerous material test and cube test to validate
expected strength as per specified grade of concrete. The trial testing conducted to estimate load at 1st crack and
failure load for normal RC column with capturing displacement using dial gauges at regular load increment in
UTM. The loading conditions are decided based on failure load to induce cracks in column under 85% loading
of the failure one. In all fifteen specimen casted and tested with three samples for failure load estimation, three
samples each for plate jacketing & angle battening system and three samples each for plate jacketing & angle
battening with column preloaded to 85% of its failure load. The angle batten system proves to be better
compared to full plate retrofitting in terms of load carrying capacity and enhancing confinement effect.
Stability of Target Resonance Modes: Ina Quadrature Polarization ContextIJERA Editor
The paper present a studyon the noise effect whenextracting the resonance residue in a quadrature polarization
setup. The accuracy and stability of the mode quadrature residues is necessary to construct the polarization matrix,
and subsequently, derive a robust polarization states of the receiver antenna. However, with lower signal-to-noise
ratios the extraction performance will degrade; in this regards, the in-phase and quadrature components of the
baseband signal demonstrated improvedextraction performancewhen used. Here, a case of two disjoint wires is
used to verify this approach.
Hamiltonian Chromatic Number of GraphsIJERA Editor
This paper studies the Hamiltonian coloring and Hamiltonian chromatic number for different graphs .the main
results are1.For any integer n greater than or equal to three, Hamiltonian chromatic number of Cn is equal to n-2.
2. G is a graph obtained by adding a pendant edge to Hamiltonian graph H, and then Hamiltonian chromatic
number of G is equal to n-1. 3. For every connected graph G of order n greater than or equal to 2, Hamiltonian
chromatic number of G is not more than one increment of square of (n-2).
Effect of Functional Ingredients Such As Mushrooms, Sesame Seeds And wheat Gl...IJERA Editor
The present research has made an efforts to evaluate the quality and shelf life of chicken meat cutlets by
incorporating functional ingredients such as mushrooms, sesame seeds and wheat gluten at optimized levels.
Mushrooms (0, 5, 10, 15 and 20 per cent levels) sesame seeds (0, 1.0, 1.5, 2.0, 2.5 and 3.0 per cent levels) and
wheat gluten (0, 1.0, 1.5, 2.0, 2.5 and 3 per cent levels) in the products for their optimization in formulation of
chicken meat cutlets. Fresh mushrooms when incorporated above 15 percent had deteriorative effect on
appearance, color, texture, flavor and also on cutlets making property. So 15 percent level was selected.
Appearance, color, texture, flavor and overall acceptability scores were maximum at 2.5% level of sesame seed
incorporation . Vital wheat gluten was added upto 3 percent there was drastic decrease in texture and flavor
scores and also on texture and overall acceptability scores. So 1.5 percent level was selected for incorporation
based on these sensory scores. On the basis of sensory evaluation, best levels of mushrooms (15.0 per cent)
sesame seeds (2.5 per cent) and wheat gluten (1.5 per cent) were incorporated in the chicken meat cutlets and
stored under frozen (-20± 2°C) for two months after packing in coextruded plastic films (conventional and
vacuum packs) to evaluate shelf life of the product. The chicken meat cutlets containing functional ingredients
had significantly (p≤ 0.05) higher acceptability than control chicken meat cutlets. Vacuum packed chicken meat
cutlets had significantly (p≤ 0.05) higher appearance, color, texture, flavor, juiciness and overall acceptability
than conventionally packed chicken meat cutlets at the end of 2 months of frozen storage period (-20± 2°C).
New Contraction Mappings in Dislocated Quasi - Metric SpacesIJERA Editor
In this paper the concept of new contraction mappings has been used in proving fixed point theorems. We
establish some common fixed point theorems in complete dislocated quasi metric spaces using new contraction
mappings.
Comparative Study of Mechanical Properties of Self - Healing Concrete Using I...IJERA Editor
This document presents a study on the mechanical properties of self-healing concrete using industrial waste steel scrap and polyethylene fiber. Methyl methacrylate is used as the self-healing agent and encapsulated in microcapsules added to the concrete mix. When cracks form, the microcapsules rupture and release the monomer to polymerize and heal the cracks. Industrial waste steel scrap and polyethylene fiber are added to evaluate their effects on compressive and tensile strength. Experimental results show that polyethylene fiber increases compressive strength while industrial waste steel scrap increases tensile strength compared to self-healing concrete without these additions. Using waste steel scrap is also found to be more economical than steel fiber for self-healing concrete applications
A brief review on mixed convection heat transfer in channel flow with vortex ...IJERA Editor
In an effort to increase processor speeds, 3D IC architecture is being aggressively pursued by researchers and
chip manufacturers. This architecture allows extremely high level of integration with enhanced electrical
performance and expanded functionality, and facilitates realization of VLSI and ULSI technologies. However,
utilizing the third dimension to provide additional device layers poses thermal challenges due to the increased
heat dissipation and complex electrical interconnects among different layers. The conflicting needs of the
cooling system requiring larger flow passage dimensions to limit the pressure drop, and the IC architecture
necessitating short interconnect distances to reduce signal latency warrant paradigm shifts in both of their
design approach. Additional considerations include the effects due to temperature non-uniformity, localized
hot spots, complex fluidic connections, and mechanical design. This paper reviews the advances in electronic
chip cooling in the last decade and provides a vision for code signing integrated cooling systems. For various
heat fluxes on each side of a chip acting as discrete heat source, the current single-phase cooling technology is
projected to provide adequate cooling, albeit with high pressure drops. Effectively mitigating the high
temperatures surrounding local hot spots remains a challenging issue. Various forms of tabulators above the
chips, different geometric arrangements of the chips positioned top and bottom wall of the duct serves very
well in the heat augmentation technique with better performance
Weightage Allocation to influential parameters in FSW for Yield Strength Eval...IJERA Editor
The document discusses weightage allocation to influential parameters in friction stir welding (FSW) for evaluating yield strength. It identifies rotational speed, welding speed, axial force, and tool pin radius as the most influential parameters. An analytical study is conducted to determine the optimal range of parameters based on the maximum temperature generated. Empirical relationships are developed to represent the effect of each parameter on yield strength. Based on the sensitivity of each parameter, weightages of 0.0375, 0.155, 0.307, and 0.5 are allocated to rotational speed, welding speed, axial force, and pin radius respectively, in a single relationship to calculate yield strength.
Comparison of Feature selection methods for diagnosis of cervical cancer usin...IJERA Editor
Even though a great attention has been given on the cervical cancer diagnosis, it is a tuff task to observe the
pap smear slide through microscope. Image Processing and Machine learning techniques helps the pathologist
to take proper decision. In this paper, we presented the diagnosis method using cervical cell image which is
obtained by Pap smear test. Image segmentation performed by multi-thresholding method and texture and shape
features are extracted related to cervical cancer. Feature selection is achieved using Mutual Information(MI),
Sequential Forward Search (SFS), Sequential Floating Forward Search (SFFS) and Random Subset Feature
Selection(RSFS) methods
Finite Element Analysis and Design Optimization of Connecting RodIJERA Editor
The objective of this study is to improve the design of connecting rod of single cylinder four stroke Otto cycle
engine by shape optimization. The main objective of this study is weight reduction of connecting rod and
improving its performance without affecting its functionality. Finite element analysis is one of the most
important tools of CAD/CAM CAE. For this study ANSYS analysis software is used for modeling, analysis and
shape design optimization. Initially, according to design considerations maximum loads were calculated for
various maximum operating loading conditions. Calculated loads used as a loading condition in various load
steps of FEM analysis. Stresses generated across all the locations of connecting rod evaluated using ANSYS
Workbench. For optimization ANSYS Shape optimization module is used and extracted the required shape of
connecting rod. Final CAD model of optimized connecting rod is prepared in Design Modeler. Static structural
analysis of modified design is performed and the results compared with baseline design. After result are
validated with the help of Modified Goodman’s Diagram. From the shape optimization we could able to achieve
14.73% weight reduction in existing connecting rod. Since the optimized design is having sufficient life, the
design is much improved as compared to the existing design
Digital Image Watermarking Based On Gradient Direction Quantization and Denoi...IJERA Editor
Digital watermarking is the art of hiding of information or data in documents, where the embedded information
or data can be extracted to resist copyright violation or to verify the uniqueness of a document which leads to
security. Protecting the digital content has become a major issue for content owners and service providers.
Watermarking using gradient direction quantization is based on the uniform quantization of the direction of
gradient vectors, which is called gradient direction watermarking (GDWM). In GDWM, the watermark bits are
embedded by quantizing the angles of significant gradient vectors at multiple wavelet scales. The proposed
scheme has the advantages of increased invisibility and robustness to amplitude scaling effects. The DWT
coefficients are modified to quantize the gradient direction based on the on the derived relationship between the
changes in the coefficients and the change in the gradient direction. In this paper, we propose a novel explicit
image filter called guided filter. It is derived from a local linear model that computes the filtering output using
the content of guidance image, which can be the input image itself or any other different image. The guided
filter naturally has a fast and non approximate linear time algorithm, regardless of the kernel size and the
intensity range. Finally, we show simulation results of denoising method using guided image filtering over
bilateral filtering
Environmental and Economic Analysis of Thermal Active Building SystemIJERA Editor
This paper is regarding one promising technological solution – which is so called Thermal Active Building
Systems (TABS) –for one of the most critical problems both in environmental and economic aspects, which is
the raising energy consumption. Buildings are the principal application target of the solution once that
population spends most part of their time inside them. Therefore, more energy is required to supply an
increasingly demand in lighting, air conditioning, heating, electronic devices and so on. In this context, TABS
emerge like a possible solution. To ensure the system efficiency or, in other words, prove its viability, it will be
applied an environmental management tool (SWOT Analysis) weighting all the pros and comparing with its
drawbacks, based on previous experiences in implantation of such system, available in literature. A basic
theoretical background, which is extremely important to a better comprehension of the system, covering both
engineering and environmental management areas, is presented on this paper. Results shown that TABS are
efficient mechanisms in the reduction of power consumption, committed with sustainable development, and
which worth the investments in a Life Cycle Cost evaluation
Analysis of Water Quality Index for Groundwater in Gudur Mandal, SPSR Nellore...IJERA Editor
This document summarizes a study analyzing the spatial variability of groundwater quality in Gudur Mandal, SPSR Nellore District, India. 280 groundwater samples were collected and analyzed for parameters like pH, TDS, hardness, chlorides, sulfates, nitrates and fluorides. Spatial interpolation using Inverse Distance Weighted technique was used to generate maps showing variation in parameter levels across locations. Regression models correlating TDS with other parameters were developed. A water quality index integrating parameter values was computed to classify water suitability. The study aims to assess groundwater quality and identify zones based on suitability for domestic use.
Optimization of Macro Block Size for Adaptive Rood Pattern Search Block Match...IJERA Editor
In area of video compression, Motion Estimation is one of the most important modules and play an important role
to design and implementation of any the video encoder. It consumes more than 85% of video encoding time due to
searching of a candidate block in the search window of the reference frame. Various block matching methods have
been developed to minimize the search time. In this context, Adaptive Rood Pattern Search is one of the less
expensive block matching methods, which is widely acceptable for better Motion Estimation in video data
processing. In this paper we have proposed to optimize the macro block size used in adaptive rood pattern search
method for improvement in motion estimation.
Comprehensive Development and Comparison of two Feed Forward Back Propagation...IJERA Editor
The development of an intelligent system for the establishment of relationship between input parameters and the
responses utilizing both reverse and forward modeling of artificial neural networks is the main objective of the
present research work. Prediction of quality characteristics such as front width, back width, front height and
back height of the weld bead geometry in Tungsten Inert Gas welding process of AA5083; H111 Aluminum
alloy is the aim in forward modeling from known set of process parameters such as current, %balance, welding
speed, arc gap, gas flow rate, and frequency. Reverse modeling meets the industrial requirements of automatic
welding to predict the recommended weld bead geometry characteristics. Comprehensive approach for the
development of two back propagation networks viz. feed forward back propagation (FFBP) and Elman back
propagation (EBP) neural networks is adopted. 212 Face centered central composite design based experimental
data is utilized for the development of both supervised learning networks with batch mode training approach. A
comparison of performance of FFBPP and EBP neural networks are made with that of stepwise multiple
regression statistical modeling. Analysis of results showed that both neural network modeling outperformed the
statistical approach in making better predictions and the models are efficient in selection of parameters
effectively for the desired responses. FFBP performance found to marginally better than that of EBP neural
network. Also the forward modeling performance was better than that of reverse modeling in both neural
networks.
Durability Studies on Concrete with Hypo Sludge as Partial Replacement of CementIJERA Editor
This paper summarizes the research work on the properties of hypo sludge when used as partial replacement for
Ordinary Portland Cement (OPC) in concrete. OPC was replaced with hypo sludge by weight at 0%, 5%, 10%,
15%, 20% and 25%. 0% replacement served as the control. Compacting factor test was carried out on fresh
concrete while Compressive Strength test was carried out on hardened 150mm concrete cubes after 7, 14 and 28
days curing in water. The results revealed that the Compacting factor decreased as the percentage replacement
of OPC with hypo sludge increased. The compressive strength of the hardened concrete also decreased with
increasing OPC replacement with hypo sludge. It is recommended that further studies be carried out to gather
more facts about the suitability of partial replacement of OPC with hypo sludge in concrete.
From previous year researches, it is concluded that testing is playing a vital role in the development of the software product. As, software testing is a single approach to assure the quality of the software so most of the development efforts are put on the software testing. But software testing is an expensive process and consumes a lot of time. So, testing should be start as early as possible in the development to control the money and time problems. Even, testing should be performed at every step in the software development life cycle (SDLC) which is a structured approach used in the development of the software product. Software testing is a tradeoff between budget, time and quality. Now a day, testing becomes a very important activity in terms of exposure, security, performance and usability. Hence, software testing faces a collection of challenges.
This document provides an overview of software testing techniques and the history of research in this area. It discusses:
1) The goals and types of software testing, including functional vs structural techniques.
2) Major milestones in the evolution of testing concepts from the 1950s to present day, shifting from debugging to prevention.
3) Key theoretical and methodological contributions to testing techniques from the 1970s onward, including work on path coverage, data flow testing, and model-based approaches.
4) How research in testing techniques has matured over time based on a technology maturation model, moving from ad hoc practices to a systematic discipline grounded in theory.
International Journal of Engineering Research and Applications (IJERA) is an open access online peer reviewed international journal that publishes research and review articles in the fields of Computer Science, Neural Networks, Electrical Engineering, Software Engineering, Information Technology, Mechanical Engineering, Chemical Engineering, Plastic Engineering, Food Technology, Textile Engineering, Nano Technology & science, Power Electronics, Electronics & Communication Engineering, Computational mathematics, Image processing, Civil Engineering, Structural Engineering, Environmental Engineering, VLSI Testing & Low Power VLSI Design etc.
Today in era of software industry there is no perfect software framework available for
analysis and software development. Currently there are enormous number of software development
process exists which can be implemented to stabilize the process of developing a software system. But no
perfect system is recognized till yet which can help software developers for opting of best software
development process. This paper present the framework of skillful system combined with Likert scale. With
the help of Likert scale we define a rule based model and delegate some mass score to every process and
develop one tool name as MuxSet which will help the software developers to select an appropriate
development process that may enhance the probability of system success.
FROM THE ART OF SOFTWARE TESTING TO TEST-AS-A-SERVICE IN CLOUD COMPUTINGijseajournal
Researchers consider that the first edition of the book "The Art of Software Testing" by Myers (1979)
initiated research in Software Testing. Since then, software testing has gone through evolutions that have
driven standards and tools. This evolution has accompanied the complexity and variety of software
deployment platforms. The migration to the cloud allowed benefits such as scalability, agility, and better
return on investment. Cloud computing requires more significant involvement in software testing to ensure
that services work as expected. In addition to testing cloud applications, cloud computing has paved the
way for testing in the Test-as-a-Service model. This review aims to understand software testing in the
context of cloud computing. Based on the knowledge explained here, we sought to linearize the evolution of
software testing, characterizing fundamental points and allowing us to compose a synthesis of the body of
knowledge in software testing, expanded by the cloud computing paradigm.
From the Art of Software Testing to Test-as-a-Service in Cloud Computingijseajournal
Researchers consider that the first edition of the book "The Art of Software Testing" by Myers (1979)
initiated research in Software Testing. Since then, software testing has gone through evolutions that have
driven standards and tools. This evolution has accompanied the complexity and variety of software
deployment platforms. The migration to the cloud allowed benefits such as scalability, agility, and better
return on investment. Cloud computing requires more significant involvement in software testing to ensure
that services work as expected. In addition to testing cloud applications, cloud computing has paved the
way for testing in the Test-as-a-Service model. This review aims to understand software testing in the
context of cloud computing. Based on the knowledge explained here, we sought to linearize the evolution of
software testing, characterizing fundamental points and allowing us to compose a synthesis of the body of
knowledge in software testing, expanded by the cloud computing paradigm.
Software Quality Analysis Using Mutation Testing SchemeEditor IJMTER
The software test coverage is used measure the safety measures. The safety critical analysis is
carried out for the source code designed in Java language. Testing provides a primary means for
assuring software in safety-critical systems. To demonstrate, particularly to a certification authority, that
sufficient testing has been performed, it is necessary to achieve the test coverage levels recommended or
mandated by safety standards and industry guidelines. Mutation testing provides an alternative or
complementary method of measuring test sufficiency, but has not been widely adopted in the safetycritical industry. The system provides an empirical evaluation of the application of mutation testing to
airborne software systems which have already satisfied the coverage requirements for certification.
The system mutation testing to safety-critical software developed using high-integrity subsets of
C and Ada, identify the most effective mutant types and analyze the root causes of failures in test cases.
Mutation testing could be effective where traditional structural coverage analysis and manual peer
review have failed. They also show that several testing issues have origins beyond the test activity and
this suggests improvements to the requirements definition and coding process. The system also
examines the relationship between program characteristics and mutation survival and considers how
program size can provide a means for targeting test areas most likely to have dormant faults. Industry
feedback is also provided, particularly on how mutation testing can be integrated into a typical
verification life cycle of airborne software. The system also covers the safety and criticality levels of
Java source code.
Bab ini membahas model pengembangan perangkat lunak yang paling umum diterapkan, tingkat uji dan jenis uji. Pemeliharaan dapat dilihat sebagai contoh spesifik dari suatu proses pembangunan.
Ini adalah tugas Testing throughout the software life cycle 2
Semoga slide ini bisa menjadi pelajaran untuk kita semua
http://sif.uin-suska.ac.id
http://fst.uin-suska.ac.id
http://www..uin-suska.ac.id
Comparison between Test-Driven Development and Conventional Development: A Ca...IJERA Editor
In Software Engineering, different techniques and approaches are being used nowadays to produce reliable
software. The software quality relies heavily on the software testing. However, not all developers are concerned
with the testing stage of a software. This has affected the software quality and has increased the cost as well. To
avoid these issues, researchers paid a lot of effort on finding the best technique that guarantee the software
quality. In this paper we aim to explore the effectiveness of building test cases using Test-Driven Development
(TDD) technique compared with the conventional technique (Test-last). The comparison measures the
effectiveness of test cases with regard to number of defects, code coverage and test cases development duration
between TDD and Test-Last. The results has been analyzes and presented to support the best technique. On an
average, the effectiveness of test cases with regards to the selected quality factors in Test-Driven Development
(TDD) was better than the conventional technique (Test-last). TDD and conventional testing had nearly the
same percentage as result in code coverage. Moreover, the number of defects found and the test cases
development duration spent in TDD are high compared with Test-Last. The results led to suggest some
contributions and achievement that could be gained from applying TDD technique in software industry. As
using TDD as development technique in young companies can produce high quality software in less time.
Software Cost Estimation Using Clustering and Ranking SchemeEditor IJMTER
Software cost estimation is an important task in the software design and development process.
Planning and budgeting tasks are carried out with reference to the software cost values. A variety of
software properties are used in the cost estimation process. Hardware, products, technology and
methodology factors are used in the cost estimation process. The software cost estimation quality is
measured with reference to the accuracy levels.
Software cost estimation is carried out using three types of techniques. They are regression based
model, anology based model and machine learning model. Each model has a set of technique for the
software cost estimation process. 11 cost estimation techniques fewer than 3 different categories are
used in the system. The Attribute Relational File Format (ARFF) is used maintain the software product
property values. The ARFF file is used as the main input for the system.
The proposed system is designed to perform the clustering and ranking of software cost
estimation methods. Non overlapped clustering technique is enhanced with optimal centroid estimation
mechanism. The system improves the clustering and ranking process accuracy. The system produces
efficient ranking results on software cost estimation methods.
International Journal of Soft Computing and Engineering (IJShildredzr1di
International Journal of Soft Computing and Engineering (IJSCE)
ISSN: 2231-2307, Volume-2, Issue-3, July 2012
251
Abstract— In recent years, software testing is becoming more
popular and important in the software development industry.
Indeed, software testing is a broad term encircling a variety of
activities along the development cycle and beyond, aimed at
different goals. Hence, software testing research faces a collection
of challenges. A consistent roadmap of most relevant challenges is
proposed here. In it, the starting point is constituted by some
important past achievements, while the destination consists of two
major identified goals to which research ultimately leads, but
which remains as reachable as goals. The routes from the
achievements to the goals are paved by outstanding research
challenges, which are discussed in the paper along with the
ongoing work.
Software testing is as old as the hills in the history of digital
computers. The testing of software is an important means of
assessing the software to determine its quality. Since testing
typically consumes 40~50% of development efforts, and consumes
more effort for systems that require higher levels of reliability, it is
a significant part of the software engineering
Software testing is a very broad area, which involves many
other technical and non-technical areas, such as specification,
design and implementation, maintenance, process and
management issues in software engineering. Our study focuses on
the state of the art in testing techniques, as well as the latest
techniques which representing the future direction of this area.
Today, testing is the most challenging and dominating activity
used by industry, therefore, improvement in its effectiveness, both
with respect to the time and resources, is taken as a major factor
by many researchers
The purpose of testing can be quality assurance, verification,
and validation or reliability estimation. It is a tradeoff between
budget, time and quality. Software Quality is the central concern
of software engineering. Testing is the single most widely used
approach to ensuring software quality.
(Keywords: SDLC, Software quality, Testing techniq
Technique .)
I. INTRODUCTION
I. Introduction: Software Testing
Software testing is the process of executing a program or
system with the intent of finding errors. Software is not unlike
other physical processes where inputs are received and
outputs are produced. Where software differs is in the manner
in which it fails. Most physical systems fail in a fixed (and
reasonably small) set of ways. By contrast, software can fail in
Manuscript received: on July, 2012
Maneela Tuteja, Department of Information TechnologyDronacharya
College of Engineering, Gurgaon, Haryana,.
Gaurav Dubey, Amity School of Computer Sciences, Amity University,
Uttar Pradesh,India.,
.
many bizarre ways. Detec ...
A novel defect detection method for software requirements inspections IJECEIAES
The requirements form the basis for all software products. Apparently, the requirements are imprecisely stated when scattered between development teams. Therefore, software applications released with some bugs, missing functionalities, or loosely implemented requirements. In literature, a limited number of related works have been developed as a tool for software requirements inspections. This paper presents a methodology to verify that the system design fulfilled all functional requirements. The proposed approach contains three phases: requirements collection, facts collection, and matching algorithm. The feedback results provided enable analysist and developer to make a decision about the initial application release while taking on consideration missing requirements or over-designed requirements.
A Complexity Based Regression Test Selection StrategyCSEIJJournal
Software is unequivocally the foremost and indispensable entity in this technologically driven world.
Therefore quality assurance, and in particular, software testing is a crucial step in the software
development cycle. This paper presents an effective test selection strategy that uses a Spectrum of
Complexity Metrics (SCM). Our aim in this paper is to increase the efficiency of the testing process by
significantly reducing the number of test cases without having a significant drop in test effectiveness. The
strategy makes use of a comprehensive taxonomy of complexity metrics based on the product level (class,
method, statement) and its characteristics.We use a series of experiments based on three applications with
a significant number of mutants to demonstrate the effectiveness of our selection strategy.For further
evaluation, we compareour approach to boundary value analysis. The results show the capability of our
approach to detect mutants as well as the seeded errors.
Introduction to Investigation And Utilizing Lean Test Metrics In Agile Softwa...IJERA Editor
The growth of the software development industry approaches the new development methodologies to deliver the
error free software to its end-user fulfilling the business values to product. The growth of tools and technology
has brought the automation in the development and software testing process, it has also increased the demand of
the fast testing and delivery of the software to end customers. Traditional software development methodologies
to trending agile software development trend have brought new philosophy, dimensions, and processes having
invested new tools to make process easy. The Agile development (Scrum, XP, FDD, BDD, ATDD, ASD,
DSDM, Kanban, Crystal and Lean) process also faces the software testing model crises because of the fast
development of life cycles, fast delivery to end users without having appropriate test metrics which make the
software testing process slow as well as increase the risk. The analysis of the testing metrics in the software
testing process and setting the right lean test metrics help to improve the software quality effectively in agile
process.
Software testing is an activity which is aimed for evaluating quality of a program and also for improving it, by identifying defects and problems. Software testing strives for achieving its goal (both implicit and explicit) but it has certain limitations, still testing can be done more effectively if certain established principles are to be followed. In spite of having limitations, software testing continues to dominate other verification techniques like static analysis, model checking and proofs. So it is indispensable to understand the goals, principles and limitations of software testing so that the effectiveness of software testing could be maximized.
The result of applying a new testing model for improving the quality of softw...amiraiti
This paper shows the result of applying a new testing model which provides the know-how for performing the different activities covered in the test process for functional testing. It was noticed that the customer risks experienced during examining the accuracy of software used in different business sectors are not the main focus of the Quality Control team members. Moreover there are no standard testing techniques used by the team members during creating the test conditions and test cases, the result is a lot of reworks.
Testing throughout the software life cycleRudy Setiawan
This document discusses software testing within different software development life cycles. It describes the V-model life cycle and iterative life cycles like agile development. The V-model uses four test levels: component testing, integration testing, system testing, and acceptance testing. Each test level has specific objectives. The document also discusses characteristics of good testing within any life cycle model, including corresponding testing for each development activity. It defines the objectives of component testing, integration testing, system testing, and acceptance testing.
Testing throughout the software life cycleRudy Setiawan
This document discusses software testing within different software development life cycles. It describes the V-model life cycle and iterative life cycles like agile development. The V-model uses four test levels: component testing, integration testing, system testing, and acceptance testing. Each test level has specific objectives. The document also discusses characteristics of good testing within any life cycle model, including corresponding testing for each development activity. It defines the objectives of component testing, integration testing, system testing, and acceptance testing.
Similar to Comparative Analysis of Model Based Testing and Formal Based Testing - A Review (20)
A SYSTEMATIC RISK ASSESSMENT APPROACH FOR SECURING THE SMART IRRIGATION SYSTEMSIJNSA Journal
The smart irrigation system represents an innovative approach to optimize water usage in agricultural and landscaping practices. The integration of cutting-edge technologies, including sensors, actuators, and data analysis, empowers this system to provide accurate monitoring and control of irrigation processes by leveraging real-time environmental conditions. The main objective of a smart irrigation system is to optimize water efficiency, minimize expenses, and foster the adoption of sustainable water management methods. This paper conducts a systematic risk assessment by exploring the key components/assets and their functionalities in the smart irrigation system. The crucial role of sensors in gathering data on soil moisture, weather patterns, and plant well-being is emphasized in this system. These sensors enable intelligent decision-making in irrigation scheduling and water distribution, leading to enhanced water efficiency and sustainable water management practices. Actuators enable automated control of irrigation devices, ensuring precise and targeted water delivery to plants. Additionally, the paper addresses the potential threat and vulnerabilities associated with smart irrigation systems. It discusses limitations of the system, such as power constraints and computational capabilities, and calculates the potential security risks. The paper suggests possible risk treatment methods for effective secure system operation. In conclusion, the paper emphasizes the significant benefits of implementing smart irrigation systems, including improved water conservation, increased crop yield, and reduced environmental impact. Additionally, based on the security analysis conducted, the paper recommends the implementation of countermeasures and security approaches to address vulnerabilities and ensure the integrity and reliability of the system. By incorporating these measures, smart irrigation technology can revolutionize water management practices in agriculture, promoting sustainability, resource efficiency, and safeguarding against potential security threats.
Optimizing Gradle Builds - Gradle DPE Tour Berlin 2024Sinan KOZAK
Sinan from the Delivery Hero mobile infrastructure engineering team shares a deep dive into performance acceleration with Gradle build cache optimizations. Sinan shares their journey into solving complex build-cache problems that affect Gradle builds. By understanding the challenges and solutions found in our journey, we aim to demonstrate the possibilities for faster builds. The case study reveals how overlapping outputs and cache misconfigurations led to significant increases in build times, especially as the project scaled up with numerous modules using Paparazzi tests. The journey from diagnosing to defeating cache issues offers invaluable lessons on maintaining cache integrity without sacrificing functionality.
Using recycled concrete aggregates (RCA) for pavements is crucial to achieving sustainability. Implementing RCA for new pavement can minimize carbon footprint, conserve natural resources, reduce harmful emissions, and lower life cycle costs. Compared to natural aggregate (NA), RCA pavement has fewer comprehensive studies and sustainability assessments.
Literature Review Basics and Understanding Reference Management.pptxDr Ramhari Poudyal
Three-day training on academic research focuses on analytical tools at United Technical College, supported by the University Grant Commission, Nepal. 24-26 May 2024
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODELgerogepatton
As digital technology becomes more deeply embedded in power systems, protecting the communication
networks of Smart Grids (SG) has emerged as a critical concern. Distributed Network Protocol 3 (DNP3)
represents a multi-tiered application layer protocol extensively utilized in Supervisory Control and Data
Acquisition (SCADA)-based smart grids to facilitate real-time data gathering and control functionalities.
Robust Intrusion Detection Systems (IDS) are necessary for early threat detection and mitigation because
of the interconnection of these networks, which makes them vulnerable to a variety of cyberattacks. To
solve this issue, this paper develops a hybrid Deep Learning (DL) model specifically designed for intrusion
detection in smart grids. The proposed approach is a combination of the Convolutional Neural Network
(CNN) and the Long-Short-Term Memory algorithms (LSTM). We employed a recent intrusion detection
dataset (DNP3), which focuses on unauthorized commands and Denial of Service (DoS) cyberattacks, to
train and test our model. The results of our experiments show that our CNN-LSTM method is much better
at finding smart grid intrusions than other deep learning algorithms used for classification. In addition,
our proposed approach improves accuracy, precision, recall, and F1 score, achieving a high detection
accuracy rate of 99.50%.
CHINA’S GEO-ECONOMIC OUTREACH IN CENTRAL ASIAN COUNTRIES AND FUTURE PROSPECTjpsjournal1
The rivalry between prominent international actors for dominance over Central Asia's hydrocarbon
reserves and the ancient silk trade route, along with China's diplomatic endeavours in the area, has been
referred to as the "New Great Game." This research centres on the power struggle, considering
geopolitical, geostrategic, and geoeconomic variables. Topics including trade, political hegemony, oil
politics, and conventional and nontraditional security are all explored and explained by the researcher.
Using Mackinder's Heartland, Spykman Rimland, and Hegemonic Stability theories, examines China's role
in Central Asia. This study adheres to the empirical epistemological method and has taken care of
objectivity. This study analyze primary and secondary research documents critically to elaborate role of
china’s geo economic outreach in central Asian countries and its future prospect. China is thriving in trade,
pipeline politics, and winning states, according to this study, thanks to important instruments like the
Shanghai Cooperation Organisation and the Belt and Road Economic Initiative. According to this study,
China is seeing significant success in commerce, pipeline politics, and gaining influence on other
governments. This success may be attributed to the effective utilisation of key tools such as the Shanghai
Cooperation Organisation and the Belt and Road Economic Initiative.
Batteries -Introduction – Types of Batteries – discharging and charging of battery - characteristics of battery –battery rating- various tests on battery- – Primary battery: silver button cell- Secondary battery :Ni-Cd battery-modern battery: lithium ion battery-maintenance of batteries-choices of batteries for electric vehicle applications.
Fuel Cells: Introduction- importance and classification of fuel cells - description, principle, components, applications of fuel cells: H2-O2 fuel cell, alkaline fuel cell, molten carbonate fuel cell and direct methanol fuel cells.
Embedded machine learning-based road conditions and driving behavior monitoringIJECEIAES
Car accident rates have increased in recent years, resulting in losses in human lives, properties, and other financial costs. An embedded machine learning-based system is developed to address this critical issue. The system can monitor road conditions, detect driving patterns, and identify aggressive driving behaviors. The system is based on neural networks trained on a comprehensive dataset of driving events, driving styles, and road conditions. The system effectively detects potential risks and helps mitigate the frequency and impact of accidents. The primary goal is to ensure the safety of drivers and vehicles. Collecting data involved gathering information on three key road events: normal street and normal drive, speed bumps, circular yellow speed bumps, and three aggressive driving actions: sudden start, sudden stop, and sudden entry. The gathered data is processed and analyzed using a machine learning system designed for limited power and memory devices. The developed system resulted in 91.9% accuracy, 93.6% precision, and 92% recall. The achieved inference time on an Arduino Nano 33 BLE Sense with a 32-bit CPU running at 64 MHz is 34 ms and requires 2.6 kB peak RAM and 139.9 kB program flash memory, making it suitable for resource-constrained embedded systems.
Harnessing WebAssembly for Real-time Stateless Streaming PipelinesChristina Lin
Traditionally, dealing with real-time data pipelines has involved significant overhead, even for straightforward tasks like data transformation or masking. However, in this talk, we’ll venture into the dynamic realm of WebAssembly (WASM) and discover how it can revolutionize the creation of stateless streaming pipelines within a Kafka (Redpanda) broker. These pipelines are adept at managing low-latency, high-data-volume scenarios.
Comparative Analysis of Model Based Testing and Formal Based Testing - A Review
1. Vatsal Mishra et al.. Int. Journal of Engineering Research and Applications www.ijera.com
ISSN: 2248-9622, Vol. 6, Issue 4, (Part - 7) April 2016, pp.49-58
www.ijera.com 49|P a g e
Comparative Analysis of Model Based Testing and Formal Based
Testing - A Review
Vatsal Mishra*, Shashank Shekhar*, Shashank Shankar* Manjula R**
* (B.Tech Computer Science and Engineering, VIT University, Vellore)
** (Associate Professor School of Computer Science and Engineering, VIT University, Vellore)
ABSTRACT
Software testing is one of the most important steps in the process of Software Development. Testing provides
the glimpse of the proper functioning of the system under different conditions. It makes it a necessary step to
choose the best testing method for the software system to be successful and accepted by a large number of
people as the market is really competitive these days and only error free systems can survive for a longer period
of time. This paper gives the comparative analysis of two major methods of testing : Formal Specifications
Based Software Testing and Model Based Software Testing, which are used widely in the process of software
development process. It brings out how these two methods of testing can provide reliability to software system
including the major uses, advantages, and disadvantages of both the testing methods. It briefly gives the detailed
comparative analysis of these two methods of software testing. It also brings out the situations where formal
specifications based testing is more effective and efficient while model based testing being effective in others.
This comparative analysis will help one in deciding on a better testing technique, depending upon the situation,
and requirements of software, for the software to be successful in long run.
Keywords : Model Based Testing, Formal based Testing, Specification Based Testing, Software Testing.
I. INTRODUCTION
Software defects days are not limited to only
coding error but the errors can happen in different
ways [5], thus comes software testing which is an
integral element of software development which
should be done in a systematic approach [1].
Software testing is a component of software
engineering which used for evaluating the
functionalities of the system to find out whether the
system is in line with functional requirements
given. It can also be termed as investigation to
check for different errors in the system and
appraise the stakeholders with all the dimensions of
the system implementation i.e. it tells the user
about various utilities as well as potential risks of
the system which was put to the test [3].
The history of software testing dates back to 1979
when Genford J Meyers initially introduced the
separation of debugging from the process of
testing[14]Further in the year 1988 Dave Gelperin
and William C. Hetzel did the classification of
software testing into goals and phases.[16-21]
In software testing we check the software by
implementing it and then marking it on various
parameters which indicates the quality of the
system being tested. Testing is not a single activity
but is a collection of activities and can be termed as
a process .The properties to evaluate depends upon
the type of system being tested, on what parameters
the client’s desire and the audience on target.
Testing can have static or dynamic in nature. In
static testing the fault finding is done without
execution of the code and in dynamic testing the
fault finding is done while the code is executed.
The verification process has static nature whereas
validation process has dynamic nature.
As we all know testing and verification is one of
the most important step in making a software, it
constitutes around 30-40% of effort and time of the
developer .There are many ways of testing the
software like white box testing, black box testing,
specification base testing ,model based testing,
visual testing, grey box testing etc[2].
Both Model Based testing and formal specification
based testing comes under black box testing.Black-
box testing is a method of software testing that
examines the functionality of an application
without peering into its internal structures or
workings. This method of test can be applied to
virtually every level of software testing: unit,
integration, system and acceptance [13].
Here the paper concentrates on two major testing
models which are the model based testing and the
formal or specification based testing. These two
models are extensively used in various commercial
and educational fields these days. These models
work towards single motive to evaluate the
software but the methodology adapted by both of
them is different. The comparative analysis shows
how they differ from each other in various aspects
and variations in their functionality and utility.
RESEARCH ARTICLE OPEN ACCESS
2. Vatsal Mishra et al.. Int. Journal of Engineering Research and Applications www.ijera.com
ISSN: 2248-9622, Vol. 6, Issue 4, (Part - 7) April 2016, pp.49-58
www.ijera.com 50|P a g e
II. RELATED WORK
In Dalal, Siddhartha R., et al. [16] the report on
various practices of development of tools and
various methodologies related to model based
testing. Some case studies have been shown which
provides details and results of application of
combination of test-generation methods on a large
scale to diverse applications. Based on these, an
insight has been given into what is practiced and
what are the obstacles in transferring these
technology to testing organizations Lyu, M.R [1]
offers a view of the development, testing, and
evaluation schemes for software reliability, and its
integration to form a unified and consistent
paradigm . Specifically, techniques and tools for
the three software reliability engineering phases
which are modeling and analysis, design and
implementation, testing and measurement have
been elucidated by the author. The book
Practical model-based testing: a tools
approach [4] gives an insight to model-based
testing in a practical manner, shows the way to
write models for testing purposes and usage of
model-based testing tools to generate test suites. It
aims at testers and software developers who wish
to use model-based testing, rather than at tool-
developers or academics used in specification
based testing. In Fujiwara, S.et al. [7] methods for
the selection of appropriate test case, an important
issue line with testing of protocol implementations
as well as software engineering, is shown. Several
issues that have an impact on the selection of a
suitable test suite including the consideration of
interaction measures, several test architectures for
protocol testing and the fact that many
specifications do not satisfy the assumptions made
by most test selection method grounds have been
shown. These papers are closely related to each
other and give an insight of evolution of model
based testing since its inception.
Hans-Martin Horcher explained a way to get more
benefits from formal specifications apart from
specification phase, in verifying the
implementation against the specifications. He
explained the use of specification in order to derive
input test data and to evaluate the test results. This
approach is described using the specification
language Z which provides a greater degree of
automation, improving the quality of testing
process [26]. Charles proposed a formal semantics
for the production of test cases from requirements
giving a syntactical characterization of the method,
which is described over the LTL formulae. He
showed various examples to prove the application
of the approach [29]. Mirza Mahmood Baig
described about an important problem in software
testing i.e. time complexity. He has decreased the
time complexity related with the software testing
with the help of Grover’s Search Algorithm [34].
Mona Batrapresented a comprehensive analysis of
formal methods including their goals, advantages,
and limitations. Her research work aimed to
help the software engineers in order to identify
the uses of formal methods at various level of
software development, and had a good reference of
the requirements phase[37].
Andersson and Runeson et al. [42] presented a
qualitative survey of the verification and validation
processes in 11 Swedish companies by exchanging
experience between the companies. They
concluded that in large companies, the documented
process is emphasized while in small companies,
key individuals have a dominating impact on the
procedures. Commercial tools are used in large
companies while small companies make in-house
tools or use shareware. Despite the differences in
approach verification and validation is important in
all industries. Gotel and Finkelstein [44]
investigated and discussed the underlying nature of
requirements traceability problem. They introduced
the distinction between pre-requirements
specification (pre-RS) traceability and post-
requirements specification (post-RS) traceability
and explained how the majority of the problems are
due to poor requirements traceability are due to
inadequate pre-RS traceability and show the
fundamental need for improvements.
Malaiyamodeled the relation among testing effort,
coverage and reliability, and present a logarithmic
model that relates testing effort to test coverage
(block, branch, e-use or p-use). The results are
consistent with the known inclusion relationships
among block, branch and p-use coverage measures
and eliminates variables like test application
strategy from consideration.
III. Model Based Testing
Model based testing is a software application
which is used for testing a system or a software in
which test cases (called as models) are generated in
whole or in part from a model that describes
functional aspects of the system under test (SUT)
which represents testing strategies and testing
environment. [4] the models are used to generate
tests which can be deployed both online as well as
offline. Model based testing can also be called as
Model Driven Testing.
The basic idea in model based testing is generation
of models which can be transition system, UML
State Machines, finite state machines, class
diagrams along with constraints, etc.[7-12]from
which complete test cases which is input and
3. Vatsal Mishra et al.. Int. Journal of Engineering Research and Applications www.ijera.com
ISSN: 2248-9622, Vol. 6, Issue 4, (Part - 7) April 2016, pp.49-58
www.ijera.com 51|P a g e
believed output pairs that can be generated. It
supports investigation, construction, and prediction
of the modeled system.
In online testing the model and the considered
system for test are connected and the tests happen
dynamically whereas in offline testing the test
cases/suites are generated which can be later be
tested with the system using a tool.
A model which describes the system or software
under the testing process can be taken as its partial
or abstract behavior towards the system. Hence the
test cases which are taken out from a model can be
said as functional tests on the similar platform of
abstraction as the model. These test cases are
collectively known as an abstract test suite.
The following diagram shows a simplified
workflow for MBT. [6]
Figure 1. Workflow of Model Based Testing
The process followed in model based testing:
1) The creation of model can be done in
several ways. [7-12] The model is created based on
the requirements, specifications or use cases which
are provided. The model goes through various
feedbacks from the user before being developed as
a formal final model. The implementation is done
based on the model.
2) After the model is created the test suites
are generated. These test suites can be derived in
various manners because the testing is
experimental and it is based on heuristics these test
suites contain test sequences and test oracle.
3) The role of test sequences is to control the
system under test, which makes it go into the
different conditions under which it can be tested
whether the system has followed the model on
which it was developed or not . The test oracle
checks the growth of the system in terms of its
implementation and delivers a pass or fail verdict
based on its conformation with the model.
4) The verdict is the final conclusion of the
testing process and it provides details about all the
artifacts. A failure indicates that the behavior of the
system under test does not go in line with the
model predictions. This generally means errors or
faults in the implementation process, but
sometimes it can also mean that a there is a flaw in
model creation or design or that the informal
requirements from which it was created were
incorrectly taken.
There are various tools which can be used for
model based testing. Some of them are:
Conformiq designer [22]commercial tool in which
models can be generated as UML State Machines
and in Qtronic Modeling Language (QML). Tests
can be exported to test management tools or
TTCN-3.
Graphwalker which is an open source tool in which
test cases are made from finite state machines and
uses search algorithms to A* or random search
algorithm to cover various states,edges,
requirements.
JSXM[23] which is an academic type software, it is
a model animation and test generator which uses
different types of EFSMs as its input.The generated
tests are then converted into JUnit test cases.
PyModel[24] which uses python as the coding
language which is an open source tool which
supports online as well as on-the-flying testing
methods.It uses compositions for controlling the
scenario. The guidance of the coverage can be done
as programmable strategy.
Spec Explorer [25] which develops the programs
in C# is a commercial tool is a successor of AsmL
test tool which is now integrated with Visual
Studio.
Some applications of model based testing are
arithmetic and table operators, message of parsing
and building, rules based system and user
interfaces .
Although this type of testing requires significantly
more up‐front effort in building themodel, it offers
an upper hand over traditional software testing
methods.
4. Vatsal Mishra et al.. Int. Journal of Engineering Research and Applications www.ijera.com
ISSN: 2248-9622, Vol. 6, Issue 4, (Part - 7) April 2016, pp.49-58
www.ijera.com 52|P a g e
IV. FORMAL SPECIFICATION BASED
TESTING
Formal Specifications based Testing has now
gained much importance in the field of software
development.The objective of Formal
Specifications based Testing is to test the
functionality of software according to the required
specifications. Formal methods of testing usually
include mathematical notations, formal logic and
proofs in some cases used in verifying the
functionalities of software. Formal Specifications
helps greatly in simplifying the process of testing
in software development process.It is one of the
most convenient testing method which helps in
detecting errors and bugs in software functioning.
It is capable of producing not only the test data sets
for testing purpose but also helps in analyzing test
results effectively and efficiently. In fact, this is
one of the major uses of Formal Specifications.
These tests might be functional or non-functional
in nature.
Most of the existing tools and techniques used for
software testing requires testing of a written set of
programs. But the evolution of formal methods of
software testing has given rise to the possibility of
starting from the specifications for introducing
some testing methodsin formal framework. Prolog
is one of the tool used in formal based testing for
test set production.
Formal Specifications based testing can be easily
fit in the software development processes without
having the need to replace traditional methods of
software development as cited in [26]. It is really
effective in case of unit testing in which individual
components are tested independently to ensure that
they operate correctly [32]. The mathematical
notations used in formal methods helps in defining
the required functionalities of the system.
There are many methods of testing based on the
formal specifications of software such as Algebraic
Specifications, Finite State Machines, transition
Systems etc. Algebraic specification is basically
used to specify the software behavior with the help
of methods rose from abstract algebra. Some tools
for developing algebraic specification languages
are LARCH, ASL etc.Some of other formal
specifications languages includeOBJ, LOTOS,
ASM, LARCH, Communicating Sequential
Processes (CSP) etc [35].
ASM (Abstract state machine) is a state machine
which operates on arbitrary data structures known
as states. The ASM Method is a scientific and
practical systems engineering method which
bridges the gap between the two ends of system
development. It uses 3 concepts:
a) ASM: a pseudo-code, which generalize
Finite State Machines
b) Ground model: a form of rigorous
blueprints
c) Refinement: a general scheme for
instantiations of model abstractions to elements of
the concrete system.
OBJ is basically a family of declarative languages
and was created by Joseph Goguen in the year of
1976. It consists of generic modules, abstract data
types, expressions to combine modules etc.
The family of Larch formal specification
languagesaremeant to be used for the accurate
specification of computer systems. They provide
the capability forbetter specification of computer
programs and the derivation of proofs regarding the
behavior of the program. Larch family has a
language called LSL (Larch Shared Language)
for algebraic specification of abstract data types.
Communicating Sequential Processes (CSP) is a
type of formal specification language and helps in
description of various patterns of interaction in
concurrent system. It belongs to the family of
mathematics known as process algebras, and is
based on message passing through channels.
LOTOS (Language of Temporal Ordering
Specification) is a formal specification language
which is basically based on temporal ordering of
events as the name suggests. LOTOS is mostly
used for specifying protocols in OSI Standard. It is
an algebraic specification language that has two
parts: a part for the data description and operations,
and a part for concurrent processes description,
which is based on process calculi.
The Z notation is one of the most
popular formal specification languagethat is used
for description and modelling of the computer
systems. It mostly targets the specification
of computer programs and computer-based systems
in general. Z consists of a standard catalogue which
is atoolkit of commonly used mathematical
predicates and mathematical functions.
Apart from this formal based methods are useful in
reduction of time complexity which is one of the
major issue in software development. It can be
done using Grover’s Algorithm as cited in [34].
These methods of testing is are also capable of
determining the causes of software failure during
testing processes. Test sets and the related
hypotheses can be generated easily using Horn
Clauses [31].
5. Vatsal Mishra et al.. Int. Journal of Engineering Research and Applications www.ijera.com
ISSN: 2248-9622, Vol. 6, Issue 4, (Part - 7) April 2016, pp.49-58
www.ijera.com 53|P a g e
V. COMPARATIVE ANALYSIS
5.1 Definitions used
5.1.1 Statement coverage (Block coverage)
In software testing, testers are required to generate
test cases to execute every statement at least once
[38]. A test case serves as an input to the program
under test, and is executed during testing.
Statement coverage is defined as the fraction of
total number of blocks or statements that are
executed by test data [38, 39].
5.1.2 Branch coverage (Decision coverage)
Branch coverage is defined as the fraction of total
number of decisions or branches that are executed
by test data [25, 39]. It also helps to ensure that no
branch results to abnormal behaviour of application
and validating all possible branches in the program
[45].
5.1.3 Path coverage
In path coverage, test case is executed at least once
i.e. all the execution paths of theprogram from
entry to exit are executed during testing [40, 41].
5.1.4 Requirement Traceability
Requirement traceability is the ability to describe
and follow a requirementin both forward and
backward direction [42], by defining and
maintainingrelationships to related development
artefacts [43] such as code, configuration files
andtest cases. Testing is a significant component in
the software development lifecycle.Having many
test cases leads to increase in effort and cost spent
on testing, thus many industrial developers, testers
and managers give a lot of importance to
traceability [44, 41]. There are some tools support
to maintain, retrieve and record trace information
manually [46]. However, this is time consuming,
labour- intensive and error-prone [47, 44]. It is
more convenient and important to create, maintain
and find the links of traceability in testing through
an automated process as requirement traceability
links are outdated when a software evolves.
e.g.: Calculation of statement coverage, branch
coverage and path coverage for the following code
snippet.
Read P
Read Q
IF P + Q > 100 THEN
Print "Large"
ENDIF
IF P > 50 THEN
Print " P Large"
ENDIF
Figure 2.Flowchart for code snippet
Statement Coverage
To calculate statement coverage, find out the
shortest number of paths following which all the
nodes will be covered. Here by traversing through
path 1A-2C-3D-E-4G-5H all the nodes are
covered. So by travelling through only one path all
the nodes 12345 are covered, so statement
coverage in this case is 1.
Branch Coverage
To calculate Branch Coverage, find out the
minimum number of paths which will ensure
covering of all the edges. In this case there is no
single path which will ensure coverage of all the
edges at one go. By following paths 1A-2C-3D-E-
4G-5H, maximum numbers of edges (A, C, D, E, G
and H) are covered but edges B and F are left. To
covers these edges we can follow 1A-2B-E-4F. By
combining the above two paths we can ensure of
travelling through all the paths. The aim is to cover
all possible true/false decisions.Hence, branch
coverage is 2.
Path Coverage
Path Coverage ensures covering of all the paths
from start to end. All possible paths are
1A-2B-E-4F
1A-2B-E-4G-5H
1A-2C-3D-E-4G-5H
1A-2C-3D-E-4F
So, path coverage is 4.
5.2 Comparison of Model Based Testing with
Formal Based Testing
We have used Lickert Scale (1-5) to show the
average rating of Formal based testing (FBT) and
Model based testing (MBT) approach while
considering some aspects of software testing [48].
6. Vatsal Mishra et al.. Int. Journal of Engineering Research and Applications www.ijera.com
ISSN: 2248-9622, Vol. 6, Issue 4, (Part - 7) April 2016, pp.49-58
www.ijera.com 54|P a g e
5.2.1 Test Coverage
MBT Score: 5
FBT Score: 4
Test coverage is a strength of both MBT and FBT.
The coverage usually depends on the experience of
the tester who is writing the test. In companies,
generally the test cases are written by experienced
testers, if not, the test cases are approved by
experienced testers. Also, in MBT, the test
coverage is higher than FBT because the test cases
are generated by considering the test coverage.
FBT has fairly high test coverage (i.e. branch, path
and statement coverage) but MBT has more
coverage because of its zero - tolerance towards the
test coverage.
5.2.2 Requirement Traceability
MBT Score: 2
FBT Score: 4
There are several ways to make the requirements
traceable through the test cases using formal
specifications. Different applications are used in
order to link the test cases to the software
requirements. There can be a separate column in
the test case which indicates that a test case
belongs to a specific requirement.
In MBT, the traceability is done in a different way.
Requirement traceability is a challenge in MBT
and industries usually find it difficult to track the
results back to the system requirements in the MBT
approach. Recently, some major studies [1, 2 ,10]
have been done in order to find out a better way to
make requirements more traceable in MBT
process.
5.2.3 Understandability of Test cases
MBT Score: 4
FBT Score: 3
The understandability of the test cases depends on
the experience of the tester who is writing the test
cases. It is a major challenge of FBT because every
tester writes the test cases according to his own
knowledge of the system and business.
In MBT, the automated test cases are not fully
understandable by humans. It depends on which
tool you are using. For example, ConformiqQtronic
and Microsoft’s Spec Explorer adds reasonable
details on the test cases, so thathumans can
understand what are the details and what is to be
tested.
5.2.4 Cost and Time
MBT Score: 5
FBT Score: 3
Cost and time are one the most important attributes
of any approach. It cannot be analyzed which is
more costly FBT or MBT. It depends on different
scenarios, the application to be tested, method of
testing and conditions of testing. In the total cost of
a project, there is around 50-70% cost for quality
assurance and if any defect arises in the release, the
cost is increased even more. MBT is known for
decreasing the overall testing cost and it takes less
time as compared to traditional software testing
approaches.
5.2.5 Test Design and Planning
MBT Score: 4
FBT Score: 2
Test design and planning depends on the system
requirements. Understanding the requirements is
one of the most important tasks before test design
and planning. If the test plans and designs are made
without fully understanding the system
requirements, there is a high chance that re-work
will be required.
Figure 3.Comparative Analysis Scores
7. Vatsal Mishra et al.. Int. Journal of Engineering Research and Applications www.ijera.com
ISSN: 2248-9622, Vol. 6, Issue 4, (Part - 7) April 2016, pp.49-58
www.ijera.com 55|P a g e
5.3 Discussion and Inference
Figure 4.Cross plot graph for Test Coverage
and Test Case detail
Figure 5.Cross plot graph for Requirement
Traceability, Time and Cost
The rating of the two approaches on constructs
helped in generating the results of our findings.
FBT has high coverage but the test cases are
not much detailed. MBT has higher test
coverage and more detailed test cases if
compared to the FBT approach. The coverage
depends on the extent of testing and
understanding of requirements. Thus, the
coverage depends on the quality of the test
cases, which depends on the quality of the
system requirements.MBT has comparatively
low requirement traceability as compared to
FBT. But at the same time, MBT is more cost
and time efficient.
Advantages of model based testing includes
less cost in project maintenance and
requirement specification frequency. Further
there is fluidity in the designing aspect i.e. in
case of addition of a feature, a new finite state
machine can be added without disturbing the
existing machine model. Which means simple
change can automatically ripple through the
entire suite of test cases and through this
higher level of automation is achieved. Hence
more importance is given to the design rather
than coding. This testing model has vast
coverage which means exhaustive testing is
possible.
However there are some difficulties which are
faced in model based testing. First, it requires
extensive formal specification to build the
model and test it. Further the test cases are
highly dependent on the model on which is
structured upon.
In formal specification based testing has many
advantages which makes it really powerful
testing technique. The main advantage of
formal testing methods is that it greatly reduces
the amount of time and effort used during later
stages of testing by efforts used in earlier
stages of system construction. It helps in
removal of inconsistencies in the process of
software development and also provides
validation to every step in software
development [26]. It also provides support in
Model Based Testing.
Another major advantage as mentioned above
include the production of best test cases or test
data sets and test result analysis which helps in
detecting very minute errors during testing
process. It is based on mathematical notation
and proofs which makes it a really reliable
technique for software testing in comparison to
other techniques of software testing. It
provides the accuracy measure of the functions
of software and at the same time is cheaper
method to implement. Abstraction is another
advantage in formal specifications method.
Apart from these, formal based methods of
software testing also has some limitations.
Formal Specifications Based Testing
techniques are quite complex for integration
testing which include system testing and sub-
system testing but can be applied. This is
because these techniques do not describe the
architecture and interrelationships between the
operations of the system. Apart from this it
does not take into account the informal
measures and hence may not produce
completely correct results in complex
situations [35]. There are some advancements
need to be done for making formal
specification based testing a more effective
tool. These can include ambiguity resolution
technique, combination of two or more
mathematical models etc. in order to get even
better results.
8. Vatsal Mishra et al.. Int. Journal of Engineering Research and Applications www.ijera.com
ISSN: 2248-9622, Vol. 6, Issue 4, (Part - 7) April 2016, pp.49-58
www.ijera.com 56|P a g e
VI. CONCLUSION
In this research paper we have compared two black
testing techniques: formal based testing and model
based testing. Model based testing generates test
cases in the form of models and tests are done in
conformance with it while in formal based testing,
specific methods are applied to test the software.
On the basis of our findings we conclude that
formal based testing is better in terms of
requirement traceability but model based testing is
more feasible in terms of cost and time of project
maintenance. Formal based testing supports and
enhances the features model based testing to a great
extent .The combined model is termed as Formal
Model Specification based Testing which combines
the characteristics of both the models and works
more efficiently.
VII. ACKNOWLEDGEMENT
We would like to acknowledge the immense
support of our Professor Dr Manjula R without
whom it was not possible to write the paper. Her
guidance formed the base of the paper and her
expertise comments greatly enhanced the
manuscript. We would also like thank our
university (VIT University, Vellore) which has
always encouraged the students to go in the field of
research and develop an interest towards
exploration and innovation.
REFERENCES
[1] Lyu, M.R. 1998. An integrated approach to
achieving high software reliability.
Aerospace Conference, 1998. Proceedings. ,
IEEE (1998), 123 – 136.
[2] Patton, Ron. Software Testing. , International
Standard Book Number: 0-672-31983-7,
2001
[3] Kaner, Cem (November 17, 2006).
"Exploratory Testing" (PDF). Florida
Institute of Technology, QualityAssurance
Institute Worldwide Annual Software
Testing Conference, Orlando, FL.
[4] Utting, Mark, and Bruno Legeard. Practical
model-based testing: a tools approach.
Morgan Kaufmann, 2010.
[5] Infamous Error Case Studies,Patton, Ron.
Software Testing. , International Standard
Book Number: 0-672-31983-7, 2001,pg10-
13
[6] https://msdn.microsoft.com/en-
us/library/ee620399.aspx
[7] Fujiwara, S., Bochmann, G., Khendek, F.,
Amalou, M., and Ghedamsi, A., “Test
Selection Basedon Finite State Models”,
IEEE Transactions on Software Engineering,
Vol. 17, No. 6., June 1991.
[8] Chow, T. S., “Testing Software Design
Modeled by Finite-State Machines,” IEEE
Transactions on Software Engineering, Vol.
SE-4, No. 3, May 1978.
[9] Holzmann, G., Design and Validation of
Computer Protocols, AT&T Bell
Laboratories,Prentice Hall, 1991.
[10] Musa, J.D., “Operational profiles in software
reliability engineering,” IEEE Software,
10(2), pp14-32.
[11] Apfelbaum, L., “Automated Functional Test
Generation”, Proceedings of the
Autotestcon’95 Conference, IEEE, 1995.
[12] Savage, P., Walters, S, and Stephenson, M.,
“Automated Test Methodology for
Operational Flight Programs”, Proceedings
of the 1997 IEEE Aerospace Conference,
1997.
[13] Black Box Testing,Patton, Ron. Software
Testing. , International Standard Book
Number: 0-672-31983-7, 2001,pg55
[14] Myers, Glenford J. (1979). The Art of
Software Testing. John Wiley and Sons.
ISBN 0411043281.
[15] Gelperin, D.; B. Hetzel (1988). "The Growth
of Software Testing". CACM 31 (6): 687–
695.doi:10.1140/62959.62965. ISSN
00010782.
[16] Dalal, Siddhartha R., et al. "Model-based
testing in practice." Proceedings of the 21st
international conference on Software
engineering. ACM, 1999.
[17] Until 1956 it was the debugging oriented
period, when testing was often associated to
9. Vatsal Mishra et al.. Int. Journal of Engineering Research and Applications www.ijera.com
ISSN: 2248-9622, Vol. 6, Issue 4, (Part - 7) April 2016, pp.49-58
www.ijera.com 57|P a g e
debugging: there was no clear difference
between testing and debugging. Gelperin,
D.;B. Hetzel(1988). "The Growth of
Software Testing". CACM 31 (6). ISSN
00010782.
[18] From 1957–1978 there was the
demonstration oriented period where
debugging and testing was distinguished
now – in this period it was shown, that
software satisfies the requirements.
Gelperin, D.; B.Hetzel (1988). "The Growth
of Software Testing". CACM 31 (6).
ISSN 00010782.
[19] The time between 1979–1982 is announced
as the destruction oriented period, where
the goal was to find errors. Gelperin,
D.; B. Hetzel (1988). "The Growth of
Software Testing". CACM 31 (6). ISSN
00010782.
[20] 1983–1987 is classified as the evaluation
oriented period: intention here is that during
the software lifecycle a product evaluation is
provided and measuring quality. Gelperin,
D.; B. Hetzel(1988). "The Growth of
Software Testing". CACM 31 (6). ISSN
00010782.
[21] From 1988 on it was seen as prevention
oriented period where tests were to
demonstrate that software satisfies its
specification, to detect faults and to prevent
faults. Gelperin, D.; B. Hetzel (1988). "The
Growth of Software Testing". CACM 31
(6).ISSN 00010782.
[22] A. Huima (2007) "Implementing Conformiq
Qtronic," Testing of Software and
Communicating Systems, Springer, pp. 1-12.
DOI: 10.1007/978-3-540-73066-8_1
[23] D. Dranidis, K. Bratanis and F. Ipate (2012)
"JSXM: a tool for automated test
generation". In Proc. of SEFM'12. DOI:
10.1007/978-3-642-33826-7_25
[24] J. Jacky (2011), "PyModel: Model-based
testing in Python", Proc. of the 9th Python in
Science Conf. (SCIPY 2011) link.
[25] M. Veanes et al. (2008) "Model-Based
Testing of Object-Oriented Reactive
Systems with Spec Explorer," Formal
Methods and Testing,Springer, pp. 39-76.
DOI: 10.1007/978-3-540- 789178_2
[26] Hans-Martin Horcher and Jan Peleska,
”Using formal specifications to support
software testing”, Springer, 1995
[27] YoonsikCheon and Myoung Kim, “A
Specification-Based Fitness Function for
EvolutionaryTesting of Object-Oriented
Programs”, ACM, 2006
[28] D. RICHARD KUHN, “Fault Classes and
Error Detection Capability of Specification-
Based Testing”, ACM, 1999
[29] Charles Pecheur, Franco Raimondi and
Guillaume Brat, “A Formal Analysis of
Requirements-Based Testing”, ACM, 2009
[30] James A. Whittaker and J. H. Poore,
“Statistical Testing for Clean room Software
Engineering”, IEEE, 1992
[31] Gilles Bernot, Marie Claude Gaudel and
Bruno Marre, “Software testing based on
formal specifications :a theory and a tool”,
Software Engineering Journal, 1991
[32] Weikai Miao and Shaoying Lin, “A Formal
Specification – Based Integration Testing
Approach”, Springer, 2013
[33] Marie-Claude Gaudel, “Software Testing
Based on Formal Specification”,
Springer,2010
[34] Mirza Mahmood Baig and Dr.Ansar Ahmad
Khan, “A Formal Technique for Reducing
Software Testing Time Complexity”,
Springer, 2010
[35] Mona Batra, Amit Malik, and Dr.Meenu
Dave, “Formal Methods : Benefits,
Challenges and Future Direction”, Journal of
Global Research in Computer Science,
2013, Volume 4, No.5
[36] Pressman Roger S: “Software Engineering”-
A Practitioner’s Approach”, McGraw Hill,
5th edition. 2000.
[37] Mona Batra, S.K Pandey: Formal methods in
requirement engineering. International
Journal of Computer Applications , pp- 7-14,
Volume 70–No.13
[38] Malaiya, Y.K.; Naixin Li; Bieman, J.;
Karcich, R.; Skibbe, B.; , "The relationship
betweentest coverage and reliability,"
Software Reliability Engineering, 1994.
Proceedings., 5th
International Symposium
on , vol., no., pp.186-195, 6-9 Nov 1994
[39] Hong Zhu, Patrick A. V. Hall, and John H.
R. May. 1997. Software unit test coverage
and adequacy. ACM Comput. Surv. 29, 4
(December 1997), 366-427
[40] Wood, M., Roper, M., Brooks, A and Miller,
J. 1997. Comparing and combining
software defect detection techniques : a
replicated empirical study. Software
Engineering— ESEC/FSE’97. (1997),
262–277
[41] http://ajoysingha.info/Documents/Branch%2
0Statement%20Path%20Coverage.pdf
[42] Andersson, C. and Runeson, P.
2002.Verification and validation in industry-
a q ualitativesurvey on the state of
practice. Empirical Software Engineering,
10. Vatsal Mishra et al.. Int. Journal of Engineering Research and Applications www.ijera.com
ISSN: 2248-9622, Vol. 6, Issue 4, (Part - 7) April 2016, pp.49-58
www.ijera.com 58|P a g e
2002. Proceedings. 2002International
Symposium n (2002), 37–41.
[43] Andrea De Lucia, FaustoFasano, Rocco
Oliveto, and GenoveffaTortora. 2007.
Recovering traceability links in software
artifact management systems using
information retrievalmethods. ACM Trans.
Softw. Eng. Methodol. 16, 4, Article 13
(September 2007).
DOI=10.1140/1276933.1276934
http://doi.acm.org/10.1140/1276933.127693
4
[44] Gotel, O.C.Z. and Finkelstein, C. 1994. An
analysis of the requirements traceability
problem. Requirements Engineering, 1994.,
Proceedings of the First International
Conference on (1994), 94–101.
[45] Tamai, T. and Kamata, M.I. 2009. Impact of
Requirements Quality on Project Success or
Failure. Design Requirements Engineering:
A Ten-Year Perspective. (2009), 258–275.
[46] “Doors,” http://www-
01.ibm.com/software/awdtools/doors/
[47] Brinkkemper, S. 2004. Requirements
engineering research the industry is and is
not waitingfor. 10th Anniversary Int.
Workshop on Requirements Engineering:
Foundation forSoftware Quality. Riga Latvia
(2004), 41–54.
[48] Agruss, C. and Johnson, B. 2000. Ad Hoc
Software Testing: A perspective on
exploration and improvisation. Florida
Institute of Technology (2000).