Devanbu, P., Selfridge, P. G., Brachman, R. J. and Ballard, B. W., "LaSSIE: a Knowledge-based Software Information System," IEEE Proceedings of 12th International Conference on Software Engineering, pp. 249261, 1990.  Home/Search   Document Details and Download   Summary   ACM   TOC   Related Articles   Check

....cost of software, sustaining its quality or reducing its degradation rate over its service life time. As for the challenge imposed to potential researchers, software maintenance has been referred to as a severe problem [22] or even as being the most difficult of all aspects of software production [9, 31]. The need for further research in the area is even more apparent in the light of statistics suggesting papers related to software maintenance are less than 1 of the papers annually published on software topics[16] We use the following definitions, based on the work of Chikofski and Cross [4] ....

....and employing deductions and other algorithms that are sometimes computationally demanding. In other words most such systems are fairly knowledge rich. Very often, KBSE systems employ expert systems or knowledge bases as their underlying technology. Some examples of these systems include [5, 9, 13, 20, 21, 26, 27, 29, 35, 36, 38]. Some of the problems that systems employing large knowledge bases face are: the great effort needed to build and maintain a knowledge base; the shortage of trained knowledge engineers to interview experts and capture their knowledge; the time consuming nature of the process which ....

P. Devanbu and B.W. Ballard. LaSSIE: A KnowledgeBased Software Information System. Automated Software Design. Edited by M.R. Lowry and R.D. McCartney, AAAI Press, 25-38, 1991.

....imperfect recall due issues such as the use of synonyms (sometimes addressed with pre enumerated vocabularies [5] semantic nets [6] and partial matching) The key underlying problem is that keywords are a poor way to capture the semantics of a query or item. Table based approaches [7] 8] 9] [10] [11] 12] are a second, increasingly popular, class of service model. A table based service model consists of a typically fixed number of attribute value pairs describing the properties of an item. Figure 2, for example, shows a table based model for an integer averaging service: Description a ....

Devanbu, P., et al., LaSSIE: a knowledge-based software information system. Communications of the ACM, 1991. 34(5): p. 34-49.

....keyword based approaches remain notoriously prone to poor precision. The key underlying problem is that keywords are a poor way to capture the semantics of a query or item. If this semantics could be captured more accurately then precision would increase. Table based approaches [7] 8] 9] [10] [11] 12] are a second, increasingly popular, class of service model. A tablebased service model consists of attribute value pairs describing the properties of an item. Figure 2 for example shows a table based model for an integer averaging service: Description a service to find the average of ....

Devanbu, P., et al., LaSSIE: a knowledge-based software information system. Communications of the ACM, 1991. 34(5): p. 34-49.

....studies [7] conclude that most software developers can only anticipate the existence of a limited portion of the components included in a repository, and that they would not actively seek the reuse of the components whose existence they do not know. This conclusion is corroborated by many reports [4, 5, 17] about reuse experience in companies. Even if software developers are willing to reuse a component, they might not be able to do so if they perceive reuse costs more than developing from scratch or if they Proceedings of 7th International Conference on Software Reuse (ICSR 7) Austin, TX, pp. ....

Devanbu, P., et al.: LASSIE: A knowledge-based software information system. Communications of the ACM, 34(5):34-49, 1991.

....thus concerned with how to represent knowledge, how to efficiently implement inferencing, and how to realize various problem solving methods. In many AI efforts, the AI developers use explicitly cognitive level notations and tools, like formal ontologies [697] knowledge representation languages [179], inferencing algorithms, and so on. These manifestly cognitive level formalisms help ensure that the analyst s cognitive level understanding of knowledge, inferencing, etc. are translated faithfully into computational implementations. A prime example is the Programmer s Apprentice (PA) project ....

Devanbu, P. T., Brachman, R. J., Selfridge, P. G., and Ballard, B. W. LaSSIE: A knowledge-based software information system. Communications of the ACM, 34(5), May 1991, pp. 34--49.

