Hafedh Mili, Fatma Mili, and Ali Mili. Reusing software: Issues and research directions. IEEE Transactions on Software Engineering, 21(6), June 1995.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....standard pattern recognition algorithms to solve specific feature detection problems. Software re use has the potential to provide a significant increase in software productivity and reliability. In fact, it has been touted as the only realistic approach to meet the needs of software industry [MIL95]. The key to software re use is a representation for software design: a component must be represented in a way that it supports both retrieval from a library as well as evaluation of usability [PEN95] The goal is to minimize adaption cost of the software to be re used, to the new task that should ....

H. Mili, F. Mili, A. Mili, "Reusing Software: Issues and Research Directions", IEEE Trans. on Software Engineering, Vol.21, No.6, pp.528-562, 1995.

....it easier the interchange and diffusion of knowledge about open source code. Our target is quite specific: the project focuses on software developers, system integrators, and, in general, experts in the field, whose dilemma is writing new code from scratch, or adapting already existing code [MMM95] We are not addressing the (knowledgeable) end user, who in general is already satisfied with simpler package search tools and web sites like FreshMeat, RPMfind, etc. It must remain clear that the finality and target of Amos is quite different form these generic software seeking sites. Amos ....

....also usually based on simple single line sentences to describe the packages, and cannot request a series of capabilities. Therefore, it is not suited to large scale components, and cannot perform a minimum cost matching (in terms of the extra effort needed to couple the retrieved packages) In [MMM95] an extensive summary of recent research works on the software matching field are analyzed and classified. Following that article, our approach can be classified as an extended lexical descriptor frame based approach, where the strict tabular based approach of adding semantics to dictionary ....

H. Mili, F. Mili, and A. Mili. Reusing Software: Issues and research directions. IEEE Transactions on Software Engineering, 1995. 10

....keyword based approaches. The software agents and distributed computing communities have developed simple table based approaches for matchmaking between tasks and online services. The software engineering community has developed by far the richest set of techniques for service retrieval [2]. We can get a good idea of the relative merits of these approaches by placing them in a precision recall space (Figure 1) high tablebased keywordbased vocabulary semantic networks Legend method improvement matching Fig. 1. The state of the art in service retrieval Recall is the ....

Mili, H., F. Mili, and A. Mili, Reusing software: issues and research directions. IEEE Transactions on Software Engineering, 1995. 21(6): p. 528-62.

