Pub Date : 1995-08-21DOI: 10.1109/SESS.1995.525954
K. Emam, Dennis R. Goldenson
The SPICE project aims to deliver an international standard for software process assessment by the end of 1996. As part of this project there is an empirical trials phase whose purpose is to ascertain the effectiveness of the prospective SPICE standard. Two of the objectives of the trials phase are: (a) to determine the extent to which SPICE-conformant assessments are repeatable (i.e., reliability), and (b) to determine the extent to which SPICE-conformant assessments are really measuring best software process practices (i.e., validity). This paper introduces the theoretical foundations for evaluating the reliability and validity of measurement, suggests some empirical research methods for investigating them in SPICE, and discusses the constraints and limitations of these methods within the context of the SPICE project.
{"title":"SPICE: an empiricist's perspective","authors":"K. Emam, Dennis R. Goldenson","doi":"10.1109/SESS.1995.525954","DOIUrl":"https://doi.org/10.1109/SESS.1995.525954","url":null,"abstract":"The SPICE project aims to deliver an international standard for software process assessment by the end of 1996. As part of this project there is an empirical trials phase whose purpose is to ascertain the effectiveness of the prospective SPICE standard. Two of the objectives of the trials phase are: (a) to determine the extent to which SPICE-conformant assessments are repeatable (i.e., reliability), and (b) to determine the extent to which SPICE-conformant assessments are really measuring best software process practices (i.e., validity). This paper introduces the theoretical foundations for evaluating the reliability and validity of measurement, suggests some empirical research methods for investigating them in SPICE, and discusses the constraints and limitations of these methods within the context of the SPICE project.","PeriodicalId":178570,"journal":{"name":"Proceedings of Software Engineering Standards Symposium","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128673626","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 : 1995-08-21DOI: 10.1109/SESS.1995.525971
B. Meek
Language independent standards have been subjected to hostile criticism in recent years, which makes it vital that the quality of the work is as high as possible. General principles of language independent standardization are presented, in the form of five rules applicable to all standardization leading to "seven golden rules" for language independent standardization specifically.
{"title":"The seven golden rules for producing language-independent standards","authors":"B. Meek","doi":"10.1109/SESS.1995.525971","DOIUrl":"https://doi.org/10.1109/SESS.1995.525971","url":null,"abstract":"Language independent standards have been subjected to hostile criticism in recent years, which makes it vital that the quality of the work is as high as possible. General principles of language independent standardization are presented, in the form of five rules applicable to all standardization leading to \"seven golden rules\" for language independent standardization specifically.","PeriodicalId":178570,"journal":{"name":"Proceedings of Software Engineering Standards Symposium","volume":"35 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131523759","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 : 1995-08-21DOI: 10.1109/SESS.1995.525961
R.J. Tate
This paper examines the process of assessing software-based systems against the IEC 880 (1986) standard "Software for Computers in the Safety Systems of Nuclear Power Stations". An overview description of IEC 880 is provided and the relationship between the requirements in the main body of the standard and the guidance provided in the appendices is discussed. Some fundamental issues to be considered when performing an assessment are highlighted. In particular, the analysis of the development lifecycle, including consideration of issues such as the multiple iterations of development phases and the use of pre-existing system components, is discussed. The various types of software/data which are present in a typical system are described and the applicability of the standard to each is reviewed. In conclusion, the author recognises the broad scope and relevance of IEC 880, but also highlights the practical problems encountered when attempting to gauge the 'compliance' of a system. The author provides some recommendations for assessors.
{"title":"Assessing software based safety systems against the requirements and recommendations of IEC 880 (1986)","authors":"R.J. Tate","doi":"10.1109/SESS.1995.525961","DOIUrl":"https://doi.org/10.1109/SESS.1995.525961","url":null,"abstract":"This paper examines the process of assessing software-based systems against the IEC 880 (1986) standard \"Software for Computers in the Safety Systems of Nuclear Power Stations\". An overview description of IEC 880 is provided and the relationship between the requirements in the main body of the standard and the guidance provided in the appendices is discussed. Some fundamental issues to be considered when performing an assessment are highlighted. In particular, the analysis of the development lifecycle, including consideration of issues such as the multiple iterations of development phases and the use of pre-existing system components, is discussed. The various types of software/data which are present in a typical system are described and the applicability of the standard to each is reviewed. In conclusion, the author recognises the broad scope and relevance of IEC 880, but also highlights the practical problems encountered when attempting to gauge the 'compliance' of a system. The author provides some recommendations for assessors.","PeriodicalId":178570,"journal":{"name":"Proceedings of Software Engineering Standards Symposium","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133716999","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 : 1995-08-21DOI: 10.1109/SESS.1995.525974
A. Abran
Material to teach evaluation and selection of new technologies is often geared towards major organizations and research centers. However, software engineers in small to medium sized organizations are often faced with the same challenge of selecting new technologies. For graduate courses in software engineering, there is currently is a lack of teaching material geared towards the needs of small to medium sized organizations. The paper discusses the redesigning of a graduate course in software engineering using as base material the work in progress of an ISO subcommittee in software engineering. The test of the redesign was carried out through a class simulation of the review process of an ISO working group. Lessons learned from both the learning and teaching perspectives are presented.
{"title":"Using ISO work-in-progress documents in teaching software engineering: an experiment","authors":"A. Abran","doi":"10.1109/SESS.1995.525974","DOIUrl":"https://doi.org/10.1109/SESS.1995.525974","url":null,"abstract":"Material to teach evaluation and selection of new technologies is often geared towards major organizations and research centers. However, software engineers in small to medium sized organizations are often faced with the same challenge of selecting new technologies. For graduate courses in software engineering, there is currently is a lack of teaching material geared towards the needs of small to medium sized organizations. The paper discusses the redesigning of a graduate course in software engineering using as base material the work in progress of an ISO subcommittee in software engineering. The test of the redesign was carried out through a class simulation of the review process of an ISO working group. Lessons learned from both the learning and teaching perspectives are presented.","PeriodicalId":178570,"journal":{"name":"Proceedings of Software Engineering Standards Symposium","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129530843","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 : 1995-08-21DOI: 10.1109/SESS.1995.525966
C. Trammell
When a population is too large for study, as is the case for all possible uses of a software system, a statistically correct sample must be drawn as a basis for inferences about the population. In statistical testing of software based on a Markov chain usage model, the rich body of analytical results available for Markov chains provides numerous insights that can be used in test planning. Further, the connection between Markov chains and operations research techniques permits a Markov usage model to be expressed as a system of constraints, with mathematical programming used to generate the optimal model for a particular objective function. Since a software usage model is based on the specification, all analyses may be performed early in the development cycle and used as a quantitative basis for management decisions. These techniques have been reduced to engineering practice and used in large projects by IBM, Ericsson, all branches of the US military, and others. In this paper, statistical experiments, Markov models, and optimization techniques are shown to provide a sound theoretical and practical basis far quantifying the reliability of software.
{"title":"Quantifying the reliability of software: statistical testing based on a usage model","authors":"C. Trammell","doi":"10.1109/SESS.1995.525966","DOIUrl":"https://doi.org/10.1109/SESS.1995.525966","url":null,"abstract":"When a population is too large for study, as is the case for all possible uses of a software system, a statistically correct sample must be drawn as a basis for inferences about the population. In statistical testing of software based on a Markov chain usage model, the rich body of analytical results available for Markov chains provides numerous insights that can be used in test planning. Further, the connection between Markov chains and operations research techniques permits a Markov usage model to be expressed as a system of constraints, with mathematical programming used to generate the optimal model for a particular objective function. Since a software usage model is based on the specification, all analyses may be performed early in the development cycle and used as a quantitative basis for management decisions. These techniques have been reduced to engineering practice and used in large projects by IBM, Ericsson, all branches of the US military, and others. In this paper, statistical experiments, Markov models, and optimization techniques are shown to provide a sound theoretical and practical basis far quantifying the reliability of software.","PeriodicalId":178570,"journal":{"name":"Proceedings of Software Engineering Standards Symposium","volume":"42 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122701366","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 : 1995-08-21DOI: 10.1109/SESS.1995.525973
R. Singh
Software is increasingly performing vital functions in systems such as consumer products, military, telecommunication, medical, and banking. However, software engineering and conventional engineering have not been integrated into a cohesive and concurrent system engineering. Consequently, software engineering is essentially developing on its own and does not fully participate in hardware/software tradeoff analyses and does not fully contribute to the system at its full potential. The article presents such system software relationship issues and presents some initial solutions that might be implemented to improve the situation.
{"title":"Harmonization of software engineering and system engineering standards","authors":"R. Singh","doi":"10.1109/SESS.1995.525973","DOIUrl":"https://doi.org/10.1109/SESS.1995.525973","url":null,"abstract":"Software is increasingly performing vital functions in systems such as consumer products, military, telecommunication, medical, and banking. However, software engineering and conventional engineering have not been integrated into a cohesive and concurrent system engineering. Consequently, software engineering is essentially developing on its own and does not fully participate in hardware/software tradeoff analyses and does not fully contribute to the system at its full potential. The article presents such system software relationship issues and presents some initial solutions that might be implemented to improve the situation.","PeriodicalId":178570,"journal":{"name":"Proceedings of Software Engineering Standards Symposium","volume":"69 6","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120927585","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 : 1995-08-21DOI: 10.1109/SESS.1995.525946
J. Brazendale
The paper gives an overview of draft international standard IEC 1508: Functional Safety: Safety-Related Systems. The objective of this standard is to provide a basis for safely automating process plant machinery, medical devices and other industrial equipment. The standard is concerned with preventing two basic types of unsafe incident. Firstly, failures of control systems that have the potential to trigger other events which in turn could lead to danger eg. fire, release of toxic materials, repeat stroke of machine, etc. Secondly, covert failures in protection systems that make them unavailable when needed for a safety action e.g. an emergency shutdown system. The paper describes how the standard treats random hardware faults, common cause faults and systematic faults (eg. design errors) in both hardware and software. Examples of incidents involving control system failure are also described.
{"title":"IEC 1508: Functional Safety: Safety-Related Systems","authors":"J. Brazendale","doi":"10.1109/SESS.1995.525946","DOIUrl":"https://doi.org/10.1109/SESS.1995.525946","url":null,"abstract":"The paper gives an overview of draft international standard IEC 1508: Functional Safety: Safety-Related Systems. The objective of this standard is to provide a basis for safely automating process plant machinery, medical devices and other industrial equipment. The standard is concerned with preventing two basic types of unsafe incident. Firstly, failures of control systems that have the potential to trigger other events which in turn could lead to danger eg. fire, release of toxic materials, repeat stroke of machine, etc. Secondly, covert failures in protection systems that make them unavailable when needed for a safety action e.g. an emergency shutdown system. The paper describes how the standard treats random hardware faults, common cause faults and systematic faults (eg. design errors) in both hardware and software. Examples of incidents involving control system failure are also described.","PeriodicalId":178570,"journal":{"name":"Proceedings of Software Engineering Standards Symposium","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129325261","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 : 1995-08-21DOI: 10.1109/SESS.1995.525952
G. Murine
Rome Laboratory has been at the forefront of exploration and development techniques designed to improve software management with tools useful in improving the control and cost of software system development. The paper defines the software quality measurements problem, explores software quality measurement system implementation concerns, summarizes the evolution of software quality measurement as a enhancement to modern software development techniques, reviews current and past Rome Laboratory software quality measurement initiatives, outlines several case studies of Rome Laboratory Software Quality Framework applications during the past fifteen years, and provides a brief overview of the Rome Laboratory Framework implementation guidebook.
{"title":"Using the Rome Laboratory framework and implementation guidebook as the basis for an international software quality metric standard","authors":"G. Murine","doi":"10.1109/SESS.1995.525952","DOIUrl":"https://doi.org/10.1109/SESS.1995.525952","url":null,"abstract":"Rome Laboratory has been at the forefront of exploration and development techniques designed to improve software management with tools useful in improving the control and cost of software system development. The paper defines the software quality measurements problem, explores software quality measurement system implementation concerns, summarizes the evolution of software quality measurement as a enhancement to modern software development techniques, reviews current and past Rome Laboratory software quality measurement initiatives, outlines several case studies of Rome Laboratory Software Quality Framework applications during the past fifteen years, and provides a brief overview of the Rome Laboratory Framework implementation guidebook.","PeriodicalId":178570,"journal":{"name":"Proceedings of Software Engineering Standards Symposium","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132297625","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 : 1995-08-21DOI: 10.1109/SESS.1995.525947
Evelyne Leret
The paper discusses standards under development at international level, concerning safety aspects of computerized instrumentation and control (I&C) systems. An overview of the surveyed standards projects is provided, followed by a brief discussion on typical matters dealt with, and a comparison with other standards also under development on these topics. Our purpose is to highlight typical matters which are discussed in standardization bodies, because they can be deemed as representative of a certain evolution of the state of the art/practices in the area of safety critical software.
{"title":"Safety of computerized I&C systems: projects of IEC standards with emphasis on power plant sector","authors":"Evelyne Leret","doi":"10.1109/SESS.1995.525947","DOIUrl":"https://doi.org/10.1109/SESS.1995.525947","url":null,"abstract":"The paper discusses standards under development at international level, concerning safety aspects of computerized instrumentation and control (I&C) systems. An overview of the surveyed standards projects is provided, followed by a brief discussion on typical matters dealt with, and a comparison with other standards also under development on these topics. Our purpose is to highlight typical matters which are discussed in standardization bodies, because they can be deemed as representative of a certain evolution of the state of the art/practices in the area of safety critical software.","PeriodicalId":178570,"journal":{"name":"Proceedings of Software Engineering Standards Symposium","volume":"51 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115231302","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 : 1995-08-21DOI: 10.1109/SESS.1995.525962
J. Bøegh
The concept of evaluation modules is introduced in order to provide a flexible and structured approach to evaluating software products. The purpose of using evaluation modules is to ensure that software evaluations can be repeatable, reproducible and objective. A standardised format of evaluation modules is described and practical experiences with applying evaluation modules are reported.
{"title":"Evaluation modules: the link between theory and practice","authors":"J. Bøegh","doi":"10.1109/SESS.1995.525962","DOIUrl":"https://doi.org/10.1109/SESS.1995.525962","url":null,"abstract":"The concept of evaluation modules is introduced in order to provide a flexible and structured approach to evaluating software products. The purpose of using evaluation modules is to ensure that software evaluations can be repeatable, reproducible and objective. A standardised format of evaluation modules is described and practical experiences with applying evaluation modules are reported.","PeriodicalId":178570,"journal":{"name":"Proceedings of Software Engineering Standards Symposium","volume":"49 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130187482","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
扫码关注我们
求助内容：
应助结果提醒方式：