V. R. Basili, "Viewing Maintenance as Reuse-Oriented Software Development", IEEE Software, Jan. 1990, pp.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....We analyse why this might be the case, and propose ways of remedying this situation. 1. Introduction A key feature of the object oriented (OO) paradigm is that of inheritance [21] Use of inheritance is claimed to reduce the amount of software maintenance necessary, ease the burden of testing [1], and produce more reliable, high quality software [2] In this paper, we investigate five OO systems, all written in C , and empirically evaluate hem using a subset of Chidamber and Kemerer s (C K) OO design metrics [11] together with two further inheritance based design metrics developed as ....

Basili, V.R., "Viewing maintenance as reuse-oriented software development", IEEE Software, 7(1), pp. 19--25, 1990.

....development. INTRODUCTION The purpose of this paper is to characterize the practical implications of traceability as a support in software maintenance using concrete examples from an industry scale project. Traceability is germane to life cycle meta models such as Basili s iterative reuse model [1]. In this model, software includes not only the resultingsource code, but also up front documents such as requirements and design specifications, which are regarded as models at various abstraction levels of the software in service [2] Maintenance in Basili s perspective initially performs and ....

Basili, V. Viewing maintenance as reuse-oriented software development. IEEE Software, 7(1):19-- 25, 1990.

....Management (IESEM) is a general framework which combines different approaches to the software maintenance problem. Our 4 project originated from a number of insights about software maintenance gained from our experience and previous research work. The focus on source code is inadequate [3], 4] Modification should also involve the other life cycle work products, for example requirements and design. Software systems are not homogeneous single version programs [15] 33] The wide variety of technologies, CASE tools, programming languages, development methods and standards is ....

V. R. Basili, "Viewing maintenance as reuse-oriented software development", IEEE Software (January 1990) 19-25.

....and Lyle write in [ Gallagher and Lyle, 1991 ] While some may view software maintenance as a less intellectually demanding activity than development, the central premise of this work is that software maintenance is more demanding. Here are some pointers to the maintainability subject: Basili, 1990; Bennet et al. 1992; Freeman and Layzell, 1994; Gallagher and Lyle, 1991; J rgensen, 1995; Schneidewind, 1987b; Kellner, 1992; Pickard and Carter, 1995; Paul and Prakash, 1994a; Hartmann and Robson, 1990 ] Program slicing A survey of program slicing techniques is given in [ Tip, 1995 ] ....

V. Basili. Viewing maintenance as reuse oriented software development. IEEE Software, 7(1):19-25, 1990. In this paper the maintenance process is incorporated in the life-cycle perspective geared towards the reusability of the various components.

....it. Reverse engineering facilities can be used to support the maintenance process. Thus, reverse engineering is the part of the maintenance process helping to understand the program in order to make the desired changes. Maintenance can also be considered as reuse oriented software development [6]. Forward engineering Forward engineering is the traditional process of moving from the requirements of the system to its design, and from design to the concrete implementation of the system. Actually, forward engineering means the same as engineering. The 19 adjective forward is only used to ....

....inthesameplaceasLOCAL BUFFER. Actually all three variables are located in the same place. We can achieve the same e#ect in C code with a union type as follows: typedef struct byte counter[ 3 ] byte threshold[ 3 ] byte status[ 4 ] generated type 1; typedef struct byte ykm data[ 6 ]; word gen info[ 2 ] generated type 2; typedef union byte local buffer[ 100 ] generated type 1 l3para data1[ 10 ] generated type 2 l3para data2[ 10 ] generated type 3; generated type 3 generated var 1; generated var 1.l3para data1[ 2 ] counter[ 3] 5; This translation is ....

[Article contains additional citation context not shown here]

Basili, V. R., Viewing maintenance as reuse-oriented software development, IEEE Software 7 (1) 1990, 19--25.

....object oriented systems, maintainability, inheritance. 1 INTRODUCTION A key feature of the object oriented (OO) paradigm is that of inheritance [19, 6, 11, 18, 20] In OO systems, use of inheritance is claimed to reduce the amount of software maintenance necessary and ease the burden of testing [1, 16, 7, 10]; the reuse of software through inheritance is claimed to produce more maintainable, understandable and reliable software [3, 2, 5] In this paper, we discuss the results of an experiment which we carried out based on that carried out by Daly et al. 12] which investigated the modifiability of ....

