Vol.1 No.2 2008

32/85

Research paper : Realization of a collaboration system for everyone to develop and manage (K. Eto et al.)−101 Synthesiology - English edition Vol.1 No.2 (2008) development, trial run of qwikWeb, and writing.Masahiro HamasakiGraduated from Faculty of Engineering, Doshisha University in 2000. Completed master’s program at Graduate School of Information Science, Nara Institute of Science and Technology in 2002. Completed doctorate program at School of Mathematical and Physical Science, Graduate University for Advanced Studies in 2005. Doctor of Science (Information Science). Joined the Information Technology Research Institute, AIST in 2005. Works on information commendation and online community. Interested in information system utilizing human network. Member of the Information Processing Society of Japan (IPS); The Institute of Electronics, Information and Communication Engineers (IEICE); and The Association for Computing Machinery (ACM). In this paper, worked mainly on data analysis of qwikWeb trial run and writing.Takuichi NishimuraCompleted master’s degree (Measurement Engineering) at Faculty of Engineering, The University of Tokyo in 1992. Joined NKK in 1992. Worked on R&D for x-ray and sound/vibration control. Dispatched to the Real World Computing Project (RWCP) Tsukuba Research Center in 1995. Returned to NKK in 1998. Joined the RWCP Tsukuba Research Center in 1999. Joined the Cyber Assist Research Center, AIST in 2001. Became leader of Real-World Interaction Group, Information Technology Research Institute, AIST in 2005. Also works as assistant professor of Department of Intelligent Interaction Technologies, Graduate School of Systems and Information Engineering, University of Tsukuba. Doctor of Engineering (Engineering). Interested in time-course data search/identification and real world information support. Member of the Information Processing Society of Japan (IPS); The Institute of Electronics, Information and Communication Engineers (IEICE); The Japanese Society for Artificial Intelligence; Human Interface Society; The Japan Society of Infrared Science and Technology; and The Association for Computing Machinery (ACM). In this paper, mainly worked on positioning of the research, theoretical development, and writing.Discussion with reviewers1 On improvements for user participationQuestion (Kazuhito Ohmaki)I think the perspective that “it is very important to have a mechanism where end users can become directly involved in system design” is important, and I think this point should be clearly stated.Answer (Kouichirou Eto)As you indicated, since the improvement process with involvement of users is important in information systems, I explained further in “2. Full Research for web system.” Although direct involvement of end users is very important, in this development, we employed a method where the users use the system, we, the developers, observed them carefully, and then we thought of the necessary functions based on our observations. Since users are novice of the system, they cannot necessarily propose truly necessary functions. However, since end users are specialists in their own respective work, the developers determined the necessary functions based on their work processes. This point was described in Chapter 2.2 On rights of softwareQuestion (Kazuhito Ohmaki)Have you clarified the rights for qwikWeb?Answer (Kouichirou Eto)The people who were involved in direct development of qwikWeb were AIST researchers only, and the relationship of rights is clear. Although QuickML had been used as part of the system, it is disclosed as free software based on General Public License (GPL). qwikWeb also is under GPL, there is no rights issue.3 On learning how to use softwaresQuestion (Kazuhito Ohmaki)Having used Wiki, the Reviewer feels that although simple, one must learn “pattern language” to some point. I would like to hear your comments on what you think of the trade-off.Answer (Kouichirou Eto)Thank you for pointing this out. First, although pattern language is background philosophy of Wiki, it does not mean that one cannot use Wiki without learning it. Anyone can start using it by learning the simple maneuvers. To make full use of Wiki, one must learn pattern language to some extent, as you point out. That means that one must learn the background philosophy of Wiki, but one can learn it gradually. In other words, by using Wiki, one can gradually become acquainted with the philosophy of pattern language, and that is one advantage of Wiki.In Wiki, it is necessary to express the sentence structure by using Wiki syntax, which is its unique mark-up language, and the time required to learn this could not be ignored. However, by writing sentences using Wiki syntax, one becomes conscious of the sentence structure. In fact, when I teach Wiki in college courses, by teaching Wiki as well as advantage of structuring sentences at the same time, the students were able to learn Wiki syntax naturally. Such trade-off does exist for Wiki syntax.As you pointed out, concerning this point, I added explanations.4 On goal of development, scenario, and selection process of componentQuestion (Motoyuki Akamatsu)In the last part of Section 2.3, you mention four points. Explanations assumed the fusion of ML and Wiki, except in the first point. I think it will be better to write a scenario by describing the four points as four goals of system design, and then to write that the Authors decided to fuse ML and Wiki after considering how to achieve the goals (Description of Scenario). Also, there must have been a selection process of component, and I think you should write the “selection process” where certain technologies other than ML and Wiki were not employed.Answer (Kouichirou Eto)The scenario, as you point out, was not clear in the original paper, so the chapters were arranged according to the process in Figure 1, and changed to reflect the flow of development from problems and solution strategy of current collaboration (“ease of management” and “accumulation and structuring of knowledge”), basic philosophy toward solution, selection of Wiki that had concept close to our basic philosophy, and employment of QuickML in basic design of the system. For selection processes, the reason for selecting Wiki as component is explained in 4.1.1, Wiki is explained in 4.1.2, the reason for selecting Quick ML as component is explained in 4.21, and Quick ML is explained in 4.2.2.(29)−

※このページを正しく表示するにはFlashPlayer9以上が必要です