A domain model based requirements engineering approach has proven to be helpful when developing software
在开发软件时，基于需求工程的领域模型被证明是很有帮助的
{"title":"How to Keep Domain Requirements Models Reasonably Sized","authors":"H. Nissen, D. Schmitz, M. Jarke, T. Rose","doi":"10.1109/MARK.2009.5","DOIUrl":"https://doi.org/10.1109/MARK.2009.5","url":null,"abstract":"A domain model based requirements engineering approach has proven to be helpful when developing software","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"21 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":"126146812","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}
Crediting requirements in a modeling process is a complex activity. Combining modeling and requirement processes is essential since the correctness of the resulting system is determined with respect to the initial requirements. Based on a dedicated metamodel for managing requirements throughout the modeling process, we have now adapted a UML2 modeling tool for use with such requirement models. This tool has been evaluated by implementing it in an industrial case study. Keywords: UML2 requirement modeling, requirement traceability, requirement verification, changes management.
{"title":"The Papyrus Tool as an Eclipse UML2-modeling Environment for Requirements","authors":"H. Dubois, F. Lakhal, S. Gérard","doi":"10.1109/MARK.2009.11","DOIUrl":"https://doi.org/10.1109/MARK.2009.11","url":null,"abstract":"Crediting requirements in a modeling process is a complex activity. Combining modeling and requirement processes is essential since the correctness of the resulting system is determined with respect to the initial requirements. Based on a dedicated metamodel for managing requirements throughout the modeling process, we have now adapted a UML2 modeling tool for use with such requirement models. This tool has been evaluated by implementing it in an industrial case study. Keywords: UML2 requirement modeling, requirement traceability, requirement verification, changes management.","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"12 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":"115880189","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 a recent study of a product line, we found that the defect reports both (1) captured new requirements information and (2) implicated undocumented, tacit requirements information in the occurrence of the defects. We report four types of requirements knowledge revealed by software defect reports from integration and system testing for two products in this highdependability product line. We argue that storeandretrievebased requirements management is insufficient to avoid recurrence of these types of defects on upcoming members of the product line. We then propose the use of two mechanisms not traditionally associated with requirements management, one formal and one informal, to improve communication of these types of requirements knowledge to developers of future products in the product line. We show how the two proposed mechanisms, namely feature models extended with assumption specifications (formal) and structured anecdotes of paradigmatic productline defects (informal), can together improve propagation of the requirements knowledge exposed by these defects to future products in the product line.
{"title":"Using Defect Reports to Build Requirements Knowledge in Product Lines","authors":"R. Lutz, N. Rouquette","doi":"10.1109/MARK.2009.13","DOIUrl":"https://doi.org/10.1109/MARK.2009.13","url":null,"abstract":"In a recent study of a product line, we found that the defect reports both (1) captured new requirements information and (2) implicated undocumented, tacit requirements information in the occurrence of the defects. We report four types of requirements knowledge revealed by software defect reports from integration and system testing for two products in this highdependability product line. We argue that storeandretrievebased requirements management is insufficient to avoid recurrence of these types of defects on upcoming members of the product line. We then propose the use of two mechanisms not traditionally associated with requirements management, one formal and one informal, to improve communication of these types of requirements knowledge to developers of future products in the product line. We show how the two proposed mechanisms, namely feature models extended with assumption specifications (formal) and structured anecdotes of paradigmatic productline defects (informal), can together improve propagation of the requirements knowledge exposed by these defects to future products in the product line.","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"34 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":"134429746","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}
Leif Singer, Olesia Brill, Sebastian Meyer, K. Schneider
IT ecosystems are ultralargescale software systems that consist of various, constantly interacting and partly autonomous subsystems as well as the users of the overall system. Because of their strong integration with everyday life, these systems are often not even perceived as IT systems by its users. This is a problem for requirements engineering, as users might not know of or may not be interested in the capabilities of the system at all. This hinders the ongoing development of the system and might prevent new kinds of utilization and new business models from being realized. By introducing rules into the infrastructure of IT ecosystems that are being monitored for adherence by agents interacting in the system, deviations from these rules can be harnessed for finding potential candidates for new or changed requirements. The deviations can be processed using techniques like data mining and pattern recognition and then forwarded to requirements engineers for review. They may then leverage these implicitly expressed requirements to identify actual changes in the needs of the users of the systems, enabling further advancements of the IT ecosystem.
{"title":"Utilizing Rule Deviations in IT Ecosystems for Implicit Requirements Elicitation","authors":"Leif Singer, Olesia Brill, Sebastian Meyer, K. Schneider","doi":"10.1109/MARK.2009.14","DOIUrl":"https://doi.org/10.1109/MARK.2009.14","url":null,"abstract":"IT ecosystems are ultralargescale software systems that consist of various, constantly interacting and partly autonomous subsystems as well as the users of the overall system. Because of their strong integration with everyday life, these systems are often not even perceived as IT systems by its users. This is a problem for requirements engineering, as users might not know of or may not be interested in the capabilities of the system at all. This hinders the ongoing development of the system and might prevent new kinds of utilization and new business models from being realized. By introducing rules into the infrastructure of IT ecosystems that are being monitored for adherence by agents interacting in the system, deviations from these rules can be harnessed for finding potential candidates for new or changed requirements. The deviations can be processed using techniques like data mining and pattern recognition and then forwarded to requirements engineers for review. They may then leverage these implicitly expressed requirements to identify actual changes in the needs of the users of the systems, enabling further advancements of the IT ecosystem.","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"24 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":"134219098","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
扫码关注我们
求助内容：
应助结果提醒方式：