The Experts below are selected from a list of 300 Experts worldwide ranked by ideXlab platform

Emerson Cabrera Paraiso - One of the best experts on this subject based on the ideXlab platform.

  • CSCWD - A semi-automatic source code Documentation method for small software development teams
    Proceedings of the 2011 15th International Conference on Computer Supported Cooperative Work in Design (CSCWD), 2011
    Co-Authors: Julio Cezar Zanoni, Milton Pires Ramos, Cesar Augusto Tacla, Gilson Yukio Sato, Emerson Cabrera Paraiso
    Abstract:

    Software developers often face the task of documenting source code. For many of them, documenting code development is a boring task. However, source code Documentation is an important task, especially when dealing with groups of developers. An updated Documentation allows group members to have greater visibility on what has been and is being developed, allowing the reuse of source code. This research aims at Designing, developing and validating a semi-automatic Documentation method for source code from the existing Design Documentation on a particular project being developed by a small team, as well as updating this Documentation from information gathered from the source code under development. It is understood as Design Documentation, those documents or parts of documents that are linked directly to the code under construction.

Kim Halskov - One of the best experts on this subject based on the ideXlab platform.

  • reflective Design Documentation
    Designing Interactive Systems, 2012
    Co-Authors: Peter Dalsgaard, Kim Halskov
    Abstract:

    Interaction Design researchers doing research through Design face not only the wicked problems in the practice of doing interaction Design, but also the wicked problems that exist in the practice of doing research. In this paper we discuss the use of a tool developed for the specific purpose of documenting Design projects and prompting reflection about Design events as part of doing research through Design. Based on cases lasting from nine to thirteen months we address specific benefits and challenges that we have encountered while employing the tool. Challenges concern roles and responsibilities, lack of routines, determining what to document, and finding the right level of detail. Benefits include support of shared reflection and discussion in on-going projects, the development, refining, and reflection upon research questions, scaffolding longitudinal and cross-project studies. Moreover, the benefits derived from entering Design materials and other kinds of artefacts into a tool may not be achieved until must later, for instance when writing research publications.

  • Conference on Designing Interactive Systems - Reflective Design Documentation
    Proceedings of the Designing Interactive Systems Conference on - DIS '12, 2012
    Co-Authors: Peter Dalsgaard, Kim Halskov
    Abstract:

    Interaction Design researchers doing research through Design face not only the wicked problems in the practice of doing interaction Design, but also the wicked problems that exist in the practice of doing research. In this paper we discuss the use of a tool developed for the specific purpose of documenting Design projects and prompting reflection about Design events as part of doing research through Design. Based on cases lasting from nine to thirteen months we address specific benefits and challenges that we have encountered while employing the tool. Challenges concern roles and responsibilities, lack of routines, determining what to document, and finding the right level of detail. Benefits include support of shared reflection and discussion in on-going projects, the development, refining, and reflection upon research questions, scaffolding longitudinal and cross-project studies. Moreover, the benefits derived from entering Design materials and other kinds of artefacts into a tool may not be achieved until must later, for instance when writing research publications.

Julio Cezar Zanoni - One of the best experts on this subject based on the ideXlab platform.

  • CSCWD - A semi-automatic source code Documentation method for small software development teams
    Proceedings of the 2011 15th International Conference on Computer Supported Cooperative Work in Design (CSCWD), 2011
    Co-Authors: Julio Cezar Zanoni, Milton Pires Ramos, Cesar Augusto Tacla, Gilson Yukio Sato, Emerson Cabrera Paraiso
    Abstract:

    Software developers often face the task of documenting source code. For many of them, documenting code development is a boring task. However, source code Documentation is an important task, especially when dealing with groups of developers. An updated Documentation allows group members to have greater visibility on what has been and is being developed, allowing the reuse of source code. This research aims at Designing, developing and validating a semi-automatic Documentation method for source code from the existing Design Documentation on a particular project being developed by a small team, as well as updating this Documentation from information gathered from the source code under development. It is understood as Design Documentation, those documents or parts of documents that are linked directly to the code under construction.

Peter Dalsgaard - One of the best experts on this subject based on the ideXlab platform.

  • reflective Design Documentation
    Designing Interactive Systems, 2012
    Co-Authors: Peter Dalsgaard, Kim Halskov
    Abstract:

    Interaction Design researchers doing research through Design face not only the wicked problems in the practice of doing interaction Design, but also the wicked problems that exist in the practice of doing research. In this paper we discuss the use of a tool developed for the specific purpose of documenting Design projects and prompting reflection about Design events as part of doing research through Design. Based on cases lasting from nine to thirteen months we address specific benefits and challenges that we have encountered while employing the tool. Challenges concern roles and responsibilities, lack of routines, determining what to document, and finding the right level of detail. Benefits include support of shared reflection and discussion in on-going projects, the development, refining, and reflection upon research questions, scaffolding longitudinal and cross-project studies. Moreover, the benefits derived from entering Design materials and other kinds of artefacts into a tool may not be achieved until must later, for instance when writing research publications.

  • Conference on Designing Interactive Systems - Reflective Design Documentation
    Proceedings of the Designing Interactive Systems Conference on - DIS '12, 2012
    Co-Authors: Peter Dalsgaard, Kim Halskov
    Abstract:

    Interaction Design researchers doing research through Design face not only the wicked problems in the practice of doing interaction Design, but also the wicked problems that exist in the practice of doing research. In this paper we discuss the use of a tool developed for the specific purpose of documenting Design projects and prompting reflection about Design events as part of doing research through Design. Based on cases lasting from nine to thirteen months we address specific benefits and challenges that we have encountered while employing the tool. Challenges concern roles and responsibilities, lack of routines, determining what to document, and finding the right level of detail. Benefits include support of shared reflection and discussion in on-going projects, the development, refining, and reflection upon research questions, scaffolding longitudinal and cross-project studies. Moreover, the benefits derived from entering Design materials and other kinds of artefacts into a tool may not be achieved until must later, for instance when writing research publications.

Lutz Prechelt - One of the best experts on this subject based on the ideXlab platform.

  • ICSM - JTourBus: Simplifying Program Understanding by Documentation that Provides Tours Through the Source Code
    2007 IEEE International Conference on Software Maintenance, 2007
    Co-Authors: Christopher Oezbek, Lutz Prechelt
    Abstract:

    Many small and medium-sized systems have little or no Design Documentation, which makes program understanding during maintenance enormously more difficult when performed by outsiders. Thus, if only minimal Design Documentation is available, which form should it take to maximize its usefulness? We suggest that it is helpful if the Documentation describes a tour through the source code, leading the user directly to relevant details. This work reports an evaluation of this conceptual idea in the form of a controlled experiment with 59 student subjects working on a difficult program understanding task in the context of the 27 KLOC JHotDraw graphics framework. One group received a plain text Documentation, the other received tour-structured Documentation which they navigated by using an Eclipse plugin called JTourBus that we constructed for the experiment. The results indicate that program understanding can be achieved somewhat faster (albeit not more correctly) with JTourBus than with a plain text document.