Loading…

Testing the completeness of specifications

A system is described that tests for the completeness of axiomatic specifications of abstract data types. For testing, the system generates a set of test cases and an implementation of the data type from the specifications. The generated implementation is such that if the specifications are not comp...

Full description

Saved in:
Bibliographic Details
Published in:IEEE transactions on software engineering 1989-05, Vol.15 (5), p.526-531
Main Author: Jalote, P.
Format: Article
Language:English
Subjects:
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
cited_by cdi_FETCH-LOGICAL-c363t-cf7027292ca6f36f548d7583d3e1d3b5a8ae9ab111334cf5c87aa4bf1b76a4583
cites cdi_FETCH-LOGICAL-c363t-cf7027292ca6f36f548d7583d3e1d3b5a8ae9ab111334cf5c87aa4bf1b76a4583
container_end_page 531
container_issue 5
container_start_page 526
container_title IEEE transactions on software engineering
container_volume 15
creator Jalote, P.
description A system is described that tests for the completeness of axiomatic specifications of abstract data types. For testing, the system generates a set of test cases and an implementation of the data type from the specifications. The generated implementation is such that if the specifications are not complete, the implementation is not complete, and the behavior of all of the sequences of valid operations on the data type is not defined. This implementation is tested with the generated test cases to detect the incompleteness of specifications. The system is implemented on a VAX system running Unix.< >
doi_str_mv 10.1109/32.24701
format article
fullrecord <record><control><sourceid>proquest_ieee_</sourceid><recordid>TN_cdi_proquest_miscellaneous_25532536</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>24701</ieee_id><sourcerecordid>28241307</sourcerecordid><originalsourceid>FETCH-LOGICAL-c363t-cf7027292ca6f36f548d7583d3e1d3b5a8ae9ab111334cf5c87aa4bf1b76a4583</originalsourceid><addsrcrecordid>eNqF0M1LwzAYBvAgCs4pePVWRESEziRv0yRHGX7BwMs8hzR7o5GurU138L83s2MHL55yeH88PHkIOWd0xhjVd8BnvJCUHZAJ06BzEJwekgmlWuVCKH1MTmL8pJQKKcWE3C4xDqF5z4YPzFy77mocsMEYs9ZnsUMXfHB2CG0TT8mRt3XEs907JW-PD8v5c754fXqZ3y9yByUMufOScsk1d7b0UHpRqJUUClaAbAWVsMqithVjDKBwXjglrS0qzypZ2iLBKbkec7u-_dqkemYdosO6tg22m2i44gUDKv-HQgAXqdSUXP6Bn-2mb9InDNNpFCoLSOhmRK5vY-zRm64Pa9t_G0bNdloD3PxOm-jVLs9GZ2vf28aFuPeSKwnltt_FyAIi7q9jxA9kyn3e</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>195580743</pqid></control><display><type>article</type><title>Testing the completeness of specifications</title><source>ABI/INFORM Global (ProQuest)</source><source>IEEE Xplore (Online service)</source><creator>Jalote, P.</creator><creatorcontrib>Jalote, P.</creatorcontrib><description>A system is described that tests for the completeness of axiomatic specifications of abstract data types. For testing, the system generates a set of test cases and an implementation of the data type from the specifications. The generated implementation is such that if the specifications are not complete, the implementation is not complete, and the behavior of all of the sequences of valid operations on the data type is not defined. This implementation is tested with the generated test cases to detect the incompleteness of specifications. The system is implemented on a VAX system running Unix.&lt; &gt;</description><identifier>ISSN: 0098-5589</identifier><identifier>EISSN: 1939-3520</identifier><identifier>DOI: 10.1109/32.24701</identifier><identifier>CODEN: IESEDJ</identifier><language>eng</language><publisher>New York, NY: IEEE</publisher><subject>Applied sciences ; Boolean ; Computer science ; Computer science; control theory; systems ; Costs ; Exact sciences and technology ; Formal specifications ; Implementations ; Language ; Semantics ; Software ; Software engineering ; Software testing ; System testing ; Testing ; Variables</subject><ispartof>IEEE transactions on software engineering, 1989-05, Vol.15 (5), p.526-531</ispartof><rights>1989 INIST-CNRS</rights><rights>Copyright Institute of Electrical and Electronics Engineers, Inc. (IEEE) May 1989</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c363t-cf7027292ca6f36f548d7583d3e1d3b5a8ae9ab111334cf5c87aa4bf1b76a4583</citedby><cites>FETCH-LOGICAL-c363t-cf7027292ca6f36f548d7583d3e1d3b5a8ae9ab111334cf5c87aa4bf1b76a4583</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://www.proquest.com/docview/195580743?pq-origsite=primo$$EHTML$$P50$$Gproquest$$H</linktohtml><link.rule.ids>314,780,784,11688,27924,27925,36060,36061,44363,54796</link.rule.ids><backlink>$$Uhttp://pascal-francis.inist.fr/vibad/index.php?action=getRecordDetail&amp;idt=7287367$$DView record in Pascal Francis$$Hfree_for_read</backlink></links><search><creatorcontrib>Jalote, P.</creatorcontrib><title>Testing the completeness of specifications</title><title>IEEE transactions on software engineering</title><addtitle>TSE</addtitle><description>A system is described that tests for the completeness of axiomatic specifications of abstract data types. For testing, the system generates a set of test cases and an implementation of the data type from the specifications. The generated implementation is such that if the specifications are not complete, the implementation is not complete, and the behavior of all of the sequences of valid operations on the data type is not defined. This implementation is tested with the generated test cases to detect the incompleteness of specifications. The system is implemented on a VAX system running Unix.&lt; &gt;</description><subject>Applied sciences</subject><subject>Boolean</subject><subject>Computer science</subject><subject>Computer science; control theory; systems</subject><subject>Costs</subject><subject>Exact sciences and technology</subject><subject>Formal specifications</subject><subject>Implementations</subject><subject>Language</subject><subject>Semantics</subject><subject>Software</subject><subject>Software engineering</subject><subject>Software testing</subject><subject>System testing</subject><subject>Testing</subject><subject>Variables</subject><issn>0098-5589</issn><issn>1939-3520</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>1989</creationdate><recordtype>article</recordtype><sourceid>M0C</sourceid><recordid>eNqF0M1LwzAYBvAgCs4pePVWRESEziRv0yRHGX7BwMs8hzR7o5GurU138L83s2MHL55yeH88PHkIOWd0xhjVd8BnvJCUHZAJ06BzEJwekgmlWuVCKH1MTmL8pJQKKcWE3C4xDqF5z4YPzFy77mocsMEYs9ZnsUMXfHB2CG0TT8mRt3XEs907JW-PD8v5c754fXqZ3y9yByUMufOScsk1d7b0UHpRqJUUClaAbAWVsMqithVjDKBwXjglrS0qzypZ2iLBKbkec7u-_dqkemYdosO6tg22m2i44gUDKv-HQgAXqdSUXP6Bn-2mb9InDNNpFCoLSOhmRK5vY-zRm64Pa9t_G0bNdloD3PxOm-jVLs9GZ2vf28aFuPeSKwnltt_FyAIi7q9jxA9kyn3e</recordid><startdate>19890501</startdate><enddate>19890501</enddate><creator>Jalote, P.</creator><general>IEEE</general><general>Institute of Electrical and Electronics Engineers</general><general>IEEE Computer Society</general><scope>IQODW</scope><scope>AAYXX</scope><scope>CITATION</scope><scope>3V.</scope><scope>7WY</scope><scope>7WZ</scope><scope>7X7</scope><scope>7XB</scope><scope>87Z</scope><scope>88E</scope><scope>88F</scope><scope>88I</scope><scope>88K</scope><scope>8AL</scope><scope>8FE</scope><scope>8FG</scope><scope>8FI</scope><scope>8FJ</scope><scope>8FK</scope><scope>8FL</scope><scope>8G5</scope><scope>ABJCF</scope><scope>ABUWG</scope><scope>AFKRA</scope><scope>ARAPS</scope><scope>AZQEC</scope><scope>BENPR</scope><scope>BEZIV</scope><scope>BGLVJ</scope><scope>CCPQU</scope><scope>DWQXO</scope><scope>FRNLG</scope><scope>FYUFA</scope><scope>F~G</scope><scope>GHDGH</scope><scope>GNUQQ</scope><scope>GUQSH</scope><scope>HCIFZ</scope><scope>JQ2</scope><scope>K60</scope><scope>K6~</scope><scope>K7-</scope><scope>K9.</scope><scope>L.-</scope><scope>L6V</scope><scope>M0C</scope><scope>M0N</scope><scope>M0S</scope><scope>M1P</scope><scope>M1Q</scope><scope>M2O</scope><scope>M2P</scope><scope>M2T</scope><scope>M7S</scope><scope>MBDVC</scope><scope>P5Z</scope><scope>P62</scope><scope>PQBIZ</scope><scope>PQBZA</scope><scope>PQEST</scope><scope>PQQKQ</scope><scope>PQUKI</scope><scope>PRINS</scope><scope>PTHSS</scope><scope>Q9U</scope><scope>7SC</scope><scope>8FD</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope></search><sort><creationdate>19890501</creationdate><title>Testing the completeness of specifications</title><author>Jalote, P.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c363t-cf7027292ca6f36f548d7583d3e1d3b5a8ae9ab111334cf5c87aa4bf1b76a4583</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>1989</creationdate><topic>Applied sciences</topic><topic>Boolean</topic><topic>Computer science</topic><topic>Computer science; control theory; systems</topic><topic>Costs</topic><topic>Exact sciences and technology</topic><topic>Formal specifications</topic><topic>Implementations</topic><topic>Language</topic><topic>Semantics</topic><topic>Software</topic><topic>Software engineering</topic><topic>Software testing</topic><topic>System testing</topic><topic>Testing</topic><topic>Variables</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Jalote, P.</creatorcontrib><collection>Pascal-Francis</collection><collection>CrossRef</collection><collection>ProQuest Central (Corporate)</collection><collection>ABI/INFORM Collection</collection><collection>ABI/INFORM Global (PDF only)</collection><collection>Health &amp; Medical Collection</collection><collection>ProQuest Central (purchase pre-March 2016)</collection><collection>ABI/INFORM Collection</collection><collection>Medical Database (Alumni Edition)</collection><collection>Military Database (Alumni Edition)</collection><collection>Science Database (Alumni Edition)</collection><collection>Telecommunications (Alumni Edition)</collection><collection>Computing Database (Alumni Edition)</collection><collection>ProQuest SciTech Collection</collection><collection>ProQuest Technology Collection</collection><collection>Hospital Premium Collection</collection><collection>Hospital Premium Collection (Alumni Edition)</collection><collection>ProQuest Central (Alumni) (purchase pre-March 2016)</collection><collection>ABI/INFORM Collection (Alumni Edition)</collection><collection>Research Library (Alumni Edition)</collection><collection>Materials Science &amp; Engineering Collection</collection><collection>ProQuest Central (Alumni)</collection><collection>ProQuest Central</collection><collection>Advanced Technologies &amp; Aerospace Collection</collection><collection>ProQuest Central Essentials</collection><collection>ProQuest Central</collection><collection>ProQuest Business Premium Collection</collection><collection>Technology Collection</collection><collection>ProQuest One Community College</collection><collection>ProQuest Central</collection><collection>Business Premium Collection (Alumni)</collection><collection>Health Research Premium Collection</collection><collection>ABI/INFORM Global (Corporate)</collection><collection>Health Research Premium Collection (Alumni)</collection><collection>ProQuest Central Student</collection><collection>Research Library Prep</collection><collection>SciTech Premium Collection</collection><collection>ProQuest Computer Science Collection</collection><collection>ProQuest Business Collection (Alumni Edition)</collection><collection>ProQuest Business Collection</collection><collection>Computer science database</collection><collection>ProQuest Health &amp; Medical Complete (Alumni)</collection><collection>ABI/INFORM Professional Advanced</collection><collection>ProQuest Engineering Collection</collection><collection>ABI/INFORM Global (ProQuest)</collection><collection>Computing Database</collection><collection>Health &amp; Medical Collection (Alumni Edition)</collection><collection>Medical Database</collection><collection>Military Database</collection><collection>ProQuest research library</collection><collection>Science Database</collection><collection>Telecommunications Database</collection><collection>Engineering Database</collection><collection>Research Library (Corporate)</collection><collection>ProQuest advanced technologies &amp; aerospace journals</collection><collection>ProQuest Advanced Technologies &amp; Aerospace Collection</collection><collection>ProQuest One Business</collection><collection>ProQuest One Business (Alumni)</collection><collection>ProQuest One Academic Eastern Edition (DO NOT USE)</collection><collection>ProQuest One Academic</collection><collection>ProQuest One Academic UKI Edition</collection><collection>ProQuest Central China</collection><collection>Engineering collection</collection><collection>ProQuest Central Basic</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts – Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><jtitle>IEEE transactions on software engineering</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Jalote, P.</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Testing the completeness of specifications</atitle><jtitle>IEEE transactions on software engineering</jtitle><stitle>TSE</stitle><date>1989-05-01</date><risdate>1989</risdate><volume>15</volume><issue>5</issue><spage>526</spage><epage>531</epage><pages>526-531</pages><issn>0098-5589</issn><eissn>1939-3520</eissn><coden>IESEDJ</coden><abstract>A system is described that tests for the completeness of axiomatic specifications of abstract data types. For testing, the system generates a set of test cases and an implementation of the data type from the specifications. The generated implementation is such that if the specifications are not complete, the implementation is not complete, and the behavior of all of the sequences of valid operations on the data type is not defined. This implementation is tested with the generated test cases to detect the incompleteness of specifications. The system is implemented on a VAX system running Unix.&lt; &gt;</abstract><cop>New York, NY</cop><pub>IEEE</pub><doi>10.1109/32.24701</doi><tpages>6</tpages></addata></record>
fulltext fulltext
identifier ISSN: 0098-5589
ispartof IEEE transactions on software engineering, 1989-05, Vol.15 (5), p.526-531
issn 0098-5589
1939-3520
language eng
recordid cdi_proquest_miscellaneous_25532536
source ABI/INFORM Global (ProQuest); IEEE Xplore (Online service)
subjects Applied sciences
Boolean
Computer science
Computer science
control theory
systems
Costs
Exact sciences and technology
Formal specifications
Implementations
Language
Semantics
Software
Software engineering
Software testing
System testing
Testing
Variables
title Testing the completeness of specifications
url http://sfxeu10.hosted.exlibrisgroup.com/loughborough?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-27T12%3A35%3A10IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_ieee_&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Testing%20the%20completeness%20of%20specifications&rft.jtitle=IEEE%20transactions%20on%20software%20engineering&rft.au=Jalote,%20P.&rft.date=1989-05-01&rft.volume=15&rft.issue=5&rft.spage=526&rft.epage=531&rft.pages=526-531&rft.issn=0098-5589&rft.eissn=1939-3520&rft.coden=IESEDJ&rft_id=info:doi/10.1109/32.24701&rft_dat=%3Cproquest_ieee_%3E28241307%3C/proquest_ieee_%3E%3Cgrp_id%3Ecdi_FETCH-LOGICAL-c363t-cf7027292ca6f36f548d7583d3e1d3b5a8ae9ab111334cf5c87aa4bf1b76a4583%3C/grp_id%3E%3Coa%3E%3C/oa%3E%3Curl%3E%3C/url%3E&rft_id=info:oai/&rft_pqid=195580743&rft_id=info:pmid/&rft_ieee_id=24701&rfr_iscdi=true