{"title":"Contribution structures [Requirements artifacts]","authors":"O. Gotel, A. Finkelstein","doi":"10.1109/ISRE.1995.512550","DOIUrl":"https://doi.org/10.1109/ISRE.1995.512550","url":null,"abstract":"The invisibility of the individuals and groups that gave rise to requirements artifacts has been identified as a primary reason for the persistence of requirements traceability problems. The paper presents an approach based on modelling the dynamic contribution structures underlying requirements artifacts, which addresses this issue. It shows how these structures can be defined, using information about the agents who have contributed to artifact production, in conjunction with details of the numerous traceability relations that hold within and between artifacts themselves. It further outlines how the approach can be implemented, demonstrates the potential it provides for \"personnel-based\" requirements traceability, and discusses issues pertinent to its uptake.","PeriodicalId":354711,"journal":{"name":"Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95)","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-03-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114933126","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}
{"title":"Improving the use case driven approach to requirements engineering","authors":"B. Regnell, K. Kimbler, Anders Wesslén","doi":"10.1109/ISRE.1995.512544","DOIUrl":"https://doi.org/10.1109/ISRE.1995.512544","url":null,"abstract":"The paper presents the idea of usage oriented requirements engineering, an extension of use case driven analysis. The main objective is to achieve a requirements engineering process resulting in a model which captures both functional requirements and system usage aspects in a comprehensive manner. The paper presents the basic concepts and the process of usage oriented requirements engineering, and the synthesized usage model resulting from this process. The role of this model in system development, and its potential applications are also discussed.","PeriodicalId":354711,"journal":{"name":"Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95)","volume":"42 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-03-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124540267","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}
Paul A. Gough, Filip T. Fodemski, Stewart A. Higgins, S. J. Ray
{"title":"Scenarios-an industrial case study and hypermedia enhancements","authors":"Paul A. Gough, Filip T. Fodemski, Stewart A. Higgins, S. J. Ray","doi":"10.1109/ISRE.1995.512541","DOIUrl":"https://doi.org/10.1109/ISRE.1995.512541","url":null,"abstract":"A study of requirements elicitation and validation within an industrial environment is reported. The key features in this part of the requirements process are: scenarios, as the prime means of elicitation; identification of domain objects, to capture the language of the domain and Fagan inspections for scenario validation by stakeholders. The process has been evaluated from both the requirements engineer's perspective and the viewpoint of the various stakeholders. The findings highlight a number of issues, both positive and negative, which are discussed. The deficiencies identified have stimulated our research. In particular it is our contention that requirements documentation need to break away from the fixation with purely textual documents to ones that are media rich. Examples of this research, such as the hypermedia Scenario Manager are described.","PeriodicalId":354711,"journal":{"name":"Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95)","volume":"90 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-03-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116631538","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}
{"title":"Consistency checking of SCR-style requirements specifications","authors":"C. Heitmeyer, B. Labaw, D. Kiskis","doi":"10.1109/ISRE.1995.512546","DOIUrl":"https://doi.org/10.1109/ISRE.1995.512546","url":null,"abstract":"The paper describes a class of formal analysis called consistency checking that mechanically checks requirements specifications, expressed in the SCR tabular notation, for application independent properties. Properties include domain coverage, type correctness, and determinism. As background, the SCR notation for specifying requirements is reviewed. A formal requirements model describing the meaning of the SCR notation is summarized, and consistency checks derived from the formal model are described. The results of experiments to evaluate the utility of automated consistency checking are presented. Where consistency checking of requirements fits in the software development process is discussed.","PeriodicalId":354711,"journal":{"name":"Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-03-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130956966","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}
{"title":"How people categorise requirements for reuse: a natural approach","authors":"N. Maiden, P. Mistry, A. Sutcliffe","doi":"10.1109/RE.1995.10001","DOIUrl":"https://doi.org/10.1109/RE.1995.10001","url":null,"abstract":"Abstract This paper reports a knowledge acquisition exercisewhich elicited experienced somare engineer' s knowledge about domains for which requirements engineering takes place. Card sorts were used to acquire software engineers' mental categorisations of these domains to inform categorization of a set of formal,reusable problem abstractions intended to assist requirements engineers.","PeriodicalId":354711,"journal":{"name":"Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95)","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-03-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126662651","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}