{"title":"Domain Knowledge Wiki for Eliciting Requirements","authors":"Takanori Ugai, Kouji Aoyama","doi":"10.1109/MARK.2009.4","DOIUrl":"https://doi.org/10.1109/MARK.2009.4","url":null,"abstract":"40990004","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114381070","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}
To push the right information to the right person at the right time, classical work on recommendation systems focuses on optimizing the rating of recommended items. Recent research on contextawareness and knowledge ex change shows potentials of recommendation systems in en gineering work. Requirements engineering can also profit from recommendation systems in several scenarios, includ ing maintaining requirements, sharing collaboration infor mation and reusing templates. By describing these scenar ios and identifying key realization challenges, this paper presents a vision on recommendation systems in require ments engineering.
{"title":"Towards a Research Agenda for Recommendation Systems in Requirements Engineering","authors":"W. Maalej, A. K. Thurimella","doi":"10.1109/MARK.2009.12","DOIUrl":"https://doi.org/10.1109/MARK.2009.12","url":null,"abstract":"To push the right information to the right person at the right time, classical work on recommendation systems focuses on optimizing the rating of recommended items. Recent research on contextawareness and knowledge ex change shows potentials of recommendation systems in en gineering work. Requirements engineering can also profit from recommendation systems in several scenarios, includ ing maintaining requirements, sharing collaboration infor mation and reusing templates. By describing these scenar ios and identifying key realization challenges, this paper presents a vision on recommendation systems in require ments engineering.","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132500252","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}
Requirements gathering, analysis, and specification are humanintensive activities that rely upon finding and engaging a relevant set of informed stakeholders. In many projects initial requirements are captured through the use of wikis or forums, or through ini tial facetoface brainstorming meetings. In this paper we introduce a technique for analyzing stakeholders' contributions, extracting domain topics, and construct ing profiles which depict stakeholders' interests in each of the topics. Content and collaborative filtering techniques are then used to identify a diverse set of stakeholders for a given topic. The approach, which can be used to support requirements related activities throughout the software development lifecycle, is illus trated through an example of an Amazonlike student webportal.
{"title":"A Machine Learning Approach for Identifying Expert Stakeholders","authors":"Carlos Castro-Herrera, J. Cleland-Huang","doi":"10.1109/MARK.2009.1","DOIUrl":"https://doi.org/10.1109/MARK.2009.1","url":null,"abstract":"Requirements gathering, analysis, and specification are humanintensive activities that rely upon finding and engaging a relevant set of informed stakeholders. In many projects initial requirements are captured through the use of wikis or forums, or through ini tial facetoface brainstorming meetings. In this paper we introduce a technique for analyzing stakeholders' contributions, extracting domain topics, and construct ing profiles which depict stakeholders' interests in each of the topics. Content and collaborative filtering techniques are then used to identify a diverse set of stakeholders for a given topic. The approach, which can be used to support requirements related activities throughout the software development lifecycle, is illus trated through an example of an Amazonlike student webportal.","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"120 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123245225","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}
This paper is a thought experiment in finding struc tures for the elicitation of requirements on top of struc tures for retrieving requirements. We transfer from structures used by the German sociologist Niklas Luhmann, who applied a wooden slip box to collect notes on processed literature. Each slip contains bib liographic information and Luhmann's thoughts to the referenced content. In this paper we propose to use Luhmann's slip box approach for requirements engi neering, by enhancing it to a multi user suited to sort requirements in a requirements repository.
{"title":"Luhmann's Slip Box -- What can we Learn from the Device for Knowledge Representation in Requirements Engineering?","authors":"Andreas Faatz, B. Zimmermann, E. Godehardt","doi":"10.1109/MARK.2009.6","DOIUrl":"https://doi.org/10.1109/MARK.2009.6","url":null,"abstract":"This paper is a thought experiment in finding struc tures for the elicitation of requirements on top of struc tures for retrieving requirements. We transfer from structures used by the German sociologist Niklas Luhmann, who applied a wooden slip box to collect notes on processed literature. Each slip contains bib liographic information and Luhmann's thoughts to the referenced content. In this paper we propose to use Luhmann's slip box approach for requirements engi neering, by enhancing it to a multi user suited to sort requirements in a requirements repository.","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"55 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122841095","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}
Ricardo Gacitúa, Lin Ma, B. Nuseibeh, P. Piwek, A. Roeck, M. Rouncefield, P. Sawyer, A. Willis, H. Yang
The importance of tacit knowledge in Requirements Engineering (RE) is widely acknowledged. While valuable work has developed techniques to expose sources of tacit knowledge during requirements elicitation, such techniques are not universally applied and tacit knowledge, continues to negatively affect the quality of the requirements. In this position paper we present a brief review and interpretation of the literature on tacit knowledge that, we believe, is useful for RE. We describe a number of techniques that offer analysts the means to reason about the effect of tacit knowledge and improve the quality of requirements and their management.
{"title":"Making Tacit Requirements Explicit","authors":"Ricardo Gacitúa, Lin Ma, B. Nuseibeh, P. Piwek, A. Roeck, M. Rouncefield, P. Sawyer, A. Willis, H. Yang","doi":"10.1109/MARK.2009.7","DOIUrl":"https://doi.org/10.1109/MARK.2009.7","url":null,"abstract":"The importance of tacit knowledge in Requirements Engineering (RE) is widely acknowledged. While valuable work has developed techniques to expose sources of tacit knowledge during requirements elicitation, such techniques are not universally applied and tacit knowledge, continues to negatively affect the quality of the requirements. In this position paper we present a brief review and interpretation of the literature on tacit knowledge that, we believe, is useful for RE. We describe a number of techniques that offer analysts the means to reason about the effect of tacit knowledge and improve the quality of requirements and their management.","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"53 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124034347","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":"Reasoning on Requirements Knowledge to Support Creativity","authors":"Klaus Schmid","doi":"10.1109/MARK.2009.10","DOIUrl":"https://doi.org/10.1109/MARK.2009.10","url":null,"abstract":"40990007","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131011085","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}
The success of very large product lines systems with globally distributed stakeholders often builds significantly on the implicit knowledge of individuals. Final products are typically built by integrating numerous detailed specifi cations of subsystems. But how exactly all these parts can and need to be integrated to build valid end products is often left unspecified and to numerous discussions, reviews and the expertise of senior architects and product managers. Building a highlevel product line requirements model that explicitly and formally specifies common and vari able requirements, their precise integration semantics and the constraints for selecting variable features helps signif icantly to manage this crucial and often tacit requirements knowledge. Based on an industrial exemplar we motivate and demonstrate such an approach and discuss our early findings regarding knowledge and rationale management in product line requirements engineering.
{"title":"Modeling and Managing Tacit Product Line Requirements Knowledge","authors":"Reinhard Stoiber, M. Glinz","doi":"10.1109/MARK.2009.8","DOIUrl":"https://doi.org/10.1109/MARK.2009.8","url":null,"abstract":"The success of very large product lines systems with globally distributed stakeholders often builds significantly on the implicit knowledge of individuals. Final products are typically built by integrating numerous detailed specifi cations of subsystems. But how exactly all these parts can and need to be integrated to build valid end products is often left unspecified and to numerous discussions, reviews and the expertise of senior architects and product managers. Building a highlevel product line requirements model that explicitly and formally specifies common and vari able requirements, their precise integration semantics and the constraints for selecting variable features helps signif icantly to manage this crucial and often tacit requirements knowledge. Based on an industrial exemplar we motivate and demonstrate such an approach and discuss our early findings regarding knowledge and rationale management in product line requirements engineering.","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"70 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129656939","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}
We present the results of our field study that describe how requirements validation was performed at an industrial software company using agile software practices. As is common in agile processes, the team did not capture requirements knowledge in a comprehensive specification document. Instead, requirements knowledge was captured in user stories, automated acceptance tests, personal notes, and conversations. Validation was performed continuously, during preiteration, iteration planning, and intra iteration using mainly conversations. Validation was also collaborative and involved all team members, including the Product Owner, programmers, and testers. The results of our field study have implications for both agile and validation methods. This successful arrangement of agile practices is instructive for agile practitioners and for researchers studying validation.
{"title":"Continuous and Collaborative Validation: A Field Study of Requirements Knowledge in Agile","authors":"R. Gallardo-Valencia, S. Sim","doi":"10.1109/MARK.2009.3","DOIUrl":"https://doi.org/10.1109/MARK.2009.3","url":null,"abstract":"We present the results of our field study that describe how requirements validation was performed at an industrial software company using agile software practices. As is common in agile processes, the team did not capture requirements knowledge in a comprehensive specification document. Instead, requirements knowledge was captured in user stories, automated acceptance tests, personal notes, and conversations. Validation was performed continuously, during preiteration, iteration planning, and intra iteration using mainly conversations. Validation was also collaborative and involved all team members, including the Product Owner, programmers, and testers. The results of our field study have implications for both agile and validation methods. This successful arrangement of agile practices is instructive for agile practitioners and for researchers studying validation.","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133826903","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}
Lin Ma, B. Nuseibeh, P. Piwek, A. Roeck, A. Willis
Tacit knowledge in requirements documents can lead to miscommunication between software engineers and
需求文档中的隐性知识可能导致软件工程师和客户之间的错误沟通
{"title":"On Presuppositions in Requirements","authors":"Lin Ma, B. Nuseibeh, P. Piwek, A. Roeck, A. Willis","doi":"10.1109/MARK.2009.9","DOIUrl":"https://doi.org/10.1109/MARK.2009.9","url":null,"abstract":"Tacit knowledge in requirements documents can lead to miscommunication between software engineers and","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"140 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115591790","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}
Properly dealing with nonfunctional requirements (NFRs) such as security, cost, and usability, requires a large body of knowledge. However, it is difficult for average requirements engineers to possess necessary knowledge and use it correctly. This paper presents an NFR pattern framework for capturing NFR knowledge using goal, problem, causal attribution, solution/means, and requirements patterns that can be reused to help produce earlyphase and latephase NFR related requirements. The NFR patterns may be organized using generalization, aggregation, and classification relationships. Reusing the patterns is defined in terms of search and apply operations. The approach is illustrated using a running example based on the TJX incident, the largest credit card theft in history, to demonstrate how knowledge of the incident and mitigation techniques from security standards could be captured and used to help understand and prevent such incident.
{"title":"Capturing, Organizing, and Reusing Knowledge of NFRs: An NFR Pattern Approach","authors":"Sam Supakkul, Tom Hill, E. Oladimeji, L. Chung","doi":"10.1109/MARK.2009.2","DOIUrl":"https://doi.org/10.1109/MARK.2009.2","url":null,"abstract":"Properly dealing with nonfunctional requirements (NFRs) such as security, cost, and usability, requires a large body of knowledge. However, it is difficult for average requirements engineers to possess necessary knowledge and use it correctly. This paper presents an NFR pattern framework for capturing NFR knowledge using goal, problem, causal attribution, solution/means, and requirements patterns that can be reused to help produce earlyphase and latephase NFR related requirements. The NFR patterns may be organized using generalization, aggregation, and classification relationships. Reusing the patterns is defined in terms of search and apply operations. The approach is illustrated using a running example based on the TJX incident, the largest credit card theft in history, to demonstrate how knowledge of the incident and mitigation techniques from security standards could be captured and used to help understand and prevent such incident.","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126166833","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
扫码关注我们
求助内容：
应助结果提醒方式：