Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324854
C. Potts
A discussion on object-oriented analysis (OOA) is summarized. Among the topics discussed are: whether objects facilitate understanding; whether autonomy facilitates understanding; whether OOA encourages premature design; whether OOA addresses requirements volatility; the Shlaer-Mellor method; the separation of problem domains; the translation of domains; the role of prototyping in requirements engineering; tool support; and the question of distinguishing models from requirements.<>
{"title":"I never knew my requirements were object-oriented until I talked to my analyst","authors":"C. Potts","doi":"10.1109/ISRE.1993.324854","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324854","url":null,"abstract":"A discussion on object-oriented analysis (OOA) is summarized. Among the topics discussed are: whether objects facilitate understanding; whether autonomy facilitates understanding; whether OOA encourages premature design; whether OOA addresses requirements volatility; the Shlaer-Mellor method; the separation of problem domains; the translation of domains; the role of prototyping in requirements engineering; tool support; and the question of distinguishing models from requirements.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129338309","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-01-04DOI: 10.1109/ISRE.1993.324849
B. Ramesh, M. Edwards
In the development of large-scale, real-time, complex computer intensive systems, it is essential to maintain traceability of requirements to various outputs to ensure that the system meets the current set of requirements. Based on an empirical study in a simulated systems development environment, several major issues that need to be considered in the development of a model of requirements traceability are addressed.<>
{"title":"Issues in the development of a requirements traceability model","authors":"B. Ramesh, M. Edwards","doi":"10.1109/ISRE.1993.324849","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324849","url":null,"abstract":"In the development of large-scale, real-time, complex computer intensive systems, it is essential to maintain traceability of requirements to various outputs to ensure that the system meets the current set of requirements. Based on an empirical study in a simulated systems development environment, several major issues that need to be considered in the development of a model of requirements traceability are addressed.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132885983","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-01-04DOI: 10.1109/ISRE.1993.324847
S. Harker, K. Eason, J. Dobson
The difficulty of handling changing requirements within traditional development processes is described. The origins of changing user and organizational requirements are discussed and different types are classified. The author identifies a number of ways in which different approaches to design may help to deal with change as well as mechanisms which should underpin effective communication between users and designers.<>
{"title":"The change and evolution of requirements as a challenge to the practice of software engineering","authors":"S. Harker, K. Eason, J. Dobson","doi":"10.1109/ISRE.1993.324847","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324847","url":null,"abstract":"The difficulty of handling changing requirements within traditional development processes is described. The origins of changing user and organizational requirements are discussed and different types are classified. The author identifies a number of ways in which different approaches to design may help to deal with change as well as mechanisms which should underpin effective communication between users and designers.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"67 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115625332","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-01-04DOI: 10.1109/ISRE.1993.324819
M. Bickerton, J. Siddiqi
A classification of requirements engineering methods based on the social assumptions made about organizations is presented. The scheme, based on a taxonomy of social theories after J. Lyotard (1984), provides a set of categories corresponding to metanarratives used within requirements engineering. A short description of each metanarrative is provided in terms of the assumptions made about the nature of society and the expected role of the requirements engineer. A decision aid for practitioners is included in the form of a table that classifies a representative sample of requirements engineering methods.<>
{"title":"The classification of requirements engineering methods","authors":"M. Bickerton, J. Siddiqi","doi":"10.1109/ISRE.1993.324819","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324819","url":null,"abstract":"A classification of requirements engineering methods based on the social assumptions made about organizations is presented. The scheme, based on a taxonomy of social theories after J. Lyotard (1984), provides a set of categories corresponding to metanarratives used within requirements engineering. A short description of each metanarrative is provided in terms of the assumptions made about the nature of society and the expected role of the requirements engineer. A decision aid for practitioners is included in the form of a table that classifies a representative sample of requirements engineering methods.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131729035","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-01-04DOI: 10.1109/ISRE.1993.324826
S. Castano, V. D. Antonellis
A methodological approach is presented to guide the definition of reusable components to be exploited for designing applications not from scratch, but by tailoring and adapting existing components. Reusability at the requirements specification level is considered, and tools to define reusable components are illustrated. Reusable components are defined as generic components with associated meta-components providing guidelines for reuse in a given application.<>
{"title":"Reuse of conceptual requirement specifications","authors":"S. Castano, V. D. Antonellis","doi":"10.1109/ISRE.1993.324826","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324826","url":null,"abstract":"A methodological approach is presented to guide the definition of reusable components to be exploited for designing applications not from scratch, but by tailoring and adapting existing components. Reusability at the requirements specification level is considered, and tools to define reusable components are illustrated. Reusable components are defined as generic components with associated meta-components providing guidelines for reuse in a given application.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"69 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131007669","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-01-04DOI: 10.1109/ISRE.1993.324858
J. Goguen
Social issues in requirements engineering are classified according to what groups are involved. Topics discussed include issues within the client organization, requirement team issues, issues between the client organization and the requirements team, and development team issues.<>
{"title":"Social issues in requirements engineering","authors":"J. Goguen","doi":"10.1109/ISRE.1993.324858","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324858","url":null,"abstract":"Social issues in requirements engineering are classified according to what groups are involved. Topics discussed include issues within the client organization, requirement team issues, issues between the client organization and the requirements team, and development team issues.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123984538","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-01-04DOI: 10.1109/ISRE.1993.324838
B. Nixon
Performance goals for information systems are treated as a class of nonfunctional requirements (NFRs). A given model for representing NFRs is given to make provisions for: representing a variety of implementation alternatives; expressing performance goals (including responsiveness) in terms of performance and information system concepts; and organizing the process into layers corresponding to subsets of the language to be implemented. The application of the framework is illustrated by mapping the conceptual design of an information system to its implementation, while attempting to meet a set of goals such as 'achieve good time performance for authorizing credit card sales'. A tool is being developed to aid this process.<>
{"title":"Dealing with performance requirements during the development of information systems","authors":"B. Nixon","doi":"10.1109/ISRE.1993.324838","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324838","url":null,"abstract":"Performance goals for information systems are treated as a class of nonfunctional requirements (NFRs). A given model for representing NFRs is given to make provisions for: representing a variety of implementation alternatives; expressing performance goals (including responsiveness) in terms of performance and information system concepts; and organizing the process into layers corresponding to subsets of the language to be implemented. The application of the framework is illustrated by mapping the conceptual design of an information system to its implementation, while attempting to meet a set of goals such as 'achieve good time performance for authorizing credit card sales'. A tool is being developed to aid this process.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"70 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124302072","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-01-04DOI: 10.1109/ISRE.1993.324842
M. D. Lubars, C. Potts, C. Richter
A field study of ten organizations was conducted to determine their current practices on definition, interpretation, analysis, and use of the requirements for their software systems and products. The field study consisted of a series of in-depth, structured interviews with practitioners of various kinds. The findings of this study are summarized, and the implications for improving practice either by organizational and methodological interventions or by introducing new technology are explained.<>
{"title":"A review of the state of the practice in requirements modeling","authors":"M. D. Lubars, C. Potts, C. Richter","doi":"10.1109/ISRE.1993.324842","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324842","url":null,"abstract":"A field study of ten organizations was conducted to determine their current practices on definition, interpretation, analysis, and use of the requirements for their software systems and products. The field study consisted of a series of in-depth, structured interviews with practitioners of various kinds. The findings of this study are summarized, and the implications for improving practice either by organizational and methodological interventions or by introducing new technology are explained.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126802154","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-01-04DOI: 10.1109/ISRE.1993.324827
K. Ryan, B. Mathews
The types of knowledge used during requirements acquisition are identified and a tool to aid in this process, the ReqColl (requirements collector), is introduced. The tool uses conceptual graphs to represent domain concepts, and attempts to recognize new concepts through the use of a matching facility. The overall approach to requirements capture is described and the approach to matching is illustrated informally. The detailed procedure for matching conceptual graphs is given. ReqColl is compared to similar work elsewhere, and some future research directions are indicated.<>
{"title":"Matching conceptual graphs as an aid to requirements re-use","authors":"K. Ryan, B. Mathews","doi":"10.1109/ISRE.1993.324827","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324827","url":null,"abstract":"The types of knowledge used during requirements acquisition are identified and a tool to aid in this process, the ReqColl (requirements collector), is introduced. The tool uses conceptual graphs to represent domain concepts, and attempts to recognize new concepts through the use of a matching facility. The overall approach to requirements capture is described and the approach to matching is illustrated informally. The detailed procedure for matching conceptual graphs is given. ReqColl is compared to similar work elsewhere, and some future research directions are indicated.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"67 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115079939","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-01-04DOI: 10.1109/ISRE.1993.324820
Linda A. Macaulay
There is an interesting recognition that software development is not merely a mathematical or technological challenge, but a complex social process. The social process at the earliest stages of software development, i.e., scoping and capturing requirements, is examined. Some of the problems that can arise when insufficient attention is paid to the social process are considered together with alternative team structures. A cooperative requirements capture method called user skills task match (USTM) is presented, in which the social process is explicitly managed through use of a human facilitator and which provides a structured approach to the management of the requirements capture task. The cooperative approach is illustrated using a case study from the electricity distribution industry within the UK.<>
{"title":"Requirements capture as a cooperative activity","authors":"Linda A. Macaulay","doi":"10.1109/ISRE.1993.324820","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324820","url":null,"abstract":"There is an interesting recognition that software development is not merely a mathematical or technological challenge, but a complex social process. The social process at the earliest stages of software development, i.e., scoping and capturing requirements, is examined. Some of the problems that can arise when insufficient attention is paid to the social process are considered together with alternative team structures. A cooperative requirements capture method called user skills task match (USTM) is presented, in which the social process is explicitly managed through use of a human facilitator and which provides a structured approach to the management of the requirements capture task. The cooperative approach is illustrated using a case study from the electricity distribution industry within the UK.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"49 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132935722","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
扫码关注我们
求助内容：
应助结果提醒方式：