....be undertaken by intelligent agents (tools) with three distinct approaches being adopted [3] 1. Highly domain speci c, model driven, rulebased question answering systems that depend on a manually populated database describing the software system. This approach is typi ed by the Lassie system [7]. 2. Plan driven, algorithmic program understanders or recognisers. Two examples of this type are the Programmer s Apprentice [28] and GRASPR [32] 3. Model driven, plausible reasoning systems. Examples of this type include DM TAO [3] IRENE [17] and HB CA [9, 10] Biggersta et al. claim ....

P. Devanbu, R. J. Brachman, P. G. Selfridge, and B. W. Ballard. LaSSIE: A knowledge-based software information system. Communications of the ACM, 34(5):35-49, May 1991.

....graph to mimic the method a human being would employ in searching components. Multi faceted classification schemas [2] use multiple facets to represent components and a conceptual distance graph to reflect the semantic relationship among terms describing components. Both CodeFinder [13] and LASSIE [1] represent components as frames. CodeFinder organizes those frames into an associated network and uses spreading activation to find components. Frames in LASSIE are organized into hierarchical, taxonomic categories. Formal method based approaches use either signatures [27] or formal specifications ....

Devanbu, P., et al., LASSIE: A Knowledge-Based Software Information Systerr Communications of the ACM. 34(5):34-49, 1991.

....structure and helps with understanding the function particular modules. This approach is used extensively in object oriented programming [18] This use of a graphical forms can be extended to represent a broad spectrum of software artifacts such as hypertext [4,14,15,47] or a knowledge base [19]. 11 Automating the modification and composition of components is a difficult process without additional information. Much research has concentrated on the reuse of design plans that contain the reasoning and design decisions which went into the original process. This work has been based on the ....

Premkumar Devanbu, Ronald J. Brachman, Peter B. Selfridge, Bruce W. Ballard. LASSIE: A Knowledge-based Software Information System Communications Of The ACM May 1991.

....articulate their information need properly. Although this assumption can be questioned in general information retrieval settings [6] it is particularly dubious in software engineering, where studies have shown that functions and methods are regularly re implemented, often differing only in name [12]. Tools and techniques are needed that not only allow search for information, but also actively alert software developers to the existence of potentially relevant knowledge. In the following sections, we present a tool and methodology for software development knowledge management that draws on ....

Devanbu, P., Brachman, R.J., Selfridge, P.G., and Ballard, B.W., "LaSSIE: A Knowledge-Based Software Information System," Communications of the ACM, vol. 34, pp. 34-49, 1991.

....kind of experience) 44] or one generic retrieval system. The latter can take advantage of the semantic relationships among the experience items for retrieval, but requires that all kinds of experience are characterized using the same formalism. Examples include specialized knowledge based systems [22, 39]. In addition to semantic relationships, Ostertag et al. consider similarity based retrieval [40] A framework for representation and retrieval techniques can be found in [24] When choosing a representation, one cannot only consider the benefits on the retrieval side, but must also consider the ....

Premkumar Devanbu, Ronald J. Brachman, Peter G. Selfridge, and Bruce W. Ballard. LaSSIE: a knowledge-based software information system. Communications of the ACM, 34(5):34--49, May 1991.

....is tenuous at best. If simplicity and intelligibility are competitively advantageous why then do systems grow to unmanageable size and loose their design integrity One reason for the loss of design integrity is that what gets changed over time is the implementation rather than the design. As [Dev91] point out, a system design often begins as a simple, cohesive and well thought out design, arrived at by a small group of experienced and knowledgeable designers and architects. After a while, though, the subsystems are implemented by people who don t have knowledge of the system design. ....

....out, a system design often begins as a simple, cohesive and well thought out design, arrived at by a small group of experienced and knowledgeable designers and architects. After a while, though, the subsystems are implemented by people who don t have knowledge of the system design. According to [Dev91] they implement their subsystems in a manner that violates the architectural principles of the large system that they are modifying. The code may work cor rectly and consequently pass system test; however this kind of violation, carried out at various points over a period of time, results in ....

P. Devanbu, R. Brachman, P. G. Selfridge & B. W. Ballard "LaSSIE: a KnowledgeBased Software Information System" Communications of the ACM Vol. 34, No. 5, May 1991.

