Hetzel, B., Making Software Measurement Work, QEB Publishing Group, 1993, 290 pages.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... software emerged 20 years ago from the empirical results gathered on a sample of MIS applications [7] As it gained wider practitioner acceptance in the 80s, the methods then available have been regularly criticized, notably for their inability to correctly measure the size of real time software [8, 9, 10, 11, 12, 13, 14, 15, 16]. Although many alternatives have been proposed, from the mid 80s to the mid 90s to address this problem, none of them seemed to have gained sufficient recognition from practitioners to be used on a regular basis across a large number of organizations and in many countries. Version 1.0 of Full ....

Hetzel B., Making software measurement work, QEB Publishing Group, 1993, 290 pages.

....software metrics, software process modelling, object oriented approach 1. Introduction It is generally recognized that the best way to assess and improve a software development process is to measure it, that is to measure effort, cost, duration, faults, failures and changes (Fenton 1991, Hetzel 1993). When collected over a number of projects in the same context these measures can be used to build prediction models for future projects (Jones 91) The actual situation in software industry reveals a limited use of process measurement. Measurement methods (such as GQM (Basili and Rombach 1988) ....

....the definition of measures is very low, because the hard part of the job becomes the definition of the process model. 4 2.3. Designing and implementing the technological support This step is dedicated to design and implement the practical environment to implement measurement (see Jones 1991, Hetzel 1993 for a deeper analysis of the topic) Three activities should be considered: collection, storage and analysis of data. For each activity the issues to be considered are: possibility to automate , if yes implementation or purchase of a tool, integration of tools, design and implementation of ....

Hetzel B. , Making software measurement work, QED, 1993.

....are formalized in term of goals, subgoals, subsubgoals and measures. Measures, defined according to Fenton s measurement framework (Fenton 1991) are formalized as scripts on the process model in an OMT query language. Step four is guided by the general principles and techniques of (Jones 1991, Hetzel 1993). The technology supporting process measurements was realized using the tools and libraries provided by G (Menga et al. 1993) the same tool used by the measured development process. The G class libraries include numerous general purpose classes, which made it easy to implement the required ....

Hetzel B. , Making software measurement work, QED, 1993.

....is the sum of the duration of all instance of Process Activity relating to Analysis Document. In activities 4 and 5 procedures to collect, store and analyse measures are designed and the required tools are chosen. This activity is guided by the general principles and techniques of (Jones 1991, Hetzel 1993). Design choices have to be made as regards: automatic or manual collection of data; design of collection procedures, sheets and forms; design of the schema of the database dedicated to store measures; design of analysis procedures and choice of techniques to present the elaborated results. In ....

Hetzel B. ,(1993), Making software measurement work, QED.

....engineering is a difficult discipline within which to conduct experiments. Furthermore, he faults the lack of hard knowledge regarding the effectiveness and utility of software engineering innovations on poor experimental designs and lack of adherence to proper measurement principles. Hetzel [Hetzel 93, p 202] has commented on the difficulty of measuring software processes and comparing their results. To guide the use of measurement within an organization, he recommends a model of software engineering that focuses upon inputs, outputs, and results. This model captures the creation of the ....

....then specify the measures that should be collected in order to track progress toward the goals. Guidelines and templates have been developed to assist the process. However, the measures must be tailored for the environment in which they will be used. This approach contrasts with Hetzel s [Hetzel 93] which is more bottom up. CMM SEI core measures. As pointed out above, for a measurement program to be successful, the set of measures to be tracked must be chosen very carefully so that the 42 CMU SEI 94 TR 13 measures accurately reflect the business and engineering objectives of the ....

Hetzel, William C. Making software measurement work. Boston : QED Pub. Group, 1993.

....by the European Commission, DGIII A, under contract ESSI AEFTA n. 10070. 2 1 INTRODUCTION It is generally recognized that the best way to assess and improve a software development process is to measure it, that is to measure effort, cost, duration, faults, failures and changes (Fenton 1991, Hetzel 1993). When collected over a number of projects in the same context, these measures can be used to build prediction models for future projects (Jones 1991) Also the product must be characterized, internally (size, complexity, modularity) and externally (functionality, usability, efficiency, ....

....but the need of strict coupling between process modelling and process measurement has not yet clearly emerged. Basili and Weiss (1984) consider the measurement process and its validation, but do not couple the measurement process and the surrounding software process. Bache and Bazzana (1994) Hetzel (1993) cite a process model but do not define nor use it. Pfleeger and McGowan (1990) associate sets of measures with the levels of the Capability Maturity Model but do not define measures on a process model. Wolf and Rosenberg (1993) define (implicitly) a process model in terms of production of events, ....

Hetzel B. ,(1993), Making software measurement work, QED.

No context found.

Hetzel, B., Making Software Measurement Work, QEB Publishing Group, 1993, 290 pages.

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