Skip Navigation

IEICE Transactions on Information and Systems 2008 E91-D(4):907-920; doi:10.1093/ietisy/e91-d.4.907
This Article
Right arrow Full Text (PDF)
Right arrow References
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrow Request Permissions
Google Scholar
Right arrow Articles by SHIROGANE, J.
Right arrow Articles by FUKAZAWA, Y.
Social Bookmarking
Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

Copyright © 2008 The Institute of Electronics, Information and Communication Engineers

Special Section on Knowledge-Based Software Engineering -- Papers -- Software Engineering

GUI Change Method according to Roles of Widgets and Change Patterns

Junko SHIROGANE1, Hajime IWATA2, Kazuhiro FUKAYA2 and Yoshiaki FUKAZAWA2

1 The author is with Tokyo Woman's Christian University, Tokyo, 167–8585 Japan. E-mail: junko{at}lab.twcu.ac.jp, 2 The authors are with Waseda University, Tokyo, 169–8555 Japan. E-mail: hajime_i{at}fuka.info.waseda.ac.jp; kazupyon{at}fuka.info.waseda.ac.jp; fukazawa{at}fuka.info.waseda.ac.jp


  Abstract

To develop usable software, it is necessary to develop Graphical User Interfaces (GUIs) in iterative steps, such as evaluating the usability of GUIs and improving GUIs. In improving GUIs, developers are often required to modify both the GUI and the logic code of the software. In our research, to facilitate GUI improvement, we propose a method of automatically searching for code to be modified and suggesting how to modify them. To search for appropriate code to be modified, we define the roles of widgets according to their purpose and the patterns for how to change GUIs. In our method, how to change GUIs is specified, and then the parts of source programs that are required to be modified are searched for. Also, we classify methods for each widget according to their functions. Using this classification, a method of modifying the code that is searched for is suggested.

Key Words: GUI, widget, usability, source program modification

Manuscript received July 2, 2007. Manuscript revised October 17, 2007.


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.