V. R. Basili, G. Caldiera, and K. D. Rombach. Goal question metric paradigm. In J. J. Marciniak, editor, Encyclopedia of Software Engineering, volume 1, pages 527--532. John Wiley & Sons, 1994.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Table 6. Examples of Metrics. Although groupware offers extensive possibilities for obtaining different types of metrics, these metrics should nevertheless be derived from the overall objectives placed on the NPD process. Here, approaches such as goal question metric approaches (see for example [6]) are helpful in clarifying the process goals and translating these goals into specific metrics. For example, if the main target in improving NPD processes were that of shortening the cycle time, then the role of time oriented metrics would be highlighted, perhaps at the expense of effort related ....

V.R. Basili, G. Caldiera and H.D. Rombach, "Goal Question Metric Paradigm," in J. J. Marciniak (ed.), Encyclopedia of Software Engineering 1, New York: John Wiley & Sons, pp. 528-532, 1994.

....scenarios and decision making for some typical evolution patterns. 4.4 Measurements and Risk Analysis Systematic and valid process improvement can be achieved only by analyzing the process in a quantitative way, i.e. requiring measurements. We can mention the Goal Question Metric (GQM) method [2], that defines goals for software process improvement, before embarking on software measurement tasks. Our method for predictive process evolution relies heavily on software metrics. Thus the project plan should include measurement of the product as well as of the process. In our case, the ....

Victor Basili, Gianluigi Caldiera, and Hans-Dieter Rombach. Goal Question Metric Paradigm. In [16], 1994.

....facilitate knowledge transfer at the Project Organizational level. Such an EF should not assume the role of a conventional, perhaps over controlling quality manager. It should rather encourage unselfish recording, synthesis and sharing of experiences. Likewise, the Goal Question Metrics (GQM) [2] method can facilitate knowledge management at the IndividualPerson level, e.g. by defining lean and relevant metrics and by insisting on regular feedback sessions. 1 3 Some examples of experience databases In a national, Norwegian Software Process Improvement effort, SPIQ (SPI for Better ....

Victor Basili, Gianluigi Caldiera, and Hans-Dieter Rombach. Goal Question Metric Paradigm. In [5], 1994.

.... are elaborated in the NFR framework [CNYM00] or classification e.g. as provided by the standard ISO IEC 9126 [ISO9126] The latter are often enhanced with domain specific knowledge as in the language extended lexicon (LEL) advocated by [CLN01] or a general knowledge base on NFRs (e.g. BI96] GQM [BCR94] is a general technique for decomposing high level NFRs into verifiable metrics. Documentation involves the following issues: how to describe NFRs, which additional information is necessary to deal with them [BKLW95] distinguishes different facets on how to describe NFRs, namely concerns, system ....

V.R. Basili, G. Caldiera, & H.D. Rombach, "Goal Question Metric Paradigm", In J.J. Marciniak (ed.), Encyclopedia of Software Engineering, vol. 1, pp.528-532, John Wiley & Sons, 1994.

....and can be performed without bias. The biggest problem with metrics is, however, the selection of metrics and the interpretation of the results. Interpretation of data from measurements must be compared to pre defined criteria that are derived from a goal. The Goal Question Metric (GQM) approach [3] helps derive metrics from questions based on the goals of the measurement program. Selecting a perspective for evaluation: Maintainability A system can be evaluated with different goals in mind and from many different perspectives. For this study we focus on maintainability, i.e. making the ....

Basili, V. R., Caldiera, G. and Rombach, H. D., "The Goal Question Metric Paradigm", Encyclopedia of Software Engineering - 2 Volume Set, pp 528-532, Copyright by John Wiley & Sons, Inc., 1994.

....making) Controlling performance of the knowledge related activities by continuously measuring performance indicators of these activities and quality indicators of the knowledge handled as well as of the results created with the help of the knowledge. The Goal Question Metrics (GQM) approach [5] is a flexible and effectively applicable approach to perform measurement of software processes, products and projects. By applying GQM, information is identified that is relevant to solving specific problems (goals) and that can be represented in a practical, applicable and interpretable way. ....

V.R. Basili, G. Caldiera, H.D. Rombach. Goal-Question-Metric Paradigm. In: J. Marciniak: Encyclopedia of Software Engineering, Volume 1, 1994, pp 528-532

