Fischer, B. (1998). Specification-Based Browsing of Software Component Libraries. Proc. Automated Software Engineering, Hawaii, 246-254.  Home/Search   Document Details and Download   Summary   Related Articles   Check

.... Ball99concept [2] 0 Boettger01modelling [6] Boettger01reconciling [7] Bojic00reverse [5] 0 Canfora99case [9] 200 Dekel02applications [12] 0 Duwel98identifying [15] Duwel99enhancing [14] Duwel00bridging [16] Eisenbarth01aiding [17] 0 Eisenbarth01feature [18] 76 Fischer98specification [19] Funk95Algorithms [21] 1.6 Godin93building [23] 0 Godin95applying [25] Godin98design [24] Huchard99from [27] 0 Krone94inference [30] 1.6 Kuipers00types [31] 100 Leblanc99environment [32] 0 0 0 0 Lindig95concept [33] Lindig97assessing [34] 5 106 1.5 Richards02assisting [35] ....

....objects. In this case the commands represent the components to be retrieved. The retrieval system provides a query by refinement interface in which a boolean query, B to (B ; B 00 ) and the concepts in the lower cover are offered as refinements to the user. 4. 3 Formal Specification Fischer[19] builds on the component retrieval work of Lindig, however, instead of keywords a formal specification that captures the behaviour of a software component is used. By exploiting the power of Formal Methods components can be retrieved based on explicit properties required for a components selection ....

B. Fischer. Specification-based browsing of software component libraries. In Automated Software Engineering, pages 74--83, 1998.

....This work was initiated by the seminal work of Turing [46] Floyd [25] and Hoare [33] who introduced the idea of programming with assertions. The work aims to exploit the presence of conditions to prove properties of interest statically [6] and dynamically [24, 35, 44] to extract components [23] and to remove infeasible paths before the consideration of control flow based text coverage criteria [29] The work aims to exploit information about execution represented by the assertions in order to analyse the programs, but does not seek to alter the programs with respect to this information. ....

B. Fischer. Specification-based browsing of software component libraries. In Thirteenth International Conference on Automated Software Engineering, pages 74--83. IEEE Computer Society Press, 1998.

....using IR methods to support software engineering tasks and recovering source code to documentation links. The research that has been conducted on the specific use of applying information retrieval methods to source code and associated documentation typically relates to indexing reusable components [12, 13, 16, 17]. Notable is the work of Maarek [16, 17] on the use of an IR approach for automatically constructing software libraries. The success of this work along with the inefficiencies and high costs of constructing the knowledge base associated with natural language parsing approaches to this problem [10] ....

Fischer, B., "Specification-Based Browsing of Software Component Libraries", in Proceedings of ASE, 1998, pp. 74-83.

....for the English language must be developed. 3. Identifying high level concept clones The method we propose for identifying high level concept clones is based on the semantic similarity measure between source code documents described earlier. These similarity measures are akin to the work by [16, 22, 38]. They compute the similarity between software elements based on structural information, with the purpose of identifying high level concepts in code. In its current form, the approach is an automated assistant to the developer in the identification of clones. To fully automate the process there ....

Fischer, B., "Specification-Based Browsing of Software Component Libraries", in Proc. of 13th ASE, 1998, pp. 74-83.

....profile. A profile is an abbreviated description of the original document that is easier to manipulate. The research that has been conducted on the specific use of applying information retrieval methods to source code and associated documentation typically relates to indexing reusable components [15, 16, 18, 28, 29, 32, 35]. Notable is the work of Maarek [28, 29] on the use of an IR approach for automatically constructing software libraries. The success of this work along with the inefficiencies and high costs of constructing the knowledge base associated with natural language parsing approaches to this problem [12, ....

.... Most of them use formal features (i.e. structural information) and two of them ( 28] and [37] use semantic information (referred to as non formal descriptive features) The research that has been conducted on the specific use of applying information retrieval methods to source code includes [15, 16, 18, 2830, 32, 35]. 7. Conclusions The experiments with the PROCSSI system show that the semantic similarity of source code documents provides valuable information that can be used in the tasks of software maintenance and evolution. It also shows that concepts from the problem domain are often spread over ....

Fischer, B., "Specification-Based Browsing of Software Component Libraries", in Proceedings of 13th ASE, 1998, pp. 74-83.

....of the most important factors to bring our discipline from craftsmanship to an industrial level. A basic starting point to enable reuse is to accumulate valuable assets in software repositories for later use. However, the larger these libraries grow, the harder it is to search in them effectively [6, 1, 21]. Some of these difficulties stem from the lack of understanding (1) on what assumptions the structure of the repository is built, 2) how the components themselves are characterized, and (3) how to formulate effective queries conforming to this characterization. Restricting application domains ....

