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

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

  • Process mining support for Capability Maturity Model Integration-based software process assessment, in principle and in practice
    Journal of Software: Evolution and Process, 2014
    Co-Authors: Jana Samalikova, Jos J M Trienekens, Rj Rob Kusters, A J M M Weijters
    Abstract:

    Currently used software process improvement methods such as the Capability Maturity Model Integration CMMI rely in their process assessments on information, which is gathered during interviews, in oral audit sessions, and from quality manuals and process standard reviews. Although valuable information about software processes can be gained in these assessments, the resulting data quality can be improved upon. This paper investigates the potential of process mining to support current software process assessment and improvement approaches. Based on an analysis of CMMI from a process mining perspective, particular CMMI model components are identified for which it is in principle possible to apply process mining techniques. Subsequently, criteria have been defined to select, with respect to these particular CMMI components, software processes for which process mining has an added value. These criteria have been applied in the selection of a particular 'minable' software process, that is, a Change Control process. Subsequently, the results of a case study from industrial practice, on the process mining of a Change Control Board process, are used to illustrate that process mining can provide CMMI assessors with relevant information. This information reflects the actual or 'real' software processes in practice, and as such, it offers an excellent basis to support assessors in understanding the 'actual' software processes. Copyright © 2014 John Wiley & Sons, Ltd.

  • Toward objective software process information: experiences from a case study
    Software Quality Journal, 2011
    Co-Authors: Jana Samalikova, Rob Kusters, Jos Trienekens, Ton Weijters, Paul Siemons
    Abstract:

    A critical problem in software development is the monitoring, Control and improvement in the processes of software developers. Software processes are often not explicitly modeled, and manuals to support the development work contain abstract guidelines and procedures. Consequently, there are huge differences between ‘actual’ and ‘official’ processes: “the actual process is what you do, with all its omissions, mistakes, and oversights. The official process is what the book, i.e., a quality manual, says you are supposed to do” (Humphrey in A discipline for software engineering. Addison-Wesley, New York, 1995 ). Software developers lack support to identify, analyze and better understand their processes. Consequently, process improvements are often not based on an in-depth understanding of the ‘actual’ processes, but on organization-wide improvement programs or ad hoc initiatives of individual developers. In this paper, we show that, based on particular data from software development projects, the underlying software development processes can be extracted and that automatically more realistic process models can be constructed. This is called software process mining (Rubin et al. in Process mining framework for software processes. Software process dynamics and agility. Springer Berlin, Heidelberg, 2007 ). The goal of process mining is to better understand the development processes, to compare constructed process models with the ‘official’ guidelines and procedures in quality manuals and, subsequently, to improve development processes. This paper reports on process mining case studies in a large industrial company in The Netherlands. The subject of the process mining is a particular process: the Change Control Board (CCB) process. The results of process mining are fed back to practice in order to subsequently improve the CCB process.

  • discovering Changes of the Change Control Board process during a software development project using process mining
    European conference on Software Process Improvement, 2009
    Co-Authors: Jana Samalikova, Jos J M Trienekens, R Rob J Kusters, A J M M Weijters
    Abstract:

    During a software process improvement program, the current state of software development processes is being assessed and improvement actions are being determined. However, these improvement actions are based on process models obtained during interviews and document studies, e.g. quality manuals. Such improvements are scarcely based on the practical way of working in an organization; they do not take into account shortcuts made due to e.g. time pressure. Becoming conscious about the presence of such deviations and understanding their causes and impacts, consequences for particular software process improvement activities in a particular organization could be proposed. This paper reports on the application of process mining techniques to discover shortcomings in the Change Control Board process in an organization during the different lifecycle phases and to determine improvement activities.

  • EuroSPI - Discovering Changes of the Change Control Board Process during a Software Development Project Using Process Mining
    Communications in Computer and Information Science, 2009
    Co-Authors: Jana Samalikova, Jos J M Trienekens, R Rob J Kusters, A J M M Weijters
    Abstract:

    During a software process improvement program, the current state of software development processes is being assessed and improvement actions are being determined. However, these improvement actions are based on process models obtained during interviews and document studies, e.g. quality manuals. Such improvements are scarcely based on the practical way of working in an organization; they do not take into account shortcuts made due to e.g. time pressure. Becoming conscious about the presence of such deviations and understanding their causes and impacts, consequences for particular software process improvement activities in a particular organization could be proposed. This paper reports on the application of process mining techniques to discover shortcomings in the Change Control Board process in an organization during the different lifecycle phases and to determine improvement activities.