....frameworks and improvement strategies [WCR97] need to be adapted to distributed contexts. The Goal Question Metric (GQM) BR88, BW88] represents a structured and systematic approach for data collection, based upon the specific needs of the project and the organization. Furthermore, as reported in [BCR94], It can be used in isolation or, better, within the context of a more general approach to software process improvement. This work suggests a new measurement approach, called Distributed GQM (D GQM) developed to overcome the limits of the classic GQM in distributed contexts. 2 The GQM The ....

....This work suggests a new measurement approach, called Distributed GQM (D GQM) developed to overcome the limits of the classic GQM in distributed contexts. 2 The GQM The main idea behind GQM is that measurement should be goal oriented and based on context characterization. According to [BCR94], the measurement model has three levels: Conceptual Level (GOAL) a goal is defined for a specific purpose based on the needs of the organization, for a variety of reasons, with respect to various quality models, from various points of view, relative to a particular environment. Operational ....

V.R. Basili, G. Caldiera, H.D. Rombach, "Goal Question Metric Paradigm", Encyclopedia of Software Engineering, John Wiley & Sons, Volume 1, 1994, pp. 528-532.

....The capability of the software product to enable modified software to be validated. e) Compliance: The capability of the software product to adhere to standards or conventions relating to maintainability. 4.2. Measuring evolvability The latest draft of ISO IEC 9126, follows the GQM approach [2, 3] to derive metrics for evolvability. Each sub characteristic acts as a goal that generates questions that have to be answered to achieve the goal. Then metrics are defined to provide the information to answer each question. Interpretations of measured value are also provided in the standard, which ....

V.R. Basili, C. Caldiera, and H.D. Rombach, "Goal Question Metric paradigm" in Encyclopedia of software engineering, vol. 1, J.J. Marciniak, Ed. John Wiley & Sons, 1994, pp. 528-532.

....planning has been initiated] OR [new goals or stakeholders are identified] OR [a change in goals or stakeholders has been recognized] Input: Project authorization information: goals, resources, schedule, budget. Risk management mandate. Output: Goal definitions. Methods and tools: GQM [4,6] Responsibility: Project manager. Resources: Project owner, project stakeholders, project personnel. Exit criteria: Goals are explicitly documented and participants agree with their definition. Table 8: The process definition information for the goal review process In the Riskit method we ....

....information items, such as observing personnel morale or monitoring database technology developments . We recommend the use of GQM as a systematic method for defining such metrics, with modifications to include any information items as leaves in GQM trees, not just traditional metrics [4,6]. The second main option in Figure 11 is contingency planning. It means that recovery plans are made for a risk scenarios but no further action is taken. Strictly speaking, contingency plans have rather marginal effect on risk reduction as they mainly buy time and marginal effort in advance. ....

V.R. Basili, G. Caldiera, and H.D. Rombach. Goal Question Metric Paradigm. In: Encyclopedia of Software Engineering, ed. J.J. Marciniak. New York: John Wiley & Sons, 1994. pp. 528-532.

....data will be collected. These data, also called metrics, form the third level in the GQM hierarchy. The metrics can be objective or subjective. The difference between the two is that subjective metrics depend on the point of view of the person generating the metrics, but objective metrics do not [BasiliCaldieraRombach94]. The data gathered must address the questions of interest generated in the previous step. Just as one question may help address more than one goal, one metric may partially answer more than one question. One of the advantages of establishing goals before choosing metrics can be seen here: since ....

....more motivated and desire to accomplish the task successfully. Michael Fredericks Page 44 06 03 99 M e t r i c Q u e s i o n G o a l 2 G o a l 1 Q u e s i o n Q u e s i o n Q u e s t o n Q u e s t o n M e r c M e t r i c M e t r i c M e r c M e t r i c Fig 7. GQM model hierarchical structure [BasiliCaldieraRombach94] Goal Purpose Issue Object (process) Viewpoint Improve the timeliness of change request processing from the project manager s viewpoint Question Q1 What is the current request processing speed Metrics M1 M2 M3 Average Cycle Time Standard deviation cases outside of the upper limit Question Q2 ....

[Article contains additional citation context not shown here]

Basili, Victor R., Gianluigi Caldiera, and H. Dieter Rombach (1994). "Goal Question Metric Paradigm." Reprinted from Encyclopedia of Software Engineering -- 2 Volume Set. John Wiley & Sons, Inc.

