Grady, Robert B. and Caswell, Deborah L. Software metrics: establishing a company-wide program. Prentice-Hall, 1987.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....purpose of helping the project to meet its goals. We call our process the Avaya Software Assessment Process (ASAP) It combines structured interviews with analysis of change data, combining aspects of CMM assessments and quantitative analyses such as used by the SEL, TAME, and others [2] 3] [9], 10] 11] 12] 13] The key aspects of ASAP are as follows. Derive assessment goals from the goals of the organization undergoing assessment, thereby providing understanding of and feedback on a wide variety of issues ranging from product quality to organizational morale to productivity to ....

Grady, Robert B. and Caswell, Deborah L., "Software Metrics: Establishing a Company-Wide Program," Englewood Cliffs N.J.: Prentice-Hall, August 1986.

.... process improvement [1, 2, 3] were often based on ad hoc measurement programmes, which either concentrated on some key aspect of the system (such as defect counts) or came as a byproduct of other activities (such as counting lines of code during compilation) The concept of the Software Factory [4, 5, 6] was based, in part, on the philosophy of measuring every aspect of the development process in order to discover those factors of central importance. Reaction to the limited success of these approaches and attempts to put the work on a more disciplined and scientific footing [7] led to top down ....

Grady, R B and Caswell, D L (1987) "Software Metrics: Establishing a Company-Wide Program", Prentice-Hall.

....It is recognised that many measurement programmes fail due to the lack of senior management commitment [1, 8] Improvement cannot be brought in as if it were a software tool. Management must take the lead in initiating measurement, defining goals and asking for feedback information. Page 3 Grady [2] states that the people who you recruit to implement your objectives send a signal to the rest of the organisation that indicates the importance of the programme. Although the measurement programme had a Development Head as the Chairman of the MWP, Director level commitment was also required to ....

....activity can not be stressed enough. It was therefore decided to incorporate Pulford s pre requisites, plus number of equally important questions into the Foundation activity. Pulford s pre requisites will now be explained further. 4. 1 Management Involvement Both Pulford [1] and Grady [2] agree that it is of up most importance that managers are involved in any measurement programme, and that management must take the lead in initiating measurement, defining goals and asking for feedback results. Therefore, the question that should really be asked is do you have managers ....

[Article contains additional citation context not shown here]

Grady, R.B. and Caswell, D.L. (1987). Software Metrics: Establishing A Company Wide Program. Englewood Cliffs, NJ. Prentice-Hall International.

....that addresses a particular transition situation. Three informal examples of transition processes are Bouldin s on the introduction of computer aided software engineering (CASE) tools in organizations [Bouldin 1989] Grady and Caswell s on the introduction of software metrics at Hewlett Packard [Grady Caswell 1987], and Strauss and Ebenau s on introducing software inspections [Strauss Ebenau 1993] Problem solving strategies can be used to uncover and systematize the dynamics of transition processes, including the goals and constraints that are operating in each situation [Fowler Levine 1992] Skills ....

Grady, R.B. & Caswell, D.L. (1987). Software metrics: Establishing a company-wide program.

....the range of aspects of software quality. Around the same time, Boehm et al. (1978) 4] published an independent list of seven factors. Years later, Bowen, Wigle and Tsai (1985) 5] produced a longer list (thirteen factors) again from work at RADC. Later attempts included Grady and Caswell (1987) [6], Deutsch and Willis (1988) 7] Forse (1989) 8] and von Maryhauser (1990) 9] University Of Strathclyde Department Of Computer Science Research Report 94 171 Page 3 Boehm et al. McCall et al. Bowen et al. Efficiency Reliability Human Engineering Modifiability Portability Testability ....

Grady, R. B. and Caswell, D. L.: 'Software Metrics: Establishing a Company-Wide Program', (Prentice-Hall, 1987)

....density i.e. number of defects per thousands of non comment source statements (KNCSS) where the number in brackets above each bar is the actual size of the system. 7 1990 s Baseline DIRs (Defect Introduction Rates) excluding DIR driver effects. 121 Figure 4. 12: Reported Defect Densities [Grady, 1987] It is very clear from the above figure that defect density varies considerably across the published results. This could partly be attributed to the differences in the definition of a counted defect. As Fenton and Pfleeger reported in their book [Fenton, 1997] these published results mostly ....

Grady, 1987 - Software Metrics: Establishing a Company-wide Program, Grady B. and Caswell D., Prentice Hall, 1987.

.... evaluated in industry on large scale software [Conte et al., 1986] Figure 3: Metrics Need a Firm Foundation Another problem in choosing metrics is that the wrong characteristic of the product or the process may be measured, or the intended objective cannot be measured consistently or accurately [Grady and Caswell 1987]. Moreover, one must ask if a chosen metric is really a reliable indicator of what it purports to measure (Figure 4) Is it sufficiently sensitive to measure an intended attribute For example, the quality of software has many facets. Quality is sometimes measured by combining scores of various ....

Grady, R.B.and D.L. Caswell (1987), Software Metrics: Establishing a Company-Wide Program, Prentice-Hall, Englewood Cliffs, NJ.

....segments and allows the measurer to reason about the object oriented space in a meaningful way. 3. SOFTWARE MEASUREMENT Many researchers have asserted the importance of software measurement. Vollman [26] wrote of the importance of software measurement to society while Grady and Caswell [11] and Chidamber and Kemerer [7] described its importance to management. Measurement is the process whereby numbers or symbols are assigned to dimensions of entities in such a manner as to describe the dimension in a meaningful way. An entity may be a thing or an event, e.g. a person, a play, a ....

Grady, Robert B., and Deborah L. Caswell, Software Metrics: Establishing A Company-Wide Program, Prentice-Hall, Inc., Englewood Cliffs, NJ, 1987.

....Automation INTRODUCTION The average lifetime of software is about 10 years, according to a study [TAM92] of 95 systems drawn from a variety of application domains. Consequently, is hardly surprising that most of the lifecycle costs for software occur during the so called maintenance phase [GRA87], since its duration dwarfs the development phase. Incomplete or nonexistent system documentation was ranked in the top four problems in software maintenance according to a Delphi study run with senior software maintenance managers [DEK92] The other top ranked technical problem was inadequate ....

R. Grady, Software Metrics: Establishing a Company-Wide Program, Prentice-Hall, 1987.

....control, and improve their software processes. We provide examples of some of these indicators in Appendix D, and others can be found in the MITRE metrics [Schultz 88] the proposed Army STEP metrics [Betz 92] the Air Force management indicators [USAF 92] and in publications like [Baumert 92] Grady 87] McGhan 91] McGhan 92] and [Rozum 92] While these publications show many graphs that we can use to help plan and track software products and processes, few define the underlying measures on which their indicators are 2 CMU SEI 92 TR 20 based. Without this information, it is easy for ....

Grady, Robert B.; & Caswell, Deborah L. Software Metrics: Establishing a Company-Wide Program. Englewood Cliffs, N.J.: Prentice-Hall, 1987.

....become familiar with the software engineering literature on the subject before attempting to use the mechanisms discussed in this report. Recent literature that provides a comprehensive overview of software measurements includes the following: Baumert 92] Conte 86] Fenton 91] Grady 92] Grady 87] Humphrey 89] Musa 87] IEEE 88a] Each of the above include extensive listings of papers, reports, and books that provide additional information on the many aspects of software measurement. CMU SEI 92 TR 22 3 4 CMU SEI 92 TR 22 2. Understanding the Framework for Counting Software Problems ....

Grady, Robert B.; & Caswell, Deborah L. Software Metrics: Establishing a Company-Wide Program. Englewood Cliffs, N J.: Prentice-Hall, 1987.

No context found.

Grady, Robert B. and Caswell, Deborah L. Software metrics: establishing a company-wide program. Prentice-Hall, 1987.

No context found.

Grady, Robert B. and Caswell, Deborah L. Software metrics: establishing a company-wide program. Prentice-Hall, 1987.

No context found.

Grady, R. and D. Caswell (1987). Software Metrics: Establishing a Company Wide Program. Prentice Hall.

No context found.

R. B. Grady and D. L. Caswell, Software Metrics: Establishing a Company -Wide Program. Englewood Cliffs, NJ: Prentice-Hall, 1987.

No context found.

Grady R. and Caswell D. "Software Metrics: Establishing a Company-Wide Program", PrenticeHall 1987.

No context found.

Grady, R. and Caswell, D. (1987). Software Metrics: Establishing a Company-Wide Program. Prentice Hall.

No context found.

Grady R.B. and Caswell D.L. (1987) Software Metrics: Establishing a Company-Wide Program, Prentice-Hall.

No context found.

Robert B. Grady and Deborah L. Caswell, Software Metrics: Establishing a Company-Wide Program, Prentice-Hall, Inc., Englewood Cliffs, New Jersey (1987) p.4.

No context found.

R. B. Grady, D. L. Caswell, "Software Metrics: Establishing a Company-Wide Program", Englewood Cliffs, New Jersey: Prentice-Hall, Inc., 1987.

No context found.

Grady, B.R., L. C.D. Software Metrics : Establishing a Company-Wide Program. Prentice-Hall, Inc., Englewood Cliffs, New Jersey, 1987.

No context found.

R. B. Grady and D. L. Caswell, Software Metrics: Establishing a Company-Wide Program. Englewood Cliffs, NJ, EUA: Prentice-Hall, 1987.

No context found.

Grady, Robert B.; & Caswell, Deborah L. Software Metrics: Establishing a Company-Wide Program. Englewood Cliffs, N.J.: Prentice-Hall, 1987.

No context found.

Grady, R. B., and Caswell, D. L., Software Metrics: Establishing a Company-Wide Program. Prentice-Hall Inc., Englewood Cliffs, NJ, 1989.

No context found.

Grady, Robert B., and Deborah L. Caswell. Software Metrics: Establishing a Company-Wide Program. Englewood Cliffs, N.J.: Prentice Hall, 1987.

First 50 documents

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