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

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

  • Assessing the Process Maturity Utilized in Software Engineering Team Project Courses
    Journal of Engineering Education, 2001
    Co-Authors: James Collofello
    Abstract:

    Many computer science departments offer an introductory software Engineering course, which normally provides an introduction to software Engineering topics in conjunction with a semester long Team project. To ensure students acquire the correct lessons from this project experience, it is essential that the Teams utilize well-defined software development processes similar to those practiced by leading software development organizations. Since its inception, the Software Engineering Institute Capability Maturity Model (CMM) has served as a guide for organizations seeking to improve their development practices, through a self-assessment questionnaire. In an effort to assess the maturity of development practices utilized in software Engineering courses, an “academic” version of the CMM questionnaire was developed. This questionnaire was distributed to a sample of software Engineering instructors in an effort to assess the maturity of academic software Engineering course projects. The questionnaire and the survey results are presented and discussed.

  • Assessing the process maturity utilized in software Engineering Team project courses
    FIE'99 Frontiers in Education. 29th Annual Frontiers in Education Conference. Designing the Future of Science and Engineering Education. Conference Pr, 1
    Co-Authors: James Collofello
    Abstract:

    As part of their curriculum, many computer science departments offer an introductory software Engineering course. This course normally provides an introduction to software Engineering topics in conjunction with a semester long Team project. The typical goals of this project are to provide students with a Team based realistic software development project experience. To ensure students acquire the correct lessons from this project experience, it is essential that the Teams utilize well-defined software development processes similar to those practised by leading software development organizations. Since its inception, the Software Engineering Institute Capability Maturity Model (CMM) has served as a guide for organizations seeking to improve their development practices. The CMM identifies five levels of maturity, each of which exemplifies the utilization of key software Engineering practices. Organizations can utilize the CMM to assess the maturity of their development processes via a self-assessment questionnaire, Although most organizations would like to believe their processes are mature, most are at the first two levels of maturity. In an effort to assess the maturity of development practices utilized in software Engineering courses, an "academic" version of the CMM questionnaire was developed. This questionnaire was distributed to a sample of software Engineering instructors in an effort to assess the maturity of academic software Engineering course projects. The questionnaire and the survey results are presented and discussed. The goal of this effort is to provide an assessment of current software Engineering course project education. As in the commercial world, this assessment will help pinpoint areas of improvement. It will also provide a challenge to software Engineering instructors to "practice what they preach " and strive for higher levels of process maturity.

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

  • Research Constructing TSP Implementation System Based on CSCW
    Computer Engineering, 2007
    Co-Authors: Sun Liping
    Abstract:

    Software programming is a process of Team collaboration.It requires Team members to work independently and coordinate closely during the exploration activities.The software process(TSP) provides effective and actual help for the standard software development and improvement process ability.But there are some problems in implementing TSP,which are caused by the poor understanding of process,difficulties in communication and collaboration,heavy workload of disposing process data,etc.This paper provides computer supported cooperative work(CSCW)-TSP system to solve these problems.CSCW-TSP system utilizes CSCW principles and technologies to make a new practical way for TSP as the software tool.It enables the software Engineering Team to apply TSP more effectively,enhances the efficiency and the quality of software development.

