Pub Date : 1993-08-30DOI: 10.1109/SESS.1993.263952
D. Hawkes, W. Struck, L. Tripp
The paper discusses the processes used in updating the industry guideline that is used in the certification of aircraft and engine systems containing software. The third generation result offers guidance for tool qualification and for the use commercial-off-the-shelf software, product service history, and alternative methods of compliance. It was transformed from a task-oriented process description to an objective-focused process description.<>
{"title":"An international safety-critical software standard for the 1990s","authors":"D. Hawkes, W. Struck, L. Tripp","doi":"10.1109/SESS.1993.263952","DOIUrl":"https://doi.org/10.1109/SESS.1993.263952","url":null,"abstract":"The paper discusses the processes used in updating the industry guideline that is used in the certification of aircraft and engine systems containing software. The third generation result offers guidance for tool qualification and for the use commercial-off-the-shelf software, product service history, and alternative methods of compliance. It was transformed from a task-oriented process description to an objective-focused process description.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"242 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":"115852113","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.263937
J. A. Graham, J.B. Higgott, A.J. Hynes
A prototype Test Support System (TSS) has been developed within BT. The objective of the TSS is to bridge the gap that currently exists between software development tools (CASE tools) and software testing tools (CAST tools). The aim being to provide end-to-end automation of the software development process and encourage test development in the earlier stages of the lifecycle. The TSS interfaces to a CASE tool and extracts relevant information from the system design. Extracted design information is developed into test procedures and test cases using a test development methodology. This methodology has been designed to comply with the internationally recognised test documentation standard IEEE-829. It can be used to develop unit, integration, system and acceptance tests, and is supported with a suite of tools. Test procedures and test cases can be extracted using the TSS and when fully developed can be executed on the target software using a test execution tool. The paper documents the experiences gained in development of the prototype TSS.<>
{"title":"Bridging the gap between CASE and CAST","authors":"J. A. Graham, J.B. Higgott, A.J. Hynes","doi":"10.1109/SESS.1993.263937","DOIUrl":"https://doi.org/10.1109/SESS.1993.263937","url":null,"abstract":"A prototype Test Support System (TSS) has been developed within BT. The objective of the TSS is to bridge the gap that currently exists between software development tools (CASE tools) and software testing tools (CAST tools). The aim being to provide end-to-end automation of the software development process and encourage test development in the earlier stages of the lifecycle. The TSS interfaces to a CASE tool and extracts relevant information from the system design. Extracted design information is developed into test procedures and test cases using a test development methodology. This methodology has been designed to comply with the internationally recognised test documentation standard IEEE-829. It can be used to develop unit, integration, system and acceptance tests, and is supported with a suite of tools. Test procedures and test cases can be extracted using the TSS and when fully developed can be executed on the target software using a test execution tool. The paper documents the experiences gained in development of the prototype TSS.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"20 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":"127156552","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.263946
K. Lano, H. Haughton
The authors discuss the significance and application of object-oriented formal specification languages to general software engineering projects and particularly to a safety-critical and mission-critical systems. They consider the role that standardisation of such languages could play in promoting their effective uptake. They give syntactic and semantic details of two object-oriented specification languages: Object-Z and Z++, and of the object-based specification language B. Aspects of these languages are considered as inputs to an eventual standard framework for such languages. These languages have been used for a wide variety of systems, from data-processing to artificial intelligence and communication protocols. They give simple examples of specifications in these languages to support a comparative evaluation.<>
{"title":"Standards and techniques for object-oriented formal specification","authors":"K. Lano, H. Haughton","doi":"10.1109/SESS.1993.263946","DOIUrl":"https://doi.org/10.1109/SESS.1993.263946","url":null,"abstract":"The authors discuss the significance and application of object-oriented formal specification languages to general software engineering projects and particularly to a safety-critical and mission-critical systems. They consider the role that standardisation of such languages could play in promoting their effective uptake. They give syntactic and semantic details of two object-oriented specification languages: Object-Z and Z++, and of the object-based specification language B. Aspects of these languages are considered as inputs to an eventual standard framework for such languages. These languages have been used for a wide variety of systems, from data-processing to artificial intelligence and communication protocols. They give simple examples of specifications in these languages to support a comparative evaluation.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"13 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":"123807886","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.263949
I. Ushakov, R. Werling, H. Nagano, H. Tadaumi, Y. Yamamoto, J. Egner
The paper describes main ideas and current state of the SC7/WG1 standardization activity in the field of graphical representation of information in software engineering. It presents projects of standards that are currently under consideration in WG1. The most important one is 'Basic Symbols' aimed at data transfer among CASE tools. The project is regarded as a focus of recent effort of different standard-making bodies to reach unified description for software engineering data.<>
{"title":"Graphical representation of information in software engineering: ISO-IEC JTC1/SC7 framework, concepts and standards activity","authors":"I. Ushakov, R. Werling, H. Nagano, H. Tadaumi, Y. Yamamoto, J. Egner","doi":"10.1109/SESS.1993.263949","DOIUrl":"https://doi.org/10.1109/SESS.1993.263949","url":null,"abstract":"The paper describes main ideas and current state of the SC7/WG1 standardization activity in the field of graphical representation of information in software engineering. It presents projects of standards that are currently under consideration in WG1. The most important one is 'Basic Symbols' aimed at data transfer among CASE tools. The project is regarded as a focus of recent effort of different standard-making bodies to reach unified description for software engineering data.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"10 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":"132615333","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.263939
M. Woodman, R. Henry
The forthcoming programming language standard for Modula-2 is the first to use a formal notation to express its language requirements. While the precision that a mathematical model brings should itself ensure high quality in conforming implementations, it is remarkable that considerable effort has been expended in adding explicit quality-attributes to the standard. The paper reports on how this has been achieved and suggests that standards based on formal models offer clear opportunities for the incorporation of quality-related requirements.<>
{"title":"Specifying quality requirements in a formally defined language standard","authors":"M. Woodman, R. Henry","doi":"10.1109/SESS.1993.263939","DOIUrl":"https://doi.org/10.1109/SESS.1993.263939","url":null,"abstract":"The forthcoming programming language standard for Modula-2 is the first to use a formal notation to express its language requirements. While the precision that a mathematical model brings should itself ensure high quality in conforming implementations, it is remarkable that considerable effort has been expended in adding explicit quality-attributes to the standard. The paper reports on how this has been achieved and suggests that standards based on formal models offer clear opportunities for the incorporation of quality-related requirements.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"47 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":"133142920","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.263963
G. Bazzana, O. Andersen, T. Jokela
The paper presents the relevant results of an awareness survey carried out in 1992 in the framework of an Esprit project SCOPE on software evaluation and certification issues. The survey identifies what are the needs and expectations for product quality evaluation based on the ISO/IEC 9126 Standard. In addition the possible links with the ISO 9000 Standard and process certification are investigated.<>
{"title":"ISO 9126 and ISO 9000: friends or foes?","authors":"G. Bazzana, O. Andersen, T. Jokela","doi":"10.1109/SESS.1993.263963","DOIUrl":"https://doi.org/10.1109/SESS.1993.263963","url":null,"abstract":"The paper presents the relevant results of an awareness survey carried out in 1992 in the framework of an Esprit project SCOPE on software evaluation and certification issues. The survey identifies what are the needs and expectations for product quality evaluation based on the ISO/IEC 9126 Standard. In addition the possible links with the ISO 9000 Standard and process certification are investigated.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"50 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":"114212552","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.263947
L. Jadoul, J. Van Dun, M. Jadoul
Because of the growing complexity of telecom systems, the use of formal specification and design languages is becoming increasingly important. They do not clarify the system description produced, but also create the possibility to support and automate the development process. At Alcatel Bell Telephone, standardized, formal techniques are being applied for software and hardware development. Software development is based on CCITT-SDI, used from specification to code generation. Hardware development methodology is based on the IEEE-VHDI. The commonalities and similarities between formal methods for hardware and software development are looked at, and complemented by a system level design methodology, based on the same principles.<>
{"title":"From software and hardware formal design towards an integrated system design methodology","authors":"L. Jadoul, J. Van Dun, M. Jadoul","doi":"10.1109/SESS.1993.263947","DOIUrl":"https://doi.org/10.1109/SESS.1993.263947","url":null,"abstract":"Because of the growing complexity of telecom systems, the use of formal specification and design languages is becoming increasingly important. They do not clarify the system description produced, but also create the possibility to support and automate the development process. At Alcatel Bell Telephone, standardized, formal techniques are being applied for software and hardware development. Software development is based on CCITT-SDI, used from specification to code generation. Hardware development methodology is based on the IEEE-VHDI. The commonalities and similarities between formal methods for hardware and software development are looked at, and complemented by a system level design methodology, based on the same principles.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"38 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":"116229845","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.263968
R. Scowen
Generic base standards, that is, ones defining these fundamental concepts of information technology, offer a way of improving standardization in IT by enabling greater commonality. The paper looks briefly at the fundamental base standards of terminology and character sets. It then considers in more depth two other generic base concepts: syntactic metalanguages (for example, Backus Naur form) and numeric floating-point constants. Case studies illustrate typical unnecessary variations in existing standards and demonstrate that even the simplest ideas are treated in widely different ways.<>
{"title":"Generic base standards","authors":"R. Scowen","doi":"10.1109/SESS.1993.263968","DOIUrl":"https://doi.org/10.1109/SESS.1993.263968","url":null,"abstract":"Generic base standards, that is, ones defining these fundamental concepts of information technology, offer a way of improving standardization in IT by enabling greater commonality. The paper looks briefly at the fundamental base standards of terminology and character sets. It then considers in more depth two other generic base concepts: syntactic metalanguages (for example, Backus Naur form) and numeric floating-point constants. Case studies illustrate typical unnecessary variations in existing standards and demonstrate that even the simplest ideas are treated in widely different ways.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"15 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":"122945258","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.263958
M. Woodman
The article questions the role of formal methods in the standardization of programming languages by examining the VDM-SL definition used in the Modula-2 standard, particularly in terms of the demands of the formal notation, the time taken to meet them and the size of the resultant document. Possible inadequacies of the formal notations used and in their applications are reviewed: the lack of generic specification and the occurrence of 'noise' is discussed. An agenda of work to be undertaken to facilitate the rapid production of formally defined language standards is proposed. A life-cycle for formally defined language standards is outlined which includes their testing. The need for the rapid production of standards is emphasized.<>
{"title":"Are formal methods a good thing for programming language standards? Setting an agenda for the future","authors":"M. Woodman","doi":"10.1109/SESS.1993.263958","DOIUrl":"https://doi.org/10.1109/SESS.1993.263958","url":null,"abstract":"The article questions the role of formal methods in the standardization of programming languages by examining the VDM-SL definition used in the Modula-2 standard, particularly in terms of the demands of the formal notation, the time taken to meet them and the size of the resultant document. Possible inadequacies of the formal notations used and in their applications are reviewed: the lack of generic specification and the occurrence of 'noise' is discussed. An agenda of work to be undertaken to facilitate the rapid production of formally defined language standards is proposed. A life-cycle for formally defined language standards is outlined which includes their testing. The need for the rapid production of standards is emphasized.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"35 13 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":"123517593","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.263957
C. Skourlas, V. Melagrakis, G. Miaoulis, J. Halaris, S. Xanthakis, J. Dragonas
The authors propose an architecture for a documentation system for standardization. They study the system in terms of organizational structure, main functions and information resources. Then, the general architecture is presented and the objectives and the features of the system are discussed for three portions of the system: the host documentation centre; the discussion group (local documentation centre); and the subscriber (documentation unit). Special emphasis is given to the information retrieval system which is the kernel of the system.<>
{"title":"The new role of a documentation system for standardization","authors":"C. Skourlas, V. Melagrakis, G. Miaoulis, J. Halaris, S. Xanthakis, J. Dragonas","doi":"10.1109/SESS.1993.263957","DOIUrl":"https://doi.org/10.1109/SESS.1993.263957","url":null,"abstract":"The authors propose an architecture for a documentation system for standardization. They study the system in terms of organizational structure, main functions and information resources. Then, the general architecture is presented and the objectives and the features of the system are discussed for three portions of the system: the host documentation centre; the discussion group (local documentation centre); and the subscriber (documentation unit). Special emphasis is given to the information retrieval system which is the kernel of the system.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"8 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":"114963839","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
扫码关注我们
求助内容：
应助结果提醒方式：