....keywordbased approaches. The software agents and distributed computing communities have developed simple table based approaches for matchmaking between tasks and on line services. The software engineering community has developed by far the richest set of techniques for service retrieval [2]. We can get a good idea of the relative merits of these approaches by placing them in a precision recall space (Figure 1) keywordbased Fig. 1. The state of the art in service retrieval Recall is the extent to which a search engine retrieves all of the items that one is interested in (i.e. ....

Mili, H., F. Mili, and A. Mili, Reusing software: issues and research directions. IEEE Transactions on Software Engineering, 1995. 21(6): p. 528-62.

....ontology, is a non trivial task and there is also ambiguity associated with the type of semantics (computational or application) that the vocabulary should describe. Finally, specification based solutions use a specification language, whose semantics define the classification and retrieval scheme [14]. The logic programming, constraint and context aware retrieval (CAR) communities are developing technologies that address the needs of a contextual matching service. In logic programming, declarative programming languages such as Prolog can be used to express matches using first order logic. ....

H. Mili, F. Mili and A. Mili, Reusing Software: Issues and Research Directions. IEEE Transactions on Software Engineering, 21, 6, pp 528-562, 1995

....processor model. EMSim was designed using object oriented (OO) techniques. The advantages of an OO approach to software design in general are well documented [5] They include many wellaccepted design goals of quality program development, such as modularity, modifiability, and maintainability [16]. Moreover, designs centered on objects are especially suited for simulation. Simulation speed is obviously an important factor in a simulator. However, the features that provide the OO approach to software design are equally or perhaps more important in a simulator. Languages such as C provide ....

H. Mili, F. Mili, and A. Mili, "Reusing software: Issues and research directions," IEEE Transactions on Software Engineering, vol. 21, June 1995.

....validated. In CBSD, the system designer has to take into account the specification of pre developed COTS components available in software repositories, that must be even considered when building the initial requirements of the system, incorporating them into all phases of the development process [17, 21]. In this approach, an abstract software architecture of the system is defined first, that describes the specification of abstract components and their relationships. These abstract components are then matched against the list of concrete COTS components available in a repository. This process ....

H. Mili, F. Mili, and A. Mili. Reusing software: Issues and research directions. IEEE Trans. SE, 21(6):528--562, 1995.

....the client that it can proceed. E05 E06 The client releases the semaphore by informing the Semaphore task. This pattern exists in Figure 5, where the Client task is Task Actor 433 4 . 6. 0 Comparison with Other Research This research has similarities to reverse engineering [6] software reuse [28], and program comprehension [25, 3] Figure 8: Detecting the Potential of RPC Deadlock Task 1 E017 E287 E323 Task 2 E344 E347 1.1 RPC 1.2 Most techniques for construction models have focussed on syntax analysis or transformation of the source code of sequential programs [40, 49, 25] ....

H. Mili, F. Mili, and A. Mili. Reusing software: Issues and research directions. IEEE Transactions on Software Engineering, 21(6):528--561, June 1995.

....Software developers will still need to browse the delivery to find the components they want, but compared to the entire repository, the browsing space is significantly smaller and the time to find the desired components is thus reduced. The delivered components are the result of a first cut search [18] automated by component repository systems. Table 2 compares context aware browsing with browsing and searching by summarizing their advantages and disadvantages. Advantages Disadvantages Low cognitive Does not scale up Browsing overheads Formulating the right Searching Fast, direct query ....

Mili, H., F. Mili, and A. Mili, Reusing Software: Issues and Research Directions. 1EEE Transactions on Software Engineering. 21(6):528-562, 1995.

....approaches Extensive research has been done in the area of shortage and retrieval of software components in a component repository or a software library. The retrieval algorithms can be classified into the following categories: text based, lexical descriptor based and specification based [7]. It has been observed that hierarchical organization of the key phrases and proper browsing tools can significantly enhance the usability of the system. 3.2.6 Formal Specification Matching Techniques Specification based techniques are in general more powerful than semi formal or informal ....

H. Mili, F. Mili and A Mili. " Reusing Software: Issues and Research Directions". IEEE Transactions on Software Engineering, vol. 21, no 6, pp. 528-562, June 1995.

.... Software reuse is the reapplication of a variety of kinds of knowledge about one system to another system in order to reduce the e ort of development and maintenance of that other system [BP89] Software reuse can itself be categorised, commonly as building block reuse and generative reuse [MMM95]. Building block reuse is the reuse of products created during the software lifecycle, such as code or documentation. Generative reuse is the reuse of the processes involved in the software lifecycle, whereby the term process we mean a sequence of activities undertaken by software engineers rather ....

....Generative reuse is the reuse of the processes involved in the software lifecycle, whereby the term process we mean a sequence of activities undertaken by software engineers rather than a process running on a CPU. Mili, Mili and Mili refer to both products and processes as reusable assets [MMM95]. All kinds of assets can be useful to a reuser. Documentation from an old project can be applied to a new and similar project, perhaps with some modi cation. This can save on the time required to write documentation for the new project, time that could be spent elsewhere or on moving the ....

Hafedh Mili, Fatma Mili, and Ali Mili. Reusing software: Issues and research directions. IEEE Transactions on Software Engineering, 21(6), June 1995.

....cases based on the program information, and supports C program testing, either using white box or black box method. CEX: Component Extractor. Software reuse, of which an important part is component based reuse, is considered as a practical and feasible approach to solving the software crisis[10]. Based on program understanding, the component extractor identifies and extracts reusable component through implementing reengineering on the class or class cluster acquired from existing software. CToC : C to C Translator. To translate non object oriented programs to objectoriented ....

Hafedh Mili, Fatma Mili, and Ali Mili, "Reusing Software: Issues and Research Directions," IEEE trans. On SE, Vol. 21, No. 6, June 1995, 528-562.

....is the supply source of mature, reliable, adaptable, and maintainable components. We define as component mining the deliberate, organised, and automated process of extracting reusable components from an existing component rich software base. Component mining is a product and process reuse activity [14] that relies on the exploration and exploitation of large pre existing componentrich fields [20] Effective component mining is supported by a clearly defined, and possibly automated, process for identifying and packaging the software components. The remainder of this paper is structured as ....

Mili H, Mili F, and Mili A. Reusing Software: Issues and Research Directions. IEEE Trans. Softw. Eng., 21(6):528--562, (June 1995).

....keyword based approaches. The software agents and distributed computing communities have developed simple frame based approaches for matchmaking between tasks and on line services. The software engineering community has developed by far the richest set of techniques for service retrieval [2]. We can get a good idea of the relative merits of these approaches by placing them in a precision recall space (Figure 1) precision high high deductive retrieval frames keywords with TFIDF keywords recall enumerated vocabulary semantic networks Legend method improvement ....

Mili, H., F. Mili, and A. Mili, Reusing software: issues and research directions. IEEE Transactions on Software Engineering, 1995. 21(6): p. 528-62.

....If we focus on reusability, a component retrieved from a library regarding only its functional behaviour may not fit into the non functional requirements of the environment, hindering or even preventing its actual integration into the new system. Despite this, usual software reuse methods (see [1] for a survey) take only functional characteristics of components into account. The main reason behind this limitation is that non functional information does not appear in components; furthermore, it often cannot be easily computed (or even cannot be computed at all) from the func This work ....

Mili, H.; Mili, F.; Mili, A.: Reusing Software: Issues and Research Directions. IEEE Transactions on Software Engineering 21, 6. IEEE Computer Society (1995)

.... once they have reused them once [6] This explains why individual ad hoc reuse has been taking place while organization wide systematic reuse has not seen the same success: software developers have their individual reuse repositories in memory, so they can reuse by memory or reuse byrecall [7]. For those components that have not yet been internalized, software developers have to resort to the mode of reuse by anticipation. The activation of reuseby anticipation mode relies on the following two enabling factors: developers anticipates the existence of reusable components; and they ....

Mili, H., F. Mili, and A. Mili, "Reusing Software: Issues and Research Directions," IEEE Transactions on Software Engineering, 21(6), pp. 528-562, 1995.

....precise representation can make the matching more precise and retrieval more effective. However, because the same representation is also used by developers to specify their reuse queries, the format of representation is limited by the developers willingness to formulate long and precise queries [30]. 2.1.4 Retrieval by Reformulation Retrieved components only match reuse queries. It is difficult for most reusers to create a well defined query on their first attempt. Retrieval by reformulation is the process through which queries are incrementally improved until they express the query that ....

....with the support of systems such as CodeBroker, it is still not clear whether software companies are willing to pay the costs associated with setting up, evolving and sustaining reuse repositories. Traditionally, there are two distinctive roles: producers and consumers of reusable components [30]. Producers of components apply domain analysis and other techniques to identify and develop reusable components, which are then consumed (reused) by developers. This dichotomous perspective on reuse is in line with the traditional viewpoint of software systems: developers who only produce the ....

Mili, H., F. Mili, and A. Mili, "Reusing Software: Issues and Research Directions," IEEE Trans. Soft. Eng., 21(6), 528-562 (1995).

....is possible. 8.1 Software Reuse Krueger [34] is an excellent survey of software reuse, with criteria for practical effectiveness. Biggerstaff and Perlis [8] contains papers on theory and applications of reuse; artificial intelligence approaches are described in [1] 39] and [60] Mili [41] extensively surveys software reuse, emphasizing technical challenges. 8.2 Software Components The Programmer s Apprentice [61] was based on reuse of clich es, somewhat analogous to our generics. This project produced some good ideas but had limited success. KBEmacs, a knowledge based editor ....