....even replace, a dedicated team of component developers [10, 33] 6. RELATED WORK Most of the previous research on reuse repositories has focused on the indexing and retrieval mechanisms. Different mechanisms, such as free text retrieval [27] multi facets classification [32] semantic networks [5], spreading activation [19] behavior sampling [18] signature matching [47] and specification matching [30] have been proposed. CodeBroker combines both free text retrieval based on LSA and signature matching in its retrieval mechanism. Parts of CodeBroker are similar to the systems that use ....

Devanbu, P., et al. LaSSIE: A Knowledge-Based Software Information System. Commun. ACM, 1991. 34(5): 34-49.

....approaches can achieve fairly high recall but at the cost of low precision. The key underlying problem is that keywords are a poor way to capture the semantics of a query or item. If this semantics could be captured more accurately then precision would increase. Frame based approaches [8] 9] [10] [11] 12] have emerged as a way of doing this. A frame consists of attribute value pairs describing the properties of an item. Figure 2 for example shows a frame for an integer averaging service: Both items and queries are described using frames: matches represent items whose (textual) property ....

Devanbu, P., et al., LaSSIE: a knowledge-based software information system. Communications of the ACM, 1991. 34(5): p. 34-49.

....repositories grow, this area also grows. Repositories are not static it is expected that they will evolve over time, and this will increase the size of (L4 L3) Many reports about reuse experience of industrial software companies illustrate this inhibiting factor of reuse. Devanbu et al. [5] report that because developers are unaware of reusable components, they repeatedly re implement the same function in one case, this occurred ten times. This kind of behavior is also observed as typical among the four companies investigated in [9] From the experience of promoting reuse, ....

....human being would employ in locating reusable components. Multi faceted classification schemas [6] use multiple facets to represent a reusable component and a conceptual distance graph to reflect the semantic relationships among terms describing reusable components. Both CodeFinder [23] and LaSSIE [5] represent reusable components as frames. CodeFinder organizes those frames into an associated network and uses spreading activation to find reusable components. Frames in LaSSIE are organized into hierarchical, taxonomic categories. It is difficult to construct such systems because they need to ....

Devanbu, P., et al., "LaSSIE: A Knowledge-Based Software Information System," Commun. of the ACM, 34(5), 34-49 (1991).

....for information they do not believe existing. Many reports about reuse experience in software companies illustrate the phenomenon of information islands. Devanbu et al. have reported that developers, unaware of reusable components, repeatedly re implement the same function in one case, ten times [3]. Similar reports can be found in [5, 20] No attempt to reuse is also caused by the perceived low reuse utility reuse utility is the ratio of reuse value to reuse cost. Due to cognitive biases against reuse, software developers tend to underestimate the reuse value and to overestimate the ....

....is also similar to those systems that use signatures to index reusable components [26] The greatest advantage of these two retrieval techniques is its low cost in both setting up the repository and posing a query. Other more complicated retrieval mechanisms have also been proposed. LaSSIE [3] and AIRS [16] use multifacets to represent reusable components, and semantic networks to support concept based retrieval. In CodeFinder [10] components are represented with frames and spread activation is used as the retrieval mechanism. Despite the sophistication of those mechanisms, empirical ....

Devanbu, P., R. J. Brachman, P. G. Selfridge, and B. W. Ballard, "LaSSIE: A Knowledge-Based Software Information System," Commun. of the ACM, 34(5), pp. 34-49, 1991.

....specification technique based on concepts, like the one described in [58] and the kind construct can be used 5 . It should be noted that even if a specification technique based on concepts was not followed at the construction of the system we could use reverse knowledge engineering to extract it [60]. 3. Trader Architecture From the discussion in the previous section we can see that in order for trading to support service selection through high level semantic service descriptions we need to change its syntactic nature to incorporate semantics. This change requires a move from the appearance ....

P. Devanbu, R. Brachman, P. Selfridge and B. Ballard, "LaSSIE: A Knowledge-based Software Information System", Communication of the ACM, vol. 34, no. 5, May 1991.

