L.Briand, C. Differding, D. Rombach, Practical Guidelines for Measurement-Based Process Improvement, in: Software Process, 2(4), December 1996.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....organizations to assess their own measurement maturity and that provides directions for the improvement of an organization s measurement processes. We have taken a first step towards validation by comparing our measurement maturity model with other guidelines for implementing measurement programs [1, 2, 3, 4]. In order to facilitate this comparison, we developed a simple four phase process model of measurement based process improvement, see figure 1. The model contains the main activities an organization has to execute to employ measurement based improvement: problem analysis, measurement program ....

L. C. Briand, C. M. Differding, and H. D. Rombach. Practical Guidelines for Measurement-Based Process Improvement. Software Process -- Improvement and Practice, 2(4):253--280, Dec. 1996.

....and its impact on the development process. As basis for this quantification a GQM based measurement program was performed. The GQM approach provides guidelines for defining measurement goals, refining them into measurable entities, and providing a context for data analysis and interpretation [3], 7] Two major processes characterise this approach. Firstly, the explicit measurement goals are refined in a top down manner into measures via questions and models tailored to the environment where measurement takes place. Secondly, the collected data are interpreted in a bottom up manner in ....

Briand, L.C., Differding, C , and Rombach, H.D., "Practical Guidelines for Measurement-Based Process Improvement", Software Process Improvement and Practice Journal, vol. 2, no. 3, 1997.

....deliver statistical results and can be processed automatically. Another advantage of their use is ease of integration with systems covering other indicators. It is important to define goals of measurement and prepare an appropriate measurement plan. This can be done with GQM (Goal Question Metric) [2] approach or FCM (Factor Criteria Metrics) structure [3] or Goal Subgoal Metrics structure [6] In application of software quality defect density metric is used. Although defects are countable ideas, it is not fully objective metric since defect classifications are made by humans. Apart from the ....

Briand, L. C., Differding C. M., Rombach D. H., "Practical Guidelines for Measurement - Based Process Improvement", Technical Report of the International Software Engineering Network (ISERN-96-05), 1996.

....5 months period, from October 99 until February 00. The goal of the case study was to validate the CAP, gain experience, and, if possible, find opportunities for improvement of the CAP. In order to characterise the CAP regarding cost, effort, duration, and benefit, a Goal Question Metric (GQM) [1,9] measurement plan was developed. The GQM goal specification was Analyse the CAP with respect to cost and benefit for the purpose of characterising from the viewpoint of the management in the context of subproject CAP X at SHS . For the sake of brevity, not the entire GQM plan but the metrics will ....

Briand, L.C., Differding, C., Rombach, H.D. Practical Guidelines for Measurement-Based Process Improvement. Software Process Improvement and Practice 2 (4), pp. 253-280, 1996

....known methodology refers to the Goal Question Metric (GQM) technique [Rombach, H.D. 1991] which have been successfully applied to CBR based Knowledge Management [Nick, 1999] The GQM evaluation methodology includes the process, templates and guidelines for the application of GQM as proposed by [Briand et al. 1996]. The GQM methodology is an industrial proven technique that has been successfully used in the Software industry. Fig. 4.1 The Basic principle of Goal Question Metric methodology ################## #################### ## ## ## ## ####### ####### ####### ## ## ######### ###### # # # ....

....tutorials, support team) Does a stable release (not to change within the next 6 months) exist Littlewood editors, Software Reliability and Metrics, pages 217 235. Elsevier Applied Science, London. Julieanne van Zyl, Dan Corbett, 2000 a] Population of a Framework for Understanding and [Briand 1996], Briand L.C. Differding C.M. Rombach H.D. Practical guidelines for measurementbased 39 59 5 Successful Scenarios and Guidelines Successful scenarios and Guidelines are documented strategies and process employed by top of class Applications. One given application can not claimed to be ....

, Briand L.C., Differding C.M., Rombach H.D. , "Practical guidelines for measurementbased process improvement", Software process, 2(4): pages 253-280

.... Personnel, Other. 2.2.3 Human Assessment The Goal Question Metric (GQM) technique [Nick, 1999] proposes the analysis of system performance from the user perspective. The GQM evaluation methodology includes the process, templates and guidelines for the application of GQM as proposed by [Briand et al. 1996]. The GQM methodology is an industrial proven technique that has been successfully used in the Software industry. Time Savings Costs Payback period 18 100 Figure 2.4 The basic principle of Goal Question Metric methodology Components: Ontologies and Problem Solving Methods . In ....