....is error prone. Much research effort has been spent on finding alternatives to keyword based description techniques (cf. 11] for a survey on software libraries and retrieval techniques) Due to their rigid semantics, formal specifications suit very well for capturing the behavior of software ([6, 25, 10, 13]) When searching for a certain asset, the query is formulated as a (partial) specification. The retrieval process is then performed by conducting a formal proof that a component s specification fulfills at least the needs expressed in the query. Unfortunately, formal methods in general are not ....

B. Fischer. Specification-Based Browsing of Software Component Libraries. In D. Redmiles and B. Nuseibeh, editors, The 13th IEEE Conference on Automated Software Engineering, Honolulu, Hawaii, October 1998. IEEE CS Press.

....1999, pp.271 274 work concerning structuring and retrieving scenarios and software components, respectively, was conducted. Regarding the search in repositories techniques for both specification based and text description based retrieval and browsing in software libraries have been developed [4, 5, 11]. Due to the highly specialized focus of these approaches they cannot be applied for searching in informal scenario repositories. In [12] a hypertext model for structuring informal requirement representations (e.g. multimedia documents) is proposed which aims at keeping the whole requirements ....

Fischer, B., "Specification-Based Browsing of Software Component Libraries", Proc. of ASE-98: The 13 th IEEE Conf. on Automated Software Engineering, Honolulu, Hawaii, 1998

....component information from repositories and result in the reuse of qualified components. Search and retrieval differ from browse. Browse means reading superficially or at random (HWG, 1996) It consists in inspecting candidate components for possible extraction, but without a predefined criterion (Fischer 1998). Accordingly, search and retrieval concern the component precision: the desired component is first specified, and components should not be retrieved unless they are absolutely relevant; while browsing concerns the recall: the repository is first navigated and inspected and then the desired ....

.... precision: the desired component is first specified, and components should not be retrieved unless they are absolutely relevant; while browsing concerns the recall: the repository is first navigated and inspected and then the desired component is specified based on the recall of the navigation (Fischer 1998). As a metaCASE repository contains a large number of components, a precise search will improve the efficiency of component reuse. We thereby study search techniques to support component retrieval and reuse. 3.1. Review of information search techniques When studying information search techniques, ....

Fischer, B. (1998). Specification-based browsing of software component libraries.

....retrieving scenarios and software components, respectively, was conducted in the fields of requirements and software engineering. Regarding the search in repositories techniques for both specification based and text description based retrieval and browsing in software libraries have been developed [7, 8, 15]. Due to the highly specialized focus of these approaches they cannot be applied for searching in informal scenario 3 repositories. In [16] a hypertext model for structuring informal requirement representations (e.g. multimedia documents) is proposed. This model aims at providing a tool for ....

# Fischer, Bernd. Specification-Based Browsing of Software Component Libraries. Proc. of ASE-98: The 13 th IEEE Conf. on Automated Software Engineering, Honolulu, Hawaii, 1998

....the structure of the repository to find a component, and it lacks meaningful road maps as to what the repository contains and how to discover the components that are needed for the current task [11] Several attempts have been made to improve the browsing of a large component repository. Fischer [6] proposes a specification based browsing mechanism that combines concepts and formal specifications to structure the repository. This mechanism enables software developers to find components by selecting features required in their task, or deselecting features not needed for the task. Drummond et. ....

Fischer, B., Specification-Based Browsing of Software Component Libraries. Automated Software Engineering. 7(2): 179-200, 2000.

....modifications are required in order to guarantee the applicability of the retrieved components. The main problem in deductive retrieval is the large number of emerging proof tasks. Naive generate and prove implementations drown any prover, but recent efforts show how to circumvent this problem [18, 17, 5]. We assume that our integrated tool uses a retrieval system such as NORA HAMMR [18] in which a pipeline of filters of increasing deductive strength are used to prune away proof tasks associated with non matching components whilst maintaining a balance between fast response and high precision. ....

B. Fischer. "Specification-based browsing of software component libraries", in D. F. Redmiles and B. Nuseibeh (eds.), Proc. 13th ASE, pp. 74--83, Honolulu, 1998. IEEE.

No context found.

Fischer, B. (1998). Specification-Based Browsing of Software Component Libraries. Proc. Automated Software Engineering, Hawaii, 246-254.

No context found.

B. Fischer. Specification-based browsing of software component libraries. In Automated Software Engineering, pages 74--83, 1998.

No context found.

B. Fischer. Specification-based browsing of software component libraries. In Thirteenth International Conference on Automated Software Engineering, pages 74--83. IEEE Computer Society Press, 1998.

No context found.

B. Fischer. Specification-based browsing of software component libraries. In Proceedings of the 13 IEEE Conference on Automated Software Engineering, pages 74--83, Honolulu, Hawaii, USA, 1998. IEEE Computer Society Press.

No context found.

B. Fischer, "Specification-based browsing of software component libraries," in Automated Software Eng,

No context found.

B. Fischer. Specification-based browsing of software component libraries. In ASE '98, pp. 74--83.

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