H. Mili, F. Mili, and A. Mili, "Reusing Software: Issues and Research Directions," IEEE Trans. Software Engineering, vol. 21, no. 6, pp. 528-562, June 1995.

....used to generate transforms for a language such as Polya. 6 Related Work 6.1 Software Reuse Krueger [24] is an excellent survey of software reuse; it also gives criteria for effective software reuse. Biggerstaff and Perlis [4] contains papers on theory and applications of software reuse. Mili [29] provides an extensive survey of approaches to software reuse, emphasizing the technical challenges of reuse for software production. Artificial intelligence approaches to software engineering are described in [1] 28] and [41] Some papers from these sources are reviewed individually in this ....

H. Mili, F. Mili, and A. Mili, "Reusing Software: Issues and Research Directions," IEEE Trans. Software Engineering, vol. 21, no. 6, pp. 528-562, June 1995.

....definition of all the operations that the component invokes on other components. 4 In some cases the result of an operation depends on the state that the component was when the operation was invoked. In this case, it is important for the component to make visible this state. categories [33]: text based, lexical descriptor based and specification based. Text based use the textual representation of a component as an implicit description of its behaviour, while employing arbitrarily complex string matching expressions to retrieve required components. Although text based solution have ....

....should describe. Finally, specification based use a specification language, whose semantics define the classification and retrieval scheme. In fact, specification based retrieval comes closest to achieving full equivalence between what a component is and does and how it is encoded [described] [33]. There are a number of specification methodologies, which deploy various degrees of formality, from informal ones [35, 36] to formal ones [37, 38] Specification based approaches are in general more powerful than both text and lexical descriptor based ones, mainly because of the wide range of ....