Phillip A Cloud - One of the best experts on this subject based on the ideXlab platform.

  • Engineering Change/part number input
    Engineering Procedures Handbook, 1998
    Co-Authors: Phillip A Cloud
    Abstract:

    This chapter provides an overview of the engineering Change/part number input procedure. This procedure gives instructions for the preparation of the engineering Change/part number cross reference file. The engineering Change/part number input is a system used to keep track of and report past and future Changes of engineering designs. This procedure is divided into two parts: engineering Change/part number and engineering Change/part number input form preparation. The originator prepares the engineering Change/part number input form E045 to establish a cross reference file of a Changed part and the engineering Change that Changed the part. The originator then forwards the completed form to document Control for filing. The procedure for processing the engineering Change/part number input form is followed by each individual responsible for entering information on the form. The originator also has to enter the document number and title, number of sheets, document size, and bill of material sheets. If the engineering Change is approved by the Change Control Board, originator enters the date of the approval in the accept column.

  • Change Control Board
    Engineering Procedures Handbook, 1998
    Co-Authors: Phillip A Cloud
    Abstract:

    This chapter discusses Change Control Board procedure. The purpose of this procedure is to establish the function, authority, and responsibility of the Change Control Board. It defines the Change Control Board and explains the schedule, function, and responsibility of both the committee as a whole and of each committee member. The Change Control Board is a committee whose function it is to review and evaluate all proposed Changes to products. This committee is comprised of a representative from each major functional area of the company. The Change Control Board meets once a week at a location predesignated by the engineering Change analyst. It is imperative that all Change Control Board representatives be punctual. If one or more members are not present at the specified time, the meeting is cancelled. The meeting is chaired by the engineering Change analyst who determines the meeting agenda. Each member reviews each engineering Change package thoroughly during the pre-analysis period. Should any Change Control Board member question a proposed Change, they contact the engineering Change analyst or the responsible engineer during the pre-analysis period, prior to the Change Control Board meeting, for clarification.

  • Engineering Change routing
    Engineering Procedures Handbook, 1998
    Co-Authors: Phillip A Cloud
    Abstract:

    This chapter provides an overview of engineering Change routing procedure. The purpose of this procedure is to provide instructions and to assign responsibilities for routing an engineering Change package through the engineering department. Engineering review Board meeting is held for the purpose of performing a review prior to the engineering Change pre-analysis period. All discrepancies about an engineering Change package are cleared up prior to a Change Control Board meeting. The engineering Change analyst is responsible for the preparation, processing, and routing of an engineering Change package. The engineering Change analyst is aware of the location of the engineering Change package at all times during the process of routing it through the engineering department. Document Control is responsible for making copies of engineering Change packages for the engineering review Board, Change Control Board pre-analysis, and final released distribution. Other responsibilities include microfilming and filing of engineering Change packages, the individual filing of the specifications and master drawings and maintaining engineering Change package distribution lists.

  • Engineering Change costing
    Engineering Procedures Handbook, 1998
    Co-Authors: Phillip A Cloud
    Abstract:

    This chapter provides an overview of engineering Change costing procedure. The purpose of this procedure is to provide instructions and to assign responsibilities for determining the cost of an engineering Change. It also provides instructions for preparing and submitting the cost analysis report form. All cost analysis reports is forwarded by Change Control Board members to document Control. Document Control uses the form for final Change Control Board processing. Each cost analysis report becomes a part of its associated engineering Change, numbered, and identified as such. A cost analysis report is required if the engineering Change calls for labor or material Changes. The associated engineering Change cannot be incorporated until the approved report is included. Each part added, deleted, and/or Changed per an engineering Change is documented on the cost analysis report and counted as a part of the total system cost Change (plus or minus). There are no areas left blank on the cost analysis report form. If any area on the form is not affected by the engineering Change, the person(s) responsible for the cost analysis report completion shall enter not applicable (N/A) in the appropriate space(s).

  • Suffix engineering Change
    Engineering Procedures Handbook, 1998
    Co-Authors: Phillip A Cloud
    Abstract:

    This chapter discusses about suffix engineering Change procedure. This procedure provides instructions and assigns responsibilities for the preparation and release of suffix engineering Changes. A suffix engineering Change is generated as a supplement to a released engineering Change when field or technical manual updates are made necessary by the nature of the original engineering Change. A suffix engineering Change is also used to correct a minor error in the documentation of the original engineering Change, according to the requirements and limitations set forth in this document. No additional Change documentation outside these guidelines is allowed in a suffix engineering Change package. Suffix “EC Number + A” is reserved for field updates field instructions made necessary by the original engineering Change. Suffix “A” is originated by engineering in conduction with field engineering. The Change Control Board is chaired by the manager of cognizant engineering group. One field suffix engineering Change allows per engineering Change. Additional field updates are the responsibility of field engineering and are coordinated through engineering and requires a new engineering Change.

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

  • Toward objective software process information: experiences from a case study
    Software Quality Journal, 2011
    Co-Authors: Jana Samalikova, Rob Kusters, Jos Trienekens, Ton Weijters, Paul Siemons
    Abstract:

    A critical problem in software development is the monitoring, Control and improvement in the processes of software developers. Software processes are often not explicitly modeled, and manuals to support the development work contain abstract guidelines and procedures. Consequently, there are huge differences between ‘actual’ and ‘official’ processes: “the actual process is what you do, with all its omissions, mistakes, and oversights. The official process is what the book, i.e., a quality manual, says you are supposed to do” (Humphrey in A discipline for software engineering. Addison-Wesley, New York, 1995 ). Software developers lack support to identify, analyze and better understand their processes. Consequently, process improvements are often not based on an in-depth understanding of the ‘actual’ processes, but on organization-wide improvement programs or ad hoc initiatives of individual developers. In this paper, we show that, based on particular data from software development projects, the underlying software development processes can be extracted and that automatically more realistic process models can be constructed. This is called software process mining (Rubin et al. in Process mining framework for software processes. Software process dynamics and agility. Springer Berlin, Heidelberg, 2007 ). The goal of process mining is to better understand the development processes, to compare constructed process models with the ‘official’ guidelines and procedures in quality manuals and, subsequently, to improve development processes. This paper reports on process mining case studies in a large industrial company in The Netherlands. The subject of the process mining is a particular process: the Change Control Board (CCB) process. The results of process mining are fed back to practice in order to subsequently improve the CCB process.

