The importance of formal specification in the design of hardware systems
B.A.L. Gwandu, D.J. Creasey
Abstract
B.A.L. Gwandu, D.J. Creasey
Abstract
This paper discusses the rules or guidelines to follow when writing a system specification. These guidelines were derived from an investigation to evaluate how people understand a written specification. The specification can be written at three basic levels: (a) the designer/manufacturer specification, (b) the supplier/retailer specification, (c) the buyer/user specification. The rules relating to the writing of these specifications are discussed.
OpenAlex reports 9 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
This paper discusses the rules or guidelines to follow when writing a system specification. These guidelines were derived from an investigation to evaluate how people understand a written specification. The specification can be written at three basic levels: (a) the designer/manufacturer specification, (b) the supplier/retailer specification, (c) the buyer/user specification. The rules relating to the writing of these specifications are discussed.
Key concepts: Formal specification, System requirements specification, Computer science, Language Of Temporal Ordering Specification, Software requirements specification, Specification language, Functional specification, Specification