....model of the domain. Knowledge based systems pay attention to the component understanding problem but, as a trade off, they require domain analysis and a great deal of pre encoded, manually provided semantic information. Some knowledge based systems for software reuse are described in [4] [7] and [13] In terms of retrieval efficiency, it is hard to decide which approach is better, automatic indexing or knowledge based, because there are no comparable empirical results about the performance of systems based on them. But, if we are interested in supporting adequately the component ....

Devanbu, P., Ballard, B.W., Brachman, R.J. and Selfridge, P.G., 1991. "LaSSIE: A Knowledge-Based Software Information System", in Automating Software Design (Lowry, M.R. and McCartney, R.D., eds.), AAAI Press/ The MIT Press.

....1987) define a knowledge structure for a software library consisting of abstract data types (ADTs) This knowledge structure supports different relations among ADTs, and it includes natural language descriptions and keywords to assist in finding and browsing activities. The LaSSIE system (Devanbu et al. 1991) embodies a frame based knowledge representation. Software components are described in terms of the operations they perform. Each of these actions is described by providing its actor, object, recipient, agent, environment, and so on. These relationships are coded in a specialized knowledge ....

....user may ask for more abstract or more specific concepts than the one selected, or follow any link from that frame to any of its fillers, since these are also concepts in the knowledge base. These requests will result in the system displaying the corresponding frame(s) Retrieval by reformulation (Devanbu et al. 1991) considers retrieval as an incremental process of retrieval cue construction. With this technique, the user and the computer system cooperate, being the former able to incrementally improve his or her query according to the results of the previous queries. In order to enhance the retrieval ....

Devanbu, P., Ballard, B.W., Brachman, R.J. & Selfridge, P.G. (1991). LaSSIE: A Knowledge-Based Software Information System, in Automating Software Design (Lowry, M.R. & McCartney, R.D., eds.), AAAI Press/ The MIT Press.

..... EXPECT translates goal expressions to LOOM definitions, following an algorithm described in [ Gil and Gonz alez, 1996 ] For example, the EXPECT goal is translated into: Notice that this translation is done automatically while in other approaches, such as COMET [ Mark , 1992 ] and LaSSIE [ Devanbu , 1991 ] it is done manually. Given a library of methods, we express the goals that they can achieve as a LOOM concept as we explained in the previous section. When a goal is posted, the matcher expresses it as a LOOM expression, and uses the classifier to determine which methods have goals that ....

P. Devanbu, R. J. Brachman, P. G. Selfridge, and B. W. Ballard. LaSSIE: A knowledgebased software information system. , 34:35-49, 1991.

....alternatively, automatic classification schemas [Maar91] typical of document retrieval systems, seem to be useful only in presence of a great amount of documentation associated with software components. Querying and browsing functionalities are usually supported by software library systems. In [Deva91], development knowledge is stored in a knowledge base where software components are organized in a semantic network; software descriptions are grouped in frames, and automatically classified. Reuse can also affect the specification phase of an application. Under this consideration, specification ....

P. Devanbu, R. J. Brachman, P. G. Selfridge, B. W. Ballard, "LaSSIE: A KnowledgeBased Software Information System", Communications of the ACM, Vol. 34, No. 5, May 1991

....development via process modelling and intelligent tools. In DAIDA [18] the design cycle is assisted through a process model and the development steps are recorded in multi layered design histories. In [2] reuse information is organized in frameworks used mainly for the design phase. In LaSSIE [10], information relating to software development is stored in frames structures, and a retrieval system is provided on the basis of frame contents. In [23] multi agent development is explicitly represented as a meta model using a knowledge based formalism; knowledge acquisition and query mechanisms ....

P. Devanbu, R. J. Brachman, P. G. Selfridge, B. W. Ballard, "LaSSIE: A Knowledge-Based Software Information System", Communication of the ACM, Vol. 34 N. 5, May 1991