V.s. Mani - One of the best experts on this subject based on the ideXlab platform.

  • usable software at the end of each takt a milestone in the lean transformation of a globally distributed software development Team
    International Conference on Global Software Engineering, 2017
    Co-Authors: M S Roopa, C Sankarasubbiah, V.s. Mani
    Abstract:

    This experience paper presents how a globally distributed software Engineering Team was able to deliver usable software at the end of each takt, why this was important, and the benefits derived. We also describe the approach taken, the challenges faced and the steps to overcome them..

  • ICGSE - Usable software at the end of each takt: a milestone in the lean transformation of a globally distributed software development Team
    2017 IEEE 12th International Conference on Global Software Engineering (ICGSE), 2017
    Co-Authors: M S Roopa, C Sankarasubbiah, V.s. Mani
    Abstract:

    This experience paper presents how a globally distributed software Engineering Team was able to deliver usable software at the end of each takt, why this was important, and the benefits derived. We also describe the approach taken, the challenges faced and the steps to overcome them..

  • ICGSE - An Approach for Enabling Effective and Systematic Software Reuse: In a Globally Distributed Software Engineering Team That Uses a Lean Development Methodology
    2016 IEEE 11th International Conference on Global Software Engineering (ICGSE), 2016
    Co-Authors: M S Roopa, V.s. Mani, Halwas Stefan
    Abstract:

    We share our experience in pursuing effective software reuse in a globally distributed software Engineering Team that uses a lean development methodology. The paper outlines the journey, starting from recognizing the potential for reuse, the steps taken to enable systematic reuse in lean projects, the challenges faced, and the corrective actions taken to ensure effectiveness of systematic reuse. The main lessons learned include: i) identification of relevant domains for reuse, ii) explicitly assigning responsibilities for reuse component development, iii) providing enabling infrastructure, iv) defining more rigorous software development processes for reuse components, and v) establishing a centralized Team for developing reuse components. The results of our successful reuse initiative including the significant increase in quality and a 12 percent reuse of total code developed have been presented.

  • system testing optimization in a globally distributed software Engineering Team
    International Conference on Global Software Engineering, 2016
    Co-Authors: Tulasi Anand, Chittoor Reddy, V.s. Mani
    Abstract:

    This practice paper presents how a test Team of a software Engineering organization spread across three countries successfully optimized the system testing effort for a large mission-critical software system that had to conform to regulatory requirements. Multiple releases of the system of the system have been delivered to customers over the 15 years it has been in the market. Each new release added new features, which increased both the number of system test cases required and the complexity of the existing system test cases. Hence, a complete cycle of system testing for every new release required more time and effort. However, it was increasingly difficult to justify or arrange for such added efforts, especially since shorter product releases were being demanded. This created a vicious cycle where the Team members, though experienced and highly-skilled, were unable to focus on initiatives to improve and optimize testing. To address this issue, we introduced the role of a test analyst to bridge the gap between the test Team and other key stakeholders. We were able to optimize the total number of system test cases and increase test execution efficiency while ensuring conformance to mandatory regulations. The practices adapted by the Team for faster test environment preparation, assisted automation, along with training and mentoring are described.

  • ICGSE - System Testing Optimization in a Globally Distributed Software Engineering Team
    2016 IEEE 11th International Conference on Global Software Engineering (ICGSE), 2016
    Co-Authors: Tulasi Anand, Chittoor Reddy, V.s. Mani
    Abstract:

    This practice paper presents how a test Team of a software Engineering organization spread across three countries successfully optimized the system testing effort for a large mission-critical software system that had to conform to regulatory requirements. Multiple releases of the system of the system have been delivered to customers over the 15 years it has been in the market. Each new release added new features, which increased both the number of system test cases required and the complexity of the existing system test cases. Hence, a complete cycle of system testing for every new release required more time and effort. However, it was increasingly difficult to justify or arrange for such added efforts, especially since shorter product releases were being demanded. This created a vicious cycle where the Team members, though experienced and highly-skilled, were unable to focus on initiatives to improve and optimize testing. To address this issue, we introduced the role of a test analyst to bridge the gap between the test Team and other key stakeholders. We were able to optimize the total number of system test cases and increase test execution efficiency while ensuring conformance to mandatory regulations. The practices adapted by the Team for faster test environment preparation, assisted automation, along with training and mentoring are described.

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

  • an investigation on the variation of software development productivity
    World Academy of Science Engineering and Technology International Journal of Computer Electrical Automation Control and Information Engineering, 2007
    Co-Authors: Zhizhong Jiang, Peter Naude, Craig Comstock
    Abstract:

    The productivity of software development is one of the major concerns for project managers. Given the increasing complexity of the software being developed and the concomitant rise in the typical project size, the productivity has not consistently improved. By analyzing the latest release of ISBSG data repository with 4106 projects ever developed, we report on the factors found to significantly influence productivity, and present an original model for the estimation of productivity during project design. We further illustrate that software development productivity has experienced irregular variations between the years 1995 and 2005. Considering the factors significant to productivity, we found its variations are primarily caused by the variations of average Team size for the development and the unbalanced use of the less productive development language 3GL. Keywords—Development Platform, Function Point, Language, Productivity, Software Engineering, Team Size.

  • The Variation of Software Development Productivity 1995-2005
    World Academy of Science Engineering and Technology International Journal of Computer Electrical Automation Control and Information Engineering, 2007
    Co-Authors: Zhizhong Jiang, Peter Naude, Craig Comstock
    Abstract:

    Software development has experienced remarkable progress in the past decade. However, due to the rising complexity and magnitude of the project the development productivity has not been consistently improved. By analyzing the latest ISBSG data repository with 4106 projects, we discovered that software development productivity has actually undergone irregular variations between the years 1995 and 2005. Considering the factors significant to the productivity, we found its variations are primarily caused by the variations of average Team size and the unbalanced uses of the less productive language 3GL. Keywords—Productivity, Programming Languages, Software Engineering, Team Size.

M S Roopa - One of the best experts on this subject based on the ideXlab platform.