V. R. Basili. Viewing maintenance as reuseoriented software development. IEEE Software, 7(1):19--25, 1990.

....as a new paradigm of the field of software engineering since McIlroy proposed the idea of a software component catalogue from which software parts could be assembled in 1967 [1] Although we can observe some reuse success stories over the last 20 years, reuse is still in its infancy. Basili [2] treated a reuse process as one of maintenance process models which support a reuseoriented development process. This view provides a choice of maintenance approaches and improves the overall evolution process. He considered three maintenance process models: the quick fix model, the ....

V. R. Basili, "Viewing maintenance as reuse-oriented software development," IEEE Software, pp. 19--25, January 1990.

.... Reed [10] domain analysis Prieto Diaz [35] Frakes, et al. 15] Kang, et al. 23] Simos [40] reuse based process Kang, et al. 24] meta and working models Castano, Bubenko [7, 8] wide spectrum reusability Lubars [27] family of requirements Lam [25] reuse based maintenance Basili [4] CASE support of early reuse Poulin [34] 3 in the following sections. 3. Keywords or Facets The main aim of RARE is to establish a collection of informal requirements text that could be reused from one project to another, and a collection of formal designs that could be used to refine them. ....

Basili, V.R. (1990): "Viewing maintenance as reuseoriented software development". IEEE Software: p. 19-25.

....and so on. Informal cutting and pasting of previous development workproducts, particularly code, is widespread. And if the software which is reused can include development processes [Hollenbach and Frakes, 1996] knowledge [Basili and Rombach, 1991] previous versions of a developed system [Basili, 1990] and so on, it is not hard to see the ubiquity of reuse. Less common, however, are certain types of formalised systematic reuse , which are often based on product families , collections of related systems [Frakes and Isoda, 1994] These methods have been proposed as a way to improve the ....

Victor R. Basili. Viewing maintenance as reuse-oriented software development. IEEE Software, pages 19--25, January 1990.

....choices, their rationale, or both, for maintenance purposes. It is this last characteris ic of transformational systems that concerns us most in this paper, namely the potential for software reuse. Maintenance t has been recognized by a number of researchers as a particular form of reuse (see e.g. [14]) Balzer et al. recognized ransformational systems potential for enhancing software reuse, whereby reusable components are maintained and e r modified at the specification level rather than at the implementation level [8] While a number of researchers hav ecognized the importance of recording ....

Victor R. Basili, "Viewing Maintenance as Reuse-Oriented Software Development," IEEE Software, vol. 7(1), pp. 1 19-25, January 1990.

....This gain would be realizable if and only if the maintainer was also the developer, i.e. the creator refiner of the application s classes. This way, the effort required in finding and understanding the affected class hierarchy would already have been expended. In fact, as Basili points out [Bas90] for effective reuse, it is important to combine the development and maintenance models. Basili even suggests that development should be considered as a subset of maintenance. Upon reflection, this would be especially true in the object oriented paradigm. The features we have described as ....

Victor R. Basili. Viewing maintenance as reuse-oriented software development. IEEE Software, 7(1):19--25, January 1990.

....We believe that these views, combined with the above textual descriptions, provide the reader with a basic understanding of the structure and operation of this system as well as a good starting point for further investigations. If one views maintenance as reuse oriented software development [17], reverse engineering can benefit everyone involved in software production, including maintainers, developers, documenters, managers, and testers. A recent taxonomy listed key objectives for reverse engineering [18] including coping with complexity, generating alternate views, detecting side ....

Victor R. Basili. Viewing maintenance as reuse-oriented software development. IEEE Software, 7(1):19--25, January 1990.

....from software development. The difference between initial development and subsequent maintenance is a matter of the degree to which specifications and associated software are reused. The maintenance process suggested here is is similar to that found in Basili s Full Reuse Maintenance Process [2]. The contribution made in this paper is the use of a logic which can be used to formalize the causes of adaptive maintenance. As a consequence of the foregoing discussion, one should realize that the logic is to indicate when a specification is no longer valid. 3 Specification Validation In ....

V.R. Basili, "Viewing Maintenance as Reuse-Oriented Software Development", IEEE Software, 1990, Vol. 7, No. 2, pp. 19--25.

