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

Biman Das - One of the best experts on this subject based on the ideXlab platform.

  • the relationship between worker satisfaction and productivity in a repetitive Industrial task
    Applied Ergonomics, 2003
    Co-Authors: Ashraf A Shikdar, Biman Das
    Abstract:

    The objective of this investigation was to determine the manner by which production standards or goals, performance or production feedback and monetary or wage incentive affected or moderated the relationship between worker satisfaction and productivity in a repetitive production task in a fishing industry. The Industrial Study was conducted to measure worker satisfaction and productivity under various experimental conditions involving production standards, performance feedback and monetary incentive. Only the participative standard and performance feedback condition affected the worker satisfaction-productivity relationship significantly for the fish-trimming task. The positive correlation coefficient (0.87) for this condition was found to be highly significant. This has an important implication for setting a strategy for achieving higher worker satisfaction and productivity in such an industry. Production standards with feedback generally improved worker satisfaction and productivity. Monetary incentive further improved worker performance but added no incremental satisfaction gain. The incorporation of production standards, performance feedback and monetary incentive affected worker satisfaction and productivity differently and this had an effect on the worker satisfaction-productivity relationship. In an earlier laboratory Study, no significant worker satisfaction-productivity relationship was found when subjects (college students) were provided with similar experimental conditions.

Chandra Alluri - One of the best experts on this subject based on the ideXlab platform.

  • An Industrial Study of applying input space partitioning to test financial calculation engines
    Empirical Software Engineering, 2014
    Co-Authors: Jeff Offutt, Chandra Alluri
    Abstract:

    This paper presents results from an Industrial Study that applied input space partitioning and semi-automated requirements modeling to large-scale Industrial software, specifically financial calculation engines. Calculation engines are used in financial service applications such as banking, mortgage, insurance, and trading to compute complex, multi-conditional formulas to make high risk financial decisions. They form the heart of financial applications, and can cause severe economic harm if incorrect. Controllability and observability of these calculation engines are low, so robust and sophisticated test methods are needed to ensure the results are valid. However, the industry norm is to use pure human-based, requirements-driven test design, usually with very little automation. The Federal Home Loan Mortgage Corporation (FHLMC), commonly known as Freddie Mac, concerned that these test design techniques may lead to ineffective and inefficient testing, partnered with a university to use high quality, sophisticated test design on several ongoing projects. The goal was to determine if such test design can be cost-effective on this type of critical software. In this Study, input space partitioning, along with automation, were applied with the help of several special-purpose tools to validate the effectiveness of input space partitioning. Results showed that these techniques were far more effective (finding more software faults) and more efficient (requiring fewer tests and less labor), and the managers reported that the testing cycle was reduced from five human days to 0.5. This Study convinced upper management to begin infusing this approach into other software development projects.