....Costs Payback period 18 100 Figure 2.4 The basic principle of Goal Question Metric methodology Components: Ontologies and Problem Solving Methods . In Proceedings of the IJCAI 99 workshop on Ontologies and ProblemSolving Methods (KRR5) Stockholm, Sweden, August 2, 1999. pp. 1.1 1. 15 [Briand 1996], Briand L.C. Differding C.M. Rombach H.D. Practical guidelines for measurement based process improvement , Software process, 2(4) pages 253 280 [Cohen, 1995] Empirical Methods for Artificial Intelligence , MIT Press [Grninger et al. Michael Grninger, Mark S. Fox, Methodology for the ....

, Briand L.C., Differding C.M., Rombach H.D. , "Practical guidelines for measurement-based process improvement", Software process, 2(4): pages 253-280

....results. In this paper we show how this combined set of internal and external success factors explains the success or failure of five industrial measurement programs. Keywords Measurement programs, success factors, measurement based improvement 1 Introduction Briand, Differding, and Rombach [3] state that Despite significant progress in the last 15 years, implementing a successful measurement program for software development is still a challenging undertaking. Five years later, this observation still stands. Even if all of the commonly agreed upon success factors for measurement ....

....efforts. 3 Success Factors for Measurement Programs In this section, we use the generic process model to illustrate the scope of the set of success factors identified by Hall and Fenton [10] section 3. 1) In [18] we have also mapped a number of other frameworks for measurement programs [3, 4, 5, 16] onto our model, with similar results. Here, we use the Hall and Fenton success factors because their list of consensus success factors has been based on several other sources such as [9, 12, 22] In section 3.2, we discuss an extension of the consensus success factors with four external success ....

Lionel C. Briand, Christiane M. Differding, and H. Dieter Rombach. Practical Guidelines for Measurement-Based Process Improvement. Software Process -- Improvement and Practice,

....Process Implementation and Change Paradigms for Process Implementation and Change Ch. 1, 7 Guidelines for Process Implementation and Change Ch. 11 Ch. 4 Ch. 16 Evaluating the Outcome of Process Implementation and Change Ch. 7 R02 05 02 01 Feiler Humphrey [51] Briand et al. [15] SEL [124] SEPG [54] Dorfmann Thayer [34] Software Engineering Process Concepts Themes Terminology Process Infrastructure The Software Engineering Process Group The Experience Factory Process Measurement Methodology in Process Measurement Process Measurement Paradigms ....

....Process Measurement Paradigms Process Definition Types of Process Definitions Life Cycle Framework Models Ch. 11 Software Life Cycle Process Models Notations for Process Definitions Process Definition Methods Automation R02 05 02 01 Feiler Humphrey [51] Briand et al. [15] SEL [124] SEPG [54] Dorfmann Thayer [34] Qualitative Process Analysis Process Definition Review Root Cause Analysis Process Implementation and Change Paradigms for Process Implementation and Change Guidelines for Process Implementation and Change Evaluating the Outcome of ....

L. Briand, C. Differding, and H. D. Rombach, "Practical Guidelines for Measurement-Based Process Improvement," Software Process Improvement and Practice, vol. 2, pp. 253-280, 1996.