....and Lyle write in [ Gallagher and Lyle, 1991 ] While some may view software maintenance as a less intellectually demanding activity than development, the central premise of this work is that software maintenance is more demanding. Here are some pointers to the maintainability subject: Basili, 1990; Bennet et al. 1992; Freeman and Layzell, 1994; Gallagher and Lyle, 1991; J rgensen, 1995; Schneidewind, 1987b; Kellner, 1992; Pickard and Carter, 1995; Paul and Prakash, 1994a; Hartmann and Robson, 1990 ] Program slicing A survey of program slicing techniques is given in [ Tip, 1995 ] Other ....

V. Basili. Viewing maintenance as reuse oriented software development. IEEE Software, 7(1):19--25, 1990. In this paper the maintenance process is incorporated in the life-cycle perspective geared towards the reusability of the various components.

....model which our subjects implicitly follow. As most maintainers in the real world, our students have become skilled in taking the source code and make the necessary changes first to the code and later, but not always, to the accompanying documentation. For this approach, called quick fix model in [3], the added design record information is not a help but a weight to suffer. Intensive training and a careful process discipline are needed to change the old habits. Readers should also note that although our subjects received lectures on design recording, they had experience only with constructing ....

V.R.Basili, "Viewing maintenance as reuseoriented software development", IEEE Software, January 1990, pp.19-25.

....that software quality can be improved by reusing quality software artifacts. Some work has also hypothesized that software reuse is an important factor in reducing maintenance costs because, when reusing quality objects, the time and effort required to maintain software products can be reduced [4, 19]. Thus, the reuse of software products, software processes, and other software artifacts is considered the technological key to enabling the software industry to achieve required levels of productivity and quality [7] This article assesses the impact of product reuse on software quality and ....

Basili, V. Viewing maintenance as reuse-oriented software development. IEEE Software 7, 1 (Jan. 1990), 19--25.

....software quality can be improved by reusing quality software artifacts. Some work has also hypothesized that software reuse is an important factor in the reduction of maintenance costs, since when reusing quality objects, the time and effort required to maintain software products can be reduced [4, 19]. This is why the reuse of software products, software processes and other software artifacts is considered the technological key to enabling the software industry to attain the required levels of productivity and quality [5] The goal of this paper is to assess the impact of product reuse on ....

V. Basili (1990). "Viewing maintenance as reuse-oriented software development". In IEEE Software, 7(1):19--25, Jan.

....an environment Can a set of applications, all based on the same underlying framework, be exploited for reuse These questions become especially interesting and relevant if we think about the state of the practice in the software maintenance field. Consider the three maintenance process models in [2]: the quick fix model, the iterative enhancement model, and the full reuse model. With the quick fix model, maintainers start by modifying the source code, then test the new version, and finally modify the existing documentation. Because of time pressure, this model is the most popular maintenance ....

V. Basili. Viewing Maintenance as Reuse-Oriented Software Development. IEEE Software, January 1990, pp. 19-25.

....software quality can be improved by reusing quality software artifacts. Some work has also hypothesized that software reuse is an important factor in the reduction of maintenance costs, since when reusing quality objects, the time and effort required to maintain software products can be reduced [Basili, 1990; Rombach, 1991] This is why the reuse of software products, software processes and other software artifacts is considered the technological key to enabling the software industry to attain the required levels of productivity and quality [Basili Rombach, 1991] Technical Report, Univ. of ....

V. Basili (1990). Viewing maintenance as reuse-oriented software development. In IEEE Software, 7(1):19--25, Jan.

No context found.

V. R. Basili, "Viewing Maintenance as Reuse-Oriented Software Development", IEEE Software, Jan. 1990, pp.

No context found.

V.R. Basili, Viewing maintenance as reuse-oriented software development, IEEE Softw. 7: 1, 1990, 19#25.

No context found.

Victor R. Basili, "Viewing Maintenance as Reuse-Oriented Software Development,", IEEE Software, Jan. 1990, pp 19-15.

No context found.

, V. Basili, "Viewing Maintenance as ReuseOriented Software Development", IEEE Software, January 1990

No context found.

Victor R. Basili. Viewing Maintenance as Reuse-Oriented Software Development. IEEE Software, pages 19--25, January 1990.

No context found.

Victor R. Basili, "Viewing Maintenance as Reuse-Oriented Software Development", IEEE Software, Vol. 7, No. 2, January, 1990, pp. 19-25.

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