.... was developed within the ESPRIT REBOOT project [Karl92] Other approaches to organizing software collections include : library cataloguing [Hopk88] hypertext (DIF, GaSc87] object oriented libraries (Eiflet [Meye90] Objective C) ER and extended models (IBM Repository [Low88] Lassie of AT T [Deva91]) and hybrid (e.g. SIB [Cons 93] As pointed out in [Gibb90] the management of large software class collections requires addressing problems related to the representation of classes, so as to capture structural and descriptive information and to allow multiple views; the representation of ....

P. Devanbu, et al., LaSSIE: A Knowledge-Based Software Information System, Communications of the ACM, May 1991.

....tool will be able to access appropriate parts of the domain knowledge in a reliable manner. The problem here is one of presenting large information structures in a manageable way. Research on related issues is ongoing in the hypertext, database and knowledge based systems communities [Shu90, RH89, DBSB91] Finally, it is felt that full specification of systems such as those used in air traffic control might best be done by using a number of different formalisms to specify different aspects of these systems. This raises a need for a theoretical framework within which specifications written in ....

P. Devanbu, R. J. Brachman, P. G. Selfridge, and B. W. Ballard. LaSSIE: A knowledge-based software information system. Communications of the ACM, 34(5), 1991.

....can be more discriminating by analysing terms in their context rather than matching individual words. A thesaurus containing synonyms, specializations and generalizations of each term avoids the problem of having to master exacts terminology. LaSSIE (Large Software System Information Environment) [3] and NLH E (Natural Language Help English) 8] follow this approach. 3 A knowledge based software reuse system based on natural language specifications In this section we outline a software reuse system based on natural language specifications.The project s goals include evaluating the defined ....

P. Devanbu, R. Brachman, P. Selfridge and B. Ballard, "LaSSIE: A Knowledge-Based Software Information System," CACM, 34(5), May. 1991, pp. 34-49.

....than matching individual words. A thesaurus containing synonyms, specializations and generalizations of each term avoids the problem of having to master exact terminology. Some of the systems that follow this approach are described below. LaSSIE (Large Software System Information Environment) [4] is composed of a knowledge base, a semantic analysis algorithm based on formal inference and a user interface incorporating a graphical browser and a natural language parser. LaSSIE helps programmers in searching useful information about a large software system and also supports the retrieval of ....

P. Devanbu, R. Brachman, P. Selfridge and B. Ballard, "LaSSIE: A Knowledge-based Software Information System," CACM, vol. 34(5), May. 1991, pp. 34-49.

.... classes of formulas; not only are they the subject of theoretical investigation within the field of knowledge representation, but they also find use in practical knowledge based systems (Beck et al. 1989; Borgida, 1992; Borgida Patel Schneider, 1992; Brachman et al. 1983; Cohen Hirsh, 1994b; Devanbu et al. 1991; Mays et al. 1987; Patel Schneider, 1989) 1.1. Classic Classic permits constructing certain quantified descriptions that distinguish a particular subset of a domain I of individuals. Classic descriptions contain primitive symbols which get mapped to arbitrary subsets of I, disjoint primitive ....

Devanbu, P., Brachman, R. J., Selfridge, P., & Ballard, B. (1991). LaSSIE: A knowledge-based software information system. Communications of the ACM, 35(5).

....as the subsumption relationship can be used to organise queries automatically and views, hence supporting data exploration and query optimisation. Description Logics have been used in a wide variety of applications including the representation of complex schemas for cars [30] software management [8] and medicine [27] data archaeology [6] mediation between heterogeneous data stores [2] and database querying [16] However, interacting with Description Logic implementations can often prove difficult. In the past, solutions involved embedding the logic in large monolithic systems with all the ....

P. Devanbu, R. Brachman, P. Selfridge, and B. Ballard. LaSSIE: A Knowledge-based software information system. Communications of the ACM, 34(5), 1991.

....library systems, most of which are local, in the sense that they help retrieving single components. e.g. ffl The PARIS system [KaRT89] a applies a theorem prover to resolve a retrieval query against formal component descriptions using temporal logic for pre and postconditions. ffl LaSSIE [DBSB91] uses the knowledge representation language KANDOR to store information about a large software project in order to provide semantic retrieval. A taxonomy of classes is induced by a frame based representation of objects. ffl The software engineering environment NORA [SFGK94] is based on logical ....

P. Devanbu, R. J. Brachman, P. G. Selfridge, and B. W. Ballard. LaSSIE: A knowledge-based software information system. Communications of the ACM, 34(5):35--49, May 1991.