....Fig. 2. LIPEs organizational and management oriented activities and product flow among them. Right Side of Fig. 1: In Non Functional System Test, the system is tested for acceptable levels of non functional quality (e.g. usability, scalability, availability [6]) based on what is stated in the scenarios. Insufficient results are documented in a nonfunctional system test report. System failures are reported as open issues. In Create System Documentation , package level documentation (using e.g. UML diagrams [11] is written as part of the documentation ....

....(GQM) GQM supports the definition of goals and their refinement into metrics as well as the interpretation of the resulting data [1, 2] The GQM paradigm explicitly states goals so that all data collection and interpretation activities are based on a clearly documented rationale. According to [6], goal oriented measurement is the definition of a measurement program based on explicit and precisely defined goals that state how measurement will be used. Advantages of goal oriented measurement are: Goal oriented measurement helps ensure adequacy, consistency, and completeness of the ....

[Article contains additional citation context not shown here]

L. C. Briand, C. Differding, and D. Rombach. Practical Guidelines for MeasurementBased Process Improvement.Software Process: Improvement and Practice, 2(4), 1997.

....results. In this paper we show how this combined set of internal and external success factors explains the success or failure of five industrial measurement programs. Keywords Measurement programs, success factors, measurement based improvement 1 Introduction Briand, Differding, and Rombach [4] state that Despite significant progress in the last 15 years, implementing a successful measurement program for software development is still a challenging undertaking. Five years later, this observation still stands. Even if all of the commonly This paper is an extended version of [24] The ....

....That factor is marked with a question mark, because it is motivated by Hall and Fenton in terms of acceptance of the measurement program by the practitioners, rather than in terms of the added value of the program. In [23] we have also mapped a number of other frameworks for measurement programs [4, 5, 6, 21] onto our model, with similar results. 3.2 External Success Factors Measurements should generate value to the organization. This value is determined outside the measurement program proper. A major factor determining the success of a measurement program is whether or not it actually does create ....

Lionel C. Briand, Christiane M. Differding, and H. Dieter Rombach. Practical Guidelines for Measurement-Based Process Improvement. Software Process -- Improvement and Practice, 2(4):253--280, December 1996.

....conducting measurements systematically. In [27] we showed that GQM also meets the requirements for good measurements in Knowledge Engineering [25, 39] and, thus, is suitable for evaluating a knowledge based system like an EB. Motivations for goal oriented measurement with GQM according to [14] are to deal with the complexity of measurement programs, stimulate a structured discussion about measurement, andensureadequacy,consistency,andcompleteness of a measurement plan (which defines how and when which data has to be collected and validated by whom) Additionally, GQM also helps to ....

Lionel C. Briand, Christiane M. Differding, and H. Dieter Rombach. Practical guidelines for measurement-based process improvement. Software Process, 2(4):253--280, December 1996.

....(data collection procedures and involved personnel) of the corresponding measurement activities. ISERN 99 19 Production and Maintenance of Software Measurement Models G. Cantone and P. Donzelli 3 But, rarely all of these aspects are equally taken into consideration by the adopted approaches [4]. This paper extends some previous works [5, 6] and abstracts on one more paper [7] It aims at integrating in a systematic way all the phases of the life cycle of a measure, by exploiting the findings achieved in the software measurement field, in order to drive software organizations towards a ....

.... [7] Furthermore, some works investigated the implementation and the improvement of measurement plans within a target organization [15] and the integration of software process and measures [16] Finally, some works presented practical guidance to plan and implement software measurement, e.g. [4]; other aimed at introducing reusable models of software quality [17] In order to tackle the complexity of the measurement problem, and to ensure the adequacy, completeness, consistency and reusability of the identified or adopted measurement models (MMs) this paper suggests a goal oriented ....

[Article contains additional citation context not shown here]

Briand, L. C., Differding C. M., and Rombach, H. D., "Practical Guidelines for MeasurementBased Process Improvement", Software Process Improvement and Practice Journal, Vol. 2, 1997. ISERN-99-19 Production and Maintenance of Software Measurement Models G. Cantone and P. Donzelli 17

....software organization [7] Finally, some works claimed a more integrated approach to software measurement. For instance, 8] analysed the intellectual process that is behind the identification and definition of measures; 9] suggested a methodology to specify, verify and use software measures; [10] presented a practical guidance to plan and implement software measurement. This paper introduces to an approach for: integrating and exploiting the variety of software measurement related works to produce an unified view of the life cycle of a measurement model, MMLC; identifying the ....

Briand, L.C., Differding C.M., Rombach, H.D., "Practical Guidelines for Measurement-Based Process Improvement", Software Process Improvement and Practice Journal, Vol. 2, 1997.

....plan has to specify the why (the underlying reasons) the what (attributes to measure) the how (data collection procedures and involved personnel) of the corresponding measurement activities. But, rarely all of these aspects are equally taken into consideration by the used methods [3]. In order to tackle such a complexity, and to ensure adequacy, completeness, consistency and reusability of the identified or adopted measures, this paper suggests a goal oriented measurement model life cycle (MMLC) While benefits vs. costs evaluation, technology transfer, and so on, need MMLCs ....

