| Henninger, S. Supporting the Construction and Evolution of Component Repositories, In Proceedings of the 18th International Conference on Software Engineering, Berlin, Germany, 1996, IEEE CS Press, pp. 279-288. |
....are deployed or component configurations changed to provide developers with on going feedback. Our approach of agents using aspect encoded information to formulate operation invocations on deployed components to validate their configurations is similar to behaviour based component repository work [12, 27]. However, we use this information to validate deployed components rather than locate components by behaviour for deployment. We have found developing most of our validation agents to be low effort key steps are to encode and extract required test case generation information, generate and run ....
Henninger, S. Supporting the Construction and Evolution of Component Repositories, In Proceedings of the 18th International Conference on Software Engineering, Berlin, Germany, 1996, IEEE CS Press, pp. 279-288.
....collaborative editing support to our tools via plug in software components. Component management. Component based systems leverage existing software artifacts (components) heavily. A shared repository of such artifacts is necessary to facilitate distributed component based systems development [16]. We have developed such a shared repository for our various modelling and implementation tools to use. In the following section we overview related work in these areas, particularly identifying gaps and weaknesses in current development methods and tools for distributed component engineering. We ....
....primarily asynchronous work. These are also needed in order to support componentbased software engineering where a large library of reusable components need to be shared. Examples of such systems include document centric ones like and BSCW [3] and software component libraries like CodeFinder [16]. One of the main problems we have found with many of these existing approaches is their reliance on either too simple indexing strategies, or use of very complex and restrictive formal program semantics. Various systems have taken an integrated approach to supporting distributed software ....
Henninger, S. Supporting the Construction and Evolution of Component Repositories, In Proceedings of the 18th International Conference on Software Engineering, Berlin, Germany, 1996, IEEE CS Press, pp. 279-288.
.... 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 used for software libraries. Examples include WiSeR [21] IBROW [17] and CodeFinder [8] Key deficiencies of existing approaches include the need to use low level, service based queries, lack of high level ....
....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 used for software libraries. Examples include WiSeR [21] IBROW [17] and CodeFinder [8]. Key deficiencies of existing approaches include the need to use low level, service based queries, lack of high level description of component capabilities, lack of validation or checking of retrieved component suitability, and lack of use of the context for which queries are being performed by ....
[Article contains additional citation context not shown here]
Henninger, S. Supporting the Construction and Evolution of Component Repositories, In Proceedings of the 18th International Conference on Software Engineering, Berlin, Germany, 1996, IEEE CS Press, pp. 279-288.
....concept by Basili et al. 4] are often suggested to face this problem. Some reuse repositories offer large selections of different types of reusable elements [31] while others place their focus only on certain aspects like, for instance, reuse of software processes [14] software components [13], or measurement plans [12] However, just storing the knowledge in a repository system is not enough. There are many questions that must be addressed in order to design an effective reuse repository, among them: What kind of user interfaces do we need How should users retrieve or store the ....
S. Henninger. Supporting the Construction and Evolution of Component Repositories. In Proc. of the 18th International Conference on Software Engineering (ICSE'18), Berlin, Germany, March 1996, IEEE Computer Society Press. 19 SFB 501 A1
....them effectively manage distributed work and tool co ordination [1, 5, 12] Component management. Component based systems leverage existing software artifacts (components) heavily. A shared repository of such artifacts is necessary to facilitate distributed component based systems development [20, 24, 30]. We describe the development of a component engineering environment made up of several tools: a component analysis, design and implementation tool; a software process management tool; a software architecture modelling tool; a component implementation and testing tool; and various 3 rd party ....
....work. These are also needed in order to support component based software engineering where a large library of reusable components need to be centralised for shared retrieval. Examples of such systems include document centric ones like and BSCW [4] and software component libraries like CodeFinder [24], and that of Pai and Bai [30] One of the main problems we have found with many of these existing approaches is their reliance on either too simple indexing strategies, or use of very complex and restrictive formal program semantics [20, 24] Integration of a component repository with other ....
[Article contains additional citation context not shown here]
Henninger, S. Supporting the Construction and Evolution of Component Repositories, In Proceedings of the 18th International Conference on Software Engineering, Berlin, Germany, 1996, IEEE CS Press, pp. 279-288.
....known with certainty or completely. This is particularly true in the retrieval of information from databases, which store objects with complex structures and are organised according to multi dimensional classification schemes that may be revised in the context of their use. Software repositories [4, 30] are examples of such databases since they store artifacts (e.g. requirements specifications, designs and code components) which are described in varying degrees of abstraction and granularity, are grouped into multiple and possibly overlapping workspaces and need to be maintained in diverse ....
....and remain stable across its life cycle. Consequently, the importance of the various features in these structures is known in advance and does not change. Often, these hypotheses turn to be wrong. Other methods rely on assessments of feature importance, which are directly provided by the users [30, 32] and as such become weak whenever users are not able to give these estimates. In this paper, we present a model of estimating the importance of the features of objects with complex structures, which are organised according to multiple classification schemes that change frequently. This model, ....
Henninger S. 1996. Supporting the Construction and Evolution of Component Repositories, In Proc. of the 18th International Conference on Software Engineering, March, Berlin, pp. 279-288
No context found.
[Henninger, 1996] Henninger, S., Supporting the Construction and Evolution of Component Repositories, Proceedings of ICSE-18, 1996.
No context found.
Henninger, S. (1996). Supporting the Construction and Evolution of Component Repositories, In Proceedings of the 18th International Conference on Software Engineering, Berlin, Germany, IEEE CS Press, pp. 279-288.
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