An Ontology-Based Support for Asset Design and Reuse

WISDOM: A website design method based on reusing design and software solutions

“…To avoid wasting time, research has proposed to insert a DM between the user and the component model and to map functional data representing the needs to the DM's functional modules. Starting with the user's selection of the DM modules, the process minimizes the number of components, using one of the following: an analytic method, such as STACE, OTSO or PORE [21], a new model between the user and the DM to decrease the time needed to identify the relevant component [22], or an ontology to refine the user query and to propose a more accurate list of specifications [23]. Like in these studies, we had to automatically build a short list of the relevant components because they were potentially high in numbers to fulfill a given functional need.…”

“…The model has only one deep level that needs to conform to the ''no more than three clicks to display content" rule. Files are generated from a template that contains references to: global variables, to take advantage of the website development template; generic classes, to take advantage of the native implementation of database interaction (e.g., to display data in tables); used components, to provide services (e.g., forums, 20 photo albums, 21 a mailing list manager 22 ); used libraries, to provide existing implementations (e.g., for creating graphs, 23 abstracting databases, 24 sending email 25 ); links with unit testing environments 26 ; and specific method prototypes, which govern interactions with the website itself.…”

Using a Semantic Wiki for Documentation Management in Very Small Projects

“…Reusing. Several authors pointed out the help of ontologies to support reuses [8], [10]. By construction, using the ISO/IEC 29110 standard in a VSE introduces its underlying ontology: process, activity, task, role, products, etc.…”

“…Locating -retrieving -resources difficulty is related to the crucial problem of interaction between resources providers and users. Ramadour et Cauvet [10] believe that this interaction can be supported and even automated by increasing the expressiveness of the language used for encoding component properties and formulating queries, enhancing therefore the quality of the retrieval.…”