Browse Prior Art Database

Component Ecosystem, will help components evolve and be reused Disclosure Number: IPCOM000016162D
Original Publication Date: 2002-Jul-14
Included in the Prior Art Database: 2003-Jun-21
Document File: 3 page(s) / 66K

Publishing Venue



Outline of the Ecosystem

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 45% of the total text.

Page 1 of 3

Component Ecosystem, will help components evolve and be reused

Outline of the Ecosystem

    Component Ecosystem utilizes the powers and heuristics of the evolving discovery engines to capture the behavior of the user(s) to search, compose, enhance and integrate functional and data models and components within a defined environment to dynamically produce solutions for a given problem.

    The system can very specifically be used for application software development, but can also be used for other areas.

    It is envisaged that the system will support the automation of the contents of the sources within a given application space (application development tools, web sites, team rooms, news, etc.). The following diagram illustrates the conceptual view of the Component Ecosystem.


deliver & execute


    Two types of components are distinguished: reusable chunks of software and information about this software. There is no restriction to the amount of function in a component; it may be a sorting routing or the employee administration component of an HR system or answer to a frequently asked question.

    The components are stored in a repository. Repositories may be offered by different vendors. When working with the system, the user may access one or multiple vendor repositories through the search mechanism.


Searching for the component that the user needs is driven by three factors:
1. what the users says he needs (e.g. "employee administration")
2. the job the user is performing (e.g. "Java* programmer")
3. past and project behavior (e.g. uses well documented code, avoids French components)

Key element here is that the combination of criteria is used (as in the Autonomy search engine) to search through the components. New element is that the using components found trains (learns) the user's behavior. In subsequent searches this behavior is used to enhance the query and thus the results. There is no predefined taxonomy in the




search criteria

job role




 submit for reuse

compose & enhance

[This page contains 1 picture or other non-text object]

Page 2 of 3

behavioral factor; the user is not asked to input behavioral criteria. Searching in components involves searching program code, comment, documentation, and many text sources related to the code.

Finding the proper component is done in iterations, where the user refines the criteria by which to search by examining existing search results and selecting relevant components. The results are presented in order, the match closesest to all three criteria is shown first.


    The components found are enhanced by the user, to fit their specific needs. This may involve creative processes such as programming, modifying, documenting. These activities are a value add and are always seen as an enhancement. The result should always be stored in the repository for others to use. No mediation should be applied.


The components found can be integrate...