....step of the MM Creation phase. Goal oriented SHs outline the high level strategy (or alternative strategies) to follow in order to solve the problem represented by a set goal. Hence, within such a strategy, they point out the necessary measurement activities, properly specified as a MP. In [3], the identification of a MP is considered as the process of deriving measurement goals from higher level goals. Here the higher level goals are named improvement goals, which in our understanding can be considered as a sub set of the non functional goal this paper takes into account. Instead a ....

Briand, L. C., Differding C. M., Rombach, H. D., "Practical Guidelines for Measurement-Based Process Improvement", Software Process Improvement and Practice Journal, Vol. 2, 1997.

....5 months period, from October 99 until February 00. The goal of the case study was to validate the CAP, gain experience, and, if possible, find opportunities for improvement of the CAP. In order to characterise the CAP regarding cost, effort, duration, and benefit, a Goal Question Metric (GQM) [1,9] measurement plan was developed. The GQM goal specification was Analyse the CAP with respect to cost and benefit for the purpose of characterising from the viewpoint of the management in the context of subproject CAP X at SHS . For the sake of brevity, not the entire GQM plan but the metrics ....

Briand, L.C., Differding, C., Rombach, H.D. Practical Guidelines for MeasurementBased Process Improvement. Software Process Improvement and Practice 2 (4), pp. 253-280, 1996

....base in practice. The major advantages of CBR in this context are the similarity based retrieval for primarily experiential knowledge and its continuous incremental learning as an integrated part of the reuse process. We demonstrate our approach by using the Goal Question Metric Paradigm (GQM) [BDR97, BW84] as an innovative technology for software engineering measurement. GQM is a goal oriented measurement approach, which helps defining and implementing operational and measurable software improvement goals. It has been successfully applied in several companies [CEM96,BCG92] such as NASA SEL, BOSCH, ....

....providing an explicit rationale for the selection of the underlying measures.The data collected is interpreted in a bottom up fashion in the context of the GQM goal, questions and models, considering the limitations and assumptions underlying each measure. More information on GQM can be found in [BDR97,GB97,GHW95, BW84]. Here, the objective is to facilitate the establishment of measurement programs in practice by reusing experiential knowledge. The following scenarios illustrate how this knowledge can be used in order to support the GQM approach. Scenario 1: Warning for potential failures Tasks of the GQM ....

L. C.Briand,C.M. Differding, H. D. Rombach.Practical Guidelines for Measurement-Based Process Improvement.SoftwareProcess ImprovementandPractice,toappear1997.

....in which inspections was applied. Articles by Barnard and Price [Barnard and Price, 1994] or Weller [Weller, 1992] Weller, 1993] are probably the most cited ones and provide good examples of data collection. In order to make a valid evaluation of inspections, one needs an evaluation model [Briand et al. 1996]. One can discern between models which do not consider costs and models that do consider costs. Models that do not consider the cost for performing inspections are presented in Fagan [Fagan, 1976] Jones [Jones, 1996] Remus [Remus, 1984] Collofello and Woodfield [Collofello and Woodfield, 1989] ....

Briand, L. C., Differding, C. M., and Rombach, H. D. (1996). Practical guidelines for measurementbased process improvement. Software Process, 2(4):253--280.

....frameworks provide a considerable amount of support for the basic activities needed to implement measurement programs. However, we also observe that the guidelines hardly provide any guidance to guarantee successful usage of the measurement program. 1 Introduction Briand, Differding, and Rombach [3] state that Despite significant progress in the last 15 years, implementing a successful measurement program for software development is still a challenging undertaking. In this paper we take a closer look at different frameworks in the literature for implementing measurement programs. One may ....

....process model. We discuss five different sources: the Measurement Technology Maturity Model described by Daskalantonakis, Yacobellis and Basili [5] the Measurement Maturity Model presented by Comer and Chard [4] the Goal oriented Measurement Process described by Briand, Differding and Rombach [3]; the success factors for measurement programs by Hall and Fenton [8] and the Measurement Capability Maturity Model proposed by ourselves in [10] 3.1 The Software Measurement Technology Maturity Framework Daskalantonakis, Yacobellis and Basili [5] define a framework to be used to assess the ....

[Article contains additional citation context not shown here]

Lionel C. Briand, Christiane M. Differding, and H. Dieter Rombach. Practical Guidelines for Measurement-Based Process Improvement. Software Process -- Improvement and Practice, 2(4):253--280, December 1996.