H. Mili, F. Mili and A. Mili, "Reusing Software: Issues and Research Directions", IEEE Transactions On Software Engineering, vol. 21, no. 6, pp. 528 -- 562, June 1995.

....reuse approaches are discussed and categorized providing a context for understanding the specific approach of domain specific languages and application generators discussed in this thesis. Much of the information in this section has been adapted from papers by Kruegar, Mili et al. and Neighbors [60,59,61]. Software reuse approaches can be separated into two categories: General Purpose . Domain Specific General purpose approaches include assets that are reusable across all or most problems, while domain specific methods include assets that are specialized for a given family of software products. ....

....were implemented in assembly. Very High Level Languages (VHLL) or sometimes called 4th Generation Languages (4GL) incorporate high level general abstractions of programing concepts explicitly in the language. They are based on application independent mathematical and computational abstractions. [59] However, with very high level languages, automation is possible at the cost of code efficiency and design quality; very highlevel languages are not intended to implement production quality software [59] Kruegar states that the primary concern in VHLLs is not efficiency in program execution ....

[Article contains additional citation context not shown here]

Mili et al., Reusing Software: Issues and research directions. IEEE Transactions on Software Engineering, Vol. 21, No. 6, June 1995.

....require the utilisation of higher level knowledge about the code. For example, rewriting procedural code in an object oriented style requires knowledge of the abstractions represented in the code, which can be extracted from the source code using reverse engineering techniques [1] Software reuse [11] is a very important issue in modern software engineering. On the one hand, there are demands for software of increasing size and complexity, which is expected to be written in a tight time schedule. Software is consequently often not delivered on time, does not meet the clients requirements, ....

....all at once. That is why Quilici calls his work a memory based approach [1] instead of a case based approach (c.f. 38] The field of software reuse is strongly related to CBR (c.f. Section 2. 1) the terms retrieval and adaptation are part of the reuse community s vocabulary (Section V of [11]) but the term case based reasoning is not in their mainstream vocabulary. As well as the explicit CBR approaches to reuse mentioned in Section 4.1, there is a lot of covert CBR (e.g. 39] Design patterns [40] share the philosophy which underlies CBR they describe solutions to recurring ....

Mili H, Mili F, Mili A. Reusing software: Issues and research directions. IEEE Transactions on Software Engineering 1995; 21(6):528-562

..... 18 7 Conclusions 18 Report No. 164, May, 1999 UNU IIST, P.O. Box 3058, Macau Introduction 1 1 Introduction Most software today is built from pre existing components, each component providing operations to generate, observe and modify its internal state [9]. Software design means composition and correctness of the design depends on the correctness of individual components. We assume that such components are given in a form which allows us to use them but not analyze, a typical situation for off the shelf components distributed as binary files. We ....

H. Mili, F. Mili, and A. Mili. Reusing Software: Issues and Research Directions. IEEE Transactions on Software Engineering, 21(6), 1995.

....the specification, classification, and retrieval of existing components; the other is component integration that involves the integration of the reused components into an application. Over the past several years, a large number of techniques have been developed to address these reuse issues [4, 5]. However, the lack of a seamless integration of these techniques imposes significant obstacles to achieving effective reuse, particularly with respect to component integration. Component integration typically involves conflict identification, component adaptation, and implementation of ....

H. Mili, F. Mili, and A. Mili. Reusing software: Issues and research directions. IEEE Transactions on Software Engineering, 21(6):528--561, June 1995.

....emphasise appropriate reuse and composition of software components as a key concept. However, finding and reusing appropriate software components is often very challenging, particularly when faced with a large collection of components and little documentation about how they can and should be used [15, 27]. This is a particular issue for end users of component based systems who want to tailor and extend their environment, but have limited understanding of component functionality and implementation [8, 16, 19] Many software component repositories have been developed, often extending the approaches ....

