Completeness in Software Requirements Specifications for    Process Control Systems
{'Code': '05010500', 'Directorate': {'Abbreviation': 'CSE', 'LongName': 'Direct For Computer & Info Scie & Enginr'}, 'Division': {'Abbreviation': 'CCF', 'LongName': 'Division of Computing and Communication Foundations'}}
{'SignBlockName': 'John D. Gannon', 'PO_EMAI': None, 'PO_PHON': None}
The goal of this work is to provide a rigorous basis for ascertaining           whether or not a given set of software requirements is internally               complete.  This will require determining the types of individual                requirements that are necessary to provide complete functional and              performance specifications along with a formal notation that will allow         the development of rules of inference and closure criteria for derived          requirements.  This problem is important both for economic and safety           reasons.  The high cost and difficulty of correction requirements               specification errors in the later stages of the software development            process implies that great leverage can be obtained by methods that             help to find problems early.  Also, a large number of software-related          accidents can be traced to requirements problems, and incompleteness in         terms of requirements is often a casual factor.  Furthermore, formal            analysis of safe software behavior cannot be guaranteed by testing              alone; analysis of the specified behavior of the system is necessary            and this is not possible if the behavioral specification is incomplete.         Emphasis will be placed on aspects of software requirements                     specification that have not previously been adequately handled                  including timing abstractions, the man/machine interface, and                   robustness.
{'FirstName': 'Nancy', 'LastName': 'Leveson', 'PI_MID_INIT': 'G', 'PI_SUFX_NAME': None, 'PI_FULL_NAME': 'Nancy G Leveson', 'EmailAddress': 'leveson@mit.edu', 'NSF_ID': '000360460', 'StartDate': '02/15/1988', 'EndDate': None, 'RoleCode': 'Principal Investigator'}
{'Name': 'University of California-Irvine', 'CityName': 'IRVINE', 'ZipCode': '926970001', 'PhoneNumber': '9498247295', 'StreetAddress': '160 ALDRICH HALL', 'StreetAddress2': None, 'CountryName': 'United States', 'StateName': 'California', 'StateCode': 'CA', 'CONGRESSDISTRICT': '47', 'CONGRESS_DISTRICT_ORG': 'CA47', 'ORG_UEI_NUM': 'MJC5FCYQTPE6', 'ORG_LGL_BUS_NAME': 'UNIVERSITY OF CALIFORNIA IRVINE', 'ORG_PRNT_UEI_NUM': 'MJC5FCYQTPE6'}
{'Name': None, 'CityName': None, 'StateCode': None, 'ZipCode': None, 'StreetAddress': None, 'CountryCode': None, 'CountryName': None, 'StateName': None, 'CountryFlag': None, 'CONGRESSDISTRICT': None, 'CONGRESS_DISTRICT_PERF': '""'}
{'Code': '288000', 'Text': 'SOFTWARE ENGINEERING AND LANGU'}
{'url': 'https://www.nsf.gov/awardsearch/download?DownloadFileName=1987&All=true', 'xml': '8718001.xml'}