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

S.j. Simon - One of the best experts on this subject based on the ideXlab platform.

  • The RMT (Recursive Multi-Threaded) tool: a computer aided Software Engineering tool for monitoring and predicting Software development progress
    Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002), 1999
    Co-Authors: A.i. Concepcion, S.j. Simon
    Abstract:

    A number of Software life-cycles for object-oriented Software development (Fountain Model, Recursive/Parallel Model, McGregor and Sykes Model, and Chaos Model Life Cycle) exist today. However, these existing life-cycles have little or no support for estimating and monitoring progress during the development of the Software. The ability to measure progress during the development is significant because it allows both the managers and the developers to determine whether a project is on schedule or not. Identifying that a project is behind schedule allows managers and developers to notify appropriate individuals of any scheduling and/or budgetary impacts at an early stage during the development and to determine appropriate course of action. This demonstration presents the Recursive Multi-Threaded (RMT) Software life-cycle and the implemented computer aided Software Engineering tool based on RMT. The RMT Tool supports the monitoring of progress during development, addresses the specific needs of the developing object-oriented Software, and attempts to resolve deficiencies found in many existing Software lifecycles. What makes RMT unique from existing Software life-cycles is its use of a "thread" for partitioning and organizing Software development activities. Threads support iteration and recursion, which are critical concepts for the development of the Software.

  • ICSE - The RMT (Recursive Multi-Threaded) tool: a computer aided Software Engineering tool for monitoring and predicting Software development progress
    Proceedings of the 21st international conference on Software engineering - ICSE '99, 1999
    Co-Authors: A.i. Concepcion, S.j. Simon
    Abstract:

    A number of Software life-cycles for object-oriented Software development (Fountain Model, Recursive/Parallel Model, McGregor and Sykes Model, and Chaos Model Life Cycle) exist today. However, these existing life-cycles have little or no support for estimating and monitoring progress during the development of the Software. The ability to measure progress during the development is significant because it allows both the managers and the developers to determine whether a project is on schedule or not. Identifying that a project is behind schedule allows managers and developers to notify appropriate individuals of any scheduling and/or budgetary impacts at an early stage during the development and to determine appropriate course of action. This demonstration presents the Recursive Multi-Threaded (RMT) Software life-cycle and the implemented computer aided Software Engineering tool based on RMT. The RMT Tool supports the monitoring of progress during development, addresses the specific needs of the developing object-oriented Software, and attempts to resolve deficiencies found in many existing Software lifecycles. What makes RMT unique from existing Software life-cycles is its use of a "thread" for partitioning and organizing Software development activities. Threads support iteration and recursion, which are critical concepts for the development of the Software.

A.i. Concepcion - One of the best experts on this subject based on the ideXlab platform.

  • The RMT (Recursive Multi-Threaded) tool: a computer aided Software Engineering tool for monitoring and predicting Software development progress
    Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002), 1999
    Co-Authors: A.i. Concepcion, S.j. Simon
    Abstract:

    A number of Software life-cycles for object-oriented Software development (Fountain Model, Recursive/Parallel Model, McGregor and Sykes Model, and Chaos Model Life Cycle) exist today. However, these existing life-cycles have little or no support for estimating and monitoring progress during the development of the Software. The ability to measure progress during the development is significant because it allows both the managers and the developers to determine whether a project is on schedule or not. Identifying that a project is behind schedule allows managers and developers to notify appropriate individuals of any scheduling and/or budgetary impacts at an early stage during the development and to determine appropriate course of action. This demonstration presents the Recursive Multi-Threaded (RMT) Software life-cycle and the implemented computer aided Software Engineering tool based on RMT. The RMT Tool supports the monitoring of progress during development, addresses the specific needs of the developing object-oriented Software, and attempts to resolve deficiencies found in many existing Software lifecycles. What makes RMT unique from existing Software life-cycles is its use of a "thread" for partitioning and organizing Software development activities. Threads support iteration and recursion, which are critical concepts for the development of the Software.

  • ICSE - The RMT (Recursive Multi-Threaded) tool: a computer aided Software Engineering tool for monitoring and predicting Software development progress
    Proceedings of the 21st international conference on Software engineering - ICSE '99, 1999
    Co-Authors: A.i. Concepcion, S.j. Simon
    Abstract:

    A number of Software life-cycles for object-oriented Software development (Fountain Model, Recursive/Parallel Model, McGregor and Sykes Model, and Chaos Model Life Cycle) exist today. However, these existing life-cycles have little or no support for estimating and monitoring progress during the development of the Software. The ability to measure progress during the development is significant because it allows both the managers and the developers to determine whether a project is on schedule or not. Identifying that a project is behind schedule allows managers and developers to notify appropriate individuals of any scheduling and/or budgetary impacts at an early stage during the development and to determine appropriate course of action. This demonstration presents the Recursive Multi-Threaded (RMT) Software life-cycle and the implemented computer aided Software Engineering tool based on RMT. The RMT Tool supports the monitoring of progress during development, addresses the specific needs of the developing object-oriented Software, and attempts to resolve deficiencies found in many existing Software lifecycles. What makes RMT unique from existing Software life-cycles is its use of a "thread" for partitioning and organizing Software development activities. Threads support iteration and recursion, which are critical concepts for the development of the Software.

