Pub Date : 1991-05-20DOI: 10.1109/SESAW.1991.151549
D. Schultz, A. Godin
This paper presents an overview of the effort associated with developing an IEEE standard. It summarizes the history of the project, including the challenges of getting started and some of the major concerns and objectives which had to be addressed as the standard developed and evolved. A technical overview of the standard, and a summary of plans for future related activities, are also included.<>
{"title":"An IEEE software life cycle processes standardization effort","authors":"D. Schultz, A. Godin","doi":"10.1109/SESAW.1991.151549","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151549","url":null,"abstract":"This paper presents an overview of the effort associated with developing an IEEE standard. It summarizes the history of the project, including the challenges of getting started and some of the major concerns and objectives which had to be addressed as the standard developed and evolved. A technical overview of the standard, and a summary of plans for future related activities, are also included.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"4 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":"123672417","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.151534
R. J. Rubey, A. C. Brewer
Many software quality assurance (SQA) standards have been written for both commercial and defense applications. An organization developing software for different application areas and for different customers will be faced with the need to conform to different SQA standards. This paper discusses past and current SQA standards with special emphasis on their similarities and differences. The authors present a generic SQA standard which integrates the existing standards into a comprehensive and consistent framework. A matrix is provided showing the sources for each quality assurance requirement in this generic standard. This generic standard would enable an organization or company to be substantively compliant with the standards used throughout the world.<>
{"title":"Software quality assurance standards-a comparison and an integration","authors":"R. J. Rubey, A. C. Brewer","doi":"10.1109/SESAW.1991.151534","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151534","url":null,"abstract":"Many software quality assurance (SQA) standards have been written for both commercial and defense applications. An organization developing software for different application areas and for different customers will be faced with the need to conform to different SQA standards. This paper discusses past and current SQA standards with special emphasis on their similarities and differences. The authors present a generic SQA standard which integrates the existing standards into a comprehensive and consistent framework. A matrix is provided showing the sources for each quality assurance requirement in this generic standard. This generic standard would enable an organization or company to be substantively compliant with the standards used throughout the world.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"56 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":"116808627","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.151539
J. Sanz
During the last few years, international, national and professional organizations are producing standards and guidelines for safety-critical software with different approaches, scopes and structures. This paper shows relevant efforts in the field. The main concepts and definitions are considered which provide the differences of focus in every application. Military and nuclear industries are the traditional users and producers of these standards, but other sectors, such as technical, medical, transport will also gain.<>
{"title":"Standardization for safety software: current status and perspectives","authors":"J. Sanz","doi":"10.1109/SESAW.1991.151539","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151539","url":null,"abstract":"During the last few years, international, national and professional organizations are producing standards and guidelines for safety-critical software with different approaches, scopes and structures. This paper shows relevant efforts in the field. The main concepts and definitions are considered which provide the differences of focus in every application. Military and nuclear industries are the traditional users and producers of these standards, but other sectors, such as technical, medical, transport will also gain.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"40 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":"124200997","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.151551
R.N. Sulgrove
Developing an IEEE standard is an involved process; it is much more than merely preparing a document for ballot. Many content issues must be addressed before a consensus for the document can be obtained. Many administrative issues must be handled. These are non-trivial tasks, especially since the working group preparing the document is a volunteer group that functions for several years. This paper explores the key issues encountered by the software productivity metrics working group, and proposes ways that other working groups might handle similar issues encountered. Its goal is to alert new standards groups to possible issues. Being able to anticipate a problem may reduce its disruptive impact and help to make things progress more smoothly.<>
{"title":"Key issues in developing a standard (software metrics)","authors":"R.N. Sulgrove","doi":"10.1109/SESAW.1991.151551","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151551","url":null,"abstract":"Developing an IEEE standard is an involved process; it is much more than merely preparing a document for ballot. Many content issues must be addressed before a consensus for the document can be obtained. Many administrative issues must be handled. These are non-trivial tasks, especially since the working group preparing the document is a volunteer group that functions for several years. This paper explores the key issues encountered by the software productivity metrics working group, and proposes ways that other working groups might handle similar issues encountered. Its goal is to alert new standards groups to possible issues. Being able to anticipate a problem may reduce its disruptive impact and help to make things progress more smoothly.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"4 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":"128417879","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.151546
B. Banerjee
This paper demonstrates the techniques used and experiences gained while implementing a new system development process. The objective of the new process was to structure the system development environment to reflect standard software life cycle management methodologies, so that the reliability of the product can be increased while reducing management costs. Although a need to change the software process was felt for a while, the involvement with the development of IEEE software engineering standards provided the additional momentum to initiate the change. Throughout the change process, these standards were used effectively as selling tools to management as well as planning and training guides. The transition was made from the existing software development environment structured around the software features to one structured around the life cycle process and management of changes.<>
{"title":"Implementation of a software configuration environment","authors":"B. Banerjee","doi":"10.1109/SESAW.1991.151546","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151546","url":null,"abstract":"This paper demonstrates the techniques used and experiences gained while implementing a new system development process. The objective of the new process was to structure the system development environment to reflect standard software life cycle management methodologies, so that the reliability of the product can be increased while reducing management costs. Although a need to change the software process was felt for a while, the involvement with the development of IEEE software engineering standards provided the additional momentum to initiate the change. Throughout the change process, these standards were used effectively as selling tools to management as well as planning and training guides. The transition was made from the existing software development environment structured around the software features to one structured around the life cycle process and management of changes.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"10 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":"131930155","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.151545
H. P. Yule, J. Formento
The Uniform Development Environment (UDE) is being investigated as a means of enforcing software engineering standards. For the programmer, it provides an environment containing the tools and utilities necessary for orderly and controlled development and maintenance of code according to requirements (DoD-STD-2167A). In addition, it provides DoD management and developer management the tools needed for all phases of software life cycle management and control, from project planning and management, to code development, configuration management, version control, and change control. This paper reports the status of UDE development and field testing.<>
{"title":"Progress report: automated computer software development standards enforcement","authors":"H. P. Yule, J. Formento","doi":"10.1109/SESAW.1991.151545","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151545","url":null,"abstract":"The Uniform Development Environment (UDE) is being investigated as a means of enforcing software engineering standards. For the programmer, it provides an environment containing the tools and utilities necessary for orderly and controlled development and maintenance of code according to requirements (DoD-STD-2167A). In addition, it provides DoD management and developer management the tools needed for all phases of software life cycle management and control, from project planning and management, to code development, configuration management, version control, and change control. This paper reports the status of UDE development and field testing.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"54 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":"122701837","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.151547
M. Lerner, M. Slovin
Standards provide a model that can be followed to give consistent results for some 'product'. It is not meant to stifle creativity but instead to provide a framework in which creativity can occur. In an environment that has implemented a number of standards for a defined product, methods (processes) and tools can be a benefit by automating much of the mundane tasking required to conform to the standard's rule set. In the area of software maintenance, the draft standard, IEEE P1219, belongs to the 'Standards in the Large' category, since it encompasses many smaller standards. As such it is a good example of the coupling of methods and tools to standards. The tools and methods section of the standard lists those tools that belong to the six steps of the maintenance process as defined in the standard. Defining the standard and its processes helps identify areas in which tools can be used advantageously as well as areas that could benefit from the development of new tools. Examples of new tool opportunities and the development of these tools is described.<>
{"title":"Methods, tools and standards (software engineering)","authors":"M. Lerner, M. Slovin","doi":"10.1109/SESAW.1991.151547","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151547","url":null,"abstract":"Standards provide a model that can be followed to give consistent results for some 'product'. It is not meant to stifle creativity but instead to provide a framework in which creativity can occur. In an environment that has implemented a number of standards for a defined product, methods (processes) and tools can be a benefit by automating much of the mundane tasking required to conform to the standard's rule set. In the area of software maintenance, the draft standard, IEEE P1219, belongs to the 'Standards in the Large' category, since it encompasses many smaller standards. As such it is a good example of the coupling of methods and tools to standards. The tools and methods section of the standard lists those tools that belong to the six steps of the maintenance process as defined in the standard. Defining the standard and its processes helps identify areas in which tools can be used advantageously as well as areas that could benefit from the development of new tools. Examples of new tool opportunities and the development of these tools is described.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"75 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":"116653689","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 : 1900-01-01DOI: 10.1109/SESAW.1991.151529
R. Fujii, C. Guerdat, P. Sullo
The global dominance that US software producers have enjoyed for many years faces many new challenges. The marketplace places increasing emphasis on product interoperability and quality systems. Vendors are being challenged to document compliance with standards which the EC, along with many other countries, have now adopted and enforce. Proprietary systems have provided an inertial 'luxury' which must be overcome. Understanding and satisfying the changing global software market will become crucial to maintaining a significant US market presence. The authors stress that the US software community must increase its awareness of international standards activities, and they advocate strong personal and corporate support for, and involvement in, these important activities.<>
{"title":"International software engineering standards: facing the challenge","authors":"R. Fujii, C. Guerdat, P. Sullo","doi":"10.1109/SESAW.1991.151529","DOIUrl":"https://doi.org/10.1109/SESAW.1991.151529","url":null,"abstract":"The global dominance that US software producers have enjoyed for many years faces many new challenges. The marketplace places increasing emphasis on product interoperability and quality systems. Vendors are being challenged to document compliance with standards which the EC, along with many other countries, have now adopted and enforce. Proprietary systems have provided an inertial 'luxury' which must be overcome. Understanding and satisfying the changing global software market will become crucial to maintaining a significant US market presence. The authors stress that the US software community must increase its awareness of international standards activities, and they advocate strong personal and corporate support for, and involvement in, these important activities.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"137 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132729411","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
扫码关注我们
求助内容：
应助结果提醒方式：