....reported from numerous organisations (cf. 4] 5] 6] 7] 9] 10] and [11] However, quite little is known about the detailed benefit, cost, and success factors of measurement. At Schlumberger Retail Petroleum Systems (RPS) measurement according to the Goal Question Metric (GQM) approach [1] [8] has been introduced in 1994. The measurement activities have been the object of continuous observation and several in depth studies. Some of which have been conducted in European technology transfer projects like CEMP 2 and PROFES 3 . Improvement initiatives at Schlumberger reach back to ....

V.R. Basili, G. Caldiera, and H.D. Rombach. Goal Question Metric Paradigm. In J.J. Marciniak, ed., Encycl. of SW Eng., vol. 1, pp. 528--532. John Wiley & Sons, 1994.

....to check if the behavior of the software system conforms to the software system description. In addition to the tasks listed above, each role should gather measurement data for quality control and or process improvement based on, for instance, goal oriented measurement programs as proposed in [5]. Management Roles. Management Roles are responsible for planning and managing project execution. We identify four main management roles: 1. Product Manager: The Product Manager initiates, evaluates, and controls the consistent change of project information during product (i.e. system) ....

V. R. Basili, G. Caldiera, H. D. Rombach. Goal Question Metric Paradigm. In J. J. Marciniak (ed.), Encyclopedia of Software Engineering, Volume 1, John Wiley & Sons, 1994, 528--532.

....allowing to select both an appropriate set of specifications to be checked and the (sub )set of consistency conditions to be applied. 4. 2 Validation of Specifications Today in practical systems development, validation techniques, in contrast to formal verification techniques, are widely used [BCR94] to gain more confidence in specifications and implementations fulfilling their requirements. However, only verification techniques can prove correctness. They will be treated in the next section. Validation techniques are the focus of this section. They cover a broad range of diverse techniques, ....

V.R. Basili, G. Caldiera, and H.-D. Rombach. Goal Question Metric Paradigm. In J.J. Marciniak, editor, Encyclopedia of Software Engineering, pages 528--532. John Wiley & Sons, 1994.

....assessment, software measurements, product and process dependency relationships, and experience factory. Software process assessment is based on the ISO 15504 for software process assessment 1 [3] Software measurements are goal oriented and based on the goal question metrics (GQM) approach [2]. The ISO 9126 [7] is used as the background reference for the product quality characteristics when defining the product process relationships. The integration of the methods is aligned with the Quality Improvement Paradigm (QIP) 16] that forms the overall structure of the methodology. The ....

....of the process dimension thus allowing a common improvement strategy. In addition to the ISO 15504 conformant output profiles, the BOOTSTRAP method generates also synthetic profiles using quartiles within the capability levels. 2. 2 The Goal Question Metrics approach Goal oriented measurement [2] represents a systematic approach for tailoring and integrating objectives of an organisation into measurement goals and their stepwise refinement into measurable values. The GQM method was chosen as an element of the PROFES improvement methodology as it is the most mature and widely used ....

[Article contains additional citation context not shown here]

Victor R. Basili, Gianluigi Caldiera, and H. Dieter Rombach. Goal Question Metric Paradigm. In John J. Marciniak, editor, Encyclopaedia of Software Engineering, Vol. 1, pages 528--532. John Wiley & Sons, 1994.

....the BOOTSTRAP methodology has been enhanced to fulfill the requirements stated for embedded systems development through the extension with new embedded software specific process areas. 2. 2 GQM One of the most popular methods for software measurement is the Goal Question Metrics approach (GQM) [1] [10] depicted in Figure 1. Implicit Models Q1 Q2 Q3 Q4 GOAL M1 M2 M3 M4 M5 M6 M7 Definition Interpretation Influencing factors Quality models Figure 1: The Goal Question Metric paradigm GQM represents a systematic approach to tailoring and integrating goals with models of the ....

Basili, Victor R., Caldiera, Gianluigi, and Rombach, H. Dieter. "Goal Question Metric Paradigm". In John J. Marciniak, editor, Encyclopaedia of Software Engineering, Volume 1, John Wiley & Sons, 1994, pp. 528-- 532.

