Özgür Ünalan, N. Riegel, Sebastian Weber, Jörg Dörr
{"title":"Using Enhanced Wiki-based Solutions for Managing Requirements","authors":"Özgür Ünalan, N. Riegel, Sebastian Weber, Jörg Dörr","doi":"10.1109/MARK.2008.10","DOIUrl":"https://doi.org/10.1109/MARK.2008.10","url":null,"abstract":"The main phases during requirements engineering include the elicitation, specification, validation, and management of requirements in order to understand what the system must do. In the age of distributed and collaborative work, suitable tools and concepts are needed to support requirements activities in this context. Based on requirements derived from basic practices of the ReqMan framework, we will introduce first solution concepts for a wiki-based requirements management tool.","PeriodicalId":319454,"journal":{"name":"2008 First International Workshop on Managing Requirements Knowledge","volume":"50 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122579633","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":"NDR Ontology: Sharing and Reusing NFR and Design Rationale Knowledge","authors":"Claudia A. López, L. M. Cysneiros, H. Astudillo","doi":"10.1109/MARK.2008.7","DOIUrl":"https://doi.org/10.1109/MARK.2008.7","url":null,"abstract":"Understanding non-functional requirements (NFR) and their solutions is a key architecture task, and reusing past solutions is an effective and efficient way to satisfy NFRs. NFR catalogues have been proposed to store and reuse NFR knowledge descriptions, yet identification of reusable knowledge inside catalogues remains quite hard and tedious. This article introduces the NDR ontology to describe NFR and design rationale knowledge, thus making it reusable and shareable via human and machine-readability. The ontology is the basis for several semantics-based applications currently under development, including view-based NFR/rationale exploration, facet-based search, and comparison of alternative solutions. Also, some approach extensions are explored, including model merging and high-end visualization of NFR knowledge.","PeriodicalId":319454,"journal":{"name":"2008 First International Workshop on Managing Requirements Knowledge","volume":"73 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115982613","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":"Recommending Terms for Glossaries: A Computer-Based Approach","authors":"E. Knauss, Sebastian Meyer, K. Schneider","doi":"10.1109/MARK.2008.8","DOIUrl":"https://doi.org/10.1109/MARK.2008.8","url":null,"abstract":"Glossaries in Software Requirements Specifications (SRS) aim at establishing a common ground of definitions. However, ambiguous terms as due to tacit knowledge are seldom captured in glossaries. In addition, even if they are captured, they are seldom read, because potential readers are convinced that they already know how the term is defined. Such misunderstandings introduce high risks in projects - especially because they are so hard to detect. Therefore, a trigger is needed to start a discussion about these potentially dangerous terms. In this paper we show how context aware requirements engineering tools can heuristically detect these terms and point out the risk attached. We introduce two simple, yet powerful heuristics: Occurence counting detects important terms, comparison with old glossaries detects terms that others found worth defining in a glossary. Thus, we make use of glossaries from past projects to suggest possible terms of interest for current projects. Our approach was implemented and applied to six software projects. Based on these experiences we show the effectivity of our heuristics and how they could be used by learning organizations to reduce such ambiguity risks in their specific domain.","PeriodicalId":319454,"journal":{"name":"2008 First International Workshop on Managing Requirements Knowledge","volume":"99 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124769033","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":"Capturing and Using Quality Attributes Knowledge in Software Architecture Evaluation Process","authors":"M. Babar, Rafael Capilla","doi":"10.1109/MARK.2008.3","DOIUrl":"https://doi.org/10.1109/MARK.2008.3","url":null,"abstract":"Architectural knowledge management approaches have paid little attention to manage knowledge about quality attributes, which are the key considerations for designing and evaluating software architecture. In this work we identify the kinds of information that needs to be captured about quality attributes with special focus on architectural design decisions. We also describe how a tool can help to capture and reuse quality attributes knowledge to improve the software architecture process.","PeriodicalId":319454,"journal":{"name":"2008 First International Workshop on Managing Requirements Knowledge","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130814865","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 Knowledge Sharing in Embedded Software Production Line","authors":"Pekka T. Savolainen, J. Sajaniemi","doi":"10.1109/MARK.2008.5","DOIUrl":"https://doi.org/10.1109/MARK.2008.5","url":null,"abstract":"A smoothly running software production line (SPL) requires consistent family-viewpoint awareness among the stakeholders through the development cycle, which in software-intensive products' engineering extends from requirements elicitation and marketing to detailed design and integration testing. To improve knowledge sharing among the stakeholders, we developed a documentation model based on feature modelling, and implemented it in a concurrent and multi-site development environment In this paper we share our experience from the field, gathered during the development and qualitative and quantitative performance analysis of this production-line kind of software development environment.","PeriodicalId":319454,"journal":{"name":"2008 First International Workshop on Managing Requirements Knowledge","volume":"45 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129100741","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":"Telos: Representing Knowledge about Control Systems?","authors":"D. Schmitz, H. Nissen, M. Jarke, T. Rose","doi":"10.1109/MARK.2008.9","DOIUrl":"https://doi.org/10.1109/MARK.2008.9","url":null,"abstract":"Telos is a formal knowledge representation language designed for the development of information systems. It has been successfully applied in many different software development projects. Although the development of control systems also includes software development, it constitutes a completely different application domain. An in-depth analysis of the development process results in a set of key characteristics of this domain. Based on this set we investigate in this paper whether the features of Telos and its implementation ConceptBase are also valuable to support the development of control systems. We first review the existing application of the Telosbased, agent- and goal-oriented language i* to requirements modelling for control systems. Then we examine carefully each single feature of Telos and ConceptBase regarding the support of the identified key characteristics. This investigation shows that nearly all characteristics are well supported and only very few require further enhancements of Telos and ConceptBase.","PeriodicalId":319454,"journal":{"name":"2008 First International Workshop on Managing Requirements Knowledge","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130592824","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":"Using the RITA Threats Ontology to Guide Requirements Elicitation: an Empirical Experiment in the Banking Sector","authors":"C. Salinesi, E. Ivankina, Willy Angole","doi":"10.1109/MARK.2008.11","DOIUrl":"https://doi.org/10.1109/MARK.2008.11","url":null,"abstract":"Eliciting requirements is an important issue of systems development projects. One particular approach to requirements elicitation is to analyse non nominal cases of systems behaviour. Non nominal behaviours can be dealt with under different perspectives such as obstacles, conflicts, or risks. RITA is a requirements elicitation method that makes use of an ontology, which englobes these different perspectives using the concept of threat. The threats ontology can be used to diagnose non nominal system behaviours, and discover new requirements to overcome them. This paper reports an empirical experiment of the RITA threats ontology in the banking sector. The experiment was undertaken with the goal to demonstrate the effectiveness of using the RITA threats ontology to discover system requirements. The paper describes the experiment, reports a few results, and raises a few questions to address in the development of ontology-based requirements engineering methods.","PeriodicalId":319454,"journal":{"name":"2008 First International Workshop on Managing Requirements Knowledge","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123245665","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":"A Dynamic Approach for Managing Stakeholder Credentials for Lightweight, Collaborative, Requirements Elicitation","authors":"Kurtis D. Todd, J. Cleland-Huang","doi":"10.1109/MARK.2008.1","DOIUrl":"https://doi.org/10.1109/MARK.2008.1","url":null,"abstract":"As software projects increase in size and complexity, and involve stakeholders across geographic and organizational boundaries, it becomes increasingly important to develop new approaches and tools for supporting distributed, collaborative and scalable requirements elicitation processes. Such processes and related tools must support relatively open and inclusive collaborations, while simultaneously constraining stakeholders' contributions according to their areas and levels of expertise. This position paper proposes a new approach that uses information retrieval methods and group dynamics to manage stakeholder credentials and provide access permissions in a dynamically evolving, open-access, requirements elicitation process.","PeriodicalId":319454,"journal":{"name":"2008 First International Workshop on Managing Requirements Knowledge","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115937546","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}
João Pedro Santos, A. Moreira, J. Araújo, Vasco Amaral, Mauricio Alférez, U. Kulesza
{"title":"Generating Requirements Analysis Models from Textual Requirements","authors":"João Pedro Santos, A. Moreira, J. Araújo, Vasco Amaral, Mauricio Alférez, U. Kulesza","doi":"10.1109/MARK.2008.4","DOIUrl":"https://doi.org/10.1109/MARK.2008.4","url":null,"abstract":"Use case modeling is a commonly used technique to describe functional requirements in requirements engineering. Typically, use cases are captured from textual requirements documents describing the functionalities the system should meet. Requirements elicitation, analysis and modeling is a time consuming and error-prone activity, which it is not usually supported by automated tools. This paper tackles this problem by taking free-form textual requirements and offering a semi-automatic process for generation of domain models, such as use cases. Our goal is twofold: (i) reduce the time spent to produce requirements artifacts; and (ii) enable future application of model-driven engineering techniques to maintain traceability information and consistency between textual and requirements visual models artifacts.","PeriodicalId":319454,"journal":{"name":"2008 First International Workshop on Managing Requirements Knowledge","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126470823","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":"ARED-CK: an Automated Requirements Elicitation Approach Based on Decision-making with Complete Knowledge","authors":"Lin Liu, Lei Lin","doi":"10.1109/MARK.2008.2","DOIUrl":"https://doi.org/10.1109/MARK.2008.2","url":null,"abstract":"Requirements elicitation, as the first phase of the software life cycle, its importance is becoming more and more prominent. How fast and accurate user requirements can be elicited, is a problem that people wants to solve for a long time. This paper proposes to establish an automated elicitation system based on domain knowledge on user requirements. By gradually perfecting and refining the original requirements description, we can acquire requirements effectively and ultimately improve the quality of requirements and the efficiency of the elicitation process. The decision-making based approach for automated requirements elicitation, ARED-CK, assumes that a fairly complete domain knowledge base is in place, based on which inquiry cycles for eliciting requirements is formulated into a decision-making problem. Through continuous interactions with the user, the requirements decision-making process use requirements models in the domain knowledge base matching with specific instances of requirements model, and ultimately identify a requirements model fit the specific purpose of the target user. Moreover, the paper put forward the proposed decision process for optimization, so that within least steps of user interaction an optimal precise requirements model can be identified.","PeriodicalId":319454,"journal":{"name":"2008 First International Workshop on Managing Requirements Knowledge","volume":"25 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121884996","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}