2002INCOSE International SymposiumRequires access

1.6.2 Formalizing a Structured Natural Language Requirements Specification Notation

Kendra Cooper, M.R. Ito

Open publisher page 9 citations

Abstract

Abstract Requirements specification notations are developed by organizations in order to meet their specific needs. For example, the Threads‐Capabilities notation, an in house notation at Raytheon Systems Canada, Ltd., has been developed and used for specifying their complex, large scale, air traffic control systems. It is a semi‐formal, structured, natural language notation. In this work, we investigate how to make this semi‐formal notation more rigorous (i.e., formal) by developing and applying a new formalization process to it. By doing this, we can obtain the advantages of formal methods (precise, unambiguous, automatic generation of test specifications, automated typechecking, etc.) while retaining the style and readability of the original notation. We call the formalized notation the Stimulus Response Requirements Specification (SRRS) notation. Our results have been successful for the specific notation. The formalized notation has been demonstrated to reduce the time and improve the quality of the requirements specifications. There is additional training time, however, needed to learn to use the notation and tools.

About this research paper

What this paper is about

Abstract Requirements specification notations are developed by organizations in order to meet their specific needs. For example, the Threads‐Capabilities notation, an in house notation at Raytheon Systems Canada, Ltd., has been developed and used for specifying their complex, large scale, air traffic control systems. It is a semi‐formal, structured, natural language notation. In this work, we investigate how to make this semi‐formal notation more rigorous (i.e., formal) by developing and applying a new formalization process to it. By doing this, we can obtain the advantages of formal methods (precise, unambiguous, automatic generation of test specifications, automated typechecking, etc.) while retaining the style and readability of the original notation. We call the formalized notation the Stimulus Response Requirements Specification (SRRS) notation. Our results have been successful for the specific notation. The formalized notation has been demonstrated to reduce the time and improve the quality of the requirements specifications. There is additional training time, however, needed to learn to use the notation and tools.

Why it matters

OpenAlex reports 9 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

Abstract Requirements specification notations are developed by organizations in order to meet their specific needs. For example, the Threads‐Capabilities notation, an in house notation at Raytheon Systems Canada, Ltd., has been developed and used for specifying their complex, large scale, air traffic control systems. It is a semi‐formal, structured, natural language notation. In this work, we investigate how to make this semi‐formal notation more rigorous (i.e., formal) by developing and applying a new formalization process to it. By doing this, we can obtain the advantages of formal methods (precise, unambiguous, automatic generation of test specifications, automated typechecking, etc.) while retaining the style and readability of the original notation. We call the formalized notation the Stimulus Response Requirements Specification (SRRS) notation. Our results have been successful for the specific notation. The formalized notation has been demonstrated to reduce the time and improve the quality of the requirements specifications. There is additional training time, however, needed to learn to use the notation and tools.

Key concepts: Notation, Computer science, Programming language, B-Method, Formal specification, Formal methods, Readability, Software engineering

Related papers

Back to paper searchBrowse research topicsOriginal source
1.6.2 Formalizing a Structured Natural Language Requirements Specification Notation — Research Paper | ScholarLens