Conference Paper

A Tool Suite for Diagnosis and Testing of Software Design Specifications.

Telcordia Technol., Morristown, NJ
DOI: 10.1109/ICDSN.2000.857553 Conference: 2000 International Conference on Dependable Systems and Networks (DSN 2000) (formerly FTCS-30 and DCCA-8), 25-28 June 2000, New York, NY, USA
Source: DBLP

ABSTRACT Available statistical data shows that the cost of finding and
repairing software rises dramatically in later development stages. Much
research has been done using verification and validation techniques to
prove correctness in terms of certain properties. Such approaches and
the approach of software testing are complementary. Testing reveals some
errors that cannot be easily identified through verification, and vice
versa. The new technology of generating implementation code from design
specifications if based on highly reliable designs is another approach
to reliable software. This paper presents a dynamic slicing technology
and an accompanying tool suite for understanding, diagnosis and testing
of software design specifications. We apply state-of-the-art technology
in coverage testing, diagnosis and understanding of software source code
to those of software designs. We use a simulation of the specifications
to collect the execution trace for computing the coverage and slicing
data. Our technology first generates a flow diagram from a specification
and then automatically analyses the coverage features of the diagram. It
collects the corresponding flow data during simulation to be mapped to
the flow diagram. The coverage information for the original
specification is then obtained from the coverage information of the flow
diagram. This technology has been used for C, C++, and Java, and has
proven effective

0 Bookmarks
 · 
54 Views
  • [Show abstract] [Hide abstract]
    ABSTRACT: The previous published paper on the topic of CodeCover highlights the strengths of CodeCover and discusses the versatility of the tool for various coverage testing needs. In this paper we are highlighting a portion of work done as part of a study project. This paper talks about the minimal efforts needed to tweak the product for specific needs. The existing, well structured code base of CodeCover can be reused as a library for implementing the work to be carried out. The impact to the lower layer of the product is minimal and at times nil for implementing the intended task because of the well laid design. In this paper we talk about how the CodeCover can be used to prioritize the test cases for uncovered branches of the code under test for a given session of testing.
    ACM SIGSOFT Software Engineering Notes 02/2014; 39(1):1-4.
  • [Show abstract] [Hide abstract]
    ABSTRACT: Design flaws of fault tolerance techniques may lead to undesired consequences in particular fault cases under very special operating conditions. Such rare "fault tolerance holes" may be very difficult to reveal. This paper presents a novel approach directing the analysis towards potential weaknesses in a fault tolerance technique. A new algorithm based on special heuristics performs partial reachability analysis of SDL models describing fault-tolerant communication. It aims at finding violations of fault tolerance properties in an efficient way. The approach does not require knowledge of the model under investigation. The new algorithm is evaluated by experiments with realistic protocols - including a large model of an industrial system - and compared to the performance of known solutions.
    Dependable Systems and Networks, 2005. DSN 2005. Proceedings. International Conference on; 01/2005
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Software metrics can provide an automated way for software practitioners to assess the quality of their software. The earlier in the software development lifecycle this information is available, the more valuable it is, since changes are much more expensive to make later in the lifecycle.Semantic metrics, introduced by Etzkorn and Delugach, assess software according to the meaning of the software's functionality in its domain. This is in contrast to traditional metrics, which use syntax measures to assess code. Because semantic metrics do not rely on the syntax or structure of code, they can be computed from requirements or design specifications before the system has been implemented. This paper focuses on using semantic metrics to assess systems that have not yet been implemented.
    Proceedings of the 42nd Annual Southeast Regional Conference, 2004, Huntsville, Alabama, USA, April 2-3, 2004; 01/2004