A translation approach to portable ontology specifications
Knowledge Acquisition - Special issue: Current issues in knowledge modeling
Software aspects of strategic defense systems
Communications of the ACM
Three levels of end-user tailoring: customization, integration, and extension
Computers and design in context
Knowledge engineering: principles and methods
Data & Knowledge Engineering - Special jubilee issue: DKE 25
Subspace: secure cross-domain communication for web mashups
Proceedings of the 16th international conference on World Wide Web
Domain model-driven software engineering: A method for discovery of dependency links
Information and Software Technology
| Hi-index | 0.00 |
Research has shown that component-based software engineering leads to software that exhibits higher quality, shorter time-to-market and therefore, lower development cost. However, the development of component-based systems has been widely plagued with problems surrounding the integration of third-party components. Currently, software developers are forced to rely on ambiguous definitions of a component's services. There is no easy to understand protocol for defining how third-party components and component compositions are described and integrated into systems. Most vendors specify their components' services in a proprietary or context dependant fashion. This makes it difficult to clearly understand a component's services, their use and their operational pre and post conditions. Software Engineering ontologies define common sharable software engineering knowledge. They explicitly define software engineering concepts, their relationships and their interactions. In this paper, we propose a Software Component Ontology that specifically defines a formal, explicit specification of a shared conceptualization in the domain of software component engineering. We propose the use of our software component ontology as the basis for the development of future component compositions and component based applications.