.... techniques, and tools available to engineers are to be applied to the problem, unless there is a compelling reason not to do so [105] Measuring results against criteria Science and engineering can be neither effective nor practical without measurement [38] Basili, Caldiera, and Rombach [9] write that an engineering discipline requires a measurement mechanism to provide feedback and assist in evaluation. In [28] DeMarco supports this view, stating, You cannot control what you cannot measure. 1.2.1. Object Oriented Analysis and Design Methodologies To address recurring issues ....

....collection of metrics to accurately measure the characteristics of interest. One approach to this problem is the Goal Question Metric paradigm, which outlines a mechanism for defining and interpreting operational, measurable goals [8] This technique advocates a three level model of measurement [9]: 33 1. Conceptual Level (goal) defined for an object with respect to various models or issues (quality) from various points of view. 2. Operational Level (question) set of questions developed to verify or assess the achievement of a particular goal. 3. Quantitative Level (metric) set of ....

[Article contains additional citation context not shown here]

V. R. Basili, G. Caldiera, and H. D. Rombach. (1994) "Goal Question Metric Paradigm," in Encyclopedia of Software Engineering, J. Marciniak, Ed. New York: John Wiley & Sons, 528-532.

....to know what goals they should have. Management does not have enough knowledge to define correct and suitable goals. Basili implies that the process of finding goals and the derivation of questions out of them is a complex matter which requires experience [Basili88] Further, Basili writes in [Basili94a] that the GQM paradigm approach may, in the beginning, has had as goal to help out with what goals to set up (templates guidelines for goal definition are included in [Basili88] However, throughout the years that the GQM has been used, the GQM has increasingly been included as a part of a bigger ....

....G3 Improve delivery date precision of the software G4 Improve (decrease) lead time of the software G5 Evaluate the type of defects found in the software These goals were derived from the interviews and the theory presented in section 2.1. The goals were set up by using the guidelines in [Basili94a]. As mentioned earlier, goals are rather straightforward to define. One problem with the GQM paradigm is to find correct questions derived from the goals. To every goal, we only managed to come up with a few questions and all the questions were rather similar for every goal. The questions are very ....

Basili, Victor R., Caldiera, Gianluigi and Rombach, Dieter H., "Goal Question Metric Paradigm", in Encyclopedia of Software Engineering, Vol. 1, editor: J. J. Marciniak, pp. 528-532, John Wiley and Sons, US, 1994.

....method 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 ....

....and integrated to suit the needs of individual software organisations or projects. The integration of well established improvement techniques such as process assessment (e.g. ISO 15504 SPICE [13] and BOOTSTRAP [14] goal oriented measurement following the Goal Question Metric (GQM) approach [1] [3] 19] process modelling, and product assessment. The PROFES improvement methodology is modular and supports the integration of improvement techniques in a way that is most beneficial for each individual software organisation. A continuous improvement cycle according to the Quality ....

[Article contains additional citation context not shown here]

Basili, V.R., Caldiera G., Rombach, H.D., Goal Question Metric Paradigm, in John J. Marciniak, editor, Encyclopaedia of Software Engineering, Vol. 1, pp. 528--532, John Wiley & Sons, 1994.

....be systematically improved and rolled out. Section 6 states the relation to existing work in the field. Section 7 gives some conclusions and future work. 2 GQM: OBJECTIVES AND BASICS As already stated, GQM is an industrial strength technology for goal oriented software 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 ....

Basili, V. R., Caldiera, G., and Rombach, H. D. (1994b). Goal Question Metric Paradigm. In Marciniak, J. J., editor, Encyclopedia of Software Engineering, volume 1, pages 528--532. John Wiley & Sons.

....metrics in a top down fashion. Metrics are integrated into products and processes as well, so that during the process execution they can be collected, and then analyzed in order to learn how to better proceed for future projects. In APEL, the GQM (Goal Question Metric) approach from Basili et al. [51, 52] was chosen. GQM is an approach for goal oriented measurement in software projects which supports measurement of products and processes. The principles upon which the GQM approach is built include: Set explicit measurement goals by considering the object (e.g. product or process) under study, ....

V. R. Basili, G. Caldiera, and H. D. Rombach. "Goal-Question-Metric Paradigm". In Encyclopedia of Software Engineering, vol. 1 pages 469-476. John Wiley & Sons, 1994.

....vector was instantiated completely and the most similar project was chosen as the reuse candidate. Both vectors are shown partially in Tab. 4.1 with differences marked in grey. QIP 2:Set Goals The effort distribution chosen as the sample goal was defined formally according to the GQM paradigm [5]. This includes, among others, the definition of the object observed, which is the underlying process model on a defined The first step of the QIP defines two activities: 1.1) Characterize the environmental factors for the experiment (1.2) Select the most suitable artifacts for reuse The second ....

