Development and Classification of Reusable Components .Net Project Source Code, Database, Documentation Report
Modules for Development and Classification of Reusable Components
The modules identified in the design process are as follows.
In addition to these modules for administrative tasks like authentication and tuning the classification.
User interface is required for providing the stated functionality. The user must be able to upload, insert and search for components. A faithful interface must be designed that is easy to use and unambiguous.
The user while searching for components may enter some keywords. He may also select some list of attributes from the interface. The query formation module should take all the keywords and form the query.
All the components will be stored in the underlying database structure with the index being maintained by the catalog. When a user sends a query to retrieve components the system will form the query and execute the query against the catalog to view matching components. The components thus received are those that satisfy the additional criteria that are given in advanced search. These components are then again submitted to matching components module to get the matching components for the given query.
The search keyword can be searched against the name of the component, the algorithm used or the function performed. In addition different attributes of the components in the library can also be searched for finding matching components. Once these results are retrieved they are submitted to formatting results module for user selection.
The results obtained in the previous module are formatted so that the user can clearly understand the functionality of component before choosing one. All the results are taken and are displayed along with their details. Now the user can select his choice of component to download or save a component in the location specified by the user.
The intent of developing this classification is to integrate existing schemes. We used attribute-value to achieve the classification. We have used the following attributes to identify components:
The attributes when used in query can narrow down the search space to be used while retrieval. To be more effective the system should be deployed and thoroughly used, then depending on the feedback system the system can be enhanced.
Here we used attributes. The system also stores the descriptions of each component uploaded in the repository. So the system can also support keyword based search. If system stores most of the component’s properties the system can serve better and can be used in different ways.