Robert J. Kauffman - One of the best experts on this subject based on the ideXlab platform.

  • automating output size and reuse metrics in a repository based computer aided Software Engineering case environment
    IEEE Transactions on Software Engineering, 1994
    Co-Authors: Rajiv D. Banker, Robert J. Kauffman, Charles R Wright, Dani Zweig
    Abstract:

    Measurement of Software development productivity is needed in order to control Software costs, but it is discouragingly labor-intensive and expensive. Computer-Aided Software Engineering (CASE) technologies/spl minus/especially repository-based, integrated CASE/spl minus/have the potential to support the automation of this measurement. We discuss the conceptual basis for the development of automated analyzers for function point and Software reuse measurement for object-based CASE. Both analyzers take advantage of the existence of a representation of the application system that is stored within an object repository, and that contains the necessary information about the application system. We also discuss metrics for Software reuse measurement, including reuse leverage, reuse value, and reuse classification that are motivated by managerial requirements and the efforts, within industry and the IEEE, to standardize measurement. The functionality and the analytical capabilities of state-of-the-art automated Software metrics analyzers are illustrated in the context of an investment banking industry application that is similar to systems deployed at the New York City-based investment bank where these tools were developed and tested. >

  • Measuring the Development Performance of Integrated Computer Aided Software Engineering (I-Case): A Synthesis of Field Study Results from the First Boston Corporation
    Analytical Methods in Software Engineering Economics, 1992
    Co-Authors: Rajiv D. Banker, Robert J. Kauffman
    Abstract:

    This paper reports on a multi-year field study conducted at the FirstBoston Corporation to investigate the performance of its object andrepository-based integrated computer aided Software Engineering (I-CASE)tool called High Productivity Systems (HPS). We present productivity andSoftware reuse results for:* three closely monitored small-scale I-CASE pilot projects; and,* twenty large-scale investment banking projects built during the firsttwo years of the I-CASE tool's deployment.Our results offer perspective on the potential for order of magnitudegains in Software development productivity when reusable Softwaredevelopment approaches are applied. They also suggest the need for newmeasurement and management approaches to foster improved Softwaredevelopment performance in the I-CASE world.

  • Reuse and productivity in integrated Computer-Aided Software Engineering: an empirical study
    Management Information Systems Quarterly, 1991
    Co-Authors: Rajiv D. Banker, Robert J. Kauffman
    Abstract:

    Growing competition in the investment banking industry has given rise to increasing demand for high functionality Software applications that can be developed in a short period of time. Yet delivering such applications creates a bottleneck in Software development activities. This dilemma can be addressed when firms shift to development methods that emphasize Software reusability. This article examines the productivity implications of object and repository-based integrated Computer-Aided Software Engineering (ICASE) Software development in the context of a major investment bank's information systems strategy. The strategy emphasizes Software reusability. Our empirical results, based on data from 20 projects that delivered Software for the bank's New Trades Processing Architecture (NTPA), indicate an order of magnitude gain in Software development productivity and the importance of reuse as a driver in realizing this result. In addition, results are presented on the extent of the learning that occurred over a two-year period after ICASE was introduced, and on the influence of the link between application characteristics and the ICASE tool set in achieving development performance. This work demonstrates the viability of the firm's IS strategy and offers new ideas for code reuse and Software development productivity measurement that can be applied in development environments that emphasize reuse.