Victor R. Basili, Gianluigi Caldiera, and H. Dieter Rombach. Goal Question Metric Paradigm. In John J. Marciniak, editor, Encyclopedia of Software Engineering, volume 1, pages 528--532. John Wiley & Sons, 1994.

....will be discussed and a short conclusion will be given in the following section. SFB 501 A1 Outlook and Conclusion 14 5 Outlook and Conclusion One key feature of goal orineted improvement is the definition of quality measures, e.g. gained by applying the Goal Question Metric (GQM) paradigm [3]. Measurement data have to be captured before and during the enactment phase. Support can be implemented by web technology via HTML template pages representing a questionnaire. The user who has to provide these data can fill in values into the corresponding fields or select values out of a ....

Victor R. Basili, Gianluigi Caldiera, and H. Dieter Rombach. Goal Question Metric Paradigm.. In John J. Marciniak, editor, Encyclopedia of Software Engineering, volume 1, pages 528--532, John Wiley & Sons, 1994.

.... attributes which correspond to measurable qualities of the objects; processes, products, and resources are instantiated with respect to types and related by a project plan [7] A second notation is used to represent GQM trees which are specifications of measurement goals from a specific viewpoint [4]. The discussion of GQM is beyond the scope of this paper. MVP L has been evaluated in several industrial settings (e.g. 15] The case studies feedback became input for evolution of MVP L. Table 1 summarizes the main concepts of MVP L. MVP E s process engine MVP S uses a project plan and ....

Victor R. Basili, Gianluigi Caldiera, and H. Dieter Rombach. Goal Question Metric Paradigm. In John J. Marciniak, editor, Encyclopedia of Software Engineering, volume 1, pages 528--532. John Wiley & Sons, 1994.

....5 Evaluating an Experience Factory Base 5.1 Choosing the Evaluation Focus Basili, Caldiera, and Rombach propose that software development must be seen and treated as a business. As already stated, an experience factory is established to improve this business by supporting and improving reuse [BCR94b]. Since the obvious ultimate goal of a business is success especially economic success , an evaluation of an experience factory and its experience base must focus on its success. Then, such an evaluation can be used to justify the establishment of an experience factory. 5.2 Choosing the ....

....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 ....

Victor R. Basili, Gianluigi Caldiera, and H. Dieter Rombach. Goal Question Metric Paradigm. In John J. Marciniak, editor, Encyclopedia of Software Engineering, volume 1, pages 528--532. John Wiley & Sons, 1994.

....with special emphasis on reusing experience and resulting needs. To demonstrate characteristics of the presented approach, an exemplary view is given to package experience resulting from a measurement based improvement program based on the application of the Goal Question Metric Approach (GQM) [6, 13]. Then we present our approach of quality patterns for structuring and storing experience models by using the idea of pattern languages. In the following section an implementation of an experience base, which supports the handling of quality patterns, is provided. Finally, conclusions and remarks ....

....need to describe goals, i.e. express what should be and why it should be investigated, and derive related metrics, i.e. define how to do the investigation and how to analyze the collected data. The most popular 2 way within the QIP is the application of the Goal Question Metric Approach (GQM, [6]) The idea of this approach is to derive metrics from a given goal by breaking down this goal through several levels of abstraction. To assist the definition of understandable goals, the GQM approach suggests a scheme that covers the following facets: object, purpose, quality focus, viewpoint, ....

V. Basili, G. Caldiera, and H. Rombach. Goal question metric paradigm. In Marciniak [17], pages 528--532.

....process improvement is a major goal for many software organizations. One framework for continuous software process improvement is the quality improvement paradigm (QIP) as introduced by Basili in [4, 1] In the context of the QIP, measurement according to the Goal Question Metric (GQM) paradigm [3] is a key technology. GQM is an approach to goal oriented measurement of software products and processes. The work described here was supported by Robert Bosch GmbH, Stuttgart, Germany. A prerequisite for any measurement program is a deep understanding of the processes and products to be ....

V. R. Basili, G. Caldiera, and H. D. Rombach. Goal Question Metric Paradigm. In J. J. Marciniak, editor, Encyclopedia of Software Engineering, volume 1, pages 528--532. John Wiley & Sons, 1994.

