Pub Date : 2009-05-19DOI: 10.1109/WIKIS4SE.2009.5069992
Thomas Riechert, T. Berger
Using Wikis for the collaborative creation of structured textual content has gained increasing importance in the past decade. As Wikis facilitate the involvement of large user groups to create content in an easy way, their application in large, spatially distributed software development efforts seems to be very promising. In this context, we present a classification of Wiki-based approaches to Requirements Engineering (RE) and discuss their suitability. Next, we introduce the ontology of an approach that aims at supporting the collaboration of stakeholders with regard to the RE process. This approach enables large stakeholder groups to elicit, semantically structure and classify requirements in the very early and creative RE phases. Instead of leveraging text-based Wikis, the approach is based on our semantic data Wiki OntoWiki, which focuses on the structuring and management of fine-grained data by employing Semantic Web technologies. OntoWiki enables the intuitive authoring of Knowledge Bases and facilitates the application of Knowledge Management methods.
{"title":"Leveraging semantic data Wikis for distributed requirements elicitation","authors":"Thomas Riechert, T. Berger","doi":"10.1109/WIKIS4SE.2009.5069992","DOIUrl":"https://doi.org/10.1109/WIKIS4SE.2009.5069992","url":null,"abstract":"Using Wikis for the collaborative creation of structured textual content has gained increasing importance in the past decade. As Wikis facilitate the involvement of large user groups to create content in an easy way, their application in large, spatially distributed software development efforts seems to be very promising. In this context, we present a classification of Wiki-based approaches to Requirements Engineering (RE) and discuss their suitability. Next, we introduce the ontology of an approach that aims at supporting the collaboration of stakeholders with regard to the RE process. This approach enables large stakeholder groups to elicit, semantically structure and classify requirements in the very early and creative RE phases. Instead of leveraging text-based Wikis, the approach is based on our semantic data Wiki OntoWiki, which focuses on the structuring and management of fine-grained data by employing Semantic Web technologies. OntoWiki enables the intuitive authoring of Knowledge Bases and facilitates the application of Knowledge Management methods.","PeriodicalId":202257,"journal":{"name":"2009 ICSE Workshop on Wikis for Software Engineering","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129082051","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 : 2009-05-19DOI: 10.1109/WIKIS4SE.2009.5069999
Jingyue Li, Claudia P. Ayala, R. Conradi
IT companies are confronted with a huge, growing Off-the-Shelf (OTS) marketplace containing incredibly large amount of diverse, partial, ephemeral, sometimes tacit and not always trustable information about OTS components. Our empirical studies illustrate that different users, such as OTS evaluator, OTS integrator, system tester, and system maintainer, need different information and knowledge about OTS components when facing different scenarios. Although a few companies are using mini-wikis internally to manage and share OTS related knowledge, knowledge sharing across companies is rare. Searching existing web portals or sites of OTS components is time consuming and often does not bring systematic knowledge. This position paper proposes role-based wikis to organize OTS components related knowledge in a systematic way. One motivation of constructing such a wiki is to provide necessary knowledge for different users to help them reduce risks. Another motivation is to provide a global centralized platform, so that OTS users can systematically share their knowledge across organizations.
{"title":"Role-based wiki for reuse of Off-the-Shelf Components","authors":"Jingyue Li, Claudia P. Ayala, R. Conradi","doi":"10.1109/WIKIS4SE.2009.5069999","DOIUrl":"https://doi.org/10.1109/WIKIS4SE.2009.5069999","url":null,"abstract":"IT companies are confronted with a huge, growing Off-the-Shelf (OTS) marketplace containing incredibly large amount of diverse, partial, ephemeral, sometimes tacit and not always trustable information about OTS components. Our empirical studies illustrate that different users, such as OTS evaluator, OTS integrator, system tester, and system maintainer, need different information and knowledge about OTS components when facing different scenarios. Although a few companies are using mini-wikis internally to manage and share OTS related knowledge, knowledge sharing across companies is rare. Searching existing web portals or sites of OTS components is time consuming and often does not bring systematic knowledge. This position paper proposes role-based wikis to organize OTS components related knowledge in a systematic way. One motivation of constructing such a wiki is to provide necessary knowledge for different users to help them reduce risks. Another motivation is to provide a global centralized platform, so that OTS users can systematically share their knowledge across organizations.","PeriodicalId":202257,"journal":{"name":"2009 ICSE Workshop on Wikis for Software Engineering","volume":"19 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132729725","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 : 2009-05-19DOI: 10.1109/WIKIS4SE.2009.5069995
C. Solís, Nour Ali, M. Babar
The absence of a disciplined approach for capturing and managing architectural knowledge causes the loss of substantial knowledge generated during the software architecture process. This paper describes the use of a Spatial Hypertext Wiki (ShyWiki) as a tool for Architectural Knowledge Management (AKM) support. Specifically, we demonstrate that ShyWiki can be used for implementing lightweight knowledge sharing workspaces, which includes AKM tools, decision support facilities, and activity awareness features. We also describe how distributed stakeholders involved in the software architecting process can share knowledge and manage their tasks by various features provided by ShyWiki.
{"title":"A Spatial Hypertext Wiki for Architectural Knowledge Management","authors":"C. Solís, Nour Ali, M. Babar","doi":"10.1109/WIKIS4SE.2009.5069995","DOIUrl":"https://doi.org/10.1109/WIKIS4SE.2009.5069995","url":null,"abstract":"The absence of a disciplined approach for capturing and managing architectural knowledge causes the loss of substantial knowledge generated during the software architecture process. This paper describes the use of a Spatial Hypertext Wiki (ShyWiki) as a tool for Architectural Knowledge Management (AKM) support. Specifically, we demonstrate that ShyWiki can be used for implementing lightweight knowledge sharing workspaces, which includes AKM tools, decision support facilities, and activity awareness features. We also describe how distributed stakeholders involved in the software architecting process can share knowledge and manage their tasks by various features provided by ShyWiki.","PeriodicalId":202257,"journal":{"name":"2009 ICSE Workshop on Wikis for Software Engineering","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133979484","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 : 2009-05-19DOI: 10.1109/WIKIS4SE.2009.5069993
L. Abeti, P. Ciancarini, Rocco Moretti
This paper presents WikiReq, a project exploiting the Semantic Mediawiki to manage both system and organizational requirements in the context of Business Process Reengineering (BPR). Our work is based on three ideas: 1) using a semantic wiki for requirements elicitation and management; 2) exploiting the wiki platform to define an argumentation system for both synchronous and asynchronous discussions among stakeholders; 3) achieving interoperability between the semantic wiki and an Integrated Development Environment (IDE) platform like Eclipse. Thus, we show how requirements acquired by the Semantic Mediawiki can be exported in the Eclipse IDE in order to partially automate the translation of organizational business processes and system artifacts from the requirements description. In order to perform such a translation we use WikiReq in the context of the Enterprise-Service-Implementation (ESI) method that we have defined. We present the WikiReq tool highlighting its relationships with model driven engineering and business process modeling.
{"title":"Wiki-based requirements management for Business Process Reengineering","authors":"L. Abeti, P. Ciancarini, Rocco Moretti","doi":"10.1109/WIKIS4SE.2009.5069993","DOIUrl":"https://doi.org/10.1109/WIKIS4SE.2009.5069993","url":null,"abstract":"This paper presents WikiReq, a project exploiting the Semantic Mediawiki to manage both system and organizational requirements in the context of Business Process Reengineering (BPR). Our work is based on three ideas: 1) using a semantic wiki for requirements elicitation and management; 2) exploiting the wiki platform to define an argumentation system for both synchronous and asynchronous discussions among stakeholders; 3) achieving interoperability between the semantic wiki and an Integrated Development Environment (IDE) platform like Eclipse. Thus, we show how requirements acquired by the Semantic Mediawiki can be exported in the Eclipse IDE in order to partially automate the translation of organizational business processes and system artifacts from the requirements description. In order to perform such a translation we use WikiReq in the context of the Enterprise-Service-Implementation (ESI) method that we have defined. We present the WikiReq tool highlighting its relationships with model driven engineering and business process modeling.","PeriodicalId":202257,"journal":{"name":"2009 ICSE Workshop on Wikis for Software Engineering","volume":"97 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116032669","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 : 2009-05-19DOI: 10.1109/WIKIS4SE.2009.5070000
Ammy Jiranida Phuwanartnurak
The success of a software development project often requires collaboration among various disciplines because, in general, individual members from a single discipline do not have all of the information, knowledge, and expertise needed to produce successful software. Interdisciplinary collaboration has created challenges in software development due to the difficulty in communicating and coordinating across disciplines. The use of wikis seems to be growing rapidly as groups and organizations are turning to the use of wikis to solve these challenges. Although wikis have been claimed to support collaboration and information sharing, the backing for this claim has not been rigorously assessed. In this paper, I describe an exploratory study of the use of wikis for information sharing in two web application development teams. The study results will help us understand how wikis are used and how they may enable successful interdisciplinary collaboration in software development.
{"title":"Interdisciplinary collaboration through wikis in software development","authors":"Ammy Jiranida Phuwanartnurak","doi":"10.1109/WIKIS4SE.2009.5070000","DOIUrl":"https://doi.org/10.1109/WIKIS4SE.2009.5070000","url":null,"abstract":"The success of a software development project often requires collaboration among various disciplines because, in general, individual members from a single discipline do not have all of the information, knowledge, and expertise needed to produce successful software. Interdisciplinary collaboration has created challenges in software development due to the difficulty in communicating and coordinating across disciplines. The use of wikis seems to be growing rapidly as groups and organizations are turning to the use of wikis to solve these challenges. Although wikis have been claimed to support collaboration and information sharing, the backing for this claim has not been rigorously assessed. In this paper, I describe an exploratory study of the use of wikis for information sharing in two web application development teams. The study results will help us understand how wikis are used and how they may enable successful interdisciplinary collaboration in software development.","PeriodicalId":202257,"journal":{"name":"2009 ICSE Workshop on Wikis for Software Engineering","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130511386","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 : 2009-05-19DOI: 10.1109/WIKIS4SE.2009.5069991
Y. Ben-Chaim, E. Farchi, O. Raz
A major problem in the software development process is that design documents are rarely kept up-to-date with the implementation, and thus become irrelevant for extracting test plans or reviews. Furthermore, design documents tend to become very long and often impossible to review and comprehend.
{"title":"An effective method for keeping design artifacts up-to-date","authors":"Y. Ben-Chaim, E. Farchi, O. Raz","doi":"10.1109/WIKIS4SE.2009.5069991","DOIUrl":"https://doi.org/10.1109/WIKIS4SE.2009.5069991","url":null,"abstract":"A major problem in the software development process is that design documents are rarely kept up-to-date with the implementation, and thus become irrelevant for extracting test plans or reviews. Furthermore, design documents tend to become very long and often impossible to review and comprehend.","PeriodicalId":202257,"journal":{"name":"2009 ICSE Workshop on Wikis for Software Engineering","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130424587","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 : 2009-05-19DOI: 10.1109/WIKIS4SE.2009.5069997
Eric Ras, Sebastian Weber
Software engineering (SE) is a highly collaborative and knowledge-intensive process involving a large number of different roles. On the one hand, it highly depends on efficient management of and access to various kinds of information about SE artifacts, processes, and knowledge, such as explicitly documented experiences. On the other hand, software engineers need to continuously learn while performing SE activities. This paper describes the underlying concept of the Flex-based wiki platform SOP, which aims at supporting the creation, storage, and exchange of SE information. One specific SOP extension called learning space generation is described in more detail: It enriches documented SE experiences with additional learning content and hence presents one effective way of integrating organizational and individual learning at the workplace. In addition, evaluation results and improvement suggestions for future work are provided.
{"title":"Software organization platform: Integrating organizational and individual learning","authors":"Eric Ras, Sebastian Weber","doi":"10.1109/WIKIS4SE.2009.5069997","DOIUrl":"https://doi.org/10.1109/WIKIS4SE.2009.5069997","url":null,"abstract":"Software engineering (SE) is a highly collaborative and knowledge-intensive process involving a large number of different roles. On the one hand, it highly depends on efficient management of and access to various kinds of information about SE artifacts, processes, and knowledge, such as explicitly documented experiences. On the other hand, software engineers need to continuously learn while performing SE activities. This paper describes the underlying concept of the Flex-based wiki platform SOP, which aims at supporting the creation, storage, and exchange of SE information. One specific SOP extension called learning space generation is described in more detail: It enriches documented SE experiences with additional learning content and hence presents one effective way of integrating organizational and individual learning at the workplace. In addition, evaluation results and improvement suggestions for future work are provided.","PeriodicalId":202257,"journal":{"name":"2009 ICSE Workshop on Wikis for Software Engineering","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125404708","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 : 2009-05-19DOI: 10.1109/WIKIS4SE.2009.5069994
E. Knauss, Olesia Brill, I. Kitzmann, Thomas Flohr
Requirements engineering is the refinement of stakeholder wishes to more or less formal requirements. Nowadays this refinement is often done in a distributed environment. In this collaborative setting Wikis are generally helpful. However, without explicit support, it is hard to achieve high quality efficiently. A smart wiki can assume responsibility of these tasks. Our SmartWiki generates context- (and process-) sensitive feedback on requirements. It automatically checks consistence and integrates constructive and analytical quality assurance in a wiki. It also helps to manage tasks, responsibilities, and experiences for organizational learning. In this paper we present our SmartWiki approach and our experiences gathered from several projects in educational and industry projects.
{"title":"SmartWiki: Support for high-quality requirements engineering in a collaborative setting","authors":"E. Knauss, Olesia Brill, I. Kitzmann, Thomas Flohr","doi":"10.1109/WIKIS4SE.2009.5069994","DOIUrl":"https://doi.org/10.1109/WIKIS4SE.2009.5069994","url":null,"abstract":"Requirements engineering is the refinement of stakeholder wishes to more or less formal requirements. Nowadays this refinement is often done in a distributed environment. In this collaborative setting Wikis are generally helpful. However, without explicit support, it is hard to achieve high quality efficiently. A smart wiki can assume responsibility of these tasks. Our SmartWiki generates context- (and process-) sensitive feedback on requirements. It automatically checks consistence and integrates constructive and analytical quality assurance in a wiki. It also helps to manage tasks, responsibilities, and experiences for organizational learning. In this paper we present our SmartWiki approach and our experiences gathered from several projects in educational and industry projects.","PeriodicalId":202257,"journal":{"name":"2009 ICSE Workshop on Wikis for Software Engineering","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123347442","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 : 2009-05-19DOI: 10.1109/WIKIS4SE.2009.5069996
Eric Ras
Even though Wikis have made their way into software engineering practice, the number of empirical evaluations is not significant enough yet to make a statement on which software engineering phases wikis should be used for. This is also due to facts that wikis and related Web technologies are evolving fast and that a lot of effort is spent on developing new, innovative wiki-based solutions for specific software engineering activities. Therefore, two case studies were conducted in which wikis were used as a technology for communication, documentation, and knowledge sharing. Based on the subjective judgments of undergraduate and graduate students, wikis were evaluated as most efficient for sharing software engineering experiences and project management related information. In addition, both case studies shed light on the kind of information that was shared most and on its quality for reuse. The findings helped us to enhance the so-called wiki-based Software Organization Platform.
{"title":"Investigating Wikis for software engineering - Results of two case studies","authors":"Eric Ras","doi":"10.1109/WIKIS4SE.2009.5069996","DOIUrl":"https://doi.org/10.1109/WIKIS4SE.2009.5069996","url":null,"abstract":"Even though Wikis have made their way into software engineering practice, the number of empirical evaluations is not significant enough yet to make a statement on which software engineering phases wikis should be used for. This is also due to facts that wikis and related Web technologies are evolving fast and that a lot of effort is spent on developing new, innovative wiki-based solutions for specific software engineering activities. Therefore, two case studies were conducted in which wikis were used as a technology for communication, documentation, and knowledge sharing. Based on the subjective judgments of undergraduate and graduate students, wikis were evaluated as most efficient for sharing software engineering experiences and project management related information. In addition, both case studies shed light on the kind of information that was shared most and on its quality for reuse. The findings helped us to enhance the so-called wiki-based Software Organization Platform.","PeriodicalId":202257,"journal":{"name":"2009 ICSE Workshop on Wikis for Software Engineering","volume":"80 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116792980","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 : 2009-05-01DOI: 10.1109/WIKIS4SE.2009.5069998
Marios Fokaefs, K. Bauer, Eleni Stroulia
Most software development today is a team activity. Project team members collaboratively work on the tasks necessary to accomplish the various project milestones. The work is usually asynchronous, i.e., not orchestrated by an explicit workflow, some times geographically distributed, and involves the use of a variety of tools which do not always interoperate. Version-control repositories are essential in supporting this collaboration but cannot satisfactorily address the problem of traceability of interdependencies among the artifacts produced by the individual tools. In this demo, we present a new collaboration tool, WikiDev 2.0, that proposes to address these problems by adopting a wiki as the central platform in which to integrate information about the various artifacts of interest and to present views on this information that cut across the individual tool boundaries. We believe that WikiDev 2.0 will advance the degree of each individual team-member's awareness of the status of the project, thus better supporting the overall team collaboration.
{"title":"WikiDev 2.0: Web-based software team collaboration","authors":"Marios Fokaefs, K. Bauer, Eleni Stroulia","doi":"10.1109/WIKIS4SE.2009.5069998","DOIUrl":"https://doi.org/10.1109/WIKIS4SE.2009.5069998","url":null,"abstract":"Most software development today is a team activity. Project team members collaboratively work on the tasks necessary to accomplish the various project milestones. The work is usually asynchronous, i.e., not orchestrated by an explicit workflow, some times geographically distributed, and involves the use of a variety of tools which do not always interoperate. Version-control repositories are essential in supporting this collaboration but cannot satisfactorily address the problem of traceability of interdependencies among the artifacts produced by the individual tools. In this demo, we present a new collaboration tool, WikiDev 2.0, that proposes to address these problems by adopting a wiki as the central platform in which to integrate information about the various artifacts of interest and to present views on this information that cut across the individual tool boundaries. We believe that WikiDev 2.0 will advance the degree of each individual team-member's awareness of the status of the project, thus better supporting the overall team collaboration.","PeriodicalId":202257,"journal":{"name":"2009 ICSE Workshop on Wikis for Software Engineering","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128933214","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
扫码关注我们
求助内容：
应助结果提醒方式：