.... is not only relevant to software development, but to information management in general, as evidenced by the huge growth in research into digital libraries [28] The need to support more effective software developer reuse of components has been an important area of research for some time [8, 12, 15], but the need to support end user reuse of software components has become more pressing in recent years as componentbased systems become widespread [4, 13, 16] Most component repositories adopt a form of syntactic indexing and querying, whereby component features (name, property and method ....

Mili, H., Mili, F., Mili, A. Reusing software: Issues and research directions, IEEE Transactions on Software Engineering 21(6), June 1995, 528-561.

....of the collection without searching the collection. The quality of retrieval schemes used can alleviate both problems, by searching collections and finding components closely resembling the desired component. However, it is still difficult for an automated retrieval scheme to reach that goal[2, 14]. Problems 1 and 2 are problems which can be addressed in a relatively direct manner. Are existing libraries large enough to exhibit these problems If so, what mechanisms do they use to alleviate these problems Eiffel: There are various libraries available for use with EiffelBench: EiffelBase, ....

H. Mili, F. Mili, and A. Mili. Reusing Software: Issues and Research Directions. IEEE Trans. Software Eng., 21(6):528--561, June 1995.

....software is studied by the software reuse community and has lead to a substantial literature base. For instance, IEEE Software 94] features a special issue on systematic software reuse and several reuse conferences, such as [Samadzadeh Zand 95] and [Sitaraman 96] and overview papers, e.g. Mili et al. 95] Part of this research domain is the research on component based software engineering. See, for example, the proceedings of the 1996 workshop on component oriented programming in [Mhlhuser 97] However, the notion of adapting reusable components to match the requirements of the application at ....

. H. Mili, F. Mili, A. Mili, `Reusing Software: Issues and Research Directions,' IEEE Transactions on Software Engineering, 21(6), pp. 528-562, 1995.

....approach to software development. A transformational approach has two major steps. First, a formal specification is derived from user requirements. Then, a set of transformations is applied to these formal specification to get an implemented system. This approach has many advantages [1, 19]. It relieves developers from labor intensive, knowledge poor tasks. It eases the documentation of design choices. Finally, it ensures correctness of the resulting software in respect to its specification. Nevertheless, existing transformational approaches have been criticized because they are ....

Mili, H., Mili, F., and Mili, A. Reusing Software: Issues and Research Directions. IEEE Transactions on Software Engineering: 21(6), 1995, June: 528-562.

....production rate. B = DB (135) DB = #development activities X a=1 Gamma activity cost without reuse a Gamma activity cost with reuse a Delta (136) C = the reuse investment (137) 3. 24 Mili, Mili and Mili [MMM95] As part of a software reuse survey paper, a probablistic model is presented [Mili et al. 1995, pp.536 7] It models the cost of attempting to reuse a component, exhibiting the authors background in information retrieval. Firstly, the user searches for a component that exactly matches the user s needs; if one is found, it is reused (at no extra cost) If not found, the user searches for ....

....model actually assumes that the cost to modify part of the component is a proportion of the cost to modify the whole component (i.e. the cost to develop the whole component) 6. Producer incentive. This is a royalty payment to the producer for the use of their software. 7. Normal cost. One model [Mili et al. 1995] adds this to location cost and modification cost. It accounts for the times when no reusable software is found, so that the cost involved in trying to find it is sunk . The model attaches a probability of occurrence to each of the reused cost terms (see section 3.24) UW Aberystwyth Computer ....

[Article contains additional citation context not shown here]

Hafedh Mili, Fatma Mili, and Ali Mili. Reusing software: Issues and research directions. IEEE Transactions on Software Engineering, 21(6):528--561, June 1995.

....can use the same processes. Keywords: Process reuse, organizational learning, casebased decision support, user interface. Software Development Processes While a great deal of the literature devoted to software reuse issues have focused on technology and techniques to re use source code [12, 23, 24], the return on investment for this activity is restricted by the amount of time spent in coding activities. In addition, upstream commitments on design issues can set a course that deviates from the existing component base, making it difficult to find suitable components in downstream phases. ....

H. Mili, F. Mili, A. Mili, "Reusing Software: Issues and Research Directions," Transactions on Software Engineering, 21(6), 1995, pp. 528-562.

.... about what kinds of reuse are most promising (large grained fine grained ) or the best technical architectures for achieving reuse (pervasive use of inheritance minimal use of inheritance ) An emerging consensus in the reuse community holds that the primary barriers to reuse are nontechnical [8, 13, 14]. Our case study sites illustrated a number of common pitfalls to avoid when trying to establish systematic reuse: allowing project level expediency take priority over building for reuse; skipping OO analysis and modeling; operating without a standardized reuse process; and failing to provide some ....

Mili, H. et al., "Reusing Software: Issues and Research Directions," IEEE Transactions on Software Engineering, Vol. 21, No. 6, 1995, pp. 528-562.

....On the other hand, the quick adaption of the internet as provider of various information, amongst them as provider of reusable software [1, 4] brought new motivation for re considering schemes to support component based reuse. Overviews of various attempts for reusing software can be found in [7, 11, 13]. Here, we focus on the basics of the software retrieval (and by the reverse side of the same token: the software description) issue. In section 2, we will address the problems involved with description of information on a more compact, and hence more abstract, general level. We will see that ....

H. Mili, F. Mili, and A. Mili. Reusing Software: Issues and Research Directions. IEEE Transactions on Software Engineering, 21(6):528--562, June 1995.

No context found.

Hafedh Mili, Fatma Mili, and Ali Mili. Reusing software: Issues and research directions. IEEE Transactions on Software Engineering, 21(6), June 1995.

No context found.

H. Mili, F. Mili and A. Mili, Reusing software: Issues and research directions, IEEE Transactions on Software Engineering 21 (1995) 528--562.

No context found.

Mili, H., Mili, F. & Mili, A. (1995), `Reusing software: Issues and research directions', IEEE Transactions on Software Engineering 21(6), 528--561.

