Pub Date : 1993-08-30DOI: 10.1109/SESS.1993.263941
J. Bøegh, H. Hausen, D. Welzel
Software quality evaluation comprises a number of steps. The first step is to identify the requirements of the evaluation. In the second step the available product information is identified and classified, and the evaluation is then specified in detail. Planning the evaluation according to that specification takes place in the third step. Conducting the evaluation and collecting the findings constitute the fourth step. Reporting is done is the final step. The article reports on a framework for this stepwise procedure. Attention is given to the problems arising during evaluation of characteristics defined in ISO/IEC 9126. The main aim of the guide is to give practical recommendations for specifying and executing an evaluation.<>
{"title":"A practitioner's guide to evaluation of software","authors":"J. Bøegh, H. Hausen, D. Welzel","doi":"10.1109/SESS.1993.263941","DOIUrl":"https://doi.org/10.1109/SESS.1993.263941","url":null,"abstract":"Software quality evaluation comprises a number of steps. The first step is to identify the requirements of the evaluation. In the second step the available product information is identified and classified, and the evaluation is then specified in detail. Planning the evaluation according to that specification takes place in the third step. Conducting the evaluation and collecting the findings constitute the fourth step. Reporting is done is the final step. The article reports on a framework for this stepwise procedure. Attention is given to the problems arising during evaluation of characteristics defined in ISO/IEC 9126. The main aim of the guide is to give practical recommendations for specifying and executing an evaluation.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115232597","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 : 1993-08-30DOI: 10.1109/SESS.1993.263953
Jonathan P. Bowen
There is great interest in ensuring correctness of safety-critical embedded systems since on the one hand the use of software gives greatly increased functionality and flexibility and on the other hand it provides unprecedented possibilities for errors. Formal methods are one technique that could improve the situation. Their use is now being suggested by an increasing number of standards in the safety-critical area. The paper compares the recommendations given by a number of important existing and emerging standards and tries to identify future trends in this area. A bibliography of standards and related publications is included.<>
{"title":"Formal methods in safety-critical standards","authors":"Jonathan P. Bowen","doi":"10.1109/SESS.1993.263953","DOIUrl":"https://doi.org/10.1109/SESS.1993.263953","url":null,"abstract":"There is great interest in ensuring correctness of safety-critical embedded systems since on the one hand the use of software gives greatly increased functionality and flexibility and on the other hand it provides unprecedented possibilities for errors. Formal methods are one technique that could improve the situation. Their use is now being suggested by an increasing number of standards in the safety-critical area. The paper compares the recommendations given by a number of important existing and emerging standards and tries to identify future trends in this area. A bibliography of standards and related publications is included.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128263284","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 : 1993-08-30DOI: 10.1109/SESS.1993.263944
M. W. Morron
The paper gives a brief overview of the activities during the eighties that led to the ECMA PCTE Standard. It also gives an up to date report on the status of both its adoption by ISO as well as its industrial impact in Europe, North America and in Japan. It uses the joint ECMA/NIST Reference Model for Frameworks to position both PCTE and other standards with respect to each other. This was based on output from the CASE Standards Coordination Meetings held under the auspices of the International Workshop on CASE, of which the author is the joint coordinator.<>
{"title":"Status of repository standards for software engineering","authors":"M. W. Morron","doi":"10.1109/SESS.1993.263944","DOIUrl":"https://doi.org/10.1109/SESS.1993.263944","url":null,"abstract":"The paper gives a brief overview of the activities during the eighties that led to the ECMA PCTE Standard. It also gives an up to date report on the status of both its adoption by ISO as well as its industrial impact in Europe, North America and in Japan. It uses the joint ECMA/NIST Reference Model for Frameworks to position both PCTE and other standards with respect to each other. This was based on output from the CASE Standards Coordination Meetings held under the auspices of the International Workshop on CASE, of which the author is the joint coordinator.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"59 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131535157","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 : 1993-08-30DOI: 10.1109/SESS.1993.263966
J. Grabowski, Peter Graubmann, Ekkart Rudolph
The most relevant issues of the standardization of the Message Sequence Chart (MSC) language within the CCITT Study Group X are discussed. The history of the new MSC recommendation Z.120 is sketched. Different types of diagrams which are closely related to MSCs are compared, since they build the basis for the MSC language. The authors distinguished these diagrams from the standardized MSC language by using the term sequence charts (SCs). Subsequently, the MSC language is introduced and several approaches towards a forthcoming formal MSC semantics are presented.<>
{"title":"The standardization of message sequence charts","authors":"J. Grabowski, Peter Graubmann, Ekkart Rudolph","doi":"10.1109/SESS.1993.263966","DOIUrl":"https://doi.org/10.1109/SESS.1993.263966","url":null,"abstract":"The most relevant issues of the standardization of the Message Sequence Chart (MSC) language within the CCITT Study Group X are discussed. The history of the new MSC recommendation Z.120 is sketched. Different types of diagrams which are closely related to MSCs are compared, since they build the basis for the MSC language. The authors distinguished these diagrams from the standardized MSC language by using the term sequence charts (SCs). Subsequently, the MSC language is introduced and several approaches towards a forthcoming formal MSC semantics are presented.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"109 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125581936","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 : 1993-08-30DOI: 10.1109/SESS.1993.263943
M. Rabemanantsoa
The paper discusses the feasibility of coupling AI (artificial intelligence) with an object-oriented database in the CAD/CAM environment. The products or parts are designed with the parametric and feature-based solid modeling Pro/Engineer. The authors go beyond data structures to integrate information about the assembly knowledge base. They design an object-oriented database called SISDES for modeling the data along with handling logic based reasoning of graph representation. The output is a knowledge-based system which integrates automated feature-recognition plus position and orientation needed for part mating. In this context, they define the possibility of contact and relative mobility for each pair of components. This latter becomes part of an AI module called XGEN (Assembly Sequences Generation) developed for knowledge processing and generating assembly sequence, i.e. the CAM activities.<>
{"title":"Knowledge-based system for assembly process-planning","authors":"M. Rabemanantsoa","doi":"10.1109/SESS.1993.263943","DOIUrl":"https://doi.org/10.1109/SESS.1993.263943","url":null,"abstract":"The paper discusses the feasibility of coupling AI (artificial intelligence) with an object-oriented database in the CAD/CAM environment. The products or parts are designed with the parametric and feature-based solid modeling Pro/Engineer. The authors go beyond data structures to integrate information about the assembly knowledge base. They design an object-oriented database called SISDES for modeling the data along with handling logic based reasoning of graph representation. The output is a knowledge-based system which integrates automated feature-recognition plus position and orientation needed for part mating. In this context, they define the possibility of contact and relative mobility for each pair of components. This latter becomes part of an AI module called XGEN (Assembly Sequences Generation) developed for knowledge processing and generating assembly sequence, i.e. the CAM activities.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"76 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121575721","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/SESS.1993.263942
M. Sakakura, Y. Fukazawa
A static program analyzer has been designed and developed. Even though it is natural that large-scale software is developed by a number of groups under standard guidelines, it is often convenient that each group have group-oriented guidelines in addition to the standard guidelines. This is because the standard guidelines do not reflect factors unique to each group. The tool regards coding styles as a set of static properties of a program. With this tool, the user can define such static properties to be detected, called irregular styles. The paper describes the definition of an irregular style, a detection strategy, and evaluation of its results.<>
{"title":"An attempt to increase software quality by detecting irregular styles","authors":"M. Sakakura, Y. Fukazawa","doi":"10.1109/SESS.1993.263942","DOIUrl":"https://doi.org/10.1109/SESS.1993.263942","url":null,"abstract":"A static program analyzer has been designed and developed. Even though it is natural that large-scale software is developed by a number of groups under standard guidelines, it is often convenient that each group have group-oriented guidelines in addition to the standard guidelines. This is because the standard guidelines do not reflect factors unique to each group. The tool regards coding styles as a set of static properties of a program. With this tool, the user can define such static properties to be detected, called irregular styles. The paper describes the definition of an irregular style, a detection strategy, and evaluation of its results.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"11 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":"122329901","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/SESS.1993.263959
D. de Pablo, C. Mazza, B. Melton
The paper presents the CASE tools policy for software development for the European Space Agency (ESA). ESA has a well established set of software engineering standards which are used in all projects. The standards, do not, however, impose any particular method but rather guide a software project manager to choose the method which best suits his needs. The ESA policy for CASE tools utilization is based on freedom for choice of commercially available products having interface standards for exchange of information between tools and the repository.<>
{"title":"The ESA CASE tools policy","authors":"D. de Pablo, C. Mazza, B. Melton","doi":"10.1109/SESS.1993.263959","DOIUrl":"https://doi.org/10.1109/SESS.1993.263959","url":null,"abstract":"The paper presents the CASE tools policy for software development for the European Space Agency (ESA). ESA has a well established set of software engineering standards which are used in all projects. The standards, do not, however, impose any particular method but rather guide a software project manager to choose the method which best suits his needs. The ESA policy for CASE tools utilization is based on freedom for choice of commercially available products having interface standards for exchange of information between tools and the repository.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"15 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":"124291392","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
扫码关注我们
求助内容：
应助结果提醒方式：