TY - GEN
T1 - Automated integrative analysis of state-based requirements
AU - Czerny, Barbara J.
AU - Heimdahl, Mats P.E.
PY - 1998/1/1
Y1 - 1998/1/1
N2 - Statically analyzing requirements specifications to assure that they possess desirable properties is an important activity in any rigorous software development project. The analysis is performed on an abstraction of the original requirements specification. Abstractions in the model may lead to spurious errors in the analysis output. Spurious errors are conditions that are reported as errors, but information abstracted out of the model precludes the reported conditions from being satisfied. A high ratio of spurious errors to true errors in the analysis output makes it difficult, error-prone, and time consuming to find and correct the true errors. We describe an iterative and integrative approach for analyzing state-based requirements that capitalizes on the strengths of a symbolic analysis component and a reasoning component while circumventing their weaknesses. The resulting analysis method is fast enough and automated enough to be used on a day-to-day basis by practicing engineers, and generates analysis reports with a small ratio of spurious errors to true errors.
AB - Statically analyzing requirements specifications to assure that they possess desirable properties is an important activity in any rigorous software development project. The analysis is performed on an abstraction of the original requirements specification. Abstractions in the model may lead to spurious errors in the analysis output. Spurious errors are conditions that are reported as errors, but information abstracted out of the model precludes the reported conditions from being satisfied. A high ratio of spurious errors to true errors in the analysis output makes it difficult, error-prone, and time consuming to find and correct the true errors. We describe an iterative and integrative approach for analyzing state-based requirements that capitalizes on the strengths of a symbolic analysis component and a reasoning component while circumventing their weaknesses. The resulting analysis method is fast enough and automated enough to be used on a day-to-day basis by practicing engineers, and generates analysis reports with a small ratio of spurious errors to true errors.
UR - http://www.scopus.com/inward/record.url?scp=84860017339&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84860017339&partnerID=8YFLogxK
U2 - 10.1109/ASE.1998.732601
DO - 10.1109/ASE.1998.732601
M3 - Conference contribution
AN - SCOPUS:84860017339
T3 - Proceedings - 13th IEEE International Conference on Automated Software Engineering, ASE 1998
SP - 125
EP - 134
BT - Proceedings - 13th IEEE International Conference on Automated Software Engineering, ASE 1998
PB - Institute of Electrical and Electronics Engineers Inc.
T2 - 13th IEEE International Conference on Automated Software Engineering, ASE 1998
Y2 - 13 October 1998 through 16 October 1998
ER -