Lientz, B.P. and Swanson, E.B., Software Maintenance Management, Addison-Wesley Publishing Co., Reading, MA, 1980.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....too great and execktion speeds must be accept able. This process I incorporates making the system and its components efficient. Maintainability: How useful the system is over a long period of time. The maintenance of a large system has proved to be an important aspect of the software lifecycle [6]. Usability: The system must be able to support the applications end users want and be user friendly. lobustness: This is a critical aspect of large scale sys tems. To quote [1] while it [robustness] may not be a serious problem for any individual application, it has to be faced up to in ....

B. Lientz and E. Swanson. Software Maintenance Management. Addison-Wesley, 1980.

....with software development. The list includes: poor software quality, lack of reuse, missed deadlines, budget overruns, and so on. If we consider the typical lifecycle of a successful software product, however, we quickly see that most of the costs are associated with its life after deployment [3, 12]. Furthermore, what is often misnamed maintenance actually consists mainly of addition of new functionality, i.e. continuous development, or software evolution [3, 12] Oddly, most software development methods seem to assume that a new application is being developed rather than that some ....

.... of a successful software product, however, we quickly see that most of the costs are associated with its life after deployment [3, 12] Furthermore, what is often misnamed maintenance actually consists mainly of addition of new functionality, i.e. continuous development, or software evolution [3, 12]. Oddly, most software development methods seem to assume that a new application is being developed rather than that some existing software base is being extended or modified, whereas in practice the latter is almost always the case. Most of the real problems with software development, in fact, ....

Bennet P. Lientz and E. Burton Swanson. Software Maintenance Management. Addison Wesley, 1980.

.... Controlled experiment, maintenance, documentation, productivity, student experiment subjects. I. INTRODUCTION Several investigations on software maintenance problems have given high priority to the problems of lacking or inadequate documentation, and a high turnover rate among maintainers ([Lientz and Swanson, 1980], Chapin, 1985] Nosek and Palvia, 1990] Foffani, 1992] Dekleva, 1992] Krogstie, 1994] It is my position that documentation must be actively maintained concurrently with source code to provide new maintainers with a solid basis for quickly becoming productive members of the maintenance ....

Lientz, B. P. and Swanson, E. B. (1980). "Software Maintenance Management". Addison-Wesley, Reading MA.

....The postal survey received 106 completed questionnaires a response rate of 33 . According to Edwards, a response rate of 20 30 for mail based questionnaires can be considered adequate [22] In their well referenced software maintenance survey, Lientz and Swanson produced a 24.6 response rate [36]. Table 1 provides a breakdown of the respondents positions, the largest proportion being software engineers (46.2 ) Table 2 presents a break down of the respondents experience of the object oriented paradigm, the largest proportion (34.4 ) having greater than 4 years experience. Further, ....

B. Lientz and E. Swanson. Software Maintenance Management. AddisonWesley, first edition, 1980.

....ratio of the number of identified program components which do not have the descriptions we assigned to the total number of identified program components. 5. 5 Extension to program debugging Two very costly activities in software maintenance are enhancements and the removing of development bugs [11, 23]. Although the emphasis of our study is to address the concern of identifying code unique to a particular feature, and common to a pair or group of features, from the point of view of program understanding, a similar approach could be used for program debugging. Excluding tests would be those that ....

B. P. Lientz and E. B. Swanson, "Software Maintenance Management," Addison-Wesley, New York, 1980.

....for t h e l a s t t h i r t y y e a r s [ M o r r i s s e y 7 9 ] T h i s i n c r e a s e i n p r o d u c t i v i t y i n c l u d e s a l l t h e developments in software engineering and the development of higher level languages. There is a shortage of qualified personnel to create software [Lentz80] As the size of a software system grows, it becomes increasingly hard to construct. The software crisis is not a problem of small systems. Adequate methods exist for a single programmer to produce 10k lines of high level source code or five programmers to produce 50k lines of high level ....

B. Lientz and E. Swanson, Software Maintenance Management , Addison-W sley 1980. e

....Construction Using Components 3 regarded as an activity after system construction which only corrected errors in the system. In reality, it has been shown that the evolution time is spent revising the goals of the system and only about 10 of the total evolution effort is spent correcting errors [Lientz80]. The remaining 90 of the evolution phase is a reiteration of the other lifecycle phases. It is difficult to test high impact tools for software production for three reasons. One reason is that the tools are used in a complex social setting where not all the users are motivated by a desire for ....