....results. In this paper we show how this combined set of internal and external success factors explains the success or failure of five industrial measurement programs. Keywords Measurement programs, success factors, measurement based improvement 1 Introduction Briand, Differding, and Rombach [3] state that Despite significant progress in the last 15 years, implementing a successful measurement program for software development is still a challenging undertaking. We fully concur with this observation. Even if all of the commonly agreed upon Submitted for publication to Transactions on ....

.... structural model of measurement 3 Success Factors for Measurement Programs In this section, we use the generic process model to illustrate the scope of the set of success factors identified by Hall and Fenton [10] In [19] we have also mapped a number of other frameworks for measurement programs [3, 4, 5, 17] onto our model, with similar results. Next, we discuss an extension of the consensus success factors with four external success factors for software measurement programs. 3.1 Internal Success Factors Hall and Fenton [10] identify a number of consensus success factors for the implementation of ....

Lionel C. Briand, Christiane M. Differding, and H. Dieter Rombach. Practical Guidelines for Measurement-Based Process Improvement. Software Process -- Improvement and Practice, 2(4):253--280, December 1996.

....uses for measurement programs in software organizations, from which we derive additional external success factors. In addition, we propose a number of activities that organizations can use to implement value generating measurement programs. 1. Introduction Briand, Differding, and Rombach [2] state that Despite significant progress in the last 15 years, implementing a successful measurement program for software development is still a challenging undertaking. We fully concur with this observation. Even if all of the commonly agreed upon success factors for measurement programs, as ....

....3. Success factors for measurement programs In this section we use the generic process model described in section 2 to illustrate the scope of the set of success factors identified by Hall and Fenton [7] In [15] we have also mapped a number of other frameworks for measurement programs [5, 4, 2, 13] onto our model. The results thereof are very similar. Hall and Fenton [7] identify a number of consensus success factors for the implementation of measurement programs. Table 1 shows these factors, that were identified after studying other literature, such as [6, 17] A closer look at the ....

L. C. Briand, C. M. Differding, and H. D. Rombach. Practical Guidelines for Measurement-Based Process Improvement. Software Process -- Improvement and Practice, 2(4):253--280, Dec. 1996.

....for defining and executing goal oriented measurement programmes. It originated from the work lead by Prof. Victor Basili at the University of Maryland and NASA Software Engineering Laboratory in 1980 s [3] It has since been further formalised and developed into a practical methodology ( 1] [8], 10] 19] GQM has been used in several European projects ( 4] 6] 9] 15] The ESPRIT project AMI has integrated its own version of the GQM paradigm with CMM style assessment, and developed tools and manuals to support the AMI method. The ESSI CEMP project introduced GQM in three ....

....influence the performance of the quality focus attributes are documented. The Role of GQM in the PROFES Improvement Methodology Submission to CONQUEST 99 7 15 Based on this information, for each measurement goal, a set of questions, metrics, and models can be defined (for details see [3] and [8]) After the measurements have been specified, a mechanism for collecting measurement data is developed. This is described in the measurement plan and in the associated data collection forms. The data is then collected and validated during the software development project according to the ....

Briand, L.C., Differding, C., Rombach, H.D., Practical guidelines for measurement-based process improvement, Software Process Improvement and Practice, 2(3): 253-280, 1996.

.... the existing system CBR PEB (CBRPEB, 1998; Nick and Tautz, 1999) The evaluation methodology is based on the Goal Question Metric (GQM) paradigm (Rombach, 1991) for goal oriented measurement and includes the process, templates, and guidelines for the application of GQM (Gresse et al. 1995; Briand et al. 1996). GQM is an industrialstrength technique that has been successfully used in the field of software engineering at, for example, NASA SEL, Robert Bosch GmbH, Allianz Lebensversicherungs AG, Digital SPA, Schlumberger RPS (CEMP Consortium, 1996) Section 2 introduces the objectives and basics of GQM. ....

....engineering measurement (Basili et al. 1994b; Gresse et al. 1995; Rombach, 1990) which has been successfully applied in several companies. GQM helps to define and implement operational and measurable software improvement goals. Motivations for goal oriented measurement with GQM according to (Briand et al. 1996) ensure adequacy, consistency, and completeness of a measurement plan 3 , deal with the complexity of measurement programs, and stimulate a structured discussion about measurement. Additionally, GQM also helps to systematically develop quality models and validate them in a context. In GQM ....

[Article contains additional citation context not shown here]

