2003
DOI: 10.1109/tse.2003.1214328
|View full text |Cite
|
Sign up to set email alerts
|

Knowledge-based repository scheme for storing and retrieving business components: a theoretical design and an empirical analysis

Abstract: Component-based development (CDB) promises to reduce complexity and cost of software development and maintenance through reuse. For CBD to be successful, a vibrant market for commercial business components is essential. One of the key requirements of an active market for business components is an effective scheme for classifying and describing them at various levels of detail, as well as a corresponding repository for storing and retrieving these components. Such a scheme needs to support various constituents … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
19
0
8

Year Published

2005
2005
2013
2013

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 55 publications
(38 citation statements)
references
References 17 publications
0
19
0
8
Order By: Relevance
“…Much domain knowledge is stored in a repository; knowledge is expressed by rules which show implicit relations [14], these rules are defined as follows: If A comes into existence, then B can be concluded, the confidence degree is CL, marked up A = (B, CL), hereinto, A is called antecedent which is combination of a series of conditions, i.e. A = A1 Λ A2 Λ A3……….…”
Section: The Design Of a Repositorymentioning
confidence: 99%
“…Much domain knowledge is stored in a repository; knowledge is expressed by rules which show implicit relations [14], these rules are defined as follows: If A comes into existence, then B can be concluded, the confidence degree is CL, marked up A = (B, CL), hereinto, A is called antecedent which is combination of a series of conditions, i.e. A = A1 Λ A2 Λ A3……….…”
Section: The Design Of a Repositorymentioning
confidence: 99%
“…The selection of OTS has been recognized as a critical process in the OTS-based development risk mitigation [5]. Regardless the specific properties of OSS and COTS components, we may consider that the high-level selection process (i.e.…”
Section: Introductionmentioning
confidence: 99%
“…Vitharana et al [91] propuseram um esquema efetivo de classificação para componentes de negócio considerando vários níveis de detalhe e abstração, além de um repositório para armazenar e recuperar tais componentes. Diferentes abordagens de classificação podem ter de ser feitas para os diferentes tipos de objetos no sistema.…”
Section: Facetas Para Componentes De Negóciounclassified
“…Vitharana [91] considera o domínio de aplicação uma informação bem definida ou estruturada (um atributo dentro do modelo de classificação • Role: papéis que o componente pode (potencialmente) assumir uma variedade de aplicações.…”
Section: Facetasunclassified
See 1 more Smart Citation