Proceedings of the 9th international World Wide Web conference on Computer networks : the international journal of computer and telecommunications netowrking
Using Wikis in Software Development
IEEE Software
EMF: Eclipse Modeling Framework 2.0
EMF: Eclipse Modeling Framework 2.0
Temporal Analysis of the Wikigraph
WI '06 Proceedings of the 2006 IEEE/WIC/ACM International Conference on Web Intelligence
Enabling Customer-Centricity Using Wikis and the Wiki Way
Journal of Management Information Systems
Bioinformatics
Web Engineering: Modelling and Implementing Web Applications (Human-Computer Interaction Series)
Web Engineering: Modelling and Implementing Web Applications (Human-Computer Interaction Series)
IEEE Software
STRUCTURAL SIMILARITIES OF COMPLEX NETWORKS: A COMPUTATIONAL MODEL BY EXAMPLE OF WIKI GRAPHS
Applied Artificial Intelligence
An Enhanced Wiki for Requirements Engineering
SEAA '09 Proceedings of the 2009 35th Euromicro Conference on Software Engineering and Advanced Applications
Toward standardised model to text transformations
ECMDA-FA'05 Proceedings of the First European conference on Model Driven Architecture: foundations and Applications
RubyTL: a practical, extensible transformation language
ECMDA-FA'06 Proceedings of the Second European conference on Model Driven Architecture: foundations and Applications
Building for social translucence: a domain analysis and prototype system
Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work
Hi-index | 0.00 |
Wikis are becoming mainstream. Studies confirm how wikis are finding their way into organizations. This paper focuses on requirements for analysis tools for corporate wikis. Corporate wikis differ from their grow-up counterparts such as Wikipedia. First, they tend to be much smaller. Second, they require analysis to be customized for their own domains. So far, most analysis tools focus on large wikis where handling efficiently large bulks of data is paramount. This tends to make analysis tools access directly the wiki database. This binds the tool to the wiki engine, hence, jeopardizing customizability and interoperability. However, corporate wikis are not so big while customizability is a desirable feature. This change in requirements advocates for analysis tools to be decoupled from the underlying wiki engines. Our approach argues for characterizing analysis tools in terms of their abstract analysis model (e.g. a graph model, a contributor model). How this analysis model is then map into wiki-implementation terms is left to the wiki administrator. The administrator, as the domain expert, can better assess which is the right terms/granularity to conduct the analysis. This accounts for suitability and interoperability gains. The approach is borne out for HistoryFlow, an IBM tool for visualizing evolving wiki pages and the interactions of multiple wiki authors.