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

Guangzhi Zheng - One of the best experts on this subject based on the ideXlab platform.

  • The influence of checklists and roles on Software Practitioner risk perception and decision-making
    Journal of Systems and Software, 2008
    Co-Authors: Mark Keil, Lars Mathiassen, Guangzhi Zheng
    Abstract:

    This paper investigates: (1) the influence of risk checklists on Software Practitioner risk perception and decision-making, and (2) the influence of role (inside project manager vs. outside consultant) on Software Practitioner risk perception and decision-making. Evidence on these points is presented based on a role playing experiment conducted with 128 Software Practitioners. Results show that (1) the risk checklist helped subjects identify more risks than they would identify without the aid of a checklist, whereas (2) the role assigned to subjects did not seem to affect either their risk perception or behavior. Moreover, the use of a risk checklist shaped subjects' perceptions of which risks were salient in the scenario, whereas the number of risks identified did not affect their decision-making. Interestingly, subjects using a checklist were able to identify more seeded risks in the scenario, but they also identified more unseeded risks. Implications for research and practice are discussed.

  • the influence of checklists and roles on Software Practitioner risk perception and decision making
    Hawaii International Conference on System Sciences, 2006
    Co-Authors: Mark Keil, Lars Mathiassen, Guangzhi Zheng
    Abstract:

    This paper investigates: (1) the influence of risk checklists on Software Practitioner risk perception and decision-making, and (2) the influence of role (inside project manager vs. outside consultant) on Software Practitioner risk perception and decision-making. Evidence on these points is presented based on a role playing experiment conducted with 128 Software Practitioners. Results show that a risk checklist helps Software Practitioners identify more risks than they would identify without the aid of a checklist. However, the role assigned to subjects did not seem to affect either their risk perception or behavior. The number of risks identified did not affect decision-making, but the use of a risk checklist appeared to shape subjects’ perceptions of which risks were salient in the scenario. Interestingly, subjects using a checklist were able to identify more seeded risks in the scenario, but they also identified more unseeded risks. Implications for research and practice are discussed.

  • HICSS - The Influence of Checklists and Roles on Software Practitioner Risk Perception and Decision-Making
    Proceedings of the 39th Annual Hawaii International Conference on System Sciences (HICSS'06), 2006
    Co-Authors: Mark Keil, Lars Mathiassen, Guangzhi Zheng
    Abstract:

    This paper investigates: (1) the influence of risk checklists on Software Practitioner risk perception and decision-making, and (2) the influence of role (inside project manager vs. outside consultant) on Software Practitioner risk perception and decision-making. Evidence on these points is presented based on a role playing experiment conducted with 128 Software Practitioners. Results show that a risk checklist helps Software Practitioners identify more risks than they would identify without the aid of a checklist. However, the role assigned to subjects did not seem to affect either their risk perception or behavior. The number of risks identified did not affect decision-making, but the use of a risk checklist appeared to shape subjects’ perceptions of which risks were salient in the scenario. Interestingly, subjects using a checklist were able to identify more seeded risks in the scenario, but they also identified more unseeded risks. Implications for research and practice are discussed.

Mark Keil - One of the best experts on this subject based on the ideXlab platform.

  • The influence of checklists and roles on Software Practitioner risk perception and decision-making
    Journal of Systems and Software, 2008
    Co-Authors: Mark Keil, Lars Mathiassen, Guangzhi Zheng
    Abstract:

    This paper investigates: (1) the influence of risk checklists on Software Practitioner risk perception and decision-making, and (2) the influence of role (inside project manager vs. outside consultant) on Software Practitioner risk perception and decision-making. Evidence on these points is presented based on a role playing experiment conducted with 128 Software Practitioners. Results show that (1) the risk checklist helped subjects identify more risks than they would identify without the aid of a checklist, whereas (2) the role assigned to subjects did not seem to affect either their risk perception or behavior. Moreover, the use of a risk checklist shaped subjects' perceptions of which risks were salient in the scenario, whereas the number of risks identified did not affect their decision-making. Interestingly, subjects using a checklist were able to identify more seeded risks in the scenario, but they also identified more unseeded risks. Implications for research and practice are discussed.

  • the influence of checklists and roles on Software Practitioner risk perception and decision making
    Hawaii International Conference on System Sciences, 2006
    Co-Authors: Mark Keil, Lars Mathiassen, Guangzhi Zheng
    Abstract:

    This paper investigates: (1) the influence of risk checklists on Software Practitioner risk perception and decision-making, and (2) the influence of role (inside project manager vs. outside consultant) on Software Practitioner risk perception and decision-making. Evidence on these points is presented based on a role playing experiment conducted with 128 Software Practitioners. Results show that a risk checklist helps Software Practitioners identify more risks than they would identify without the aid of a checklist. However, the role assigned to subjects did not seem to affect either their risk perception or behavior. The number of risks identified did not affect decision-making, but the use of a risk checklist appeared to shape subjects’ perceptions of which risks were salient in the scenario. Interestingly, subjects using a checklist were able to identify more seeded risks in the scenario, but they also identified more unseeded risks. Implications for research and practice are discussed.

  • HICSS - The Influence of Checklists and Roles on Software Practitioner Risk Perception and Decision-Making
    Proceedings of the 39th Annual Hawaii International Conference on System Sciences (HICSS'06), 2006
    Co-Authors: Mark Keil, Lars Mathiassen, Guangzhi Zheng
    Abstract:

    This paper investigates: (1) the influence of risk checklists on Software Practitioner risk perception and decision-making, and (2) the influence of role (inside project manager vs. outside consultant) on Software Practitioner risk perception and decision-making. Evidence on these points is presented based on a role playing experiment conducted with 128 Software Practitioners. Results show that a risk checklist helps Software Practitioners identify more risks than they would identify without the aid of a checklist. However, the role assigned to subjects did not seem to affect either their risk perception or behavior. The number of risks identified did not affect decision-making, but the use of a risk checklist appeared to shape subjects’ perceptions of which risks were salient in the scenario. Interestingly, subjects using a checklist were able to identify more seeded risks in the scenario, but they also identified more unseeded risks. Implications for research and practice are discussed.

Lars Mathiassen - One of the best experts on this subject based on the ideXlab platform.

  • The influence of checklists and roles on Software Practitioner risk perception and decision-making
    Journal of Systems and Software, 2008
    Co-Authors: Mark Keil, Lars Mathiassen, Guangzhi Zheng
    Abstract:

    This paper investigates: (1) the influence of risk checklists on Software Practitioner risk perception and decision-making, and (2) the influence of role (inside project manager vs. outside consultant) on Software Practitioner risk perception and decision-making. Evidence on these points is presented based on a role playing experiment conducted with 128 Software Practitioners. Results show that (1) the risk checklist helped subjects identify more risks than they would identify without the aid of a checklist, whereas (2) the role assigned to subjects did not seem to affect either their risk perception or behavior. Moreover, the use of a risk checklist shaped subjects' perceptions of which risks were salient in the scenario, whereas the number of risks identified did not affect their decision-making. Interestingly, subjects using a checklist were able to identify more seeded risks in the scenario, but they also identified more unseeded risks. Implications for research and practice are discussed.

  • the influence of checklists and roles on Software Practitioner risk perception and decision making
    Hawaii International Conference on System Sciences, 2006
    Co-Authors: Mark Keil, Lars Mathiassen, Guangzhi Zheng
    Abstract:

    This paper investigates: (1) the influence of risk checklists on Software Practitioner risk perception and decision-making, and (2) the influence of role (inside project manager vs. outside consultant) on Software Practitioner risk perception and decision-making. Evidence on these points is presented based on a role playing experiment conducted with 128 Software Practitioners. Results show that a risk checklist helps Software Practitioners identify more risks than they would identify without the aid of a checklist. However, the role assigned to subjects did not seem to affect either their risk perception or behavior. The number of risks identified did not affect decision-making, but the use of a risk checklist appeared to shape subjects’ perceptions of which risks were salient in the scenario. Interestingly, subjects using a checklist were able to identify more seeded risks in the scenario, but they also identified more unseeded risks. Implications for research and practice are discussed.

  • HICSS - The Influence of Checklists and Roles on Software Practitioner Risk Perception and Decision-Making
    Proceedings of the 39th Annual Hawaii International Conference on System Sciences (HICSS'06), 2006
    Co-Authors: Mark Keil, Lars Mathiassen, Guangzhi Zheng
    Abstract:

    This paper investigates: (1) the influence of risk checklists on Software Practitioner risk perception and decision-making, and (2) the influence of role (inside project manager vs. outside consultant) on Software Practitioner risk perception and decision-making. Evidence on these points is presented based on a role playing experiment conducted with 128 Software Practitioners. Results show that a risk checklist helps Software Practitioners identify more risks than they would identify without the aid of a checklist. However, the role assigned to subjects did not seem to affect either their risk perception or behavior. The number of risks identified did not affect decision-making, but the use of a risk checklist appeared to shape subjects’ perceptions of which risks were salient in the scenario. Interestingly, subjects using a checklist were able to identify more seeded risks in the scenario, but they also identified more unseeded risks. Implications for research and practice are discussed.

David R Luginbuhl - One of the best experts on this subject based on the ideXlab platform.

  • teaching Software verification and validation to Software Practitioner
    SEI Conference on Software Engineering Education, 1992
    Co-Authors: James E Cardow, David R Luginbuhl
    Abstract:

    We describe the development and teaching of a two-week course in Software verification and validation (V&V). The course is taught to Air Force Software Practitioners by faculty at the Air Force Institute of Technology (AFIT). We show that by organizing teaching materials using a framework involving interrelationships of activities throughout the Software development life cycle, we were able to significantly enhance the development and teaching of the course. Such an organization is logical since V&V pervades all activities in every part of the life cycle.

  • CSEE - Teaching Software Verification and Validation to Software Practitioner
    Software Engineering Education, 1992
    Co-Authors: James E Cardow, David R Luginbuhl
    Abstract:

    We describe the development and teaching of a two-week course in Software verification and validation (V&V). The course is taught to Air Force Software Practitioners by faculty at the Air Force Institute of Technology (AFIT). We show that by organizing teaching materials using a framework involving interrelationships of activities throughout the Software development life cycle, we were able to significantly enhance the development and teaching of the course. Such an organization is logical since V&V pervades all activities in every part of the life cycle.

Asadullah Shah - One of the best experts on this subject based on the ideXlab platform.

  • Agile Methods Acceptance Model: Understanding Factors for Implementing Agile Methods in Pakistan
    Sindh University Research Journal, 2019
    Co-Authors: Yasir Ali Solangi, Zulfiqar Ali Solangi, A. Maitlo, Shahmurad Chandio, Asadullah Shah
    Abstract:

    Agile Software development methods can deliver quality Software yet it perceived that adoption and acceptance of agile methods by the consumers has been lower in Pakistan. However, this research study proposes an extended model of technology acceptance to understand the perception of the potential Software Practitioner teams towards adoption and acceptance of agile methods in Software development. The theoretical research framework in this study incorporates determinants such as productivity, awareness of agile methods, and customer collaboration along with latent factors perceived ease of use and perceived usefulness. It is intended that the systematic research framework of integrated factors would be supportive enough to adopt agile Software development solutions in Software industry of Pakistan.