A J M M Weijters - One of the best experts on this subject based on the ideXlab platform.

  • Process mining support for Capability Maturity Model Integration-based software process assessment, in principle and in practice
    Journal of Software: Evolution and Process, 2014
    Co-Authors: Jana Samalikova, Jos J M Trienekens, Rj Rob Kusters, A J M M Weijters
    Abstract:

    Currently used software process improvement methods such as the Capability Maturity Model Integration CMMI rely in their process assessments on information, which is gathered during interviews, in oral audit sessions, and from quality manuals and process standard reviews. Although valuable information about software processes can be gained in these assessments, the resulting data quality can be improved upon. This paper investigates the potential of process mining to support current software process assessment and improvement approaches. Based on an analysis of CMMI from a process mining perspective, particular CMMI model components are identified for which it is in principle possible to apply process mining techniques. Subsequently, criteria have been defined to select, with respect to these particular CMMI components, software processes for which process mining has an added value. These criteria have been applied in the selection of a particular 'minable' software process, that is, a Change Control process. Subsequently, the results of a case study from industrial practice, on the process mining of a Change Control Board process, are used to illustrate that process mining can provide CMMI assessors with relevant information. This information reflects the actual or 'real' software processes in practice, and as such, it offers an excellent basis to support assessors in understanding the 'actual' software processes. Copyright © 2014 John Wiley & Sons, Ltd.

  • discovering Changes of the Change Control Board process during a software development project using process mining
    European conference on Software Process Improvement, 2009
    Co-Authors: Jana Samalikova, Jos J M Trienekens, R Rob J Kusters, A J M M Weijters
    Abstract:

    During a software process improvement program, the current state of software development processes is being assessed and improvement actions are being determined. However, these improvement actions are based on process models obtained during interviews and document studies, e.g. quality manuals. Such improvements are scarcely based on the practical way of working in an organization; they do not take into account shortcuts made due to e.g. time pressure. Becoming conscious about the presence of such deviations and understanding their causes and impacts, consequences for particular software process improvement activities in a particular organization could be proposed. This paper reports on the application of process mining techniques to discover shortcomings in the Change Control Board process in an organization during the different lifecycle phases and to determine improvement activities.

  • EuroSPI - Discovering Changes of the Change Control Board Process during a Software Development Project Using Process Mining
    Communications in Computer and Information Science, 2009
    Co-Authors: Jana Samalikova, Jos J M Trienekens, R Rob J Kusters, A J M M Weijters
    Abstract:

    During a software process improvement program, the current state of software development processes is being assessed and improvement actions are being determined. However, these improvement actions are based on process models obtained during interviews and document studies, e.g. quality manuals. Such improvements are scarcely based on the practical way of working in an organization; they do not take into account shortcuts made due to e.g. time pressure. Becoming conscious about the presence of such deviations and understanding their causes and impacts, consequences for particular software process improvement activities in a particular organization could be proposed. This paper reports on the application of process mining techniques to discover shortcomings in the Change Control Board process in an organization during the different lifecycle phases and to determine improvement activities.

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

  • Toward objective software process information: experiences from a case study
    Software Quality Journal, 2011
    Co-Authors: Jana Samalikova, Rob Kusters, Jos Trienekens, Ton Weijters, Paul Siemons
    Abstract:

    A critical problem in software development is the monitoring, Control and improvement in the processes of software developers. Software processes are often not explicitly modeled, and manuals to support the development work contain abstract guidelines and procedures. Consequently, there are huge differences between ‘actual’ and ‘official’ processes: “the actual process is what you do, with all its omissions, mistakes, and oversights. The official process is what the book, i.e., a quality manual, says you are supposed to do” (Humphrey in A discipline for software engineering. Addison-Wesley, New York, 1995 ). Software developers lack support to identify, analyze and better understand their processes. Consequently, process improvements are often not based on an in-depth understanding of the ‘actual’ processes, but on organization-wide improvement programs or ad hoc initiatives of individual developers. In this paper, we show that, based on particular data from software development projects, the underlying software development processes can be extracted and that automatically more realistic process models can be constructed. This is called software process mining (Rubin et al. in Process mining framework for software processes. Software process dynamics and agility. Springer Berlin, Heidelberg, 2007 ). The goal of process mining is to better understand the development processes, to compare constructed process models with the ‘official’ guidelines and procedures in quality manuals and, subsequently, to improve development processes. This paper reports on process mining case studies in a large industrial company in The Netherlands. The subject of the process mining is a particular process: the Change Control Board (CCB) process. The results of process mining are fed back to practice in order to subsequently improve the CCB process.