Rajiv D. Banker - One of the best experts on this subject based on the ideXlab platform.

  • automating output size and reuse metrics in a repository based computer aided Software Engineering case environment
    IEEE Transactions on Software Engineering, 1994
    Co-Authors: Rajiv D. Banker, Robert J. Kauffman, Charles R Wright, Dani Zweig
    Abstract:

    Measurement of Software development productivity is needed in order to control Software costs, but it is discouragingly labor-intensive and expensive. Computer-Aided Software Engineering (CASE) technologies/spl minus/especially repository-based, integrated CASE/spl minus/have the potential to support the automation of this measurement. We discuss the conceptual basis for the development of automated analyzers for function point and Software reuse measurement for object-based CASE. Both analyzers take advantage of the existence of a representation of the application system that is stored within an object repository, and that contains the necessary information about the application system. We also discuss metrics for Software reuse measurement, including reuse leverage, reuse value, and reuse classification that are motivated by managerial requirements and the efforts, within industry and the IEEE, to standardize measurement. The functionality and the analytical capabilities of state-of-the-art automated Software metrics analyzers are illustrated in the context of an investment banking industry application that is similar to systems deployed at the New York City-based investment bank where these tools were developed and tested. >

  • Measuring the Development Performance of Integrated Computer Aided Software Engineering (I-Case): A Synthesis of Field Study Results from the First Boston Corporation
    Analytical Methods in Software Engineering Economics, 1992
    Co-Authors: Rajiv D. Banker, Robert J. Kauffman
    Abstract:

    This paper reports on a multi-year field study conducted at the FirstBoston Corporation to investigate the performance of its object andrepository-based integrated computer aided Software Engineering (I-CASE)tool called High Productivity Systems (HPS). We present productivity andSoftware reuse results for:* three closely monitored small-scale I-CASE pilot projects; and,* twenty large-scale investment banking projects built during the firsttwo years of the I-CASE tool's deployment.Our results offer perspective on the potential for order of magnitudegains in Software development productivity when reusable Softwaredevelopment approaches are applied. They also suggest the need for newmeasurement and management approaches to foster improved Softwaredevelopment performance in the I-CASE world.

  • Reuse and productivity in integrated Computer-Aided Software Engineering: an empirical study
    Management Information Systems Quarterly, 1991
    Co-Authors: Rajiv D. Banker, Robert J. Kauffman
    Abstract:

    Growing competition in the investment banking industry has given rise to increasing demand for high functionality Software applications that can be developed in a short period of time. Yet delivering such applications creates a bottleneck in Software development activities. This dilemma can be addressed when firms shift to development methods that emphasize Software reusability. This article examines the productivity implications of object and repository-based integrated Computer-Aided Software Engineering (ICASE) Software development in the context of a major investment bank's information systems strategy. The strategy emphasizes Software reusability. Our empirical results, based on data from 20 projects that delivered Software for the bank's New Trades Processing Architecture (NTPA), indicate an order of magnitude gain in Software development productivity and the importance of reuse as a driver in realizing this result. In addition, results are presented on the extent of the learning that occurred over a two-year period after ICASE was introduced, and on the influence of the link between application characteristics and the ICASE tool set in achieving development performance. This work demonstrates the viability of the firm's IS strategy and offers new ideas for code reuse and Software development productivity measurement that can be applied in development environments that emphasize reuse.

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