{"title":"Editorial: Software process and its support","authors":"N. Madhavji, Wilhelm Schäfer","doi":"10.1049/sej.1991.0025","DOIUrl":"https://doi.org/10.1049/sej.1991.0025","url":null,"abstract":"","PeriodicalId":41522,"journal":{"name":"e-Informatica Software Engineering Journal","volume":null,"pages":null},"PeriodicalIF":0.8,"publicationDate":"1991-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"80668440","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}
Specifications can be written in languages which have formal semantics. Their very formality, and the similarities with some aspects of implementation languages, invites the idea that specifications might be executed. This paper presents a number of arguments against that idea. The aim is to warn of the dangers of limiting specification languages to the point where all of their constructs can be executed. While conceding the difficulties of relating specifications to an understanding of the ‘requirements’ for a system, it is argued that other solutions should be sought than ‘executable specification languages’.
{"title":"Specifications are not (necessarily) executable","authors":"I. Hayes, Cliff B. Jones","doi":"10.1049/SEJ.1989.0045","DOIUrl":"https://doi.org/10.1049/SEJ.1989.0045","url":null,"abstract":"Specifications can be written in languages which have formal semantics. Their very formality, and the similarities with some aspects of implementation languages, invites the idea that specifications might be executed. This paper presents a number of arguments against that idea. The aim is to warn of the dangers of limiting specification languages to the point where all of their constructs can be executed. While conceding the difficulties of relating specifications to an understanding of the ‘requirements’ for a system, it is argued that other solutions should be sought than ‘executable specification languages’.","PeriodicalId":41522,"journal":{"name":"e-Informatica Software Engineering Journal","volume":null,"pages":null},"PeriodicalIF":0.8,"publicationDate":"1989-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"86165446","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}
Distributed computer systems offer the potential for growth and change. Although the underlying support mechanisms for change (software creation, binding, deletion) are well understood, there has been no consensus on how evolutionary change can be managed and controlled. This paper suggests that, since distributed systems are specified and constructed in terms of their software structure (configuration), it is appropriate that changes should be specified in terms of structure and managed at the configuration level. We present a model for managing evolution which separates structural concerns at the configuration level from those application concerns at the component level. This permits the formulation of general structural rules for change without the need to consider application state, and the specification of application actions without knowledge of the actual structural changes which may be introduced. To illustrate the approach and discuss pragmatic aspects, the model is applied to an example problem which has been implemented and tested in the Conic environment for distributed systems.
{"title":"Managing evolution in distributed systems","authors":"J. Kramer, J. Magee, M. Sloman","doi":"10.1049/SEJ.1989.0044","DOIUrl":"https://doi.org/10.1049/SEJ.1989.0044","url":null,"abstract":"Distributed computer systems offer the potential for growth and change. Although the underlying support mechanisms for change (software creation, binding, deletion) are well understood, there has been no consensus on how evolutionary change can be managed and controlled. This paper suggests that, since distributed systems are specified and constructed in terms of their software structure (configuration), it is appropriate that changes should be specified in terms of structure and managed at the configuration level. We present a model for managing evolution which separates structural concerns at the configuration level from those application concerns at the component level. This permits the formulation of general structural rules for change without the need to consider application state, and the specification of application actions without knowledge of the actual structural changes which may be introduced. To illustrate the approach and discuss pragmatic aspects, the model is applied to an example problem which has been implemented and tested in the Conic environment for distributed systems.","PeriodicalId":41522,"journal":{"name":"e-Informatica Software Engineering Journal","volume":null,"pages":null},"PeriodicalIF":0.8,"publicationDate":"1989-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"83115866","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}
In the specification notation known as Z, schemas are used to structure mathematical descriptions. This paper describes the language of schemas and the conventions that are employed in their use. It also describes how proof obligations are generated during specification, and how these obligations may be discharged. The paper contains many examples, mostly taken from the specification of the user interface to a small, but realistic, software component.
{"title":"Structuring specifications in Z","authors":"J. C. P. Woodcook","doi":"10.1049/SEJ.1989.0007","DOIUrl":"https://doi.org/10.1049/SEJ.1989.0007","url":null,"abstract":"In the specification notation known as Z, schemas are used to structure mathematical descriptions. This paper describes the language of schemas and the conventions that are employed in their use. It also describes how proof obligations are generated during specification, and how these obligations may be discharged. The paper contains many examples, mostly taken from the specification of the user interface to a small, but realistic, software component.","PeriodicalId":41522,"journal":{"name":"e-Informatica Software Engineering Journal","volume":null,"pages":null},"PeriodicalIF":0.8,"publicationDate":"1989-01-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"82221999","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
扫码关注我们
求助内容：
应助结果提醒方式：