Ontology classification for semantic-web-based software engineering


Published on

A detailed presentation about

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Ontology classification for semantic-web-based software engineering

  1. 1. <ul><li>Ontology Classification for Semantic-Web-Based Software Engineering </li></ul><ul><li>IEEE TRANSACTIONS ON SERVICES COMPUTING, </li></ul><ul><li>DECEMBER 2009 </li></ul>
  2. 2. By. P. Victer Paul Dear, We planned to share our eBooks and project/seminar contents for free to all needed friends like u.. To get to know about more free computerscience ebooks and technology advancements in computer science. Please visit.... http://free-computerscience-ebooks.blogspot.com/ http://recent-computer-technology.blogspot.com/ http://computertechnologiesebooks.blogspot.com/ Please to keep provide many eBooks and technology news for FREE. Encourage us by Clicking on the advertisement in these Blog.
  3. 3. About Authors <ul><li>Yajing Zhao </li></ul><ul><ul><li>Working toward the PhD degree at the University of Texas at Dallas. </li></ul></ul><ul><ul><li>Software architecture and design, service oriented architecture, semantic Web services. </li></ul></ul><ul><li>Jing Dong, Senior Member, IEEE </li></ul><ul><ul><li>PhD degrees in computer science from the University of Waterloo, Canada, in 2002. </li></ul></ul><ul><ul><li>Formal and automated methods for software engineering, software modeling and design, services computing, and visualization </li></ul></ul><ul><li>Tu Peng </li></ul><ul><ul><li>Working toward the PhD degree at the University of Texas at Dallas. </li></ul></ul><ul><ul><li>Formal modeling and verification of software design, security, services computing, and model checking </li></ul></ul>
  4. 4. Aim <ul><li>The Semantic Web provides a way to improve information sharing and reuse. </li></ul><ul><li>In Software Engineering, Information sharing and reuse have the following benefits: </li></ul><ul><ul><li>improving productivity </li></ul></ul><ul><ul><li>shortening development life cycle </li></ul></ul><ul><ul><li>decreasing cost </li></ul></ul><ul><ul><li>increasing product quality </li></ul></ul><ul><li>classifies the ontologies developed for software engineering and presents the benefits of their applications </li></ul>
  5. 5. Introduction <ul><li>The Semantic Web which helps sharing and reusing data across application, enterprise, and community boundaries. </li></ul><ul><li>Ontology defines a set of representational primitives with which a domain of knowledge is modeled. </li></ul><ul><li>The W3C standards, </li></ul><ul><ul><li>OWL </li></ul></ul><ul><ul><li>RDF </li></ul></ul><ul><li>maintains information in the format that can be understood and processed by automated tools </li></ul>
  6. 6. Introduction <ul><li>Software development is a complex process which produces a large amount of information. </li></ul><ul><li>Effort has been made to improve the software process like IDE,CASE. </li></ul><ul><li>Reusing existing information saves efforts. A method that facilitates information retrieval and promotes reuse is highly demanded. </li></ul><ul><li>Globalization need information sharing helps to prevent inconsistency. </li></ul>
  7. 7. Software Process Ontology <ul><li>Each oval with solid border represents a concept, each directed line represents a relationship between two concepts, and the text on the line denotes the type of the relationship. </li></ul><ul><li>an oval with dashed lines represents an ontology, which can be seen as a meta concept. </li></ul><ul><li>Ontology 1. Software process ontology </li></ul>
  8. 8. Domain Ontologies <ul><li>Domain engineering collects useful information within a specific domain, which can be maintained and reused in future application development in the same domain. </li></ul><ul><li>Reusing domain information may reduce time and save the effort of gathering information. </li></ul><ul><li>Ontology 2. Application domain ontology , which represents the knowledge of an application domain and the business information required for building software applications in a specific domain. </li></ul><ul><li>Ontology 3. Application domain feature model ontology , which models the features of software systems in the same application domain. </li></ul>
  9. 9. Requirement Ontology <ul><li>Desired software characteristics specified by the customer </li></ul><ul><ul><li>Functional Requirements (FRs) </li></ul></ul><ul><ul><ul><li>sequence of actions under a particular context </li></ul></ul></ul><ul><ul><li>Non-Functional Requirements (NFRs) </li></ul></ul><ul><ul><ul><li>quality-related characteristics of a system. </li></ul></ul></ul><ul><li>Ontology 4. System behavior ontology , which models system behaviors. </li></ul><ul><li>The main concepts of this ontology include event, action, reservation, etc. </li></ul><ul><li>Relationships include making agreement, making reservation, etc. </li></ul>
  10. 10. Quality Ontologies <ul><li>measured along the software attributes: capacity, usability, performance, reliability, installability, maintainability, availability, etc </li></ul><ul><li>Ontology 15. Quality ontology </li></ul><ul><li>Ontology 16. Testing ontology </li></ul><ul><li>Ontology 17. Defect ontology </li></ul>
  11. 11. Technology Ontology <ul><li>built to act as a library, to provide engineers with possible information, and to help engineers to pick up the most appropriate tools or technologies </li></ul><ul><li>Ontology 18. Technology ontology , which is a repository of software development technologies (J2EE,.Net), environments, platforms, tools. </li></ul>
  12. 12. Other Ontologies <ul><li>Architecture and Design Ontologies </li></ul><ul><ul><li>Ontology 5. Software architecture ontology </li></ul></ul><ul><ul><li>Ontology 6. Application logic ontology </li></ul></ul><ul><ul><li>Ontology 7. Object-Oriented design ontology </li></ul></ul><ul><li>Implementation Ontologies </li></ul><ul><ul><li>Ontology 9. Software artifact ontology </li></ul></ul><ul><ul><li>Ontology 10. Object-oriented source code ontology </li></ul></ul><ul><ul><li>Ontology 11. Version ontology </li></ul></ul><ul><ul><li>Ontology 12. System configuration ontology </li></ul></ul><ul><li>Documentation Ontologies </li></ul><ul><ul><li>Ontology 13. Documentation ontology </li></ul></ul><ul><ul><li>Ontology 14. Document ontology </li></ul></ul>
  13. 13. Semantic Web Applications In Software Engineering <ul><li>how these ontologies and the Semantic Web technologies are used to improve software engineering. </li></ul><ul><li>problems from two perspective in software engineering, </li></ul><ul><ul><li>The life-cycle perspective </li></ul></ul><ul><ul><ul><li>problem exist in a particular software engineering phase </li></ul></ul></ul><ul><ul><li>The critical issue perspective </li></ul></ul><ul><ul><ul><li>problem exist throughout the entire life </li></ul></ul></ul><ul><li>introduces problems from these perspectives and discusses how they can be improved by using the Semantic Web technologies </li></ul>
  14. 14. From Life-Cycle Perspective <ul><ul><li>Requirement Engineering Phase </li></ul></ul><ul><ul><ul><li>Application domain ontology and quality ontology </li></ul></ul></ul><ul><ul><li>Software Design Phase </li></ul></ul><ul><ul><ul><li>Application domain feature model ontology and Pattern ontology </li></ul></ul></ul><ul><ul><li>Implementation and Integration Phase </li></ul></ul><ul><ul><ul><li>Application domain ontology and testing ontology </li></ul></ul></ul><ul><ul><li>Software Testing Phase </li></ul></ul><ul><ul><ul><li>Software testing ontology </li></ul></ul></ul><ul><ul><li>Software Maintenance Phase </li></ul></ul><ul><ul><ul><li>Software maintenance ontology </li></ul></ul></ul>
  15. 15. Usage of Ontologies to Support Engineering Phases <ul><ul><li>‘ x’ indicates that the ontology has been used by some researcher work to solve problems. </li></ul></ul><ul><ul><li>‘ ?’ indicates that the ontology can be used to solve the problem but there is no work on it yet </li></ul></ul>
  16. 16. From Critical Issues Perspective <ul><li>Documentation </li></ul><ul><ul><li>software artifact ontology and application domain ontology </li></ul></ul><ul><li>Traceability </li></ul><ul><ul><li>object-oriented source code ontology and documentation ontology </li></ul></ul><ul><li>Change Control </li></ul><ul><ul><li>domain ontology, pattern and version ontology </li></ul></ul><ul><li>Quality Control </li></ul><ul><ul><li>object-oriented source code ontology, defect ontology, and version ontology </li></ul></ul><ul><li>Reuse </li></ul><ul><ul><li>software artifact ontology and the domain ontology </li></ul></ul>
  17. 17. Benefits of Ontologies to Critical Issues <ul><ul><li>‘ x’ indicates that the ontology has been used by some researcher work to solve problems. </li></ul></ul><ul><ul><li>‘ ?’ indicates that the ontology can be used to solve the problem but there is no work on it yet </li></ul></ul>
  18. 18. Conclusion <ul><li>many discussions and suggestions about improving software engineering process by using ontology and the Semantic Web techniques. </li></ul><ul><li>To the best of our knowledge, there is no classification or assessment on these approaches yet. </li></ul><ul><li>Our goal in this paper is to provide a review on current status of this field. </li></ul>
  19. 19. References <ul><li>A.P. Ambro´ sio, D.C. de Santos, F.N. de Lucena, and J.C. de Silva, “Software Engineering Documentation: An Ontology-Based Approach,” Proc. Web Media and LA-Web Joint Conf. 10th Brazilian Symp. Multimedia and the Web Second Latin Am. Web Congress, pp. 38-40, 2004. </li></ul><ul><li>A. April, J.-M. Desharnais, and R. Dumke, “A Formalism of Ontology to Support a Software Maintenance Knowledge-Based System,” Proc. 18th Int’l Conf. Software Eng. and Knowledge Eng., 2006. </li></ul>
  20. 20. <ul><li>Queries </li></ul>
  21. 21. <ul><li>Thank you </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.