Software verification and validation configuration management system
First Claim
1. An automated method of releasing software which includes multiple routines at least some of which selectively call others of said routines, share public variables and share common statements, said method comprising steps of:
- storing said software in a software file;
generating a release file identifying impact locations where a routine is used by another routine and where public variables and common statements are used; and
operating a programmed digital computer to;
identify actual locations in said software stored in said software file where a routine is used by another routine and where any public variables and common statements are used; and
compare said identified actual locations with said identified impact locations and generate an output indicating any discrepancies therebetween.
1 Assignment
0 Petitions
Accused Products
Abstract
Differences between both the code and documentation of a revised generation of software and a previous generation are compared by a digital computer with the intended revisions stored in a release file. When all discrepancies have been eliminated, and for the original generation of the software, actual impacts in the form of the locations in the program where one routine is called by another and where common statements and public variables are used, are compared with expected impacts stored in the release file. When all actual impacts have been identified, the revised software, or the original version in the case of newly created software, is stored in a library with the code and documentation paired, and with each revision of each unit identified for later retrieval and reconstruction of any software generation. The latest generation of the software is then simultaneously verified, preferably by an automated process in a programmed computer, and validated through testing of the auto-linked program in PROMs inserted in the actual hardware.
-
Citations
13 Claims
-
1. An automated method of releasing software which includes multiple routines at least some of which selectively call others of said routines, share public variables and share common statements, said method comprising steps of:
-
storing said software in a software file; generating a release file identifying impact locations where a routine is used by another routine and where public variables and common statements are used; and operating a programmed digital computer to; identify actual locations in said software stored in said software file where a routine is used by another routine and where any public variables and common statements are used; and compare said identified actual locations with said identified impact locations and generate an output indicating any discrepancies therebetween. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A method of assuring the integrity of software which has been revised comprising:
-
storing a first generation of said software including code and documentation of the code in a software library; generating a software file containing a revised generation of said code and documentation; generating a release file identifying each of the revisions to said first generation of code and documentation included in said revised generation of said code and documentation; and operating a digital computer to; compare the revised generation of said code and documentation in said software file with the first generation of code and documentation in said software library and identify each of the differences therebetween; compare said differences with the revisions contained in said release file; and identify discrepancies therebetween. - View Dependent Claims (10, 11, 12, 13)
-
Specification