....(Section 5.2) the experiment design (Section 5.3) and the details of the data collection process (Section 5.4) 5. 1 Measurement Instrument used for Gathering Data We have used techniques from Social Sciences and MIS to add to Basili s Goal Question Metric measurement paradigm, GQM [8], especially in the area of validation tests [13] The goals of our investigation and constructs were published in a 3 page workshop position paper [31] at the start of our experiment. Below we describe the steps which we followed in our GQM derivative method: 1. Identify a set of goals based upon ....

Basili, V., Rombach H., "Goal Question Metric Paradigm," Encyclopedia of Software Engineering, vol. 2, 1994, John Wiley & Sons, Inc.

....scenarios and decision making for some typical evolution patterns. 4.4 Measurements and Risk Analysis Systematic and valid process improvement can be achieved only by analyzing the process in a quantitative way, i.e. requiring measurements. We can mention the Goal QuestionMetric (GQM) method [2], that defines goals for software process improvement, before embarking on software measurement tasks. Our method for predictive process evolution relies heavily on software metrics. Thus the project plan should include measurement of the product as well as of the process. In our case, the process ....

Victor Basili, Gianluigi Caldiera, and Hans-Dieter Rombach. Goal Question Metric Paradigm. In [17], 1994.

....and differences between our replication and the original experiment, and discuss the problems encountered during the preparation, execution and analysis of the experiment. 2. 1 Goals and Hypotheses The main goal of the original experiment can be defined using a Goal Question Metric (GQM) template (Basili, 1994): 4 Analyze the detection techniques for SRS inspections for the purpose of assessment with respect to the number and type of defects uncovered from the point of view of the researcher We established hypotheses in order to confirm the results of the original experiment. The original ....

Basili, V. R., Caldiera, G., and Rombach, H. D., 1994. Goal Question Metric paradigm. Encyclopedia of Software Engineering. Marciniak J. J. (ed.), Ney York, NY: John Wiley & Sons.

No context found.

Basili, V.R., Caldiera, G., and Rombach, H.D. "Goal Question Metric Paradigm." Encyclopedia of Software Engineering. John Wiley & Sons, 1994. 528-532.

....data will be collected. These data, also called metrics, form the third level in the GQM hierarchy. The metrics can be objective or subjective. The difference between the two is that subjective metrics depend on the point of view of the person generating the metrics, but objective metrics do not [BasiliCaldieraRombach94]. The data gathered must address the questions of interest generated in the previous step. Just as one question may help address more than one goal, one metric may partially answer more than one question. One of the advantages of establishing goals before choosing metrics can be seen here: since ....

....Question Q5 Is the current performance satisfactory from the point of view of the project manager Metrics M7 Subjective evaluation by Project manager Question Q6 Is the performance visibly improving Metrics M8 Current average cycle time 100 Baseline average cycle time Fig 8. Example GQM Model [BasiliCaldieraRombach94] Fig 7. GQM model hierarchical structure [BasiliCaldieraRombach94] Goal 1 Goal 2 Question Question Question Question Question Metric Metric Metric Metric Metric Metric ################################## 23 Using Defect Tracking and Analysis to Improve Software Quality C. Tools and Procedures ....

[Article contains additional citation context not shown here]

Basili, Victor R., Gianluigi Caldiera, and H. Dieter Rombach (1994). "Goal Question Metric Paradigm." Reprinted from Encyclopedia of Software Engineering -- 2 Volume Set. John Wiley & Sons, Inc.

....in part how that data can be analyzed. We suggest using the GQM Paradigm to support the processes of stating goals, refining goals in an operational way into metrics, and interpreting the resulting data. The GQM Paradigm supports the definition of goals and their refinement into concrete metrics [BR88, BCR94, DHL96]. The idea behind the GQM Paradigm is that measurement should be based on goals. By stating goals explicitly, all data collection and interpretation activities are based on a clearly documented rationale. Goal template. We can derive a series of goals for this class of experiments using the ....

Victor R. Basili, Gianluigi Caldiera, and H. Dieter Rombach. Goal Question Metric Paradigm. In John J. Marciniak, editor, Encyclopedia of Software Engineering, volume 1, pages 528--532. John Wiley & Sons, 1994.

