Pub Date : 1991-05-20DOI: 10.1109/SESAW.1991.151528
D. Sova
NASA is moving to establish agencywide standards as a result of a number of external and internal influences. This paper addresses the challenges and mechanisms used to establish agencywide NASA software standards. The author examines the standards development, approval, and implementation process from the perspective of NASA's Software Management and Assurance Program (SMAP). The paper concludes with a status of the software policy and standards under development through the sponsorship of the software assurance organization.<>
{"title":"Agency level software standards development at NASA","authors":"D. Sova","doi":"10.1109/SESAW.1991.151528","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151528","url":null,"abstract":"NASA is moving to establish agencywide standards as a result of a number of external and internal influences. This paper addresses the challenges and mechanisms used to establish agencywide NASA software standards. The author examines the standards development, approval, and implementation process from the perspective of NASA's Software Management and Assurance Program (SMAP). The paper concludes with a status of the software policy and standards under development through the sponsorship of the software assurance organization.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115622151","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1991-05-20DOI: 10.1109/SESAW.1991.151536
H. J. Bender, A. Gries
Documentation has been called the lifeline of computer systems. This is especially true for the Mission Operations Division (MOD) at the NASA Goddard Space Flight Center, where the high visibility of spacecraft missions requires quick and accurate resolution of computer problems. To develop documentation to support this environment, the MOD has devised a documentation structure and tailoring scheme that is flexible but not flimsy, ordered but not rigid, and focused without being limited. This paper describes the essential elements of this structure.<>
{"title":"Standards for mission operations documentation","authors":"H. J. Bender, A. Gries","doi":"10.1109/SESAW.1991.151536","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151536","url":null,"abstract":"Documentation has been called the lifeline of computer systems. This is especially true for the Mission Operations Division (MOD) at the NASA Goddard Space Flight Center, where the high visibility of spacecraft missions requires quick and accurate resolution of computer problems. To develop documentation to support this environment, the MOD has devised a documentation structure and tailoring scheme that is flexible but not flimsy, ordered but not rigid, and focused without being limited. This paper describes the essential elements of this structure.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"67 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133126610","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1991-05-20DOI: 10.1109/SESAW.1991.151530
J. Fairclough, C. Mazza
This paper describes the principles on which the ESA software engineering standards are based, the response to their adoption inside and outside the agency, and their evolution. The process of producing standards is considered in some detail, and the usefulness of structured methods for the development of standards is demonstrated.<>
{"title":"Evolution of the ESA software engineering standards","authors":"J. Fairclough, C. Mazza","doi":"10.1109/SESAW.1991.151530","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151530","url":null,"abstract":"This paper describes the principles on which the ESA software engineering standards are based, the response to their adoption inside and outside the agency, and their evolution. The process of producing standards is considered in some detail, and the usefulness of structured methods for the development of standards is demonstrated.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"26 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123561295","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1991-05-20DOI: 10.1109/SESAW.1991.151523
H. Ljungkvist
This paper describes a corporate process in which a set of software engineering standards were produced by and integrated into a multi-national organization. The paper is intended as an input to people who are about to conduct similar activities in other organizations, as well as for the members of the working groups producing and updating international standards. The experiences gained in this standardization project are highlighted. The rationale for using IEEE standards as a starting-point and how these standards influenced the result and contributed to the success of the project are described.<>
{"title":"The process of producing corporate standards","authors":"H. Ljungkvist","doi":"10.1109/SESAW.1991.151523","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151523","url":null,"abstract":"This paper describes a corporate process in which a set of software engineering standards were produced by and integrated into a multi-national organization. The paper is intended as an input to people who are about to conduct similar activities in other organizations, as well as for the members of the working groups producing and updating international standards. The experiences gained in this standardization project are highlighted. The rationale for using IEEE standards as a starting-point and how these standards influenced the result and contributed to the success of the project are described.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"27 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121685895","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1991-05-20DOI: 10.1109/SESAW.1991.151541
C. L. Wright, A. J. Zawilski
This paper describes several standards that deal with aspects of software safety. Four descriptive attributes common to such standards are defined and specific standards are contrasted using these attributes.<>
{"title":"Existing and emerging standards for software safety","authors":"C. L. Wright, A. J. Zawilski","doi":"10.1109/SESAW.1991.151541","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151541","url":null,"abstract":"This paper describes several standards that deal with aspects of software safety. Four descriptive attributes common to such standards are defined and specific standards are contrasted using these attributes.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"25 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115991264","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1991-05-20DOI: 10.1109/SESAW.1991.151540
L. Tripp, W. Struck, B. Pflug
This paper discusses the application of a multiple team inspection in the revision of a software standard which is applied to the procurement of safety-critical systems used on commercial airplanes. The discussion includes material on the background of the standard and its revision, the inspection process, the application of a multiple team approach to inspections and results, lessons learned, and conclusions.<>
{"title":"The application of multiple team inspections on a safety-critical software standard","authors":"L. Tripp, W. Struck, B. Pflug","doi":"10.1109/SESAW.1991.151540","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151540","url":null,"abstract":"This paper discusses the application of a multiple team inspection in the revision of a software standard which is applied to the procurement of safety-critical systems used on commercial airplanes. The discussion includes material on the background of the standard and its revision, the inspection process, the application of a multiple team approach to inspections and results, lessons learned, and conclusions.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117233468","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1991-05-20DOI: 10.1109/SESAW.1991.151525
R. Stevens
Current software standards (rightly) take a reductionist view of the methodology needed for software development. But for developments of large 'software systems', the needs for commonality, or developments of software within the systems lifecycle, current standards may not be enough. Some help towards these problems may be available by abstracting the systems engineering process. ISD has been developing a structured approach to handling systems requirements, and this has revealed many of the problems and incompatibilities between the two disciplines. It also provides some pointers to help complex software developers.<>
{"title":"Software engineering related to systems requirements","authors":"R. Stevens","doi":"10.1109/SESAW.1991.151525","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151525","url":null,"abstract":"Current software standards (rightly) take a reductionist view of the methodology needed for software development. But for developments of large 'software systems', the needs for commonality, or developments of software within the systems lifecycle, current standards may not be enough. Some help towards these problems may be available by abstracting the systems engineering process. ISD has been developing a structured approach to handling systems requirements, and this has revealed many of the problems and incompatibilities between the two disciplines. It also provides some pointers to help complex software developers.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115023247","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1991-05-20DOI: 10.1109/SESAW.1991.151526
P. Katsoulakos, F. Maclennan, R. Shaw
The paper describes the framework of the Lloyd's Register guidelines for dependable computer-based systems (LRGDS). It defines the development approach adopted by the guidelines, the industrial needs that they address and the technical requirements it attempts to satisfy. The LRGDS model focuses on how the management of software development should be handled through the production of appropriate plans. Based on these plans assessment of whether the development process has been carried out properly can be undertaken and fitness for purpose established.<>
{"title":"LR guidelines for the development of dependable computer-based systems","authors":"P. Katsoulakos, F. Maclennan, R. Shaw","doi":"10.1109/SESAW.1991.151526","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151526","url":null,"abstract":"The paper describes the framework of the Lloyd's Register guidelines for dependable computer-based systems (LRGDS). It defines the development approach adopted by the guidelines, the industrial needs that they address and the technical requirements it attempts to satisfy. The LRGDS model focuses on how the management of software development should be handled through the production of appropriate plans. Based on these plans assessment of whether the development process has been carried out properly can be undertaken and fitness for purpose established.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126706529","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1991-05-20DOI: 10.1109/SESAW.1991.151524
R.E. Shanklin
The success of any set of standards depends on the degree of compliance at all technical and management levels. Several problems with standards produced by classical development efforts are discussed and are attributed to the failure to consider the standards user during the generation of standards. The people who use and need standards the most (e.g. programmers using coding standards and designers using PDL standards) should be involved in the generation of those standards. Users want standards to be clear, short, relevant, and easy to reference. An alternative approach to standards development is presented, and that approach is shown to solve some problems with standards compliance.<>
{"title":"Developing standards with and for the user (software engineering)","authors":"R.E. Shanklin","doi":"10.1109/SESAW.1991.151524","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151524","url":null,"abstract":"The success of any set of standards depends on the degree of compliance at all technical and management levels. Several problems with standards produced by classical development efforts are discussed and are attributed to the failure to consider the standards user during the generation of standards. The people who use and need standards the most (e.g. programmers using coding standards and designers using PDL standards) should be involved in the generation of those standards. Users want standards to be clear, short, relevant, and easy to reference. An alternative approach to standards development is presented, and that approach is shown to solve some problems with standards compliance.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133292571","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1991-05-20DOI: 10.1109/SESAW.1991.151550
N. Schneidewind
Describes an IEEE standard which provides a methodology for establishing quality requirements and for identifying, implementing, analyzing and validating software quality metrics.<>
描述了一个IEEE标准，该标准为建立质量需求以及识别、实现、分析和验证软件质量度量提供了一种方法
{"title":"Report on the IEEE standard for a software quality metrics methodology (draft) P1061, with discussion of metrics validation","authors":"N. Schneidewind","doi":"10.1109/SESAW.1991.151550","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151550","url":null,"abstract":"Describes an IEEE standard which provides a methodology for establishing quality requirements and for identifying, implementing, analyzing and validating software quality metrics.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"44 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130850313","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：