No context found.

Hafedh Mili, Fatma Mili, and Ali Mili. Reusing software: Issues and research directions. IEEE Transactions on Software Engineering, 1995.

No context found.

Mili, H., Mili, F. & Mili, A. (1995), `Reusing software: Issues and research directions', IEEE Transactions on Software Engineering 21(6).

No context found.

H. Mili, F. Mili, and A. Mili, "Reusing Software: Issues and Research Directions," IEEE Transactions on Software Engineering, vol. 21, pp. 528-562, 1995.

No context found.

H. Mili, F. Mili, and A. Mili. Reusing Software: Issues and research directions. IEEE Transactions on Software Engineering, 1995. 23

No context found.

H. Mili, F. Mili, and A. Mili. Reusing Software: Issues and research directions. IEEE Transactions on Software Engineering, 1995.

No context found.

H. Mili, F. Mili and A. Mili, "Reusing software: Issues and Research Directions", IEEE Transaction on Software Engineering, v. 21, 1995, pp. 528-561.

No context found.

Mili, Hafedh, Mili, Fatma, and Mili, Ali. Reusing Software: Issues and Research Directions, IEEE Transactions on Software Engineering, 21(6): 528-558, June 1995.

No context found.

F. M. H. Mili and A. Mili, "Reusing software: Issues and research directions," IEEE Transactions On Software Engineering, vol. 21, no. 6, 1995.

No context found.

Mili, H., Mili, F., Mili, A.: Reusing Software: Issues and Research Directions. IEEE Trans. Software Eng. 21 (1995) 528-561

No context found.

H. Mili, F. Mili, and A. Mili. Reusing software: Issues and research directions. IEEE Trans. Softw. Eng., 21(6):528-- 562, June 1995.

No context found.

H. Mili, F. Mili and A Mili. Reusing Software: Issues and Research Directions. IEEE Transactions On Software Engineering, vol. 21, no. 6, pp.528-562, June 1995.

No context found.

Mili, H.; Mili, F.; Mili, A.: Reusing Software: Issues and Research Directions; IEEE Transactions on Software Engineering, Vol. 21 No.6, June 1995.

No context found.

H. Mili, F. Mili, and A. Mili. Reusing Software: Issues and research directions. IEEE Transactions on Software Engineering, 1995.

No context found.

H. Mili, F. Mili, and A. Mili. Reusing Software: Issues and research directions. IEEE Transactions on Software Engineering, 1995.

No context found.

H. Mili, F. Mili, and A. Mili, "Reusing Software: Issues and Research Directions," IEEE Trans. Software Eng., Vol. 21, No. 6, 1995, pp. 528--560.

First 50 documents  Next 50

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