....process) In general, a quality model (QM) can be seen as a function accepting some measurement data and producing a statement about whether a particular quality goal has been achieved or not. The GQM approach may be used to specify the interpretation rules for quality models in a structured way [2]. Processes can be related to quality models via attributes. Any quality model QM=f(m 1 ,m 2 , m n ) defined in terms of n measures m i , can be reflected via attributes in MVP L. Each process measure m i is defined as an attribute within a process model. Similarly, product and ....

Victor R. Basili, Gianluigi Caldiera, and H. Dieter Rombach, "Goal Question Metric Paradigm ", Encyclopedia of Software Engineering, John C. Marciniak (Ed.), John Wiley & Sons, Volume I, 1994, pages 528 - 532.

No context found.

V. R. Basili, G. Caldiera, and K. D. Rombach. Goal question metric paradigm. In J. J. Marciniak, editor, Encyclopedia of Software Engineering, volume 1, pages 527--532. John Wiley & Sons, 1994.

No context found.

Basili V.R., Caldiera G. and Rombach H.D., "Goal/Question/Metric Paradigm." In Marciniak J.J., editor, Encyclopedia of Software Engineering, volume 1, pages 528-532. John Wiley & Sons, 1994.

No context found.

Basili, V. R., Caldiera, G., Rombach, H. D.: Goal Question Metric Paradigm. In J. J. Marciniak (ed.), Encyclopedia of Software Engineering, John Wiley & Sons (1994)

No context found.

Basili, V. R., Caldiera, G., & Rombach, H. D. (1994). Goal question metric paradigm. In J. J.

No context found.

V. R. Basili. Goal Question Metrics Paradigm, in Encyclopedia of Software Engineering (J. Marciniak ed.), pages 528--532. John Weily and Sons, 1994.

No context found.

V.R. Basili, C. Caldiera, and H.D. Rombach, "Goal/Question/ Metric Paradigm," Encyclopaedia of Software Engineering, Vol. 1, J.J. Marciniak, ed., John Wiley and Sons, New York, 1994, pp. 528-532.

No context found.

V. R. Basili, G. Caldiera, and H. D. Rombach. Goal Question Metric Paradigm. In J. J. Marciniak, editor, Encyclopedia of Software Engineering, volume 1, pages 528--532. John Wiley & Sons, 1994.

No context found.

Victor R. Basili, Gianluigi Caldiera, and Hans-Dieter Rombach: "The Goal Question Metric Paradigm", In

No context found.

V. R. Basili, G. Caldiera, and H. D. Rombach. "Goal-Question-Metric Paradigm". In Encyclopedia of Software Engineering, vol. 1 pages 469-476. John Wiley & Sons, 1994.

No context found.

. V. Basili, C. Caldeira, and H. D. Rombach, Goal Question Metric Paradigm, in J. Marciniak (ed.), Encyclopedia of Software Engineering, John Wiley and Sons, 1994, pp. 528-532.

No context found.

V.R. Basili, G. Caldiera, & H.D. Rombach, "Goal Question Metric Paradigm", In J.J. Marciniak (ed.), Encyclopedia of Software Engineering, vol.1, pp.528--532, John Wiley & Sons, 1994.

No context found.

Basili, V., Caldiera, G., Rombach, H.D. Goal Question Metric Paradigm. In Encyclopedia of Software Engineering. John Wiley & Sons, #1994#.

No context found.

.

No context found.

V. R. Basili, G. Caldiera, and H. D. Rombach. Goal Question Metric Paradigm. In: Ensyclopedia of Software Engineering, ed. J. J. Marciniak. New York: John Wiley & Sons, 1994.pp. 528-532.

No context found.

V.R. Basili, G. Caldiera, and H.D. Rombach. Goal Question Metric Paradigm. In: Encyclopedia of Software Engineering, ed. J.J. Marciniak. New York: John Wiley & Sons, 1994. pp. 528-532.

No context found.

Victor R. Basili, Gianluigi Caldiera, and H. Dieter Rombach. Goal Question Metric Paradigm. In John J. Marciniak, editor, Encyclopedia of Software Engineering, volume 1, pages 528-- 532. John Wiley & Sons, 1994.

No context found.

Basili, V.; Caldiera, G; Rombach H.D. (1994b): Goal question metric paradigm. In: Marciniak, J. (ed.): Encyclopedia of Software Engineering, vol. 1. Wiley, New York, pp. 528-532.

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