....systems (inventory, accounting, billing, etc. and simple process control systems are all areas where many thousands of similar systems exist. It is not at all clear that the constructors of these systems are craftsmen. In fact, with the rapidly increasing numbers of analysts and programmers [Lientz80] it is doubtful that the constructors of these systems are craftsmen. In our view, the high cost of custom software systems has never been clearly represented since the use of standard parts and assemblies to build lowcost systems has not been an alternative. Historically, hardware construction ....

Lientz, B.P., and Swanson, E.B., Software Maintenance Management, Addison-Wesley, 1980.

....status. In fact, some consider a system to be in a legacy state even before it is being deployed The evolution of software system could be due to changes in the original requirements, adopting a different hardware platform or to improve its efficiency. The classification of maintenance approach [15] indicates the various types of change that can be seen through the maintenance process. As a result, this is seen as an indication of the type of evolutionary changes that may occur to software. Because of its complexity, the likelihood of subtle errors is much greater and some of these errors ....

B. Lientz and E. Swanson. Software Maintenance Management. Addison Wesley, 1980.

....Cooperative Evaluation 1. Introduction Within this paper we are concerned with the role that usability evaluation has to play in the evolution of interactive systems (IS) Underlying our work is the evidence that much IS development takes place in the maintenance phase of application development [1,2,3,4]. However, usability does not appear to be part of the ethos or process of IS maintenance. This is despite the recognition that IS with poor usability may result in: greater training requirements; incomplete utilization of IS; failure of an IS to achieve its intended purpose; and slower than ....

....social, legal, ethical and managerial context of an IS. Further to this, changes are more often than not evolutionary in nature and not easily amenable to the form of one shot application development predominant in HCI methods [6] The evolution of tasks is evidenced in studies of IS maintenance [1,2,3,4]. These studies suggest that developers are faced with constant pressure to adapt IS to reflect changes. It is not the case that improved analysis [e.g. 5, 8] will mitigate all changes as anecdotal evidence suggests that requirements can change in as little as six months [9] Thus, many authors ....

Lientz, E. and Swanson, B., Software Maintenance Management. Reading: Addison-Wesley, 1980.

....50 of all computer resources and research by Boehm [1] has shown that maintenance costs can be up to ten times those of an initial development. Software maintenance processes are initiated for a number of reasons. These differing reasons result in four categories of maintenance activities [8]. These are: Perfective maintenance this involves improving functionality of software in response to a userdefined changes. Corrective maintenance this process involves the correction of errors that have been identified within the software. Adaptive maintenance this process involves ....

....environment. Preventative maintenance this involves updating the software in order to improve upon its future maintainability without changing its current functionality. The costs of the maintenance processes are not distributed evenly across all categories. Studies by Leintz and Swanson [8] show that 50 of the total maintenance costs can be attributed to perfective maintenance, 25 for adaptive maintenance, whereas only 21 of the total costs are attributed to corrective maintenance and 4 for preventive maintenance. The maintenance process requires an understanding of the ....

[Article contains additional citation context not shown here]

Leintz B.P., Swanson E.B., `Software Maintenance Management', Addison Wesley, 1980

....See the next section on survey construction for more on this . Low response rates there is a danger when sending out surveys that you get a low response rate. For mail based questionnaires, Edwards [5] found a response rate of 20 30 , and in a software maintenance study, Lientz and Swanson [8] only received a 24.6 response rate. In an attempt to reduce this problem, various companies were contacted prior to the completion of the survey via Strathclyde University graduates now in their employment to see if they would be interested in participating 2.3 Survey Construction The time to ....

B. Lientz and E. Swanson, Software Maintenance Management, First Edition, Addison-Wesley, 1980.

....management and personnel administration. Most applications were used only by the company itself. The median effort of a maintenance task was about 16 work hours. Approx. 9 of the effort was spent on corrective, 40 on adaptive, 45 on perfective and 6 on preventive maintenance (definitions in [31]) 40 of the tasks involved introduction deletion of new modules, 34 major changes in interfaces, 30 major changes in control flow, 29 major changes in data declaration and 27 major changes in data or assignments. A maintenance task was allocated to only one person. The average length of ....

....the particular part of the application changed in the maintenance task. In other words, the average experience level of the maintainers was rather high. The distributions of types of tasks, the technology used and the sizes of the applications were similar to what was found in studies such as [31] and [34] i.e. the organisation subject to our study is a typical maintenance organisation. 2 Although we will describe them as maintainers in this paper, they considered themselves as system developers or programmers. 4 The maintenance process in the studied organisation followed, typically, ....

R. J. Lientz and E. B. Swanson, Software maintenance management. Reading Mass.: Addison-Wesley, 1980.

....for example, assessment of maintenance costs, personnel planning, release scheduling, etc. Additional information that would be valuable to be included in the database is the kind of change performed in a release (corrective, adaptive, perfective, or preventive maintenance as described in [16]) It would be useful to correlate the behavior of the evolution to the kinds of changes. We believe that software evolution observations based on release history information opens up a whole area of research. Such structural information about a system is obtained relatively easily (during ....

Lientz B.P. and Swanson E.B., Software Maintenance Management, Addison-Wesley, 1980.

....software architecture description, scenario elicitation, scenario evaluation and interpretation. 1. Introduction The world around most software systems is constantly changing. This requires software systems to be modified several times after their initial development. A number of studies [9, 22] have shown that 50 to 70 of the total lifecycle cost of a software system is spent after initial development. One of the reasons for the high cost of software maintenance is that productivity of changing existing code is at least an order of magnitude lower than developing new software or ....

B.P. Lientz and E.B. Swanson. Software Maintenance Management, Reading, MA: AddisonWesley. 1980.

No context found.

Lientz, B.P. and Swanson, E.B., Software Maintenance Management, Addison-Wesley Publishing Co., Reading, MA, 1980.

No context found.

B. P. Lientz and E. B. Swanson. Software Maintenance Management. Addison Wesley, 1980.

No context found.

B. Lientz and E. Swanson, Software Maintenance Management, First Edition, Addison-Wesley, 1980.

No context found.

B. Lientz and E. Swanson. Software Maintenance Management. Addison-Wesley, 1980.

No context found.

. B.P. Lientz and E.B. Swanson, Software Maintenance Management, Addison-Wesley, Reading, Mass., 1980.

No context found.

Lientz, B.P. & Swanson, E.B. (1980). Software Maintenance Management; Addison-Wesley, Reading M.A..

No context found.

B. P. Lientz and E. B. Swanson. Software Maintenance Management. Addison Wesley, 1980.

No context found.

Lientz, B.P. and E.B. Swanson, Software Maintenance Management, Reading, Mass.: Addison-Wesley, 1980.

No context found.

Lienz B. and Swanson E. (1980). Software Maintenance Management, Addison-Wesley.

No context found.

Lienz B. and Swanson E. (1980). Software Maintenance Management, Addison-Wesley.

No context found.

Lientz B.P. and Swanson E.B., Software Maintenance Management, Addison-Wesley, 1980.

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