.... acceptance of the feature, and or the development cycle (not to mention the profitability to the manufacturer) Researchers within the telecommunications field are addressing this problem through the creation of software development environments [BELA90a] software information systems [BELA90b, DEVA91] and requirements capturing systems [BERG90, KELL87] This paper describes GATOR, the GATherer Of Requirements, a natural language based system designed to assist developers of new telephony features in the task of specifying functional requirements. In the next section we provide a summary of ....

Devanbu, P., R. J. Brachman, P. G. Selfridge, and B. W. Ballard, LaSSIE: A Knowledge-Based Software Information System, CACM, Vol. 34, No. 5, pp. 34 - 49, 1991.

.... Practical applications of description logics (terminological systems) using these and other terminological languages exist in a wide variety of domains: data and knowledge management systems [3] 2] global information systems [16] clinical information systems [23] or software engineering [6]. In our project we choose to use Classic for several reasons. The language is expressive enough to be useful and limited in a way that tractable reasoning is assured. The language is simple and small enough to be really usable because it can be learnt by non experts 4 3 in computer science. ....

P. Devanbu, R.J. Brachman, P. Selfridge, and B. Ballard, `LaSSIE: a knowledge-based software information system', Communications of the ACM, 34(5), 34--49, (1991).

....MATS. Status: Fully implemented prototype. Impact: Enabling technology for automatic or interactive response to temporal patterns of events. 1 Introduction Terminological knowledge representation (tkr) systems are used to represent and reason with conceptual knowledge in many application areas [21, 2, 22, 6, 9, 17]. However, the applicability of contemporary tkr systems is limited by restrictions on both their representation language and their inferences [8] Our work extends the scope and utility of tkr by representing complex constraint networks in a terminological framework, and by extending the range ....

....3 Metric arc M1 i1F ( Gammam1; Q1; R1; n1)j1G w metric arc M2 i2F ( Gammam2; Q2; R2; n2)j2G iff (1) Gammam1 Gammam2, 2) Q1 wQ2, 3) R1 wR2, and (4) n1 n2. Whenever M2 describes a metric relationship, M1 must also describe it. The constraint i1F (6; 9)j1G describes 6 but 9 units, i. e, [6,9], and subsumes i2F (7; 8)j2G describing 7 but 8 units, i.e. 7,8] Node i1 will be mapped to i2, and j1 to j2, as discussed below. Definition 4 Equality arc E1 rname i (c1) rname j (d1) w equality arc E2 rnamek (c2) rname l (d2) iff rname i = rnamek rname j = rname l . Whenever E2 ....

P. Devanbu, R. J. Brachman, B. W. Ballard, and P. E. Selfridge. Lassie: A knowledge-based software information system. CACM, 34(5), May 1991.

....the Common Lisp Object System, and a Prolog interpreter. Furthermore, there is an experimental component that combines a neural network and a semantic net to facilitate feature detection. 6.2.2. LaSSIE Our work is similar to approaches taken at the highest level of abstraction, such as LaSSIE [Devanbu et al. 1991]. LaSSIE is a knowledge based information system designed to support maintenance and enhancements on a large software system. The LaSSIE knowledge base uses frames to represent information about the software s domain, architecture, and code. A formally defined inheritance relation between ....

Devanbu, P., R. J. Brachman, P. G. Selfridge, and B. W. Ballard (1991), "LaSSIE: A KnowledgeBased Software Information System," Communications of the ACM, 34, 5, 35-49.

.... is instance checking and amounts to verify whether the individual a is an instance of the concept C with respect to the knowledge base K, i.e. in symbols K = C(a) DL systems has been used for building a variety of applications including (see [14] systems supporting software management [13], browsing and querying of networked information sources [16] knowledge mining [4] data archaeology [9] planning [35] learning [22] natural language understanding [7] clinical information system [18] digital libraries [36] software configuration management system [39] and web source ....

Premkumar Devanbu, Ronald J. Brachman, Peter J. Selfridge, and Bruce W. Ballard. LASSIE: A knowledge-based software information system. Communications of the ACM, 34(5):36--49, 1991.

....process is supported by an ontology of concepts that captures semantic relations instead of a type hierarchy. Semantic trading uses information about the behavior of the components, which is extracted either by the knowledge acquired at system design or by reverse knowledge engineering (see [12] for a discussion about reverse knowledge engineering) This information is used to construct an ontology of the system s domain. In fact, if a design process like the one described in [13] was followed, then the concepts of the ontology are directly the concepts (types) identified during the ....

P. Devanbu, R. Brachman, P. Selfridge and B. Ballard, "LaSSIE: A Knowledge-based Software Information System", Communication of the ACM, vol. 34, no. 5, May 1991.

No context found.

Premkumar Devanbu, Ronald J. Brachman, Bruce Ballard, and Peter G. Selfridge. LaSSIE: A knowledge-based software information system. Communications of the ACM, 34(5):35-49, May 1991.

No context found.

Devanbu, P., Brachman, R. J., Selfridge, P. G., and Ballard, B. W., "LaSSIE: A knowledge-based software information system," Comm. of the ACM, 34(5), May, 1991, pp. 34--49.

No context found.

Devanbu, P., Selfridge, P. G., Brachman, R. J. and Ballard, B. W., "LaSSIE: a Knowledge-based Software Information System," IEEE Proceedings of 12th International Conference on Software Engineering, pp. 249261, 1990.

No context found.

Devanbu, P., et. al., LaSSIE: A Knowledge Based Software Information System. CACM 34 (5): 35-48.

No context found.

P. Devanbu, R. J. Brachman, P. G. Selfridge, and B. W. Ballard, "LaSSIE: A KnowledgeBased Software Information System," Communications of the ACM, vol. 34, pp. 34-49, 1991.

No context found.

Premkumar Devanbu, Ronald J. Brachman, Peter J. Selfridge, and Bruce W. Ballard. LASSIE: A knowledge-based software information system. Communications of the ACM, 34(5):36--49, 1991.

No context found.

P.T. Devanbu, R.J. Brachman, P.G. Selfridge, and B.W. Ballard. Lassie: a knowledge-based software information system. In International Conference on Software Engineering, pages 249--261, 1990.

No context found.

P.T. Devanbu, R.J. Brachman, P.G. Selfridge, and B.W. Ballard. Lassie: a knowledgebased software information system. In International Conference on Software Engineering, pages 249--261, 1990.

No context found.

Devanbu, P., Brachman, R.J., Selfridge, P.G. & Ballard, B.W.: LaSSIE: A KnowledgeBased Software Information System, Communications of the ACM, vol.34(5), pp.34--49, 1991.

No context found.

P. Devanbu, R. J. Brachman, P. G. Selfridge, and B. W. Ballard, "LaSSIE: A KnowledgeBased Software Information System," Communications of the ACM, 34(5), pp. 34-49, 1991.

No context found.

P. Devanbu, R. Brachman, P. Selfridge, and B. Ballard. Lassie: A knowledge-based software information system. In Proceedingsof the 12th International Conferenceon Software Engineering, pages 249--261, Los Alamitos, CA, 1990. IEEE Computer Society Press

No context found.

P. T. Devanbu, R. Brachman, P. Selfridge, and B. Ballard. Lassie: a knowledge-based software information system. In Proc. of Int'l Conf. on SE, pages 249--261, 1990.

No context found.

P. Devanbu, R. J. Brachman, P. G. Selfridge, and B. W. Ballard, "LaSSIE: A KnowledgeBased Software Information System," Communications of the ACM, vol. 34, pp. 34-49, 1991.

No context found.

P. Devanbu, R. J. Brachman, P. G. Sefridge, and B. W. Ballard. LaSSIE: A knowledge-based software information system. Communications of the ACM, 34(5):34--49, 1991.

No context found.

P. Devanbu, R. Brachman, P. Selfridge and B. Ballard ". LaSSIE: A Knowledge-Based Software Information System. Communications of the ACM, Vol 34, No 5, p34-49, May 1991.

No context found.

Devanbu, P., and R. Brachman, P. Selfridge, and B. Ballard, LaSSIE: A Knowledge-Based Software Information System, Communications of the ACM, Vol 34, No 5, pp. 3549, May 1991.

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