2013Unpublished venueRequires access

Knowledge-Guided Methodology for Specification Analysis

Bhanu Pratap Singh, Arunprasath Shankar, Yuriy Shiyanovskii, Francis Wolff, C. Papachristou, Daniel Weyer, Steve Clay, Jim Morrison

Open publisher page 2 citations

Abstract

The number of Soft-IP vendors and designsbecoming available on the global market is growing at aphenomenal rate. The current practice of evaluating Soft IPsusing their specification is a time consuming manual process. A specification document is primarily written in English, which serves as a common language for internal product development teams as well as customers. Designers have a preference for writing specifications in an informal natural language using text and notations, including diagrams, charts and tables. The lack of formality of specification documents is a limiting factor intheir analysis. The current state-of-the-art in hardware design lacks any specification analysis technique. In this paper, we present a knowledge-guided methodology for specification analysis that can automatically analyze specification documents. Our approach avoids formal specification. Instead we rely on domain-based ontologies to capture design behavior. We tested our approach by analyzing floating point specification from several third party IP vendors. We define spec coverage and requirement coverage metrics to quantify our results.

About this research paper

What this paper is about

The number of Soft-IP vendors and designsbecoming available on the global market is growing at aphenomenal rate. The current practice of evaluating Soft IPsusing their specification is a time consuming manual process. A specification document is primarily written in English, which serves as a common language for internal product development teams as well as customers. Designers have a preference for writing specifications in an informal natural language using text and notations, including diagrams, charts and tables. The lack of formality of specification documents is a limiting factor intheir analysis. The current state-of-the-art in hardware design lacks any specification analysis technique. In this paper, we present a knowledge-guided methodology for specification analysis that can automatically analyze specification documents. Our approach avoids formal specification. Instead we rely on domain-based ontologies to capture design behavior. We tested our approach by analyzing floating point specification from several third party IP vendors. We define spec coverage and requirement coverage metrics to quantify our results.

Why it matters

OpenAlex reports 2 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

The number of Soft-IP vendors and designsbecoming available on the global market is growing at aphenomenal rate. The current practice of evaluating Soft IPsusing their specification is a time consuming manual process. A specification document is primarily written in English, which serves as a common language for internal product development teams as well as customers. Designers have a preference for writing specifications in an informal natural language using text and notations, including diagrams, charts and tables. The lack of formality of specification documents is a limiting factor intheir analysis. The current state-of-the-art in hardware design lacks any specification analysis technique. In this paper, we present a knowledge-guided methodology for specification analysis that can automatically analyze specification documents. Our approach avoids formal specification. Instead we rely on domain-based ontologies to capture design behavior. We tested our approach by analyzing floating point specification from several third party IP vendors. We define spec coverage and requirement coverage metrics to quantify our results.

Key concepts: Computer science, Formality, Formal specification, Specification language, Language Of Temporal Ordering Specification, Programming language specification, Software requirements specification, Programming language

Related papers

Back to paper searchBrowse research topicsOriginal source
Knowledge-Guided Methodology for Specification Analysis — Research Paper | ScholarLens