Michel S. Soares - One of the best experts on this subject based on the ideXlab platform.

  • a systematic mapping Study on software architectures description based on iso iec ieee 42010 2011
    International Conference on Computational Science and Its Applications, 2019
    Co-Authors: Ademir A C, Sanjay Misra, Michel S. Soares
    Abstract:

    Software architecture is considered an important area of Software Engineering, as it is useful for managing the development and maintenance of large scale software-intensive systems. Due to Software Architecture importance, the ISO/IEC/IEEE 42010:2011 standard was published in 2011. In this paper, we present a Systematic Mapping Study (SMS) for describing studies that explicitly used the ISO/IEC/IEEE 42010:2011 standard, and identifying which parts of this standard were most considered in the literature. Through the research, we selected 19 papers published between 2007 and September 2018. One interesting result is that ISO/IEC/IEEE 42010:2011 standard has been used, and its presence in papers has increased since 2016. However, parts of the standard are still not considered in practice. Industry and academia can still benefit from learning and improve the use of ISO/IEC/IEEE 42010:2011. Based on our findings, we suggest further research to analyze all the aspects of the standard as well as an Industrial Study.

  • ICCSA (5) - A Systematic Mapping Study on Software Architectures Description Based on ISO/IEC/IEEE 42010: 2011.
    Computational Science and Its Applications – ICCSA 2019, 2019
    Co-Authors: Ademir A. C. Júnior, Sanjay Misra, Michel S. Soares
    Abstract:

    Software architecture is considered an important area of Software Engineering, as it is useful for managing the development and maintenance of large scale software-intensive systems. Due to Software Architecture importance, the ISO/IEC/IEEE 42010:2011 standard was published in 2011. In this paper, we present a Systematic Mapping Study (SMS) for describing studies that explicitly used the ISO/IEC/IEEE 42010:2011 standard, and identifying which parts of this standard were most considered in the literature. Through the research, we selected 19 papers published between 2007 and September 2018. One interesting result is that ISO/IEC/IEEE 42010:2011 standard has been used, and its presence in papers has increased since 2016. However, parts of the standard are still not considered in practice. Industry and academia can still benefit from learning and improve the use of ISO/IEC/IEEE 42010:2011. Based on our findings, we suggest further research to analyze all the aspects of the standard as well as an Industrial Study.

  • A Systematic Mapping Study on Software Architectures Description Based on ISO/IEC/IEEE 42010:2011
    Computational Science and Its Applications – ICCSA 2019, 2019
    Co-Authors: Ademir A. C. Júnior, Sanjay Misra, Michel S. Soares
    Abstract:

    Software architecture is considered an important area of Software Engineering, as it is useful for managing the development and maintenance of large scale software-intensive systems . Due to Software Architecture importance, the ISO/IEC/IEEE 42010:2011 standard was published in 2011. In this paper, we present a Systematic Mapping Study (SMS) for describing studies that explicitly used the ISO/IEC/IEEE 42010:2011 standard, and identifying which parts of this standard were most considered in the literature. Through the research, we selected 19 papers published between 2007 and September 2018. One interesting result is that ISO/IEC/IEEE 42010:2011 standard has been used, and its presence in papers has increased since 2016. However, parts of the standard are still not considered in practice. Industry and academia can still benefit from learning and improve the use of ISO/IEC/IEEE 42010:2011. Based on our findings, we suggest further research to analyze all the aspects of the standard as well as an Industrial Study.

Zhen Ming Jiang - One of the best experts on this subject based on the ideXlab platform.

  • an Industrial Study on the risk of software changes
    Foundations of Software Engineering, 2012
    Co-Authors: Emad Shihab, Ahmed E Hassan, Bram Adams, Zhen Ming Jiang
    Abstract:

    Modelling and understanding bugs has been the focus of much of the Software Engineering research today. However, organizations are interested in more than just bugs. In particular, they are more concerned about managing risk, i.e., the likelihood that a code or design change will cause a negative impact on their products and processes, regardless of whether or not it introduces a bug. In this paper, we conduct a year-long Study involving more than 450 developers of a large enterprise, spanning more than 60 teams, to better understand risky changes, i.e., changes for which developers believe that additional attention is needed in the form of careful code or design reviewing and/or more testing. Our findings show that different developers and different teams have their own criteria for determining risky changes. Using factors extracted from the changes and the history of the files modified by the changes, we are able to accurately identify risky changes with a recall of more than 67%, and a precision improvement of 87% (using developer specific models) and 37% (using team specific models), over a random model. We find that the number of lines and chunks of code added by the change, the bugginess of the files being changed, the number of bug reports linked to a change and the developer experience are the best indicators of change risk. In addition, we find that when a change has many related changes, the reliability of developers in marking risky changes is negatively affected. Our findings and models are being used today in practice to manage the risk of software projects.

  • SIGSOFT FSE - An Industrial Study on the risk of software changes
    Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering - FSE '12, 2012
    Co-Authors: Emad Shihab, Ahmed E Hassan, Bram Adams, Zhen Ming Jiang
    Abstract:

    Modelling and understanding bugs has been the focus of much of the Software Engineering research today. However, organizations are interested in more than just bugs. In particular, they are more concerned about managing risk, i.e., the likelihood that a code or design change will cause a negative impact on their products and processes, regardless of whether or not it introduces a bug. In this paper, we conduct a year-long Study involving more than 450 developers of a large enterprise, spanning more than 60 teams, to better understand risky changes, i.e., changes for which developers believe that additional attention is needed in the form of careful code or design reviewing and/or more testing. Our findings show that different developers and different teams have their own criteria for determining risky changes. Using factors extracted from the changes and the history of the files modified by the changes, we are able to accurately identify risky changes with a recall of more than 67%, and a precision improvement of 87% (using developer specific models) and 37% (using team specific models), over a random model. We find that the number of lines and chunks of code added by the change, the bugginess of the files being changed, the number of bug reports linked to a change and the developer experience are the best indicators of change risk. In addition, we find that when a change has many related changes, the reliability of developers in marking risky changes is negatively affected. Our findings and models are being used today in practice to manage the risk of software projects.

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