Briand, L. C., Differding, C. M., and Rombach, H. D. (1996). Practical guidelines for measurement-based process improvement. Software Process, 2(4):253--280.

.... an effort model can consist of a functional relationship between single process elements and empirically derived effort data) The instrumentation of product and process models for the purpose of applying quality models is represented by GQM models, especially Abstraction Sheets and GQM plans [9, 6, 14]. 2. Instances are software artifacts that are consumed, produced, or modified during the development process. An instance refers to exactly one thing in a specific experiment context (in contrast to models that refer to a group of similar things) Some sample instances stored in the SFB EB are: ....

Lionel C. Briand, Christiane M. Differding, and H. Dieter Rombach. Practical guidelines for measurement-based process improvement. Special issue of International Journal of Software Engineering & Knowledge Engineering, 1997.

....establishment of an experience factory. 5. 2 Choosing the Evaluation Technique For the evaluation a standard technique of the Fraunhofer IESE and the AG Software Engineering of the University of Kaiserslautern for goal oriented measurement and evaluation the Goal Question Metric (GQM) approach [BCR94b, GHW95, BDR96, HR97] is used. GQM is an innovative technology for goal oriented software engineering measurement. GQM helps defining and implementing operational and measurable software improvement goals. It has been successfully applied in several companies, such as NASA SEL, Bosch, Digital, and Schlumberger ....

Lionel C. Briand, Christiane M. Differding, and H. Dieter Rombach. Practical guidelines for measurement -based process improvement. Software Process, 2(4):253--280, December 1996.

....can be defined based on other Measures, hence the reflexive association on the class. PredictiveModels are defined based on refined hypotheses (RefinedHypothesis) which refine previously defined empirical hypotheses. GQM filled the gap between goals and measures by means of questions and models [13], and gave recommendations on how to define them. GQM MEDEA does not rely on questions to fill that gap, but it defines the steps to carry out, the relationships among them, the sources of information, and shows the integrated use of hypotheses, abstractions, and theoretical and empirical ....

....corporation and environment may be a useful starting point, especially if complemented with knowledge provided by the people involved in the development environment. Performing this step in a systematic manner requires goal definition techniques. We use the Goal Question Metric (GQM) paradigm [13], 2] 5] 6] which provides a template and guidelines to define measurement goals and refine them into concrete and realistic questions, which subsequently lead to the definition of measures. Here is a summary of templates that can be used to define goals: Object of study: products, ....

[Article contains additional citation context not shown here]

L. Briand, C. Differding, and D. Rombach, "Practical Guidelines for Measurement-Based Process Improvement," Software Process Improvement and Practice, 1997.

....identify the factors driving the quality of meetings outcomes in the organisation under study. The following subsections describe how the dependent and independent variables are being measured and provides the setting of the study. Using the Goal Question Metric approach to software measurement [4], an initial set of variables was selected with the help of developers and managers. 2.1. Dependent Variable We want to identify the factors driving the quality of meetings outcome. So the dependent variable is the quality of the outcome of a meeting as it was perceived by the participants. ....

L. Briand, C. Differding, D. Rombach. Practical Guidelines for Measurement-Based Process Improvement, Software Process: Practice and Improvement, 1997

....relies on the acquisition of data and factual information in order to suggest process improvement actions. As opposed to the models presented above, it does not rely on a generic model of software development and predefined improvement steps (an overview of this approach to SPI is given in [4]) In the context of measurement based process improvement, another advantage is that precise cost information is usually readily available and can therefore be used for computing quantitative and objective cost estimates. However, it is difficult to determine to which extent the cost figures ....

L. Briand, C. Differding, and H. D. Rombach: "Practical Guidelines for Measurement-Based Process Improvement". InProceedings of ISCN'96, 1996.

No context found.

L.Briand, C. Differding, D. Rombach, Practical Guidelines for Measurement-Based Process Improvement, in: Software Process, 2(4), December 1996.

No context found.

L. C. Briand, C. M. Differding, and H. D. Rombach. Practical guidelines for measurement -based process improvement. Software Process, 2(4):253--280, Dec. 1996.

No context found.

Briand, L. C., Differding, C. M., and Rombach, H. D., 1996. Practical guidelines for measurement-based process improvement. Software Process, 2(4):253-280. Handbook on Software Engineering and Knowledge Engineering

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC