B. P. Lientz and E. B. Swanson. Software maintenance management: a study of the maintenance of computer application software in 487 data processing organizations. AddisonWesley, 1980.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....available and many systems are being built with some change support in place. Because of this, there is a need for a common vocabulary and conceptual framework to categorize and compare the evolution support o#ered by the various tools and techniques. More than two decades ago, Lientz and Swanson [26] proposed a mutually exclusive and exhaustive software maintenance typology that distinguishes between perfective, adaptive and corrective maintenance activities. This typology was further refined in [7] into an evidence based classification of 12 di#erent types of software evolution and software ....

....did not cope with all possible aspects of software change. For example, the who question identifies the stakeholders involved in software change, which is an important influencing factor that is not covered in the current taxonomy. The why question is also excluded since it has been treated in [26, 7]. Secondly, the proposed taxonomy provides only one of the infinitely many ways in which software change mechanisms can be grouped. Finally, the taxonomy is subject to continuous evolution, since the elements that it classifies continue to evolve, due to scientific and technological advances in ....

B. P. Lientz and E. B. Swanson. Software maintenance management: a study of the maintenance of computer application software in 487 data processing organizations. Addison-Wesley, 1980.

....from scratch, nowadays software development has to deal more and more with understanding and reworking legacy programs which have evolved over times. Studies on the effort on software development prove that the portion spent for software maintenance has increased dramatically from 49 in 1977 [28] to more than 90 in 1995 [29] cf. 30, p 31] Incremental software development approaches like Extreme Programming [3] suspend the artifical distinction between software development and software maintenance. Understanding, changing, correcting, and adapting software systems are immanent steps ....

Lientz, B. P. and E. B. Swanson, "Software Maintenance Management, A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations", Addison-Wesley, 1980.

....the way for their improvement. Results from an experiment to evaluate the performance of two architecture recovery techniques suggested by Hutchens and Basili are presented. 1 Introduction It has been widely acknowledged that software maintenance consumes 60 80 of a software system s total cost [LS80]. The activities performed during maintenance may broadly be classified as: a) understand how the software functions, b) design and implement a change, and c) validate the change [Par86] The working of a program is typically understood by reading its source code and documentation. While reading ....

B. Lientz and E. Swanson. Software Maintenance Management: A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. Addison-Wesley, Reading, MA, 1980.

....Compare this with the frequently heard phrase that 30 percent of the total costs of a system are devoted to its initial construction: the remaining 70 percent are spent on maintenance and adjustments to new requirements and new operating environments. These costs are confirmed in many studies [28, 30]. 29] gives a recent summary of these findings. The decreases at Hartford Insurance were not caused by a decrease in the volume or amount of changes. Rather, the decreases were attributable to their program of restructuring and remodularizing their legacy systems prior to carrying out extensive ....

B.P. Lientz and E.B. Swanson. Software Maintenance Management---A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. Reading MA: Addison-Wesley, 1980.

....commenting style, variable naming conventions, etc [35] So maybe we could argue that there is no such measure at all. Still, the wish from many companies is to improve maintainability after all major part of the total cost of a system is due to maintenance, as is confirmed in many studies [32, 38]; 36] gives a recent summary of these findings. It is also known that programmers working on a system for some time, typically maintenance programmers, consider the code to be their own [47] Due to this fact, special care should be taken towards code inspections in general [20] or temporarily ....

B.P. Lientz and E.B. Swanson. Software Maintenance Management---A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. Reading MA: Addison-Wesley, 1980.

....in general, software maintenance gets out of hand. One of the most well known facts about software maintenance is that it is expensive in manpower and resources. Estimates of the magnitude of software maintenance costs range from 50 to slightly more than 80 of overall software life cycle costs [39, 12, 35, 76, 86, 13, 58, 65, 83, 78]. Not only the total cost is high, but also the cost per unit of work is high. Already in the early seventies the ratio of the costs for development to costs for maintenance was more than 1 to 50 [103] This ratio has gone up since then. One study reveals that only 8 of the postrelease work on ....

B.P. Lientz and E.B. Swanson. Software Maintenance Management---A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. Reading MA: Addison-Wesley, 1980.

....so that we can generate different tools, more efficient tools, or more convenient tools. Most importantly, we are able to use generic language technology to enable tool supported maintenance and automated reengineering of software; the most urgent and expensive parts of the software life cycle [79, 97, 12, 62, 90, 83]. In Figure 1, we present a number of language oriented tools: a compiler, a language reference manual, an on line manual, a pretty printer, some analysis tools (data flow analyzers, control flow analyzers, complexity metric tools and so on) renovation tools (language converters, mass maintenance ....

B.P. Lientz and E.B. Swanson. Software Maintenance Management---A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. Reading MA: Addison-Wesley, 1980.

....delivered to the customer. Software maintenance is defined as (IEEE, 1990) The process of modifying a software system or component after delivery to correct faults, improve performance or other attributes, or adapt to a changed environment . Usually, four types of maintenance are distinguished (Lientz and Swanson, 1980): 1. Corrective maintenance deals with the repair of faults found. 2. Adaptive maintenance deals with adapting the software to changes in the environment, such as new hardware or the next release of an operating system. Adaptive maintenance does not lead to changes in the system s functionality. ....

Lientz, B.P.; and Swanson, E.B. (1980) Software Maintenance Management: A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations, Addison-Wesley Publishing Company, Reading, Mass, pp. ??.

....language. x 1 Introduction Software development is a complex and costly process. In particular, maintaining the source code usually proves to be difficult and time consuming. Some studies have shown that software maintenance can account for 70 of the total software system s lifetime cost [Lientz Swanson 80] There are two choices for dealing with the maintenance of a system. One is to re develop the system to meet the new requirements. The other is to make appropriate changes to the existing system. Since most legacy systems cost so much to produce and are used critically on a daily basis, ....

Lientz, B. and Swanson, E. "Software Maintenance Management: A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations," Addison-Wesley, Reading, MA, 1980.

....Throughout their lifetimes, software systems undergo numerous changes. To make these changes, we have to understand these systems, identify and evaluate alternative modification strategies, implement the changes, and validate their correctness. In practice, the cost of these activities is enormous[1, 2, 5, 6]. Consider the problem of validating modified software. One common way to do this is to rerun tests from existing test suites (called regression testing) Although valuable, this is often very expensive. For instance, some companies must release software products for users who speak different ....

B. P. Lientz and E. B. Swanson. Software Maintenance Management: A Study of the Maintenance of Computer Applications Software in 487 Data Processing Organizations. AddisonWesley, Reading, MA, 1980.

....on the premises of the model, and experiments conducted to see if the data fits the model. This section develops a maintenance cost model accommodating restructuring. It is common knowledge that maintenance is the most expensive component of the overall software process, running as high as 70 [Lientz Swanson 80] Belady and Lehman have related software structure and the cost of maintenance at the macro level of detail, providing an equation that relates system age, structure, and maintenance costs. Parnas s work is less quantitative, but provides guidelines for building structurally robust programs. ....

B. Lientz and E. Swanson. Software Maintenance Management: A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. Addison-Wesley, Reading, MA, 1980.

....1 Introduction Large, long lived and data intensive application systems that satisfy a complete area of information processing requirements, such as most information systems, CAD CAM systems, CASE environments, etc. must continuously undergo change in order to reflect change in their environments [9, 12, 15]. Figures describing the maintenance proportion of the total lifetime expenditure on a software system vary between 50 and 90 [4, 16, 24] As application systems live longer and grow in size and complexity, it is likely that this trend will continue. In this paper we use Boehm s definition of ....

Lientz, B.P. and Swanson, E.B. Software Maintenance Management: A Study of the Maintenance in 487 Data Processing Organizations. Addison-Wesley Publishing Company, Reading, Mass., 1980.

....of software maintenance varies with the kind of program, condition of documentation, and structure of source code, but the figures documented in the literature suggest the enormity of the cost. Lientz and Swanson observed that large companies spent 50 of their programming effort on maintenance [Lientz Swanson 80] Boehm documented an Air Force project where the cost to develop the program was 30 per line, and cost to maintain the program was 4,000 per line [Boehm 75] Maintenance of software systems becomes more expensive over time as repeated modifications degrade the software s structure. Over time, ....

B. Lientz and E. Swanson. Software Maintenance Management: A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. Addison-Wesley, Reading MA, 1980.

....the special problems of directmanipulation program restructuring at the design level, and relate it to other approaches for manipulating designs. 1 The Problem Software is perceived to be too expensive relative to its quality. Since maintenance is the dominant phase in the program life cycle [9], substantially reducing the cost of software requires lowering the cost of maintenance. As useful software ages, modifications to meet the needs and demands of users are layered upon the original implementation. Modifications unanticipated in the design sometimes are not easily integrated into ....

B. Lientz and E. Swanson. Software Maintenance Management: A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. Addison-Wesley, Reading MA, 1980.

....estimation of analysis times. However, we believe that our estimates understate the analysis time required by our technique. 5 Conclusions and Future Work This work is important for two reasons. The first reason is economic. The cost of software maintenance dominates the overall cost of software [9, 34, 35]. Moreover, the cost of maintenance, measured in terms of the percentage of software budget spent on maintenance, is increasing [5, 37, 48] Because regression testing constitutes a significant percentage of maintenance costs [5, 9, 29] improvements in regression testing processes can ....

B.P. Lientz and E.B. Swanson. Software Maintenance Management: A Study of the Maintenance of Computer Applications Software in 487 Data Processing Organizations. Addison-Wesley, Reading, MA, 1980.

No context found.

B. P. Lientz and E. B. Swanson. Software maintenance management: a study of the maintenance of computer application software in 487 data processing organizations. AddisonWesley, 1980.

No context found.

B. P. Lientz and E. B. Swanson. Software maintenance management: a study of the maintenance of computer application software in 487 data processing organizations. Addison-Wesley, 1980.

No context found.

Lientz, B. P. and E. B. Swanson, "Software maintenance management: a study of the maintenance of computer application software in 487 data processing organizations," Addison-Wesley, 1980.

No context found.

B. P. Lientz and E. B. Swanson. Software maintenance management: a study of the maintenance of computer application software in 487 data processing organizations. Addison-Wesley, 1980.

No context found.

B. P. Lientz and E. B. Swanson. Software maintenance management: a study of the maintenance of computer application software in 487 data processing organizations. Addison-Wesley, 1980.

No context found.

B. P. Lientz and E. B. Swanson. Software Maintenance Management: A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. Addison-Wesley, 1980.

No context found.

B.P. Lientz and E.B. Swanson. Software Maintenance Management -- A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. Reading MA: Addison-Wesley, 1980.

No context found.

B. Lientz and E.B. Swanson, Software Maintenance Management: A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations, Addison-Wesley, Reading, Mass. 1980.

No context found.

B. Lientz and E. Swanson. 'Software Maintenance Management: A Study of the Maintenance of Computer Application Software' in 487 Data Processing Organizations. Addison-Wesley, Reading, MA, 1980.

No context found.

Lientz, B.P. & E.B. Swanson (1980), Software Maintenance Management---A Study of the Maintenance of Computer Application Software in 487 18 Evolutionary Software Engineering: A Component-based Approach Data Processing Organizations, Reading MA: Addison-Wesley.

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