Towards a software component ontology
Research has shown that component-based software engineering leads to software that exhibits higher quality, shorter time-tomarket and therefore, lower development cost. However, the development of component-based systems has been widely plagued with problems surrounding the integration of third-par...
| Main Authors: | , , |
|---|---|
| Other Authors: | |
| Format: | Conference Paper |
| Published: |
Association for Computing Machinery (ACM)
2008
|
| Subjects: | |
| Online Access: | http://doi.acm.org/10.1145/1497308.1497400 http://hdl.handle.net/20.500.11937/26544 |
| Summary: | Research has shown that component-based software engineering leads to software that exhibits higher quality, shorter time-tomarket 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 componentsand 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. |
|---|